Estimation

Requirement-based implementation effort in hours, complexity, rationale, dependencies, risks, and planning confidence.

Last updated: 2026-06-29 11:49
RTRFQX Review TeamWorkspace

Estimation

Requirement-based implementation effort in hours, complexity, rationale, dependencies, risks, and planning confidence.

Total Estimated Hours41268Jira timetracking/fallback
Estimated Requirements1789estimation rows
Missing Estimation0customer reqs
Weak Rationale0needs review
Decision-Downgraded652customer/security gate

Estimation Confidence Gate

Downstream engineering artifacts remain provisional until customer clarification closure evidence is complete.

BLOCKED BY CUSTOMER DECISIONP1 OPENSECURITY REVIEW OPENNO AUTO CLOSURE
472open clarification questions
6P1 decisions
0answered by additional PDFs
6security weak areas

Open Customer Decisions & Clarifications

Totals by Complexity

ComplexityRequirements
Low complexity263
High complexity744
Medium complexity782

Total Hours by Category / Domain

Category / DomainEstimated Hours
System14704
IT / backend8090
Software7032
Cybersecurity5560
Hardware3344
Interface1409
Process / compliance1113
Tooling16

Search and Filters

Requirement-Based Estimation

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

Customer Requirement IDLinked System Requirement ID(s)Requirement CategoryImplementation ComplexityEstimated HoursEstimation RationaleAssumptionsDependenciesRisksConfidence LevelEstimation StatusPhase / SprintOpen Questions
1.1NoneCybersecurityLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
1.2NoneHardwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
1.3NoneCybersecurityHigh complexity18Unverified security control could leave a residual risk in the cybersecurity case.Internal review confirms wording and scope.OEM/Customer Review InterfaceUnverified security control could leave a residual risk in the cybersecurity case.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedComplete internal review of wording and baseline scope.
1.4NoneHardwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo supplier action - document reference / boilerplate.
RFQX-1001379436-P10-000-01-0005NoneCybersecurityHigh complexity56Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceUnverified security control could leave a residual risk in the cybersecurity case.MediumESTIMATEDDefine and codeNo supplier action - document reference / boilerplate.
INFO_SEC_001NoneCybersecurityMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_SEC_0001SSR-CON-001CybersecurityHigh complexity18Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceUnverified security control could leave a residual risk in the cybersecurity case.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_SEC_0002SSR-VIH-001CybersecurityHigh complexity18Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceUnverified security control could leave a residual risk in the cybersecurity case.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
RFQX-1001379436-P10-000-01-0009NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-1001379436-P10-000-01-0010NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-1001379436-P10-000-01-0011NoneSoftwareMedium complexity24Limited; standard implementation and verification risk.Internal review confirms wording and scope.OP-011; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
REQ_SEC_0003SSR-CON-002CybersecurityHigh complexity16Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceUnverified security control could leave a residual risk in the cybersecurity case.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_SEC_0022SSR-CON-002CybersecurityHigh complexity16Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.NoneUnverified security control could leave a residual risk in the cybersecurity case.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
RFQX-1001379436-P10-000-01-0014NoneCybersecurityHigh complexity56Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.OP-011; NoneUnverified security control could leave a residual risk in the cybersecurity case.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
REQ_SEC_0023SSR-CON-002CybersecurityHigh complexity16Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.NoneUnverified security control could leave a residual risk in the cybersecurity case.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
RFQX-1001379436-P10-000-01-0016NoneCybersecurityHigh complexity56Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.OP-011; NoneUnverified security control could leave a residual risk in the cybersecurity case.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
REQ_SEC_0024SSR-CON-001CybersecurityHigh complexity16Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceUnverified security control could leave a residual risk in the cybersecurity case.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_SEC_0004SSR-CON-001CybersecurityHigh complexity16Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceUnverified security control could leave a residual risk in the cybersecurity case.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_SEC_0005SSR-CON-001CybersecurityHigh complexity16Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceUnverified security control could leave a residual risk in the cybersecurity case.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_SEC_0040NoneHardwareHigh complexity16Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_SEC_0007SSR-CON-003SoftwareMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_SEC_0025SSR-HW-001HardwareHigh complexity8Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_SEC_0041NoneProcess / complianceLow complexity16Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_SEC_0042SSR-CON-002CybersecurityHigh complexity16Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceUnverified security control could leave a residual risk in the cybersecurity case.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_SEC_0008SSR-DAI-001CybersecurityHigh complexity16Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceUnverified security control could leave a residual risk in the cybersecurity case.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
RFQX-1001379436-P10-000-01-0026NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
REQ_SEC_0009SSR-CON-002CybersecurityHigh complexity16Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceUnverified security control could leave a residual risk in the cybersecurity case.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_SEC_0020SSR-SYS-001SystemHigh complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_SEC_0010SSR-PROD-001HardwareHigh complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_SEC_0011SSR-COM-001HardwareHigh complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_SEC_0012SSR-COM-002SystemMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_SEC_0013SSR-COM-003SystemMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
RFQX-1001379436-P10-000-01-0033NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
REQ_SEC_0014SSR-COM-002SystemMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
RFQX-1001379436-P10-000-01-0035NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
REQ_SEC_0026SSR-COM-001HardwareHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-008; OEM/Customer Review InterfaceResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
REQ_SEC_0027SSR-CON-002CybersecurityHigh complexity16Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceUnverified security control could leave a residual risk in the cybersecurity case.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_SEC_0028SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
REQ_SEC_0029SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
REQ_SEC_0006SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
REQ_SEC_0016SSR-KEY-001CybersecurityHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-003; OEM/Customer Review InterfaceResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
REQ_SEC_0019SSR-KEY-001CybersecurityHigh complexity24Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.NoneUnverified security control could leave a residual risk in the cybersecurity case.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_SEC_0021SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_SEC_0015SSR-CON-002CybersecurityHigh complexity16Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceUnverified security control could leave a residual risk in the cybersecurity case.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_SEC_0043SSR-CON-002CybersecurityHigh complexity24Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.NoneUnverified security control could leave a residual risk in the cybersecurity case.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_SEC_0030SSR-CON-002CybersecurityHigh complexity8Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceUnverified security control could leave a residual risk in the cybersecurity case.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_SEC_0044SSR-VIH-002Process / complianceMedium complexity8Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_SEC_0045SSR-VIH-001CybersecurityHigh complexity8Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.NoneUnverified security control could leave a residual risk in the cybersecurity case.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_SEC_0046SSR-VIH-002Process / complianceMedium complexity8Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_SEC_0032SSR-VIH-002Process / complianceMedium complexity8Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_SEC_0033SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
RFQX-1001379436-P10-000-01-0052NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-1001379436-P10-000-01-0053NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
REQ_SEC_0034SSR-VIH-003SystemMedium complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-006; OEM/Customer Review InterfaceResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
REQ_SEC_0035SSR-VIH-003SystemMedium complexity8Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
RFQX-1001379436-P10-000-01-0056NoneCybersecurityHigh complexity56Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.OP-006; NoneUnverified security control could leave a residual risk in the cybersecurity case.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm the split of monitoring, triage, vulnerability handling and field response between OEM PSIRT and supplier.
RFQX-1001379436-P10-000-01-0057NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
REQ_SEC_0036SSR-VIH-004InterfaceHigh complexity8Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.External Interfaces; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_SEC_0037SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_SEC_0047SSR-HW-001HardwareHigh complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
REQ_SEC_0048SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_SEC_0049SSR-LIFE-001HardwareHigh complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
REQ_SEC_0050SSR-HW-001HardwareHigh complexity8Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OEM/Customer Review InterfaceResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RFQX-1001379436-P10-000-01-0064NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-1001379436-P10-000-01-0065NoneHardwareHigh complexity56Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-1001379436-P10-000-01-0066NoneHardwareHigh complexity56Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
REQ_SEC_0051SSR-LOG-001CybersecurityHigh complexity8Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.NoneUnverified security control could leave a residual risk in the cybersecurity case.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
RFQX-3299216-1-0001NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
2.1SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
2.2NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
2.3SSR-HW-001HardwareHigh complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
2.4NoneInterfaceMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
2.5NoneInterfaceMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
2.6SSR-SYS-001SystemMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
RFQX-3299216-1-0008NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-001; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm the exact ECU designation/variant and the agreed item definition and boundary used for the risk analysis (TARA).
RFQX-3299216-1-0009NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-001; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm the exact ECU designation/variant and the agreed item definition and boundary used for the risk analysis (TARA).
RFQX-3299216-1-0010NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0011NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-008; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm production/debug hardening expectations (debug lock, secure end-of-line, developer-access policy).
2.7SSR-SYS-001SystemMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
2.8SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
2.11SSR-SYS-001SystemMedium complexity16Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
RFQX-3299216-1-0015NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-001; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm the exact ECU designation/variant and the agreed item definition and boundary used for the risk analysis (TARA).
RFQX-3299216-1-0016NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0017NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0018NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0019NoneHardwareHigh complexity56Limited; standard implementation and verification risk.Internal baseline decision recorded.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeComplete internal review of wording and baseline scope.
4.1NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
4.2SSR-SYS-001SystemHigh complexity9Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
4.3SSR-SYS-001SystemMedium complexity21Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
4.5NoneInterfaceLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
4.6SSR-COM-004IT / backendHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
4.7SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
4.8SSR-SYS-001SystemMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
53612101SSR-SYS-001SystemMedium complexity19Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
RFQX-3299216-1-0028NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
4.9SSR-SYS-001SystemMedium complexity19Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
4.10SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
4.11SSR-DAI-002InterfaceMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.External InterfacesLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
4.12SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
4.13SSR-COM-004IT / backendHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
4.14SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
4.15SSR-TOOL-001ToolingMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
4.16SSR-DAI-003IT / backendHigh complexity8Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RFQX-3299216-1-0037NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0038NoneIT / backendHigh complexity56Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-011; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
4.17SSR-TOOL-002IT / backendHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
4.18SSR-TOOL-002IT / backendHigh complexity19Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
4.19SSR-COM-005HardwareHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-004; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.MediumESTIMATEDDefine and codeAgree responsibility split (DIA) for the non-ECU portion.
4.20SSR-COM-005HardwareHigh complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
4.21SSR-TOOL-002IT / backendHigh complexity16Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
RFQX-3299216-1-0044NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0045NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
4.22NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
4.23SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
4.24NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
4.25SSR-TOOL-002IT / backendHigh complexity16Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
RFQX-3299216-1-0050NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0051NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
REQ 5.10SSR-TOOL-002IT / backendHigh complexity16Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
REQ 6.4NoneIT / backendHigh complexity19Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-3299216-1-0054NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
REQ 6.4SSR-TOOL-002IT / backendHigh complexity19Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
RFQX-3299216-1-0056NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
5.3SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
5.4SSR-TOOL-002IT / backendHigh complexity16Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
5.5SSR-HW-001HardwareHigh complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
5.6SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
5.7SSR-COM-006SoftwareMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
5.9SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
RFQX-3299216-1-0063NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0064NoneSystemHigh complexity56Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0065NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0066NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0067NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0068NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0069NoneSystemLow complexity8Limited; standard implementation and verification risk.Internal baseline decision recorded.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeComplete internal review of wording and baseline scope.
REQ 5.1SSR-SYS-002Process / complianceMedium complexity19Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
5.11SSR-SYS-001SystemMedium complexity19Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
RFQX-3299216-1-0072NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0073NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
REQ 8.1SSR-SYS-001SystemMedium complexity19Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
5.14SSR-SYS-003SoftwareMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
RFQX-3299216-1-0076NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0077NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0078NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
6.2SSR-DAI-003IT / backendHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
6.3NoneInterfaceLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-3299216-1-0081NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0082NoneIT / backendHigh complexity56Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
6.3.1SSR-COM-005HardwareHigh complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
6.3.2SSR-COM-007InterfaceMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.External InterfacesLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
RFQX-3299216-1-0085NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0086NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0087NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
6.4SSR-COM-004IT / backendHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
6.5.2SSR-SYS-001SystemHigh complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
RFQX-3299216-1-0090NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-008; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm production/debug hardening expectations (debug lock, secure end-of-line, developer-access policy).
RFQX-3299216-1-0091NoneInterfaceMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-008; External InterfacesLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm production/debug hardening expectations (debug lock, secure end-of-line, developer-access policy).
RFQX-3299216-1-0092NoneInterfaceMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; External InterfacesLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0093NoneIT / backendHigh complexity56Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-011; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0094NoneInterfaceMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; External InterfacesLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
REQ 6.3NoneInterfaceLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-3299216-1-0096NoneInterfaceMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; External InterfacesLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0097NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
6.6NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
6.7NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
6.8NoneInterfaceLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
6.9SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
6.10SSR-COM-007InterfaceMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.External Interfaces; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
6.11SSR-COM-007InterfaceMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.External Interfaces; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
6.12SSR-COM-007InterfaceMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.External Interfaces; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
6.14SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
RFQX-3299216-1-0106NoneInterfaceMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; External InterfacesLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
REQ 6.20SSR-RBAC-001CybersecurityHigh complexity24Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.NoneUnverified security control could leave a residual risk in the cybersecurity case.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ 6.22NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-3299216-1-0109NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
6.14.2SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
6.14.3SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
6.14.4SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
6.14.5SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
6.14.6SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
6.14.8SSR-SYS-001SystemMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
6.14.9SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
RFQX-3299216-1-0117NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0118NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
6.15SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
6.16SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
6.17SSR-SYS-001SystemHigh complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
6.18SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
6.19.1SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
6.19.2SSR-SYS-001SystemHigh complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
6.20SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
6.21SSR-RBAC-001CybersecurityHigh complexity24Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.NoneUnverified security control could leave a residual risk in the cybersecurity case.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
6.22NoneCybersecurityHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
6.22.1NoneSystemHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
6.22.2NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
6.22.3NoneSystemHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-3299216-1-0131NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0132NoneSystemHigh complexity56Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
6.23SSR-VV-001SystemMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
6.24SSR-DIAG-001InterfaceMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.External Interfaces; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
6.25SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
6.26SSR-COM-008SoftwareMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
6.27SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
6.28SSR-SYS-003SoftwareMedium complexity8Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
RFQX-3299216-1-0140NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0141NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-3299216-1-0142NoneSoftwareMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
7.1SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
7.3SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
7.4SSR-HW-001HardwareHigh complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
7.5SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
7.6NoneHardwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-3299216-1-0148NoneHardwareHigh complexity56Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0149NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0150NoneHardwareHigh complexity56Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
7.10NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
7.11NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
7.12SSR-COM-007InterfaceMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.External InterfacesLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
7.13SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
7.15NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
7.16NoneProcess / complianceLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
7.17NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
7.18NoneSoftwareLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
7.20NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-3299216-1-0160NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0161NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0162NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0163NoneIT / backendHigh complexity56Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0164NoneInterfaceMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; External InterfacesLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0165NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0166NoneInterfaceMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; External InterfacesLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0167NoneInterfaceMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; External InterfacesLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0168NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0169NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0170NoneInterfaceMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; External InterfacesLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
7.34SSR-COM-007InterfaceMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.External InterfacesLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
7.35SSR-COM-007InterfaceMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.External InterfacesLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
7.38NoneInterfaceMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-3299216-1-0174NoneInterfaceMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; External InterfacesLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0175NoneInterfaceMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; External InterfacesLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0176NoneSystemHigh complexity56Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-004; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm the update chain ownership (backend/campaign vs. ECU programming) and the authenticity/integrity scheme to be applied.
7.39SSR-COM-007InterfaceMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.External Interfaces; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
7.40SSR-COM-007InterfaceMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.External InterfacesLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
RFQX-3299216-1-0179NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0180NoneInterfaceMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; External InterfacesLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
7.45SSR-TOOL-002IT / backendHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RFQX-3299216-1-0182NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0183NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0184NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0185NoneProcess / complianceMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0186NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0187NoneInterfaceMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; External InterfacesLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0188NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0189NoneProcess / complianceMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0190NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0191NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0192NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0193NoneIT / backendHigh complexity56Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0194NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0195NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0196NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
8.2NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
8.3SSR-SYS-001SystemMedium complexity16Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
8.5SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
8.8SSR-LIFE-002SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
8.9SSR-TOOL-002IT / backendHigh complexity16Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
RFQX-3299216-1-0202NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0203NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0204NoneHardwareHigh complexity56Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0205NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0206NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
9.1SSR-SYS-001SystemMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
9.2SSR-SYS-001SystemMedium complexity16Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
RFQX-3299216-1-0209NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0210NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0211NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0212NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
10.1SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
10.2SSR-SYS-003SoftwareMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
RFQX-3299216-1-0215NoneInterfaceMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; External InterfacesLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0216NoneHardwareHigh complexity56Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0217NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
10.4SSR-SYS-003SoftwareMedium complexity19Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
RFQX-3299216-1-0219NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0220NoneSoftwareMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0221NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0222NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.5.11NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.5.12NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.5.13NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.5.14NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.5.15NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.5.16SSR-SYS-001SystemMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
10.5.17NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.5.18NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.5.19NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.5.20NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.5.21NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.5.22NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.5.23NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.5.24NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.5.25NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.5.26NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.5.27NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.5.28NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.5.29NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.5.30NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.5.31NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.5.32NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.5.33SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
10.5.34NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.5.35NoneSoftwareLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.5.36NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.6NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.6.1NoneHardwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.6.2NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.6.3NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.6.4NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.6.5NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.6.6NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-3299216-1-0256NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
10.7.14NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.7.15NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.7.16NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.7.17NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.7.18NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.7.19NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.7.20NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.7.21NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.7.22NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.7.23NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.7.24NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.7.25NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.7.26NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.7.27NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.7.28NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.7.29NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.7.30NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.7.31NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.7.32NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.7.33NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.7.34NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
10.7.35NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-3299216-1-0279NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0280NoneProcess / complianceMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0281NoneProcess / complianceMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0282NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0283NoneProcess / complianceMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
12.2NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
12.3SSR-SYS-003SoftwareMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
RFQX-3299216-1-0286NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0287NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0288NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0289NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0290NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0291NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0292NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0293NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0294NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0295NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0296NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0297NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0298NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0299NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0300NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-3299216-1-0301NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-3299216-1-0302NoneInterfaceMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; External InterfacesLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
REQ 5.1NoneSystemMedium complexity19Limited; standard implementation and verification risk.Internal baseline decision recorded.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeComplete internal review of wording and baseline scope.
RFQX-3299216-1-0304NoneSystemMedium complexity24Limited; standard implementation and verification risk.Internal baseline decision recorded.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeComplete internal review of wording and baseline scope.
RFQX-3299216-1-0305NoneSystemMedium complexity24Limited; standard implementation and verification risk.Internal baseline decision recorded.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeComplete internal review of wording and baseline scope.
RFQX-3299216-1-0306NoneSoftwareMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-009; NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm the DIA / responsibility (RASIC/CIA) split for each cybersecurity work product before supplier scope is fixed.
18850001NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
20000002NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-3299216-1-0309NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-CVS123-2-0001NoneSoftwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo supplier action - document reference / boilerplate.
RFQX-CVS123-2-0002NoneProcess / complianceMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-009; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm the DIA / responsibility (RASIC/CIA) split for each cybersecurity work product before supplier scope is fixed.
RFQX-CVS123-2-0003NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
SUV2_INFO 1NoneSoftwareLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 2NoneSoftwareMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 3NoneHardwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 4NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 5NoneSoftwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 6NoneCybersecurityHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 7NoneCybersecurityHigh complexity56Unverified security control could leave a residual risk in the cybersecurity case.Customer confirms it is binding.NoneUnverified security control could leave a residual risk in the cybersecurity case.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 8NoneIT / backendHigh complexity56Limited; standard implementation and verification risk.Customer confirms it is binding.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 9NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-CVS123-2-0013NoneSoftwareLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-CVS123-2-0014NoneIT / backendHigh complexity56Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
SUV2_INFO 10NoneHardwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 11NoneHardwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 12NoneCybersecurityMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 13NoneProcess / complianceMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-CVS123-2-0019NoneSoftwareMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-001; NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm the exact ECU designation/variant and the agreed item definition and boundary used for the risk analysis (TARA).
RFQX-CVS123-2-0020NoneSoftwareMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-CVS123-2-0021NoneSoftwareMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-CVS123-2-0022NoneSoftwareHigh complexity56Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-CVS123-2-0023NoneCybersecurityHigh complexity56Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.OP-002; NoneUnverified security control could leave a residual risk in the cybersecurity case.MediumESTIMATEDDefine and codeConfirm the diagnostic role model, the authorized services per role, and which party owns the diagnostic authorization policy.
RFQX-CVS123-2-0024NoneSoftwareMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-CVS123-2-0025NoneSoftwareLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0051NoneSystemMedium complexity32Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-CVS123-2-0027NoneSoftwareLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0051NoneSystemMedium complexity21Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-CVS123-2-0029NoneSoftwareMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-CVS123-2-0030NoneHardwareHigh complexity56Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-004; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm the update chain ownership (backend/campaign vs. ECU programming) and the authenticity/integrity scheme to be applied.
RFQX-CVS123-2-0031NoneCybersecurityHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 15NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 16NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 1SSR-RBAC-001CybersecurityHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-002; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RFQX-CVS123-2-0035NoneSoftwareMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
SUV2_REQ 2SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_REQ 3SSR-BOOT-001SoftwareMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
SUV2_REQ 4NoneSystemLow complexity5Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 3SSR-BOOT-002HardwareHigh complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
RFQX-CVS123-2-0040NoneSoftwareMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-CVS123-2-0041NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
SUV2_REQ 5SSR-UPD-001SoftwareHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-004; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_REQ 6SSR-UPD-002SystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SUV2_REQ 7SSR-BOOT-003SystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
SUV2_INFO 17NoneHardwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 8SSR-DIAG-002IT / backendHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OEM/Customer Review InterfaceResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_REQ 9SSR-RBAC-001CybersecurityHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-002; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_REQ 10SSR-UPD-001SoftwareMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
SUV2_REQ 11SSR-UPD-001SoftwareMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
SUV2_REQ 12SSR-UPD-001SoftwareHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-004; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.MediumESTIMATEDDefine and codeAgree responsibility split (DIA) for the non-ECU portion.
SUV2_REQ 13SSR-SYS-001SystemMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
SUV2_REQ 14SSR-RBAC-001CybersecurityHigh complexity24Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.NoneUnverified security control could leave a residual risk in the cybersecurity case.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
RFQX-CVS123-2-0053NoneSoftwareMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
SUV2_INFO 18NoneSoftwareLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-CVS123-2-0055SSR-BOOT-004IT / backendHigh complexity56Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-004; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_REQ 15SSR-RBAC-001CybersecurityHigh complexity24Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.NoneUnverified security control could leave a residual risk in the cybersecurity case.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
SUV2_INFO 19NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 16SSR-SYS-003SoftwareMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
SUV2_REQ 17SSR-SYS-003SoftwareMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_REQ 18NoneSoftwareLow complexity16Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 19SSR-DAI-004SoftwareHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-008; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_REQ 20SSR-UPD-002SystemHigh complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
SUV2_INFO 20NoneHardwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 182SSR-UPD-002SystemHigh complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
SUV2_INFO 129NoneInterfaceMedium complexity24Limited; standard implementation and verification risk.Customer confirms it is binding.External Interfaces; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 21SSR-SYS-003SoftwareMedium complexity8Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
SUV2_INFO 130NoneSoftwareMedium complexity24Limited; standard implementation and verification risk.Customer confirms it is binding.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 22SSR-SYS-003SoftwareMedium complexity8Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
RFQX-CVS123-2-0069NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
SUV2_REQ 23SSR-UPD-002SystemHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-004; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_REQ 24SSR-UPD-002SystemHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-004; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_REQ 25SSR-BOOT-001SoftwareMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
SUV2_INFO 21NoneSoftwareLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 22NoneSoftwareLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-CVS123-2-0075NoneSoftwareHigh complexity56Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-011; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
SUV2_INFO 23NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 24NoneSoftwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 26SSR-RBAC-002CybersecurityHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-002; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_REQ 27SSR-RBAC-002CybersecurityHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-002; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_INFO 25NoneSoftwareMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 26NoneSoftwareMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 27NoneSoftwareMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 28NoneSoftwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 29NoneSoftwareMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 30NoneInterfaceHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 31NoneCybersecurityHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 32NoneSoftwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 33NoneSoftwareLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 34NoneCybersecurityLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 35NoneCybersecurityHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 36NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 37NoneSoftwareLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 38NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 39NoneIT / backendHigh complexity56Limited; standard implementation and verification risk.Customer confirms it is binding.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-CVS123-2-0095NoneSoftwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 40NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 41NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 42NoneCybersecurityMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 43NoneSoftwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 44NoneSoftwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 45NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 46NoneCybersecurityMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 47NoneCybersecurityHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 48NoneSoftwareLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 49NoneSoftwareLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 50NoneSoftwareLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 51NoneHardwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 52NoneSoftwareLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 53NoneSoftwareMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 28SSR-DAI-004SoftwareHigh complexity19Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_INFO 54NoneCybersecurityMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 29SSR-TOOL-002IT / backendHigh complexity29Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_INFO 55NoneCybersecurityHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 30SSR-SDT-001SoftwareHigh complexity19Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_INFO 56NoneCybersecurityMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 57NoneCybersecurityHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 58NoneSoftwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 59NoneSoftwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 60NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 61NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 62NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 63NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 64NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 65NoneSoftwareMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 66NoneSoftwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0051NoneIT / backendHigh complexity32Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 67NoneHardwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 68NoneSoftwareLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 69NoneSoftwareLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 70NoneSoftwareLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 71NoneSoftwareLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 72NoneSoftwareLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 73NoneSoftwareLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 74NoneHardwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 75NoneSoftwareLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 76NoneSoftwareMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 77NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 99NoneIT / backendHigh complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 78NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 79NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 119NoneSoftwareHigh complexity5Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 80NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 126NoneSoftwareMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 81NoneSoftwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 82NoneHardwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 87NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 88NoneSoftwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 89NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 90NoneSoftwareMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 91NoneSoftwareLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 92NoneSoftwareMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 93NoneSoftwareMedium complexity24Limited; standard implementation and verification risk.Customer confirms it is binding.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-CVS123-2-0153NoneHardwareHigh complexity56Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-011; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
SUV2_INFO 94NoneSoftwareMedium complexity24Limited; standard implementation and verification risk.Customer confirms it is binding.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 95NoneSoftwareLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 96NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 97NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 27NoneSystemHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 83NoneSoftwareLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 84NoneSoftwareLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 85NoneSoftwareHigh complexity56Limited; standard implementation and verification risk.Customer confirms it is binding.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 86NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 99NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 33SSR-UPD-003IT / backendHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OEM/Customer Review InterfaceResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_REQ 34SSR-UPD-004HardwareHigh complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
SUV2_REQ 35SSR-RBAC-001CybersecurityHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-002; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_REQ 36SSR-TOOL-003SoftwareHigh complexity16Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_REQ 37SSR-SYS-003SoftwareMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
SUV2_REQ 38SSR-TOOL-002IT / backendHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_INFO 100NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 39NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 62NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 63SSR-COM-002SystemMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SUV2_INFO 101NoneHardwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 40SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
SUV2_REQ 41SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_REQ 42SSR-SYS-003SoftwareMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
SUV2_REQ 43SSR-UPD-001SoftwareMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
SUV2_REQ 44SSR-BOOT-005SoftwareMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
SUV2_INFO 102NoneSoftwareMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 45SSR-SYS-003SoftwareMedium complexity8Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
RFQX-CVS123-2-0182NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-CVS123-2-0183NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
SUV2_REQ 46SSR-UPD-001SoftwareMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SUV2_REQ 47SSR-UPD-002SystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
SUV2_REQ 48SSR-TOOL-002IT / backendHigh complexity16Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_REQ 49SSR-UPD-003IT / backendHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-002; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_REQ 50SSR-UPD-001SoftwareHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-004; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RFQX-CVS123-2-0189NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
SUV2_REQ 51SSR-TOOL-003SoftwareHigh complexity16Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_INFO 103NoneCybersecurityHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 52SSR-RBAC-001CybersecurityHigh complexity26Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.NoneUnverified security control could leave a residual risk in the cybersecurity case.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
SUV2_REQ 53SSR-SYS-001SystemMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SUV2_REQ 54NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 104NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 55SSR-CON-002CybersecurityHigh complexity26Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.NoneUnverified security control could leave a residual risk in the cybersecurity case.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SUV2_REQ 62SSR-UPD-001SoftwareHigh complexity26Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-004; OEM/Customer Review InterfaceResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_INFO 106NoneSoftwareMedium complexity24Limited; standard implementation and verification risk.Customer confirms it is binding.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 63SSR-UPD-001SoftwareHigh complexity26Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-004; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.MediumESTIMATEDDefine and codeAgree responsibility split (DIA) for the non-ECU portion.
SUV2_REQ 64SSR-TOOL-002IT / backendHigh complexity18Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_REQ 65SSR-CON-002CybersecurityHigh complexity26Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_INFO 107NoneHardwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 66SSR-TOOL-003SoftwareHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_REQ 67SSR-SDT-001SoftwareHigh complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
SUV2_REQ 68SSR-TOOL-003SoftwareHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RFQX-CVS123-2-0206NoneSoftwareMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-004; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm the update chain ownership (backend/campaign vs. ECU programming) and the authenticity/integrity scheme to be applied.
SUV2_REQ 69SSR-VV-002IT / backendHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OEM/Customer Review InterfaceResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_INFO 108NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 71SSR-TOOL-002IT / backendHigh complexity18Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_INFO 109NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 190SSR-COM-006SoftwareHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_INFO 150NoneSoftwareMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 72SSR-TOOL-003SoftwareHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_REQ 73SSR-TOOL-003SoftwareHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_REQ 74SSR-TOOL-003SoftwareHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_REQ 165SSR-VV-003SoftwareHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OEM/Customer Review InterfaceResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_REQ 166SSR-VV-003SoftwareHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OEM/Customer Review InterfaceResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_REQ 167SSR-TOOL-003SoftwareHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_INFO 137NoneSoftwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 75SSR-TOOL-002IT / backendHigh complexity18Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_REQ 80NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 76SSR-TOOL-002IT / backendHigh complexity18Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_REQ 77SSR-TOOL-003SoftwareHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_REQ 78SSR-TOOL-003SoftwareHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_REQ 79SSR-TOOL-002IT / backendHigh complexity18Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_REQ 81SSR-TOOL-002IT / backendHigh complexity18Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_REQ 82SSR-TOOL-003SoftwareHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_REQ 83SSR-TOOL-002IT / backendHigh complexity18Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_REQ 84SSR-TOOL-003SoftwareHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_REQ 85SSR-TOOL-003SoftwareHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_REQ 86NoneSoftwareMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 87SSR-TOOL-002IT / backendHigh complexity18Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_REQ 88SSR-TOOL-002IT / backendHigh complexity18Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_REQ 89SSR-TOOL-003SoftwareHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_REQ 90SSR-TOOL-002IT / backendHigh complexity18Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_REQ 92NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 91SSR-TOOL-002IT / backendHigh complexity16Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_REQ 93SSR-TOOL-002IT / backendHigh complexity16Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_REQ 94SSR-TOOL-003SoftwareHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_REQ 95SSR-DAI-003IT / backendHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_REQ 96SSR-COM-009IT / backendHigh complexity18Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_REQ 97SSR-RBAC-001CybersecurityHigh complexity26Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-002; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_REQ 98SSR-CON-002CybersecurityHigh complexity26Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_REQ 181SSR-RBAC-002CybersecurityHigh complexity26Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-002; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_INFO 110NoneHardwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 99SSR-DAI-004SoftwareHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_REQ 100SSR-SDT-001SoftwareMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SUV2_REQ 101NoneIT / backendHigh complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 111NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 102SSR-TOOL-002IT / backendHigh complexity18Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_REQ 103SSR-DIAG-002IT / backendHigh complexity18Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_REQ 104NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 114NoneHardwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 105SSR-TOOL-002IT / backendHigh complexity18Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_INFO 112NoneHardwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 106SSR-TOOL-003SoftwareHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_INFO 113NoneHardwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 107SSR-BOOT-002HardwareHigh complexity26Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
SUV2_REQ 4NoneHardwareHigh complexity26Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 108SSR-TOOL-003SoftwareHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_REQ 109SSR-SDT-001SoftwareMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SUV2_REQ 110SSR-TOOL-002IT / backendHigh complexity18Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_REQ 111SSR-TOOL-002IT / backendHigh complexity18Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_REQ 112NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 113SSR-TOOL-002IT / backendHigh complexity18Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_REQ 62SSR-SYS-003SoftwareMedium complexity18Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
SUV2_REQ 63NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 114SSR-SYS-001SystemMedium complexity18Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
SUV2_REQ 115SSR-TOOL-003SoftwareHigh complexity26Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_INFO 115NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 143SSR-UPD-002SystemMedium complexity26Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SUV2_INFO 124NoneSoftwareMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 116SSR-TOOL-002IT / backendHigh complexity18Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
RFQX-CVS123-2-0274NoneSoftwareMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-001; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm the exact ECU designation/variant and the agreed item definition and boundary used for the risk analysis (TARA).
SUV2_REQ 117SSR-SYS-001SystemMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
SUV2_REQ 118SSR-TOOL-002IT / backendHigh complexity18Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_REQ 119SSR-DAI-004SoftwareHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_REQ 120SSR-DAI-004SoftwareHigh complexity26Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_REQ 121SSR-DAI-003IT / backendHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_INFO 140NoneInterfaceMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 122SSR-TOOL-002IT / backendHigh complexity18Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_REQ 123SSR-TOOL-002IT / backendHigh complexity18Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_REQ 124NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 125SSR-TOOL-002IT / backendHigh complexity18Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_REQ 126SSR-DAI-005SoftwareHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OEM/Customer Review InterfaceResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RFQX-CVS123-2-0286NoneCybersecurityHigh complexity56Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-002; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm the diagnostic role model, the authorized services per role, and which party owns the diagnostic authorization policy.
SUV2_REQ 146NoneHardwareHigh complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 151NoneSoftwareMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 169NoneSoftwareMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 170NoneSoftwareMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 128NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 171SSR-TOOL-002IT / backendHigh complexity16Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_INFO 138NoneInterfaceLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 172SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
SUV2_REQ 173SSR-TOOL-002IT / backendHigh complexity29Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_INFO 139NoneSystemHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 174SSR-DAI-003IT / backendHigh complexity8Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_REQ 175SSR-TOOL-002IT / backendHigh complexity16Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_REQ 183SSR-UPD-001SoftwareHigh complexity29Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OEM/Customer Review InterfaceResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_REQ 128NoneInterfaceMedium complexity19Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 141NoneSoftwareMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 176SSR-TOOL-002IT / backendHigh complexity19Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_REQ 177SSR-RBAC-001CybersecurityHigh complexity29Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-002; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_REQ 178NoneSoftwareMedium complexity21Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 179NoneSoftwareMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 180NoneSoftwareMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 131NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 129SSR-TOOL-002IT / backendHigh complexity18Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_REQ 130SSR-TOOL-002IT / backendHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_REQ 132SSR-TOOL-002IT / backendHigh complexity18Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_REQ 133SSR-TOOL-002IT / backendHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_INFO 117NoneCybersecurityHigh complexity56Unverified security control could leave a residual risk in the cybersecurity case.Customer confirms it is binding.OEM/Customer Review InterfaceUnverified security control could leave a residual risk in the cybersecurity case.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 134SSR-TOOL-002IT / backendHigh complexity16Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_INFO 119NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 120NoneHardwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 184SSR-HW-001HardwareHigh complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
SUV2_REQ 185SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
SUV2_INFO 138NoneSoftwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 161SSR-SYS-003SoftwareMedium complexity8Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
SUV2_REQ 168SSR-SYS-002Process / complianceMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_INFO 135NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-CVS123-2-0322NoneSoftwareMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
SUV2_REQ 135SSR-TOOL-002IT / backendHigh complexity16Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_INFO 121NoneSoftwareLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 138SSR-TOOL-002IT / backendHigh complexity16Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_REQ 152SSR-VV-003SoftwareHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OEM/Customer Review InterfaceResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_INFO 125NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 153SSR-TOOL-003SoftwareHigh complexity19Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_REQ 154SSR-TOOL-002IT / backendHigh complexity19Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_INFO 126NoneHardwareHigh complexity56Limited; standard implementation and verification risk.Customer confirms it is binding.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 155SSR-SYS-003SoftwareMedium complexity19Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
SUV2_INFO 127NoneHardwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 156SSR-UPD-001SoftwareHigh complexity29Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
SUV2_REQ 157SSR-HW-001HardwareHigh complexity19Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_REQ 158SSR-VV-002IT / backendHigh complexity19Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OEM/Customer Review InterfaceResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_REQ 159SSR-TOOL-003SoftwareHigh complexity16Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_REQ 160SSR-DAI-004SoftwareHigh complexity8Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SUV2_INFO 131NoneSoftwareHigh complexity56Limited; standard implementation and verification risk.Customer confirms it is binding.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 147SSR-TOOL-003SoftwareHigh complexity16Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
SUV2_REQ 148SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
SUV2_REQ 149SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
SUV2_REQ 150SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
RFQX-CVS123-2-0343NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
SUV2_INFO 134NoneSoftwareLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 133NoneSoftwareLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_INFO 132NoneHardwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
00868000NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
00930000NoneHardwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-CVS123-2-0349NoneHardwareHigh complexity56Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-004; NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm the update chain ownership (backend/campaign vs. ECU programming) and the authenticity/integrity scheme to be applied.
00930000SSR-SDT-002HardwareHigh complexity19Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.MediumESTIMATEDDefine and codeAgree responsibility split (DIA) for the non-ECU portion.
RFQX-CVS123-2-0351NoneIT / backendHigh complexity56Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-011; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.MediumESTIMATEDDefine and codeConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-CVS124-0001NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-CVS124-0002NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo supplier action - document reference / boilerplate.
RFQX-CVS124-0003NoneProcess / complianceMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-009; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm the DIA / responsibility (RASIC/CIA) split for each cybersecurity work product before supplier scope is fixed.
RFQX-CVS124-0004NoneIT / backendHigh complexity56Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
4.1NoneIT / backendHigh complexity18Limited; standard implementation and verification risk.Internal review confirms wording and scope.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedComplete internal review of wording and baseline scope.
4.2NoneCybersecurityHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo supplier action - document reference / boilerplate.
RFQX-CVS124-0007NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-CVS124-0008NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-CVS124-0009NoneSystemLow complexity8Limited; standard implementation and verification risk.Internal baseline decision recorded.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeComplete internal review of wording and baseline scope.
RFQX-CVS124-0010NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-CVS124-0011NoneIT / backendHigh complexity56Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-CVS124-0012NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-CVS124-0013NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
4.3SSR-BOOT-001SoftwareHigh complexity32Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-002; OEM/Customer Review InterfaceResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.MediumESTIMATEDDefine and codeAgree responsibility split (DIA) for the non-ECU portion.
RFQX-CVS124-0015NoneSystemLow complexity8Limited; standard implementation and verification risk.Internal baseline decision recorded.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeComplete internal review of wording and baseline scope.
RFQX-CVS124-0016NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-CVS124-0017NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
REQ_UDS_0001SSR-TOOL-002IT / backendHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
REQ_UDS_0002SSR-SYS-001SystemMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_UDS_0003NoneSoftwareHigh complexity26Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
INFO_UDS_0001NoneInterfaceMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
INFO_UDS_0002NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0004NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0005SSR-UPD-004HardwareHigh complexity26Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_UDS_0006NoneSoftwareMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0231NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0007NoneSoftwareMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0232SSR-UPD-004HardwareHigh complexity26Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_UDS_0008NoneCybersecurityHigh complexity26Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0009NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0233SSR-UPD-004HardwareHigh complexity26Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_UDS_0010NoneSoftwareHigh complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0234NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0011NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0235NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0012SSR-SYS-001SystemMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_UDS_0013NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0014NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-CVS124-0039NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
REQ_UDS_0015NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
INFO_UDS_0003NoneSoftwareMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0016NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0236SSR-UPD-004HardwareHigh complexity26Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_UDS_0017NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0018NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0019NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0237NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0020NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0021NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0022NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
INFO_UDS_0039NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms it is binding.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0339NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0340NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0341NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0023NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0025NoneHardwareHigh complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0026NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0027SSR-HW-001HardwareHigh complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0028NoneSoftwareHigh complexity26Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0029SSR-UPD-001SoftwareHigh complexity26Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_UDS_0030NoneSoftwareHigh complexity26Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
INFO_UDS_0004NoneSoftwareMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0032NoneSoftwareHigh complexity26Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0033NoneSoftwareMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0034NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
INFO_UDS_0005NoneCybersecurityMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
INFO_UDS_0040NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0036NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
INFO_UDS_0006NoneInterfaceMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0037NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
INFO_UDS_0007NoneInterfaceMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0038NoneSystemHigh complexity26Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0039NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0238SSR-UPD-004HardwareHigh complexity26Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_UDS_0040SSR-RBAC-001CybersecurityHigh complexity26Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.NoneUnverified security control could leave a residual risk in the cybersecurity case.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_UDS_0041NoneCybersecurityHigh complexity26Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0042SSR-RBAC-001CybersecurityHigh complexity26Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.NoneUnverified security control could leave a residual risk in the cybersecurity case.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_UDS_0043SSR-RBAC-001CybersecurityHigh complexity26Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceUnverified security control could leave a residual risk in the cybersecurity case.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_UDS_0044SSR-SYS-003SoftwareMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0045NoneCybersecurityHigh complexity26Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
INFO_UDS_0038NoneSoftwareMedium complexity24Limited; standard implementation and verification risk.Customer confirms it is binding.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0046SSR-SYS-003SoftwareMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_UDS_0047SSR-RBAC-003IT / backendHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
REQ_UDS_0048SSR-RBAC-004SoftwareMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_UDS_0049NoneSystemHigh complexity26Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
INFO_UDS_0008NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms it is binding.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0050SSR-DIAG-003SystemHigh complexity26Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_UDS_0051SSR-TOOL-002IT / backendHigh complexity32Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-009; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
REQ_UDS_0338SSR-SYS-001SystemMedium complexity19Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0305_1NoneSoftwareHigh complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
INFO_UDS_0019NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0305NoneSystemMedium complexity19Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0337NoneSystemMedium complexity21Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0306_2NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0307_3NoneSoftwareHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0308_4NoneIT / backendHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0309_5NoneSoftwareHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0310_6NoneSoftwareHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0311_7NoneSoftwareLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0312_8NoneSoftwareHigh complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0313_9NoneSoftwareLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0314_10NoneSoftwareHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0315_11NoneSoftwareHigh complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0306NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0316_12NoneSoftwareLow complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0317_13NoneSystemLow complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0318_14NoneIT / backendHigh complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0319_15NoneIT / backendHigh complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0320_16NoneSoftwareLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0321_17NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0322_18NoneSoftwareHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0323_19NoneIT / backendHigh complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0324_20NoneSystemLow complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0325_21NoneIT / backendHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0326_22NoneSoftwareHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0327_23NoneSoftwareHigh complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0316NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0328_24NoneSoftwareHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0329_25NoneSoftwareHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0330_26NoneCybersecurityHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0331_27NoneCybersecurityHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0332_28NoneSoftwareHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0333_29NoneSoftwareHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0334_30NoneSoftwareLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0335_31NoneSoftwareLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0336_32NoneSoftwareHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0337_33NoneSoftwareHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0328NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0052SSR-SYS-002Process / complianceMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_UDS_0053SSR-HW-001HardwareHigh complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
INFO_UDS_0009NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0054SSR-SYS-001SystemMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0055SSR-SYS-002Process / complianceMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0056SSR-SYS-002Process / complianceMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0342SSR-RBAC-004SoftwareMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_UDS_0239NoneSystemHigh complexity26Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0057SSR-UPD-001SoftwareHigh complexity26Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
RFQX-CVS124-0138NoneSoftwareMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
REQ_UDS_0058NoneSoftwareHigh complexity26Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0059SSR-UPD-001SoftwareMedium complexity26Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
RFQX-CVS124-0141NoneIT / backendHigh complexity56Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-004; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm the update chain ownership (backend/campaign vs. ECU programming) and the authenticity/integrity scheme to be applied.
REQ_UDS_0060SSR-UPD-003IT / backendHigh complexity26Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-004; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RFQX-CVS124-0143NoneHardwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0240NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0061SSR-UPD-002SystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0241SSR-DIAG-004Process / complianceHigh complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_UDS_0242SSR-SYS-002Process / complianceMedium complexity8Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0243NoneSoftwareLow complexity16Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0062SSR-COM-007InterfaceMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.External InterfacesLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0063SSR-SYS-003SoftwareMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0064NoneCybersecurityHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0065SSR-HW-001HardwareHigh complexity8Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
REQ_UDS_0066SSR-HW-001HardwareHigh complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0067SSR-TOOL-002IT / backendHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OEM/Customer Review InterfaceResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
REQ_UDS_0244NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0068NoneCybersecurityHigh complexity26Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0069SSR-TOOL-003SoftwareHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RFQX-CVS124-0158NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-CVS124-0159NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
REQ_UDS_0070SSR-KEY-001CybersecurityHigh complexity26Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.NoneUnverified security control could leave a residual risk in the cybersecurity case.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_UDS_0071SSR-TOOL-003SoftwareHigh complexity26Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
REQ_UDS_0072SSR-SYS-003SoftwareHigh complexity26Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
INFO_UDS_0010NoneIT / backendHigh complexity56Limited; standard implementation and verification risk.Customer confirms it is binding.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0073NoneSoftwareMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0245SSR-SYS-002Process / complianceMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0246NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0074NoneSoftwareMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0075SSR-COM-006SoftwareHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RFQX-CVS124-0169NoneIT / backendHigh complexity56Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
INFO_UDS_0011NoneSoftwareMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0076SSR-RBAC-001CybersecurityHigh complexity26Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-002; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
REQ_UDS_0077SSR-COM-002SystemMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
INFO_UDS_0012NoneSoftwareMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0248NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
INFO_UDS_0013NoneSoftwareMedium complexity24Limited; standard implementation and verification risk.Customer confirms it is binding.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0078NoneSoftwareMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0079NoneSoftwareMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0080NoneSoftwareMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0247NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0081SSR-SYS-003SoftwareMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
INFO_UDS_0014NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0249SSR-SYS-002Process / complianceMedium complexity8Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0250NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0251NoneSoftwareLow complexity16Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0343SSR-UPD-001SoftwareHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-004; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
REQ_UDS_0344SSR-RBAC-001CybersecurityHigh complexity24Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.NoneUnverified security control could leave a residual risk in the cybersecurity case.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_UDS_0345NoneProcess / complianceLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0346NoneProcess / complianceLow complexity16Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0347NoneSystemLow complexity16Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0348NoneProcess / complianceLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0349NoneProcess / complianceLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0082SSR-TOOL-003SoftwareHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
REQ_UDS_0083SSR-BOOT-005SoftwareHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
INFO_UDS_0015NoneSoftwareMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0084SSR-SYS-001SystemMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0254NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0085NoneSoftwareMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0086SSR-COM-006SoftwareMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0252NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0253NoneSoftwareMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0087SSR-DIAG-005HardwareHigh complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0255SSR-SYS-002Process / complianceMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0088SSR-DIAG-003SystemMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0259NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0256NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0257NoneSoftwareLow complexity16Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0089SSR-DIAG-006SoftwareMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0090NoneIT / backendHigh complexity16Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0091SSR-HW-001HardwareHigh complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0092SSR-KEY-001CybersecurityHigh complexity24Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.NoneUnverified security control could leave a residual risk in the cybersecurity case.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_UDS_0093NoneHardwareHigh complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-CVS124-0212NoneSoftwareMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
REQ_UDS_0258SSR-SYS-002Process / complianceMedium complexity8Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0260NoneSoftwareHigh complexity26Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0261NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0262SSR-SYS-002Process / complianceMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0263NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0264NoneSoftwareMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0265NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0094NoneSoftwareMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0095NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0266SSR-SYS-002Process / complianceMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0267SSR-DIAG-004Process / complianceMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0096NoneSoftwareMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0097SSR-TOOL-002IT / backendHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
REQ_UDS_0268SSR-DIAG-004Process / complianceMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0098NoneSoftwareMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0269SSR-SYS-002Process / complianceMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0270SSR-DIAG-004Process / complianceMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0271SSR-DIAG-004Process / complianceMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0272NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0273SSR-DIAG-004Process / complianceMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0274SSR-DIAG-004Process / complianceMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0275SSR-DIAG-004Process / complianceMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0276SSR-DIAG-004Process / complianceMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0277SSR-DIAG-004Process / complianceMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
RFQX-CVS124-0237NoneSoftwareMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
REQ_UDS_0099SSR-DIAG-006SoftwareMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
RFQX-CVS124-0239NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-CVS124-0240NoneHardwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-CVS124-0241NoneInterfaceMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; External InterfacesLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
REQ_UDS_0304SSR-DIAG-003SystemMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0100NoneSoftwareMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0101SSR-SYS-003SoftwareMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
RFQX-CVS124-0245NoneSoftwareMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-CVS124-0246NoneHardwareHigh complexity56Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-001; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm the exact ECU designation/variant and the agreed item definition and boundary used for the risk analysis (TARA).
RFQX-CVS124-0247NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-CVS124-0248NoneSystemHigh complexity56Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-004; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm the update chain ownership (backend/campaign vs. ECU programming) and the authenticity/integrity scheme to be applied.
RFQX-CVS124-0249NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
REQ_UDS_0278SSR-SYS-002Process / complianceMedium complexity8Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0279SSR-DIAG-004Process / complianceMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0280SSR-DIAG-004Process / complianceMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0281NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0282SSR-SYS-002Process / complianceMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0283NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0102SSR-DIAG-004Process / complianceMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0103NoneSoftwareMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0104NoneSoftwareMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0284SSR-SYS-002Process / complianceMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0285NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0286NoneSoftwareMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0287NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0105NoneSoftwareMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0106SSR-SYS-002Process / complianceMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
RFQX-CVS124-0265NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
REQ_UDS_0107NoneSoftwareHigh complexity26Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0288SSR-SYS-002Process / complianceMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0289NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0290NoneSoftwareMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0108SSR-HW-001HardwareHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
INFO_UDS_0017NoneHardwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0109SSR-TOOL-003SoftwareHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
REQ_UDS_0110SSR-SDT-001SoftwareHigh complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_UDS_0111SSR-TOOL-003SoftwareHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
REQ_UDS_0112SSR-TOOL-003SoftwareHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
REQ_UDS_0113NoneSoftwareMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0114NoneSoftwareMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0115NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0116NoneSoftwareMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0117NoneSoftwareMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0118NoneSoftwareMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0295NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0119NoneSoftwareMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0291SSR-SYS-002Process / complianceMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0292SSR-SYS-002Process / complianceMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0293NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0120NoneSoftwareMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0294SSR-SYS-002Process / complianceMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0296SSR-SYS-002Process / complianceMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0297SSR-SYS-002Process / complianceMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0298NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0299NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0300NoneSoftwareMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0121NoneSoftwareMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0122SSR-SYS-001SystemMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0123NoneSoftwareMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0124SSR-SYS-001SystemMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0301NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0302NoneSoftwareMedium complexity16Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0125SSR-SYS-003SoftwareMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0303NoneInterfaceLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0126SSR-SYS-002Process / complianceMedium complexity8Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0127SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0128SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0129SSR-RBAC-004SoftwareHigh complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_UDS_0130SSR-RBAC-004SoftwareHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-002; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
REQ_UDS_0133SSR-RBAC-004SoftwareHigh complexity26Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_UDS_0134NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0135NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0136NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0137NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0138SSR-SYS-002Process / complianceMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0139SSR-SYS-003SoftwareHigh complexity26Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0140NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0141SSR-SYS-003SoftwareMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
RFQX-CVS124-0316NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-CVS124-0317NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-CVS124-0318NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-CVS124-0319NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-CVS124-0320NoneHardwareHigh complexity56Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
REQ_UDS_0142SSR-SYS-003SoftwareMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0143NoneSoftwareMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0144NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0145NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0146SSR-SYS-002Process / complianceMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
INFO_UDS_0018NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0147SSR-UPD-002SystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
RFQX-CVS124-0328NoneSystemMedium complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-009; OEM/Customer Review InterfaceResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm the DIA / responsibility (RASIC/CIA) split for each cybersecurity work product before supplier scope is fixed.
REQ_UDS_0148SSR-UPD-002SystemMedium complexity26Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_UDS_0149SSR-UPD-002SystemMedium complexity26Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
RFQX-CVS124-0331NoneHardwareHigh complexity56Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
REQ_UDS_0150SSR-SYS-003SoftwareMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_UDS_0151SSR-SYS-001SystemMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0152SSR-SYS-001SystemMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0153NoneSystemMedium complexity26Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0154SSR-UPD-002SystemMedium complexity26Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0155SSR-UPD-002SystemMedium complexity26Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0156SSR-SYS-001SystemMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0157SSR-UPD-002SystemMedium complexity26Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
RFQX-CVS124-0340NoneSoftwareMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-004; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm the update chain ownership (backend/campaign vs. ECU programming) and the authenticity/integrity scheme to be applied.
REQ_UDS_0158SSR-TOOL-003SoftwareHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
INFO_UDS_0020NoneHardwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0159SSR-BOOT-002HardwareHigh complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
INFO_UDS_0021NoneHardwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0160SSR-TOOL-003SoftwareHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
REQ_UDS_0161SSR-SDT-001SoftwareMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
RFQX-CVS124-0347NoneHardwareHigh complexity56Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
REQ_UDS_0162SSR-UPD-002SystemMedium complexity26Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0163NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0164SSR-SYS-001SystemMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0165NoneSystemHigh complexity26Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SUV2_REQ 62SSR-SYS-003SoftwareMedium complexity18Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
SUV2_REQ 63NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0166SSR-BOOT-005SoftwareMedium complexity26Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_UDS_0167NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0168SSR-SYS-001SystemMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
INFO_UDS_0022NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
INFO_UDS_0023NoneHardwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
INFO_UDS_0024NoneHardwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
INFO_UDS_0025NoneHardwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0169NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0170SSR-DAI-006IT / backendHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OEM/Customer Review InterfaceResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
INFO_UDS_0026NoneSoftwareMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0171SSR-TOOL-003SoftwareHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
REQ_UDS_0172SSR-DAI-006IT / backendHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OEM/Customer Review InterfaceResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
REQ_UDS_0173SSR-UPD-002SystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0174SSR-SYS-001SystemMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0175SSR-SYS-003SoftwareMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0176SSR-DAI-007SystemMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_UDS_0177SSR-DAI-005SoftwareMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_UDS_0178SSR-DAI-007SystemMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_UDS_0179SSR-SYS-001SystemMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0180SSR-SYS-001SystemMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0181SSR-SYS-003SoftwareMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
RFQX-CVS124-0375NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
REQ_UDS_0182SSR-SYS-001SystemMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
RFQX-CVS124-0377NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
INFO_UDS_0027NoneInterfaceMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
INFO_UDS_0028NoneSoftwareMedium complexity24Limited; standard implementation and verification risk.Customer confirms it is binding.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
INFO_UDS_0029NoneIT / backendHigh complexity56Limited; standard implementation and verification risk.Customer confirms it is binding.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0183SSR-TOOL-002IT / backendHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RFQX-CVS124-0382NoneSoftwareMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-001; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm the exact ECU designation/variant and the agreed item definition and boundary used for the risk analysis (TARA).
REQ_UDS_0184SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_UDS_0185SSR-TOOL-002IT / backendHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
REQ_UDS_0186SSR-DAI-004SoftwareHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
REQ_UDS_0187SSR-DAI-004SoftwareHigh complexity26Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
REQ_UDS_0188SSR-DAI-003IT / backendHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
REQ_UDS_0189SSR-UPD-002SystemMedium complexity26Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0190SSR-UPD-001SoftwareHigh complexity26Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-004; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
REQ_UDS_0191SSR-SYS-001SystemMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0192SSR-UPD-001SoftwareMedium complexity26Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0193SSR-UPD-002SystemMedium complexity26Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
INFO_UDS_0030NoneSoftwareMedium complexity24Limited; standard implementation and verification risk.Customer confirms it is binding.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
INFO_UDS_0031NoneSoftwareMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
INFO_UDS_0032NoneHardwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
INFO_UDS_0033NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0194SSR-UPD-003IT / backendHigh complexity26Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-004; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
REQ_UDS_0195SSR-SYS-003SoftwareMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_UDS_0196NoneHardwareHigh complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0197SSR-DIAG-003SystemMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
INFO_UDS_0034NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0198SSR-SYS-001SystemMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0199SSR-SYS-001SystemMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0200SSR-SYS-001SystemMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0201SSR-SYS-001SystemMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0202SSR-TOOL-002IT / backendHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
REQ_UDS_0203SSR-DIAG-003SystemMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0204SSR-DIAG-003SystemMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0205SSR-DIAG-003SystemMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0206SSR-SYS-001SystemMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
INFO_UDS_0035NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0207SSR-SYS-001SystemMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0208NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0209NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0210SSR-DIAG-003SystemHigh complexity26Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_UDS_0210SSR-DIAG-003SystemHigh complexity26Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_UDS_0211SSR-SYS-001SystemMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0212SSR-DIAG-003SystemHigh complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
INFO_UDS_0036NoneSystemHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0213SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0214SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_UDS_0215NoneSystemHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0216NoneSystemHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0217NoneSystemHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
INFO_UDS_0037NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0218NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0219SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
REQ_UDS_0220NoneSystemHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0221NoneSystemHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0222NoneSystemHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0223SSR-RBAC-001CybersecurityHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-002; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
REQ_UDS_0224SSR-RBAC-001CybersecurityHigh complexity24Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.NoneUnverified security control could leave a residual risk in the cybersecurity case.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
RFQX-CVS124-0433SSR-COM-004IT / backendHigh complexity56Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
REQ_UDS_0225SSR-TOOL-004SystemHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
REQ_UDS_0226SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0227SSR-TOOL-002IT / backendHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
REQ_UDS_0228SSR-SYS-002Process / complianceMedium complexity8Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
REQ_UDS_0229SSR-TOOL-004SystemHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
REQ_UDS_0230SSR-TOOL-004SystemHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OEM/Customer Review InterfaceResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
INFO_UDS_0039NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0339NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0340NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0341NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0342NoneSystemLow complexity5Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0343NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0344NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0345NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0346NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0347NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0348NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0349NoneSystemLow complexity16Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0003NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0034NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
INFO_UDS_0040NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0036NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0037NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0045NoneSoftwareLow complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0048NoneSystemHigh complexity26Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0107NoneSystemHigh complexity26Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0180NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0193NoneSystemHigh complexity26Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0045NoneSoftwareLow complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0053NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0054NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
REQ_UDS_0024NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-CVS151-0001NoneSystemHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo supplier action - document reference / boilerplate.
RFQX-CVS151-0002NoneProcess / complianceMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-009; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm the DIA / responsibility (RASIC/CIA) split for each cybersecurity work product before supplier scope is fixed.
RFQX-CVS151-0003NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-CVS151-0004NoneCybersecurityHigh complexity56Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.OP-002; NoneUnverified security control could leave a residual risk in the cybersecurity case.MediumESTIMATEDDefine and codeConfirm the diagnostic role model, the authorized services per role, and which party owns the diagnostic authorization policy.
RBAC_INFO 1NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RBAC_INFO 2NoneHardwareHigh complexity56Limited; standard implementation and verification risk.Customer confirms it is binding.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RBAC_INFO 3NoneSoftwareMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RBAC_INFO 4NoneCybersecurityMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RBAC_INFO 5NoneSoftwareMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RBAC_INFO 6NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RBAC_REQ 1SSR-RBAC-005SystemMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
RBAC_INFO 7NoneCybersecurityHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RBAC_INFO 8NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RBAC_REQ 2SSR-TOOL-002IT / backendHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RBAC_INFO 9NoneInterfaceLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RBAC_REQ 3SSR-TOOL-002IT / backendHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RBAC_INFO 46NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RBAC_REQ 4SSR-TOOL-002IT / backendHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RBAC_REQ 5SSR-RBAC-003IT / backendHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RBAC_INFO 10NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms it is binding.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RBAC_INFO 11NoneInterfaceLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RBAC_INFO 12NoneCybersecurityMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RBAC_REQ 6SSR-TOOL-002IT / backendHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RBAC_INFO 13NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RBAC_INFO 14NoneInterfaceLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RBAC_INFO 15NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RBAC_INFO 16NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RBAC_REQ 27SSR-TOOL-002IT / backendHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RBAC_INFO 41NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RBAC_REQ 7SSR-RBAC-003IT / backendHigh complexity19Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RBAC_INFO 18NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RBAC_REQ 8SSR-TOOL-002IT / backendHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RBAC_REQ 9SSR-TOOL-002IT / backendHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RBAC_INFO 19NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms it is binding.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RBAC_REQ 10SSR-RBAC-003IT / backendHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RFQX-CVS151-0036NoneIT / backendHigh complexity56Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RBAC_REQ 11SSR-RBAC-003IT / backendHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-002; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RBAC_INFO 35NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RBAC_INFO 20NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RBAC_REQ 12SSR-RBAC-003IT / backendHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RBAC_REQ 13SSR-RBAC-003IT / backendHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-002; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RBAC_INFO 36NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RBAC_INFO 21NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RBAC_REQ 14SSR-TOOL-002IT / backendHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RBAC_REQ 15SSR-RBAC-001CybersecurityHigh complexity26Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-002; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RBAC_INFO 22NoneCybersecurityMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RBAC_INFO 23NoneCybersecurityMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RBAC_REQ 16SSR-TOOL-002IT / backendHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RFQX-CVS151-0049NoneIT / backendHigh complexity56Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-002; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm the diagnostic role model, the authorized services per role, and which party owns the diagnostic authorization policy.
RBAC_REQ 17SSR-TOOL-002IT / backendHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RBAC_REQ 18SSR-SYS-001SystemMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
RBAC_INFO 24NoneCybersecurityMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RBAC_REQ 19SSR-TOOL-002IT / backendHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RFQX-CVS151-0054NoneIT / backendHigh complexity56Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-002; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm the diagnostic role model, the authorized services per role, and which party owns the diagnostic authorization policy.
RBAC_REQ 20SSR-TOOL-002IT / backendHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RBAC_INFO 25NoneCybersecurityMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RBAC_REQ 21SSR-TOOL-002IT / backendHigh complexity18Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RFQX-CVS151-0058NoneIT / backendHigh complexity56Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-002; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm the diagnostic role model, the authorized services per role, and which party owns the diagnostic authorization policy.
RBAC_INFO 26NoneCybersecurityHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RBAC_REQ 22SSR-KEY-001CybersecurityHigh complexity26Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-003; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RBAC_INFO 27NoneCybersecurityHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RBAC_REQ 23SSR-RBAC-003IT / backendHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RBAC_INFO 28NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RBAC_INFO 29NoneInterfaceHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-CVS151-0065SSR-COM-004IT / backendHigh complexity56Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-002; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RBAC_REQ 36SSR-KEY-001CybersecurityHigh complexity29Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-002; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RBAC_INFO 30NoneSoftwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RBAC_REQ 35SSR-RBAC-004SoftwareHigh complexity19Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RBAC_INFO 32NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RBAC_INFO 33NoneCybersecurityHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RBAC_REQ 32SSR-RBAC-004SoftwareHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RBAC_INFO 34NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-CVS151-0073NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeNo supplier action - document reference / boilerplate.
RBAC_REQ 33SSR-RBAC-003IT / backendHigh complexity19Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RBAC_REQ 34SSR-RBAC-003IT / backendHigh complexity19Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RBAC_INFO 37NoneSoftwareMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RBAC_INFO 38NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-CVS151-0078SSR-RBAC-005SystemHigh complexity56Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
RBAC_REQ 24SSR-TOOL-002IT / backendHigh complexity29Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RBAC_REQ 25SSR-TOOL-002IT / backendHigh complexity19Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RBAC_REQ 26SSR-TOOL-002IT / backendHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RBAC_INFO 40NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms it is binding.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RBAC_REQ 28SSR-RBAC-001CybersecurityHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-002; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RBAC_INFO 42NoneIT / backendHigh complexity56Limited; standard implementation and verification risk.Customer confirms it is binding.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RBAC_REQ 29SSR-RBAC-004SoftwareHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-002; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RBAC_REQ 30SSR-RBAC-003IT / backendHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-002; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RBAC_INFO 43NoneIT / backendHigh complexity56Limited; standard implementation and verification risk.Customer confirms it is binding.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RBAC_REQ 31SSR-RBAC-003IT / backendHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-002; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RBAC_INFO 44NoneIT / backendHigh complexity56Limited; standard implementation and verification risk.Customer confirms it is binding.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RBAC_INFO 45NoneCybersecurityMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-CVS151-0091NoneCybersecurityHigh complexity56Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.OP-003; NoneUnverified security control could leave a residual risk in the cybersecurity case.MediumESTIMATEDDefine and codeConfirm ownership and provisioning flow for keys/certificates (generation, injection, storage, renewal, revocation) between OEM and supplier.
RFQX-CVS151-0092NoneSoftwareMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-CVS151-0093NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-CVS151-0094NoneInterfaceMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; External InterfacesLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-CVS154-0001NoneCybersecurityLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo supplier action - document reference / boilerplate.
RFQX-CVS154-0002NoneProcess / complianceMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-009; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm the DIA / responsibility (RASIC/CIA) split for each cybersecurity work product before supplier scope is fixed.
RFQX-CVS154-0003NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-CVS154-0004NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
DSC_BASE_INFO 1NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
DSC_BASE_INFO 2NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
DSC_BASE_INFO 3NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
DSC_BASE_REQ 37SSR-TOOL-002IT / backendHigh complexity16Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
DSC_BASE_REQ 43SSR-TOOL-002IT / backendHigh complexity16Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
DSC_BASE_REQ 29SSR-VV-002IT / backendHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OEM/Customer Review InterfaceResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
DSC_BASE_REQ 30SSR-TOOL-002IT / backendHigh complexity16Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
DSC_BASE_REQ 31SSR-TOOL-002IT / backendHigh complexity16Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
DSC_BASE_REQ 45SSR-VV-002IT / backendHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OEM/Customer Review InterfaceResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
DSC_BASE_REQ 46SSR-TOOL-002IT / backendHigh complexity16Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
DSC_BASE_REQ 49SSR-TOOL-002IT / backendHigh complexity16Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
DSC_BASE_REQ 26SSR-VV-002IT / backendHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OEM/Customer Review InterfaceResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
DSC_BASE_INFO 44NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms it is binding.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
DSC_BASE_INFO 33NoneIT / backendHigh complexity56Limited; standard implementation and verification risk.Customer confirms it is binding.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
DSC_BASE_INFO 4NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
DSC_BASE_INFO 38NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
DSC_BASE_REQ 5SSR-VV-001SystemMedium complexity19Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
DSC_BASE_INFO 6NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-CVS154-0023NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
DSC_BASE_INFO 7NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-CVS154-0025NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-CVS154-0026NoneSystemHigh complexity56Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-001; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm the exact ECU designation/variant and the agreed item definition and boundary used for the risk analysis (TARA).
DSC_BASE_REQ 47SSR-TOOL-002IT / backendHigh complexity16Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
DSC_BASE_INFO 9NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
DSC_BASE_REQ 39SSR-TOOL-002IT / backendHigh complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
DSC_BASE_INFO 40NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
DSC_BASE_REQ 11SSR-SYS-001SystemMedium complexity19Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
RFQX-CVS154-0032NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
DSC_BASE_INFO 17NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
DSC_BASE_REQ 41SSR-SYS-001SystemMedium complexity19Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
DSC_BASE_REQ 42NoneIT / backendHigh complexity19Limited; standard implementation and verification risk.Internal review confirms wording and scope.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedComplete internal review of wording and baseline scope.
DSC_BASE_REQ 19SSR-COM-009IT / backendHigh complexity16Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
DSC_BASE_REQ 51SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
REQ_DSC_BASE_20SSR-TOOL-003SoftwareHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
DSC_BASE_REQ 34SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
DSC_BASE_REQ 27SSR-TOOL-002IT / backendHigh complexity16Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
DSC_BASE_REQ 50SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
DSC_BASE_INFO 35NoneSystemHigh complexity56Limited; standard implementation and verification risk.Customer confirms it is binding.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
DSC_BASE_REQ 28SSR-TOOL-002IT / backendHigh complexity16Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
DSC_BASE_REQ 22SSR-KEY-001CybersecurityHigh complexity24Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.NoneUnverified security control could leave a residual risk in the cybersecurity case.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
DSC_BASE_INFO 36NoneSystemHigh complexity56Limited; standard implementation and verification risk.Customer confirms it is binding.OEM/Customer Review InterfaceLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
DSC_BASE_REQ 48SSR-TOOL-002IT / backendHigh complexity16Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
RFQX-CVS154-0047NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-CVS31-0001NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-CVS31-0002NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo supplier action - document reference / boilerplate.
RFQX-CVS31-0003NoneProcess / complianceMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-009; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm the DIA / responsibility (RASIC/CIA) split for each cybersecurity work product before supplier scope is fixed.
RFQX-CVS31-0004NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-CVS31-0005NoneIT / backendHigh complexity56Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
1.1SSR-RBAC-001CybersecurityHigh complexity29Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.OEM/Customer Review InterfaceUnverified security control could leave a residual risk in the cybersecurity case.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
RFQX-CVS31-0007NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-CVS31-0008NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.OP-011; OEM/Customer Review InterfaceLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-CVS31-0009NoneIT / backendHigh complexity56Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-011; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-CVS31-0010NoneIT / backendHigh complexity56Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-011; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
AUTH_INFO 1NoneProcess / complianceMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 1SSR-TOOL-002IT / backendHigh complexity21Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
AUTH_INFO 2NoneProcess / complianceMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 155SSR-RBAC-006SoftwareHigh complexity26Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-002; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RFQX-CVS31-0015NoneSoftwareHigh complexity56Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-002; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm the diagnostic role model, the authorized services per role, and which party owns the diagnostic authorization policy.
AUTH_REQ 2SSR-KEY-002SystemHigh complexity32Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
AUTH_REQ 117SSR-DAI-001CybersecurityHigh complexity26Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-002; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_INFO 30NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 118SSR-KEY-003IT / backendHigh complexity26Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-003; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_INFO 24NoneIT / backendHigh complexity56Limited; standard implementation and verification risk.Customer confirms it is binding.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 45SSR-DAI-001CybersecurityHigh complexity26Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-003; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_REQ 119SSR-TOOL-002IT / backendHigh complexity26Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_INFO 27NoneCybersecurityHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 3SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
AUTH_REQ 4SSR-SYS-002Process / complianceMedium complexity10Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
AUTH_REQ 172SSR-KEY-002SystemHigh complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
AUTH_REQ 173SSR-KEY-003IT / backendHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-003; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_REQ 174SSR-KEY-003IT / backendHigh complexity26Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-003; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_REQ 5SSR-KEY-002SystemHigh complexity26Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
AUTH_REQ 120SSR-TOOL-002IT / backendHigh complexity26Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_REQ 6SSR-TOOL-004SystemHigh complexity26Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_INFO 143NoneCybersecurityHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 7SSR-DAI-008SystemMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
AUTH_INFO 60NoneSystemHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 4NoneCybersecurityHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 121SSR-KEY-003IT / backendHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-003; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_REQ 122SSR-KEY-001CybersecurityHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-003; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_REQ 123SSR-KEY-003IT / backendHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-003; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_INFO 5NoneCybersecurityHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 8SSR-SYS-001SystemMedium complexity18Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
AUTH_REQ 116SSR-DAI-003IT / backendHigh complexity26Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_REQ 110SSR-RBAC-004SoftwareHigh complexity26Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-002; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_REQ 111SSR-TOOL-002IT / backendHigh complexity26Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_INFO 31NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 112SSR-TOOL-002IT / backendHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_REQ 113SSR-DAI-006IT / backendHigh complexity26Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OEM/Customer Review InterfaceResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_REQ 114SSR-COM-004IT / backendHigh complexity26Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_REQ 115SSR-DAI-003IT / backendHigh complexity26Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RFQX-CVS31-0049NoneIT / backendHigh complexity56Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-011; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
AUTH_INFO 141NoneCybersecurityHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 160SSR-SYS-001SystemMedium complexity21Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
AUTH_INFO 142NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 3NoneCybersecurityHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 161SSR-SYS-001SystemMedium complexity21Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
AUTH_INFO 140NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 162SSR-DAI-008SystemMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
AUTH_INFO 145NoneSystemHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 124SSR-TOOL-002IT / backendHigh complexity26Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_REQ 125SSR-TOOL-002IT / backendHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_REQ 126SSR-COM-004IT / backendHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-004; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_REQ 127SSR-DAI-006IT / backendHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OEM/Customer Review InterfaceResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_REQ 128SSR-DAI-006IT / backendHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-004; OEM/Customer Review InterfaceResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_REQ 129SSR-TOOL-002IT / backendHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-004; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_INFO 11NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 159SSR-SYS-001SystemMedium complexity21Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
AUTH_REQ 96SSR-RBAC-004SoftwareHigh complexity26Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
AUTH_REQ 158SSR-TOOL-002IT / backendHigh complexity26Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_REQ 130SSR-TOOL-002IT / backendHigh complexity18Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
AUTH_INFO 32NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 131SSR-COM-004IT / backendHigh complexity26Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-004; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_REQ 132SSR-COM-004IT / backendHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_INFO 133NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 175SSR-DAI-001CybersecurityHigh complexity24Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.NoneUnverified security control could leave a residual risk in the cybersecurity case.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
AUTH_REQ 176SSR-KEY-001CybersecurityHigh complexity24Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.NoneUnverified security control could leave a residual risk in the cybersecurity case.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
AUTH_REQ 177SSR-KEY-001CybersecurityHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-003; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_INFO 101NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 163SSR-KEY-002SystemHigh complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
AUTH_REQ 164SSR-KEY-001CybersecurityHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-003; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_INFO 7NoneCybersecurityHigh complexity56Unverified security control could leave a residual risk in the cybersecurity case.Customer confirms it is binding.NoneUnverified security control could leave a residual risk in the cybersecurity case.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 165SSR-KEY-001CybersecurityHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-003; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_REQ 134SSR-DAI-001CybersecurityHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-003; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_REQ 166NoneIT / backendHigh complexity19Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 9SSR-KEY-001CybersecurityHigh complexity29Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-003; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_REQ 106SSR-SYS-001SystemMedium complexity19Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
AUTH_INFO 25NoneCybersecurityHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 100NoneCybersecurityHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 11NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 170SSR-KEY-001CybersecurityHigh complexity24Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.NoneUnverified security control could leave a residual risk in the cybersecurity case.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
AUTH_REQ 13SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
AUTH_INFO 8NoneSystemLow complexity8Limited; standard implementation and verification risk.Customer confirms it is binding.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 9NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-CVS31-0092NoneCybersecurityHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 14SSR-RBAC-003IT / backendHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_INFO 61NoneSoftwareHigh complexity56Limited; standard implementation and verification risk.Customer confirms it is binding.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 135SSR-RBAC-003IT / backendHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RFQX-CVS31-0096NoneCybersecurityHigh complexity56Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-003; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm ownership and provisioning flow for keys/certificates (generation, injection, storage, renewal, revocation) between OEM and supplier.
AUTH_INFO 33NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 136SSR-RBAC-003IT / backendHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RFQX-CVS31-0099NoneCybersecurityHigh complexity56Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-003; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm ownership and provisioning flow for keys/certificates (generation, injection, storage, renewal, revocation) between OEM and supplier.
AUTH_REQ 42SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
AUTH_REQ 15SSR-KEY-001CybersecurityHigh complexity24Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.NoneUnverified security control could leave a residual risk in the cybersecurity case.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
AUTH_REQ 47SSR-KEY-001CybersecurityHigh complexity24Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.NoneUnverified security control could leave a residual risk in the cybersecurity case.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
AUTH_REQ 95SSR-KEY-001CybersecurityHigh complexity24Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.NoneUnverified security control could leave a residual risk in the cybersecurity case.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
AUTH_REQ 107SSR-SYS-001SystemHigh complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
AUTH_REQ 105SSR-DAI-008SystemMedium complexity8Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
AUTH_REQ 169SSR-KEY-001CybersecurityHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-003; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_INFO 137NoneCybersecurityHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 138NoneIT / backendHigh complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 143NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 139NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 156SSR-DIAG-006SoftwareHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-002; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_INFO 134NoneSoftwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 16SSR-TOOL-002IT / backendHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_REQ 17NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 18NoneProcess / complianceLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 19NoneSystemHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 20NoneSystemHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 10NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 157SSR-DIAG-006SoftwareHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-002; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_REQ 140SSR-TOOL-002IT / backendHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_REQ 141NoneSystemHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 142NoneCybersecurityHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 144NoneCybersecurityHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 145NoneCybersecurityHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 146NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 34NoneCybersecurityHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 35NoneSystemHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 21SSR-TOOL-002IT / backendHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_REQ 22NoneSystemHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 23NoneSystemHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 147NoneCybersecurityHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 148NoneCybersecurityHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 149SSR-TOOL-002IT / backendHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_REQ 150SSR-TOOL-002IT / backendHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_INFO 135NoneCybersecurityHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 136NoneCybersecurityHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 167SSR-KEY-002SystemHigh complexity29Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
AUTH_REQ 168SSR-SYS-001SystemHigh complexity29Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
AUTH_INFO 146NoneCybersecurityHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 26NoneSystemHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 24SSR-COM-006SoftwareHigh complexity29Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_REQ 33SSR-SYS-001SystemMedium complexity19Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
AUTH_REQ 25SSR-RBAC-004SoftwareHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-002; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_INFO 12NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 13NoneProcess / complianceLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 109SSR-SYS-001SystemHigh complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
AUTH_REQ 26SSR-TOOL-002IT / backendHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_REQ 27SSR-TOOL-002IT / backendHigh complexity16Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedConfirm responsibility allocation, then implement and verify.
AUTH_INFO 147NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 148NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 28SSR-TOOL-002IT / backendHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_REQ 29SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
AUTH_INFO 14NoneSystemLow complexity8Limited; standard implementation and verification risk.Customer confirms it is binding.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 38NoneSystemHigh complexity56Limited; standard implementation and verification risk.Customer confirms it is binding.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 133SSR-SYS-001SystemMedium complexity8Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeConfirm responsibility allocation, then implement and verify.
AUTH_REQ 151SSR-KEY-003IT / backendHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-003; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_REQ 152SSR-COM-004IT / backendHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_REQ 153SSR-COM-004IT / backendHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
AUTH_INFO 36NoneSystemHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 154SSR-SYS-001SystemHigh complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
AUTH_INFO 37NoneSystemHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 167NoneSystemMedium complexity19Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 169NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 12NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-CVS31-0165NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeNo supplier action - document reference / boilerplate.
AUTH_REQ 4NoneSystemMedium complexity19Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 159NoneSystemMedium complexity21Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 1NoneSystemMedium complexity21Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 160NoneSystemMedium complexity21Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 2NoneSystemMedium complexity21Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 161NoneSystemMedium complexity21Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 3NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 162NoneSystemLow complexity5Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 5NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 163NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 6NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 164NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 7NoneSystemLow complexity5Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 165NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 8NoneSystemLow complexity5Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 166NoneSystemMedium complexity19Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 12NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 170NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 10NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 171NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 1NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 141NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 2NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 142NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 3NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 143NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 4NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 140NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 5NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 145NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 11NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 146NoneSystemHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 135NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 136NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 167NoneSystemLow complexity5Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 168NoneCybersecurityHigh complexity29Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 169NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 137NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 107NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 136NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 60NoneSystemHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 127NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 128NoneSystemHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 12NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 137NoneIT / backendHigh complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 135NoneIT / backendHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 155NoneSystemLow complexity5Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 117NoneSystemLow complexity5Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 45NoneSystemLow complexity5Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 3NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 122NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 5NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 164NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 9NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 136NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 156NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 172NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 173NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 6NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 175NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 176NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 177NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 147NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 147NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 1NoneSystemMedium complexity21Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 155NoneSystemLow complexity5Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 117NoneSystemLow complexity5Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 24NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 45NoneSystemLow complexity5Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 3NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 122NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 5NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 164NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 9NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 136NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 156NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 157NoneSystemHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 24NoneSystemHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 171NoneCybersecurityHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 100NoneCybersecurityHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 108NoneSystemHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 172NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 173NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 174NoneProcess / complianceHigh complexity26Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 6NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 175NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 176NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_REQ 177NoneSystemLow complexity4Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
AUTH_INFO 101NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-CVS32-0001NoneSystemMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
RFQX-CVS32-0002NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo supplier action - document reference / boilerplate.
RFQX-CVS32-0003NoneProcess / complianceMedium complexity24Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-009; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm the DIA / responsibility (RASIC/CIA) split for each cybersecurity work product before supplier scope is fixed.
RFQX-CVS32-0004NoneIT / backendHigh complexity56Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
1.1NoneCybersecurityHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo supplier action - document reference / boilerplate.
1.2NoneCybersecurityHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
1.3SSR-KEY-004CybersecurityHigh complexity26Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-004; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RFQX-CVS32-0008NoneCybersecurityHigh complexity56Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.OP-011; NoneUnverified security control could leave a residual risk in the cybersecurity case.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
SDT_REQ 1SSR-COM-010SystemMedium complexity19Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SDT_INFO 1NoneSoftwareMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 2NoneInterfaceMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 2SSR-COM-010SystemMedium complexity19Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SDT_REQ 3NoneCybersecurityHigh complexity29Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-CVS32-0014NoneCybersecurityHigh complexity56Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-002; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm the diagnostic role model, the authorized services per role, and which party owns the diagnostic authorization policy.
SDT_INFO 3NoneSoftwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 4SSR-RBAC-007CybersecurityHigh complexity29Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-002; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RFQX-CVS32-0017NoneSystemHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 4NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 5SSR-COM-011SoftwareHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-005; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
RFQX-CVS32-0020NoneSoftwareHigh complexity56Limited; standard implementation and verification risk.Customer confirms responsibility allocation and implementation method.OP-011; NoneLimited; standard implementation and verification risk.LowBLOCKED / NEEDS CUSTOMER DECISIONCustomer clarificationConfirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
SDT_INFO 5NoneInterfaceMedium complexity24Limited; standard implementation and verification risk.Customer confirms it is binding.External InterfacesLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 6NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 7NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 8NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 6SSR-COM-009IT / backendHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SDT_REQ 7SSR-COM-007InterfaceMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.External InterfacesLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SDT_REQ 8SSR-COM-009IT / backendHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-005; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SDT_REQ 9SSR-COM-009IT / backendHigh complexity29Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-005; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SDT_REQ 10SSR-COM-007InterfaceHigh complexity24Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.External InterfacesLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
SDT_REQ 11SSR-COM-007InterfaceMedium complexity19Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.External InterfacesLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SDT_REQ 12SSR-COM-009IT / backendHigh complexity29Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-005; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SDT_INFO 9NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 13SSR-COM-009IT / backendHigh complexity19Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SDT_INFO 10NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 71NoneSystemMedium complexity19Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 9NoneIT / backendHigh complexity19Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 11NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 12NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 13NoneInterfaceMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 14SSR-COM-010SystemMedium complexity19Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SDT_INFO 14NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 15NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 16NoneInterfaceMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 15SSR-COM-007InterfaceMedium complexity19Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.External InterfacesLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SDT_INFO 17NoneCybersecurityHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 16SSR-COM-010SystemMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SDT_REQ 17SSR-COM-007InterfaceMedium complexity18Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.External InterfacesLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SDT_REQ 18SSR-COM-009IT / backendHigh complexity26Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-005; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SDT_REQ 19NoneSystemMedium complexity18Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 18NoneCybersecurityHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 20SSR-KEY-004CybersecurityHigh complexity26Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-005; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SDT_INFO 19NoneCybersecurityHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 21SSR-COM-010SystemHigh complexity32Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
SDT_REQ 22SSR-VV-004IT / backendHigh complexity32Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-005; OEM/Customer Review InterfaceResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SDT_INFO 20NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 23SSR-KEY-004CybersecurityHigh complexity29Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SDT_REQ 24SSR-RBAC-006SoftwareHigh complexity29Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
SDT_REQ 25SSR-COM-011SoftwareMedium complexity19Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SDT_REQ 26SSR-COM-011SoftwareHigh complexity29Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
SDT_INFO 21NoneSystemHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 22NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 23NoneCybersecurityHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 24NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 27SSR-COM-011SoftwareMedium complexity19Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SDT_REQ 28SSR-KEY-004CybersecurityHigh complexity29Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SDT_REQ 29SSR-KEY-004CybersecurityHigh complexity29Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SDT_INFO 25NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 30SSR-KEY-004CybersecurityHigh complexity29Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.NoneUnverified security control could leave a residual risk in the cybersecurity case.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
SDT_REQ 31SSR-COM-010SystemMedium complexity19Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SDT_REQ 32SSR-COM-010SystemMedium complexity19Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SDT_REQ 33SSR-COM-007InterfaceMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.External InterfacesLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SDT_INFO 26NoneInterfaceLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 34SSR-DAI-009CybersecurityHigh complexity16Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.NoneUnverified security control could leave a residual risk in the cybersecurity case.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SDT_REQ 35SSR-COM-007InterfaceMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.External InterfacesLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SDT_REQ 36SSR-COM-007InterfaceMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.External InterfacesLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SDT_REQ 37SSR-COM-007InterfaceMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.External InterfacesLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SDT_REQ 38SSR-COM-010SystemMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SDT_REQ 39SSR-COM-007InterfaceMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.External InterfacesLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SDT_REQ 41NoneSystemLow complexity16Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 42SSR-COM-009IT / backendHigh complexity29Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-005; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SDT_REQ 43NoneSystemLow complexity16Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 44SSR-DAI-009CybersecurityHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-005; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SDT_REQ 46SSR-COM-009IT / backendHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SDT_REQ 47SSR-COM-009IT / backendHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SDT_REQ 48SSR-COM-009IT / backendHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SDT_INFO 27NoneSoftwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 28NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-CVS32-0088SSR-COM-007InterfaceLow complexity8Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.External InterfacesLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SDT_INFO 29NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 30NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 49SSR-COM-011SoftwareMedium complexity19Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SDT_REQ 50SSR-DAI-009CybersecurityHigh complexity29Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SDT_REQ 51SSR-DAI-009CybersecurityHigh complexity29Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SDT_INFO 49NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 52SSR-KEY-004CybersecurityHigh complexity29Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.NoneUnverified security control could leave a residual risk in the cybersecurity case.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
SDT_REQ 91SSR-COM-010SystemMedium complexity19Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SDT_REQ 89NoneSystemMedium complexity19Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 90NoneSystemLow complexity19Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 54SSR-COM-010SystemMedium complexity19Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SDT_REQ 55SSR-COM-007InterfaceMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.External InterfacesLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SDT_REQ 56SSR-COM-007InterfaceMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.External InterfacesLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SDT_REQ 57SSR-COM-007InterfaceMedium complexity19Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.External InterfacesLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SDT_REQ 58SSR-COM-010SystemMedium complexity19Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SDT_REQ 59SSR-COM-007InterfaceMedium complexity19Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.External InterfacesLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SDT_REQ 60NoneSystemLow complexity19Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 61SSR-COM-012IT / backendHigh complexity29Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-005; OEM/Customer Review InterfaceResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SDT_REQ 62NoneSystemLow complexity16Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 63SSR-COM-009IT / backendHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-005; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SDT_REQ 64SSR-COM-009IT / backendHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SDT_REQ 65SSR-COM-009IT / backendHigh complexity16Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SDT_REQ 66SSR-COM-007InterfaceMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.External InterfacesLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SDT_INFO 31NoneSoftwareHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 32NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 33NoneCybersecurityHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 34NoneSoftwareMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
RFQX-CVS32-0116NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 35NoneCybersecurityHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 36NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 67SSR-COM-009IT / backendHigh complexity29Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SDT_REQ 68SSR-COM-013CybersecurityHigh complexity29Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-005; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SDT_REQ 69SSR-COM-009IT / backendHigh complexity29Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-005; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SDT_REQ 70SSR-COM-009IT / backendHigh complexity29Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-005; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SDT_REQ 71SSR-COM-009IT / backendHigh complexity29Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-005; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SDT_REQ 88SSR-COM-009IT / backendHigh complexity29Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-005; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SDT_REQ 72SSR-COM-009IT / backendHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-005; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SDT_REQ 73SSR-COM-009IT / backendHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-005; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SDT_INFO 37NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 74SSR-COM-009IT / backendHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-005; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SDT_INFO 38NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 75SSR-COM-009IT / backendHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-005; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SDT_REQ 76SSR-COM-009IT / backendHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-005; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SDT_INFO 39NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 77SSR-DAI-009CybersecurityHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-005; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SDT_INFO 40NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 41NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 42NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 43NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 44NoneCybersecurityMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 78SSR-DAI-009CybersecurityHigh complexity29Unverified security control could leave a residual risk in the cybersecurity case.Customer approves the proposed implementation method and responsibility allocation.NoneUnverified security control could leave a residual risk in the cybersecurity case.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedValidate assumption with customer; complete mapping; implement.
SDT_REQ 79SSR-COM-010SystemMedium complexity19Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SDT_REQ 80SSR-COM-010SystemMedium complexity19Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SDT_REQ 81SSR-COM-010SystemMedium complexity19Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SDT_REQ 82SSR-COM-010SystemMedium complexity19Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SDT_REQ 83SSR-COM-010SystemMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SDT_REQ 84SSR-COM-010SystemMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SDT_REQ 85SSR-COM-010SystemMedium complexity16Limited; standard implementation and verification risk.Customer approves the proposed implementation method and responsibility allocation.NoneLimited; standard implementation and verification risk.MediumESTIMATEDDefine and codeValidate assumption with customer; complete mapping; implement.
SDT_REQ 86SSR-COM-009IT / backendHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-005; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SDT_INFO 45NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 46NoneIT / backendHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 47NoneInterfaceLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 87SSR-COM-009IT / backendHigh complexity24Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion.OP-005; NoneResponsibility gap between OEM and supplier could leave a security control unimplemented or duplicated.LowESTIMATED WITH ASSUMPTIONDefine and code - assumption gatedAgree responsibility split (DIA) for the non-ECU portion.
SDT_REQ 7NoneSystemLow complexity16Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 48NoneInterfaceLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 7NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 14NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 15NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 22NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 25NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 7NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 14NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 15NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 17NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 22NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 25NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 49NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 13NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 17NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 16NoneSystemHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 20NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 21NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 24NoneSystemHigh complexity56Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 31NoneSystemHigh complexity29Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 34NoneSystemHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 37NoneSystemHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 38NoneSystemHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 39NoneSystemHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 41NoneSystemHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 42NoneSystemHigh complexity29Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 43NoneSystemHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 44NoneSystemHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 48NoneSystemHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 27NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 30NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 49NoneSystemHigh complexity29Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 50NoneSystemHigh complexity29Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 51NoneSystemLow complexity19Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 49NoneSystemLow complexity8Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 52NoneSystemLow complexity19Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 89NoneSystemLow complexity19Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 90NoneSystemMedium complexity19Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 91NoneSystemHigh complexity29Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 54NoneSystemHigh complexity29Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 57NoneSystemHigh complexity29Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 58NoneSystemHigh complexity29Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 59NoneSystemHigh complexity29Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 60NoneSystemHigh complexity29Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 61NoneSystemHigh complexity29Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 62NoneSystemHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 63NoneSystemHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 66NoneSystemHigh complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_INFO 33NoneSystemMedium complexity24Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 88NoneIT / backendHigh complexity29Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.
SDT_REQ 88NoneSystemHigh complexity29Misinterpreted requirement could drive wrong design and late change cost.Customer confirms it is binding.NoneMisinterpreted requirement could drive wrong design and late change cost.MediumESTIMATEDDefine and codeNo action unless the customer confirms it is binding.