Estimation
Requirement-based implementation effort in hours, complexity, rationale, dependencies, risks, and planning confidence.
Search
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
Totals by Complexity
| Complexity | Requirements |
|---|---|
| Low complexity | 263 |
| High complexity | 744 |
| Medium complexity | 782 |
Total Hours by Category / Domain
| Category / Domain | Estimated Hours |
|---|---|
| System | 14704 |
| IT / backend | 8090 |
| Software | 7032 |
| Cybersecurity | 5560 |
| Hardware | 3344 |
| Interface | 1409 |
| Process / compliance | 1113 |
| Tooling | 16 |
Search and Filters
Requirement-Based Estimation
This table is horizontally scrollable. Use the bottom scrollbar to view all columns.
| Customer Requirement ID | Linked System Requirement ID(s) | Requirement Category | Implementation Complexity | Estimated Hours | Estimation Rationale | Assumptions | Dependencies | Risks | Confidence Level | Estimation Status | Phase / Sprint | Open Questions |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1.1 | None | Cybersecurity | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 1.2 | None | Hardware | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 1.3 | None | Cybersecurity | High complexity | 18 | Unverified security control could leave a residual risk in the cybersecurity case. | Internal review confirms wording and scope. | OEM/Customer Review Interface | Unverified security control could leave a residual risk in the cybersecurity case. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Complete internal review of wording and baseline scope. |
| 1.4 | None | Hardware | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No supplier action - document reference / boilerplate. |
| RFQX-1001379436-P10-000-01-0005 | None | Cybersecurity | High complexity | 56 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Unverified security control could leave a residual risk in the cybersecurity case. | Medium | ESTIMATED | Define and code | No supplier action - document reference / boilerplate. |
| INFO_SEC_001 | None | Cybersecurity | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_SEC_0001 | SSR-CON-001 | Cybersecurity | High complexity | 18 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Unverified security control could leave a residual risk in the cybersecurity case. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_SEC_0002 | SSR-VIH-001 | Cybersecurity | High complexity | 18 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Unverified security control could leave a residual risk in the cybersecurity case. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| RFQX-1001379436-P10-000-01-0009 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm 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-0010 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm 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-0011 | None | Software | Medium complexity | 24 | Limited; standard implementation and verification risk. | Internal review confirms wording and scope. | OP-011; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| REQ_SEC_0003 | SSR-CON-002 | Cybersecurity | High complexity | 16 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Unverified security control could leave a residual risk in the cybersecurity case. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_SEC_0022 | SSR-CON-002 | Cybersecurity | High complexity | 16 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | None | Unverified security control could leave a residual risk in the cybersecurity case. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| RFQX-1001379436-P10-000-01-0014 | None | Cybersecurity | High complexity | 56 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; None | Unverified security control could leave a residual risk in the cybersecurity case. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| REQ_SEC_0023 | SSR-CON-002 | Cybersecurity | High complexity | 16 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | None | Unverified security control could leave a residual risk in the cybersecurity case. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| RFQX-1001379436-P10-000-01-0016 | None | Cybersecurity | High complexity | 56 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; None | Unverified security control could leave a residual risk in the cybersecurity case. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| REQ_SEC_0024 | SSR-CON-001 | Cybersecurity | High complexity | 16 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Unverified security control could leave a residual risk in the cybersecurity case. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_SEC_0004 | SSR-CON-001 | Cybersecurity | High complexity | 16 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Unverified security control could leave a residual risk in the cybersecurity case. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_SEC_0005 | SSR-CON-001 | Cybersecurity | High complexity | 16 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Unverified security control could leave a residual risk in the cybersecurity case. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_SEC_0040 | None | Hardware | High complexity | 16 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_SEC_0007 | SSR-CON-003 | Software | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_SEC_0025 | SSR-HW-001 | Hardware | High complexity | 8 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_SEC_0041 | None | Process / compliance | Low complexity | 16 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_SEC_0042 | SSR-CON-002 | Cybersecurity | High complexity | 16 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Unverified security control could leave a residual risk in the cybersecurity case. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_SEC_0008 | SSR-DAI-001 | Cybersecurity | High complexity | 16 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Unverified security control could leave a residual risk in the cybersecurity case. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| RFQX-1001379436-P10-000-01-0026 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| REQ_SEC_0009 | SSR-CON-002 | Cybersecurity | High complexity | 16 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Unverified security control could leave a residual risk in the cybersecurity case. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_SEC_0020 | SSR-SYS-001 | System | High complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_SEC_0010 | SSR-PROD-001 | Hardware | High complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_SEC_0011 | SSR-COM-001 | Hardware | High complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_SEC_0012 | SSR-COM-002 | System | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_SEC_0013 | SSR-COM-003 | System | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| RFQX-1001379436-P10-000-01-0033 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| REQ_SEC_0014 | SSR-COM-002 | System | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| RFQX-1001379436-P10-000-01-0035 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| REQ_SEC_0026 | SSR-COM-001 | Hardware | High complexity | 24 | Responsibility gap 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 Interface | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| REQ_SEC_0027 | SSR-CON-002 | Cybersecurity | High complexity | 16 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Unverified security control could leave a residual risk in the cybersecurity case. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_SEC_0028 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| REQ_SEC_0029 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| REQ_SEC_0006 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| REQ_SEC_0016 | SSR-KEY-001 | Cybersecurity | High complexity | 24 | Responsibility gap 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 Interface | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| REQ_SEC_0019 | SSR-KEY-001 | Cybersecurity | High complexity | 24 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | None | Unverified security control could leave a residual risk in the cybersecurity case. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_SEC_0021 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_SEC_0015 | SSR-CON-002 | Cybersecurity | High complexity | 16 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Unverified security control could leave a residual risk in the cybersecurity case. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_SEC_0043 | SSR-CON-002 | Cybersecurity | High complexity | 24 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | None | Unverified security control could leave a residual risk in the cybersecurity case. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_SEC_0030 | SSR-CON-002 | Cybersecurity | High complexity | 8 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Unverified security control could leave a residual risk in the cybersecurity case. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_SEC_0044 | SSR-VIH-002 | Process / compliance | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_SEC_0045 | SSR-VIH-001 | Cybersecurity | High complexity | 8 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | None | Unverified security control could leave a residual risk in the cybersecurity case. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_SEC_0046 | SSR-VIH-002 | Process / compliance | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_SEC_0032 | SSR-VIH-002 | Process / compliance | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_SEC_0033 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| RFQX-1001379436-P10-000-01-0052 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm 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-0053 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| REQ_SEC_0034 | SSR-VIH-003 | System | Medium complexity | 24 | Responsibility gap 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 Interface | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| REQ_SEC_0035 | SSR-VIH-003 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| RFQX-1001379436-P10-000-01-0056 | None | Cybersecurity | High complexity | 56 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | OP-006; None | Unverified security control could leave a residual risk in the cybersecurity case. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm the split of monitoring, triage, vulnerability handling and field response between OEM PSIRT and supplier. |
| RFQX-1001379436-P10-000-01-0057 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| REQ_SEC_0036 | SSR-VIH-004 | Interface | High complexity | 8 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | External Interfaces; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_SEC_0037 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_SEC_0047 | SSR-HW-001 | Hardware | High complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| REQ_SEC_0048 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_SEC_0049 | SSR-LIFE-001 | Hardware | High complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| REQ_SEC_0050 | SSR-HW-001 | Hardware | High complexity | 8 | Responsibility gap 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 Interface | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RFQX-1001379436-P10-000-01-0064 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm 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-0065 | None | Hardware | High complexity | 56 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm 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-0066 | None | Hardware | High complexity | 56 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| REQ_SEC_0051 | SSR-LOG-001 | Cybersecurity | High complexity | 8 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | None | Unverified security control could leave a residual risk in the cybersecurity case. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| RFQX-3299216-1-0001 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| 2.1 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| 2.2 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 2.3 | SSR-HW-001 | Hardware | High complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| 2.4 | None | Interface | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 2.5 | None | Interface | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 2.6 | SSR-SYS-001 | System | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| RFQX-3299216-1-0008 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-001; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm the exact ECU designation/variant and the agreed item definition and boundary used for the risk analysis (TARA). |
| RFQX-3299216-1-0009 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-001; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm the exact ECU designation/variant and the agreed item definition and boundary used for the risk analysis (TARA). |
| RFQX-3299216-1-0010 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0011 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-008; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm production/debug hardening expectations (debug lock, secure end-of-line, developer-access policy). |
| 2.7 | SSR-SYS-001 | System | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| 2.8 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| 2.11 | SSR-SYS-001 | System | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| RFQX-3299216-1-0015 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-001; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm the exact ECU designation/variant and the agreed item definition and boundary used for the risk analysis (TARA). |
| RFQX-3299216-1-0016 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0017 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0018 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0019 | None | Hardware | High complexity | 56 | Limited; standard implementation and verification risk. | Internal baseline decision recorded. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Complete internal review of wording and baseline scope. |
| 4.1 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 4.2 | SSR-SYS-001 | System | High complexity | 9 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| 4.3 | SSR-SYS-001 | System | Medium complexity | 21 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| 4.5 | None | Interface | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 4.6 | SSR-COM-004 | IT / backend | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| 4.7 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| 4.8 | SSR-SYS-001 | System | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| 53612101 | SSR-SYS-001 | System | Medium complexity | 19 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| RFQX-3299216-1-0028 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| 4.9 | SSR-SYS-001 | System | Medium complexity | 19 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| 4.10 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| 4.11 | SSR-DAI-002 | Interface | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | External Interfaces | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| 4.12 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| 4.13 | SSR-COM-004 | IT / backend | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| 4.14 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| 4.15 | SSR-TOOL-001 | Tooling | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| 4.16 | SSR-DAI-003 | IT / backend | High complexity | 8 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RFQX-3299216-1-0037 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0038 | None | IT / backend | High complexity | 56 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| 4.17 | SSR-TOOL-002 | IT / backend | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| 4.18 | SSR-TOOL-002 | IT / backend | High complexity | 19 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| 4.19 | SSR-COM-005 | Hardware | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Medium | ESTIMATED | Define and code | Agree responsibility split (DIA) for the non-ECU portion. |
| 4.20 | SSR-COM-005 | Hardware | High complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| 4.21 | SSR-TOOL-002 | IT / backend | High complexity | 16 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| RFQX-3299216-1-0044 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0045 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| 4.22 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 4.23 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| 4.24 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 4.25 | SSR-TOOL-002 | IT / backend | High complexity | 16 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| RFQX-3299216-1-0050 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0051 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| REQ 5.10 | SSR-TOOL-002 | IT / backend | High complexity | 16 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| REQ 6.4 | None | IT / backend | High complexity | 19 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-3299216-1-0054 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| REQ 6.4 | SSR-TOOL-002 | IT / backend | High complexity | 19 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| RFQX-3299216-1-0056 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| 5.3 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| 5.4 | SSR-TOOL-002 | IT / backend | High complexity | 16 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| 5.5 | SSR-HW-001 | Hardware | High complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| 5.6 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| 5.7 | SSR-COM-006 | Software | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| 5.9 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| RFQX-3299216-1-0063 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0064 | None | System | High complexity | 56 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0065 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0066 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0067 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0068 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0069 | None | System | Low complexity | 8 | Limited; standard implementation and verification risk. | Internal baseline decision recorded. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Complete internal review of wording and baseline scope. |
| REQ 5.1 | SSR-SYS-002 | Process / compliance | Medium complexity | 19 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| 5.11 | SSR-SYS-001 | System | Medium complexity | 19 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| RFQX-3299216-1-0072 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0073 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| REQ 8.1 | SSR-SYS-001 | System | Medium complexity | 19 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| 5.14 | SSR-SYS-003 | Software | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| RFQX-3299216-1-0076 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0077 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0078 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| 6.2 | SSR-DAI-003 | IT / backend | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| 6.3 | None | Interface | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-3299216-1-0081 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0082 | None | IT / backend | High complexity | 56 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| 6.3.1 | SSR-COM-005 | Hardware | High complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| 6.3.2 | SSR-COM-007 | Interface | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | External Interfaces | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| RFQX-3299216-1-0085 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0086 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0087 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| 6.4 | SSR-COM-004 | IT / backend | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| 6.5.2 | SSR-SYS-001 | System | High complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| RFQX-3299216-1-0090 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-008; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm production/debug hardening expectations (debug lock, secure end-of-line, developer-access policy). |
| RFQX-3299216-1-0091 | None | Interface | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-008; External Interfaces | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm production/debug hardening expectations (debug lock, secure end-of-line, developer-access policy). |
| RFQX-3299216-1-0092 | None | Interface | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; External Interfaces | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0093 | None | IT / backend | High complexity | 56 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0094 | None | Interface | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; External Interfaces | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| REQ 6.3 | None | Interface | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-3299216-1-0096 | None | Interface | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; External Interfaces | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0097 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| 6.6 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 6.7 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 6.8 | None | Interface | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 6.9 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| 6.10 | SSR-COM-007 | Interface | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | External Interfaces; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| 6.11 | SSR-COM-007 | Interface | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | External Interfaces; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| 6.12 | SSR-COM-007 | Interface | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | External Interfaces; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| 6.14 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| RFQX-3299216-1-0106 | None | Interface | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; External Interfaces | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| REQ 6.20 | SSR-RBAC-001 | Cybersecurity | High complexity | 24 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | None | Unverified security control could leave a residual risk in the cybersecurity case. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ 6.22 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-3299216-1-0109 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| 6.14.2 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| 6.14.3 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| 6.14.4 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| 6.14.5 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| 6.14.6 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| 6.14.8 | SSR-SYS-001 | System | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| 6.14.9 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| RFQX-3299216-1-0117 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0118 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| 6.15 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| 6.16 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| 6.17 | SSR-SYS-001 | System | High complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| 6.18 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| 6.19.1 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| 6.19.2 | SSR-SYS-001 | System | High complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| 6.20 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| 6.21 | SSR-RBAC-001 | Cybersecurity | High complexity | 24 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | None | Unverified security control could leave a residual risk in the cybersecurity case. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| 6.22 | None | Cybersecurity | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 6.22.1 | None | System | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 6.22.2 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 6.22.3 | None | System | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-3299216-1-0131 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0132 | None | System | High complexity | 56 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| 6.23 | SSR-VV-001 | System | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| 6.24 | SSR-DIAG-001 | Interface | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | External Interfaces; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| 6.25 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| 6.26 | SSR-COM-008 | Software | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| 6.27 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| 6.28 | SSR-SYS-003 | Software | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| RFQX-3299216-1-0140 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0141 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-3299216-1-0142 | None | Software | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| 7.1 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| 7.3 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| 7.4 | SSR-HW-001 | Hardware | High complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| 7.5 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| 7.6 | None | Hardware | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-3299216-1-0148 | None | Hardware | High complexity | 56 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0149 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0150 | None | Hardware | High complexity | 56 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| 7.10 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 7.11 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 7.12 | SSR-COM-007 | Interface | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | External Interfaces | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| 7.13 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| 7.15 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 7.16 | None | Process / compliance | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 7.17 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 7.18 | None | Software | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 7.20 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-3299216-1-0160 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0161 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0162 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0163 | None | IT / backend | High complexity | 56 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0164 | None | Interface | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; External Interfaces | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0165 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0166 | None | Interface | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; External Interfaces | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0167 | None | Interface | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; External Interfaces | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0168 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0169 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0170 | None | Interface | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; External Interfaces | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| 7.34 | SSR-COM-007 | Interface | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | External Interfaces | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| 7.35 | SSR-COM-007 | Interface | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | External Interfaces | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| 7.38 | None | Interface | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-3299216-1-0174 | None | Interface | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; External Interfaces | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0175 | None | Interface | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; External Interfaces | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0176 | None | System | High complexity | 56 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-004; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm the update chain ownership (backend/campaign vs. ECU programming) and the authenticity/integrity scheme to be applied. |
| 7.39 | SSR-COM-007 | Interface | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | External Interfaces; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| 7.40 | SSR-COM-007 | Interface | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | External Interfaces | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| RFQX-3299216-1-0179 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0180 | None | Interface | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; External Interfaces | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| 7.45 | SSR-TOOL-002 | IT / backend | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RFQX-3299216-1-0182 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0183 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0184 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0185 | None | Process / compliance | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0186 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0187 | None | Interface | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; External Interfaces | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0188 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0189 | None | Process / compliance | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0190 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0191 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0192 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0193 | None | IT / backend | High complexity | 56 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0194 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0195 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0196 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| 8.2 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 8.3 | SSR-SYS-001 | System | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| 8.5 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| 8.8 | SSR-LIFE-002 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| 8.9 | SSR-TOOL-002 | IT / backend | High complexity | 16 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| RFQX-3299216-1-0202 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0203 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0204 | None | Hardware | High complexity | 56 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0205 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0206 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| 9.1 | SSR-SYS-001 | System | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| 9.2 | SSR-SYS-001 | System | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| RFQX-3299216-1-0209 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0210 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0211 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0212 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| 10.1 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| 10.2 | SSR-SYS-003 | Software | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| RFQX-3299216-1-0215 | None | Interface | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; External Interfaces | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0216 | None | Hardware | High complexity | 56 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0217 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| 10.4 | SSR-SYS-003 | Software | Medium complexity | 19 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| RFQX-3299216-1-0219 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0220 | None | Software | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0221 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0222 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.5.11 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.5.12 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.5.13 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.5.14 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.5.15 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.5.16 | SSR-SYS-001 | System | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| 10.5.17 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.5.18 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.5.19 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.5.20 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.5.21 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.5.22 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.5.23 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.5.24 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.5.25 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.5.26 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.5.27 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.5.28 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.5.29 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.5.30 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.5.31 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.5.32 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.5.33 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| 10.5.34 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.5.35 | None | Software | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.5.36 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.6 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.6.1 | None | Hardware | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.6.2 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.6.3 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.6.4 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.6.5 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.6.6 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-3299216-1-0256 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| 10.7.14 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.7.15 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.7.16 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.7.17 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.7.18 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.7.19 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.7.20 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.7.21 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.7.22 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.7.23 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.7.24 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.7.25 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.7.26 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.7.27 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.7.28 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.7.29 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.7.30 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.7.31 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.7.32 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.7.33 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.7.34 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 10.7.35 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-3299216-1-0279 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0280 | None | Process / compliance | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0281 | None | Process / compliance | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0282 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0283 | None | Process / compliance | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| 12.2 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 12.3 | SSR-SYS-003 | Software | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| RFQX-3299216-1-0286 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0287 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0288 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0289 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0290 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0291 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0292 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0293 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0294 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0295 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0296 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0297 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0298 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0299 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0300 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-3299216-1-0301 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-3299216-1-0302 | None | Interface | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; External Interfaces | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| REQ 5.1 | None | System | Medium complexity | 19 | Limited; standard implementation and verification risk. | Internal baseline decision recorded. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Complete internal review of wording and baseline scope. |
| RFQX-3299216-1-0304 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Internal baseline decision recorded. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Complete internal review of wording and baseline scope. |
| RFQX-3299216-1-0305 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Internal baseline decision recorded. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Complete internal review of wording and baseline scope. |
| RFQX-3299216-1-0306 | None | Software | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-009; None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm the DIA / responsibility (RASIC/CIA) split for each cybersecurity work product before supplier scope is fixed. |
| 18850001 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 20000002 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-3299216-1-0309 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-CVS123-2-0001 | None | Software | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No supplier action - document reference / boilerplate. |
| RFQX-CVS123-2-0002 | None | Process / compliance | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-009; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm the DIA / responsibility (RASIC/CIA) split for each cybersecurity work product before supplier scope is fixed. |
| RFQX-CVS123-2-0003 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| SUV2_INFO 1 | None | Software | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 2 | None | Software | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 3 | None | Hardware | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 4 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 5 | None | Software | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 6 | None | Cybersecurity | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 7 | None | Cybersecurity | High complexity | 56 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer confirms it is binding. | None | Unverified security control could leave a residual risk in the cybersecurity case. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 8 | None | IT / backend | High complexity | 56 | Limited; standard implementation and verification risk. | Customer confirms it is binding. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 9 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-CVS123-2-0013 | None | Software | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-CVS123-2-0014 | None | IT / backend | High complexity | 56 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| SUV2_INFO 10 | None | Hardware | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 11 | None | Hardware | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 12 | None | Cybersecurity | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 13 | None | Process / compliance | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-CVS123-2-0019 | None | Software | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-001; None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm the exact ECU designation/variant and the agreed item definition and boundary used for the risk analysis (TARA). |
| RFQX-CVS123-2-0020 | None | Software | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-CVS123-2-0021 | None | Software | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-CVS123-2-0022 | None | Software | High complexity | 56 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-CVS123-2-0023 | None | Cybersecurity | High complexity | 56 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | OP-002; None | Unverified security control could leave a residual risk in the cybersecurity case. | Medium | ESTIMATED | Define and code | Confirm the diagnostic role model, the authorized services per role, and which party owns the diagnostic authorization policy. |
| RFQX-CVS123-2-0024 | None | Software | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-CVS123-2-0025 | None | Software | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0051 | None | System | Medium complexity | 32 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-CVS123-2-0027 | None | Software | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0051 | None | System | Medium complexity | 21 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-CVS123-2-0029 | None | Software | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-CVS123-2-0030 | None | Hardware | High complexity | 56 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-004; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm the update chain ownership (backend/campaign vs. ECU programming) and the authenticity/integrity scheme to be applied. |
| RFQX-CVS123-2-0031 | None | Cybersecurity | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 15 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 16 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 1 | SSR-RBAC-001 | Cybersecurity | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RFQX-CVS123-2-0035 | None | Software | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| SUV2_REQ 2 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 3 | SSR-BOOT-001 | Software | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| SUV2_REQ 4 | None | System | Low complexity | 5 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 3 | SSR-BOOT-002 | Hardware | High complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| RFQX-CVS123-2-0040 | None | Software | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-CVS123-2-0041 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| SUV2_REQ 5 | SSR-UPD-001 | Software | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_REQ 6 | SSR-UPD-002 | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SUV2_REQ 7 | SSR-BOOT-003 | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| SUV2_INFO 17 | None | Hardware | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 8 | SSR-DIAG-002 | IT / backend | High complexity | 16 | Responsibility gap 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 Interface | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_REQ 9 | SSR-RBAC-001 | Cybersecurity | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_REQ 10 | SSR-UPD-001 | Software | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| SUV2_REQ 11 | SSR-UPD-001 | Software | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| SUV2_REQ 12 | SSR-UPD-001 | Software | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Medium | ESTIMATED | Define and code | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_REQ 13 | SSR-SYS-001 | System | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| SUV2_REQ 14 | SSR-RBAC-001 | Cybersecurity | High complexity | 24 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | None | Unverified security control could leave a residual risk in the cybersecurity case. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| RFQX-CVS123-2-0053 | None | Software | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| SUV2_INFO 18 | None | Software | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-CVS123-2-0055 | SSR-BOOT-004 | IT / backend | High complexity | 56 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_REQ 15 | SSR-RBAC-001 | Cybersecurity | High complexity | 24 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | None | Unverified security control could leave a residual risk in the cybersecurity case. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| SUV2_INFO 19 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 16 | SSR-SYS-003 | Software | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 17 | SSR-SYS-003 | Software | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 18 | None | Software | Low complexity | 16 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 19 | SSR-DAI-004 | Software | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_REQ 20 | SSR-UPD-002 | System | High complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| SUV2_INFO 20 | None | Hardware | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 182 | SSR-UPD-002 | System | High complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| SUV2_INFO 129 | None | Interface | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms it is binding. | External Interfaces; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 21 | SSR-SYS-003 | Software | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| SUV2_INFO 130 | None | Software | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms it is binding. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 22 | SSR-SYS-003 | Software | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| RFQX-CVS123-2-0069 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| SUV2_REQ 23 | SSR-UPD-002 | System | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_REQ 24 | SSR-UPD-002 | System | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_REQ 25 | SSR-BOOT-001 | Software | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| SUV2_INFO 21 | None | Software | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 22 | None | Software | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-CVS123-2-0075 | None | Software | High complexity | 56 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| SUV2_INFO 23 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 24 | None | Software | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 26 | SSR-RBAC-002 | Cybersecurity | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_REQ 27 | SSR-RBAC-002 | Cybersecurity | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_INFO 25 | None | Software | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 26 | None | Software | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 27 | None | Software | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 28 | None | Software | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 29 | None | Software | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 30 | None | Interface | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 31 | None | Cybersecurity | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 32 | None | Software | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 33 | None | Software | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 34 | None | Cybersecurity | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 35 | None | Cybersecurity | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 36 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 37 | None | Software | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 38 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 39 | None | IT / backend | High complexity | 56 | Limited; standard implementation and verification risk. | Customer confirms it is binding. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-CVS123-2-0095 | None | Software | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 40 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 41 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 42 | None | Cybersecurity | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 43 | None | Software | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 44 | None | Software | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 45 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 46 | None | Cybersecurity | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 47 | None | Cybersecurity | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 48 | None | Software | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 49 | None | Software | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 50 | None | Software | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 51 | None | Hardware | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 52 | None | Software | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 53 | None | Software | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 28 | SSR-DAI-004 | Software | High complexity | 19 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_INFO 54 | None | Cybersecurity | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 29 | SSR-TOOL-002 | IT / backend | High complexity | 29 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_INFO 55 | None | Cybersecurity | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 30 | SSR-SDT-001 | Software | High complexity | 19 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_INFO 56 | None | Cybersecurity | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 57 | None | Cybersecurity | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 58 | None | Software | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 59 | None | Software | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 60 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 61 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 62 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 63 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 64 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 65 | None | Software | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 66 | None | Software | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0051 | None | IT / backend | High complexity | 32 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 67 | None | Hardware | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 68 | None | Software | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 69 | None | Software | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 70 | None | Software | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 71 | None | Software | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 72 | None | Software | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 73 | None | Software | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 74 | None | Hardware | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 75 | None | Software | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 76 | None | Software | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 77 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 99 | None | IT / backend | High complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 78 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 79 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 119 | None | Software | High complexity | 5 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 80 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 126 | None | Software | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 81 | None | Software | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 82 | None | Hardware | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 87 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 88 | None | Software | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 89 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 90 | None | Software | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 91 | None | Software | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 92 | None | Software | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 93 | None | Software | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms it is binding. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-CVS123-2-0153 | None | Hardware | High complexity | 56 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| SUV2_INFO 94 | None | Software | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms it is binding. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 95 | None | Software | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 96 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 97 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 27 | None | System | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 83 | None | Software | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 84 | None | Software | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 85 | None | Software | High complexity | 56 | Limited; standard implementation and verification risk. | Customer confirms it is binding. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 86 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 99 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 33 | SSR-UPD-003 | IT / backend | High complexity | 24 | Responsibility gap 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 Interface | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_REQ 34 | SSR-UPD-004 | Hardware | High complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| SUV2_REQ 35 | SSR-RBAC-001 | Cybersecurity | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_REQ 36 | SSR-TOOL-003 | Software | High complexity | 16 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 37 | SSR-SYS-003 | Software | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 38 | SSR-TOOL-002 | IT / backend | High complexity | 24 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_INFO 100 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 39 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 62 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 63 | SSR-COM-002 | System | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SUV2_INFO 101 | None | Hardware | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 40 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 41 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 42 | SSR-SYS-003 | Software | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 43 | SSR-UPD-001 | Software | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| SUV2_REQ 44 | SSR-BOOT-005 | Software | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| SUV2_INFO 102 | None | Software | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 45 | SSR-SYS-003 | Software | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| RFQX-CVS123-2-0182 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-CVS123-2-0183 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| SUV2_REQ 46 | SSR-UPD-001 | Software | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SUV2_REQ 47 | SSR-UPD-002 | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| SUV2_REQ 48 | SSR-TOOL-002 | IT / backend | High complexity | 16 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 49 | SSR-UPD-003 | IT / backend | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_REQ 50 | SSR-UPD-001 | Software | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RFQX-CVS123-2-0189 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| SUV2_REQ 51 | SSR-TOOL-003 | Software | High complexity | 16 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_INFO 103 | None | Cybersecurity | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 52 | SSR-RBAC-001 | Cybersecurity | High complexity | 26 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | None | Unverified security control could leave a residual risk in the cybersecurity case. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| SUV2_REQ 53 | SSR-SYS-001 | System | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SUV2_REQ 54 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 104 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 55 | SSR-CON-002 | Cybersecurity | High complexity | 26 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | None | Unverified security control could leave a residual risk in the cybersecurity case. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SUV2_REQ 62 | SSR-UPD-001 | Software | High complexity | 26 | Responsibility gap 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 Interface | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_INFO 106 | None | Software | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms it is binding. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 63 | SSR-UPD-001 | Software | High complexity | 26 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Medium | ESTIMATED | Define and code | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_REQ 64 | SSR-TOOL-002 | IT / backend | High complexity | 18 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 65 | SSR-CON-002 | Cybersecurity | High complexity | 26 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_INFO 107 | None | Hardware | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 66 | SSR-TOOL-003 | Software | High complexity | 18 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_REQ 67 | SSR-SDT-001 | Software | High complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| SUV2_REQ 68 | SSR-TOOL-003 | Software | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RFQX-CVS123-2-0206 | None | Software | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-004; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm the update chain ownership (backend/campaign vs. ECU programming) and the authenticity/integrity scheme to be applied. |
| SUV2_REQ 69 | SSR-VV-002 | IT / backend | High complexity | 16 | Responsibility gap 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 Interface | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_INFO 108 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 71 | SSR-TOOL-002 | IT / backend | High complexity | 18 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_INFO 109 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 190 | SSR-COM-006 | Software | High complexity | 18 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_INFO 150 | None | Software | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 72 | SSR-TOOL-003 | Software | High complexity | 18 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_REQ 73 | SSR-TOOL-003 | Software | High complexity | 18 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_REQ 74 | SSR-TOOL-003 | Software | High complexity | 18 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_REQ 165 | SSR-VV-003 | Software | High complexity | 18 | Responsibility gap 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 Interface | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_REQ 166 | SSR-VV-003 | Software | High complexity | 18 | Responsibility gap 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 Interface | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_REQ 167 | SSR-TOOL-003 | Software | High complexity | 18 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_INFO 137 | None | Software | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 75 | SSR-TOOL-002 | IT / backend | High complexity | 18 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 80 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 76 | SSR-TOOL-002 | IT / backend | High complexity | 18 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 77 | SSR-TOOL-003 | Software | High complexity | 18 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_REQ 78 | SSR-TOOL-003 | Software | High complexity | 18 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_REQ 79 | SSR-TOOL-002 | IT / backend | High complexity | 18 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 81 | SSR-TOOL-002 | IT / backend | High complexity | 18 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 82 | SSR-TOOL-003 | Software | High complexity | 18 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_REQ 83 | SSR-TOOL-002 | IT / backend | High complexity | 18 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 84 | SSR-TOOL-003 | Software | High complexity | 18 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_REQ 85 | SSR-TOOL-003 | Software | High complexity | 18 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_REQ 86 | None | Software | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 87 | SSR-TOOL-002 | IT / backend | High complexity | 18 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 88 | SSR-TOOL-002 | IT / backend | High complexity | 18 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 89 | SSR-TOOL-003 | Software | High complexity | 18 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_REQ 90 | SSR-TOOL-002 | IT / backend | High complexity | 18 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 92 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 91 | SSR-TOOL-002 | IT / backend | High complexity | 16 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 93 | SSR-TOOL-002 | IT / backend | High complexity | 16 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 94 | SSR-TOOL-003 | Software | High complexity | 18 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_REQ 95 | SSR-DAI-003 | IT / backend | High complexity | 18 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_REQ 96 | SSR-COM-009 | IT / backend | High complexity | 18 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 97 | SSR-RBAC-001 | Cybersecurity | High complexity | 26 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_REQ 98 | SSR-CON-002 | Cybersecurity | High complexity | 26 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_REQ 181 | SSR-RBAC-002 | Cybersecurity | High complexity | 26 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_INFO 110 | None | Hardware | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 99 | SSR-DAI-004 | Software | High complexity | 18 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_REQ 100 | SSR-SDT-001 | Software | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SUV2_REQ 101 | None | IT / backend | High complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 111 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 102 | SSR-TOOL-002 | IT / backend | High complexity | 18 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 103 | SSR-DIAG-002 | IT / backend | High complexity | 18 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 104 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 114 | None | Hardware | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 105 | SSR-TOOL-002 | IT / backend | High complexity | 18 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_INFO 112 | None | Hardware | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 106 | SSR-TOOL-003 | Software | High complexity | 18 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_INFO 113 | None | Hardware | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 107 | SSR-BOOT-002 | Hardware | High complexity | 26 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| SUV2_REQ 4 | None | Hardware | High complexity | 26 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 108 | SSR-TOOL-003 | Software | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_REQ 109 | SSR-SDT-001 | Software | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SUV2_REQ 110 | SSR-TOOL-002 | IT / backend | High complexity | 18 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 111 | SSR-TOOL-002 | IT / backend | High complexity | 18 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 112 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 113 | SSR-TOOL-002 | IT / backend | High complexity | 18 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 62 | SSR-SYS-003 | Software | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 63 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 114 | SSR-SYS-001 | System | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 115 | SSR-TOOL-003 | Software | High complexity | 26 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_INFO 115 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 143 | SSR-UPD-002 | System | Medium complexity | 26 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SUV2_INFO 124 | None | Software | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 116 | SSR-TOOL-002 | IT / backend | High complexity | 18 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| RFQX-CVS123-2-0274 | None | Software | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-001; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm the exact ECU designation/variant and the agreed item definition and boundary used for the risk analysis (TARA). |
| SUV2_REQ 117 | SSR-SYS-001 | System | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| SUV2_REQ 118 | SSR-TOOL-002 | IT / backend | High complexity | 18 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 119 | SSR-DAI-004 | Software | High complexity | 18 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_REQ 120 | SSR-DAI-004 | Software | High complexity | 26 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_REQ 121 | SSR-DAI-003 | IT / backend | High complexity | 18 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_INFO 140 | None | Interface | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 122 | SSR-TOOL-002 | IT / backend | High complexity | 18 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 123 | SSR-TOOL-002 | IT / backend | High complexity | 18 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 124 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 125 | SSR-TOOL-002 | IT / backend | High complexity | 18 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 126 | SSR-DAI-005 | Software | High complexity | 18 | Responsibility gap 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 Interface | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RFQX-CVS123-2-0286 | None | Cybersecurity | High complexity | 56 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm the diagnostic role model, the authorized services per role, and which party owns the diagnostic authorization policy. |
| SUV2_REQ 146 | None | Hardware | High complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 151 | None | Software | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 169 | None | Software | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 170 | None | Software | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 128 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 171 | SSR-TOOL-002 | IT / backend | High complexity | 16 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_INFO 138 | None | Interface | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 172 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 173 | SSR-TOOL-002 | IT / backend | High complexity | 29 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_INFO 139 | None | System | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 174 | SSR-DAI-003 | IT / backend | High complexity | 8 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_REQ 175 | SSR-TOOL-002 | IT / backend | High complexity | 16 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 183 | SSR-UPD-001 | Software | High complexity | 29 | Responsibility gap 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 Interface | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_REQ 128 | None | Interface | Medium complexity | 19 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 141 | None | Software | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 176 | SSR-TOOL-002 | IT / backend | High complexity | 19 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 177 | SSR-RBAC-001 | Cybersecurity | High complexity | 29 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_REQ 178 | None | Software | Medium complexity | 21 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 179 | None | Software | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 180 | None | Software | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 131 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 129 | SSR-TOOL-002 | IT / backend | High complexity | 18 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 130 | SSR-TOOL-002 | IT / backend | High complexity | 18 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_REQ 132 | SSR-TOOL-002 | IT / backend | High complexity | 18 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 133 | SSR-TOOL-002 | IT / backend | High complexity | 18 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_INFO 117 | None | Cybersecurity | High complexity | 56 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer confirms it is binding. | OEM/Customer Review Interface | Unverified security control could leave a residual risk in the cybersecurity case. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 134 | SSR-TOOL-002 | IT / backend | High complexity | 16 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_INFO 119 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 120 | None | Hardware | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 184 | SSR-HW-001 | Hardware | High complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 185 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| SUV2_INFO 138 | None | Software | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 161 | SSR-SYS-003 | Software | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| SUV2_REQ 168 | SSR-SYS-002 | Process / compliance | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_INFO 135 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-CVS123-2-0322 | None | Software | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| SUV2_REQ 135 | SSR-TOOL-002 | IT / backend | High complexity | 16 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_INFO 121 | None | Software | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 138 | SSR-TOOL-002 | IT / backend | High complexity | 16 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 152 | SSR-VV-003 | Software | High complexity | 16 | Responsibility gap 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 Interface | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_INFO 125 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 153 | SSR-TOOL-003 | Software | High complexity | 19 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 154 | SSR-TOOL-002 | IT / backend | High complexity | 19 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_INFO 126 | None | Hardware | High complexity | 56 | Limited; standard implementation and verification risk. | Customer confirms it is binding. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 155 | SSR-SYS-003 | Software | Medium complexity | 19 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| SUV2_INFO 127 | None | Hardware | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 156 | SSR-UPD-001 | Software | High complexity | 29 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| SUV2_REQ 157 | SSR-HW-001 | Hardware | High complexity | 19 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_REQ 158 | SSR-VV-002 | IT / backend | High complexity | 19 | Responsibility gap 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 Interface | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_REQ 159 | SSR-TOOL-003 | Software | High complexity | 16 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 160 | SSR-DAI-004 | Software | High complexity | 8 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SUV2_INFO 131 | None | Software | High complexity | 56 | Limited; standard implementation and verification risk. | Customer confirms it is binding. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 147 | SSR-TOOL-003 | Software | High complexity | 16 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 148 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 149 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 150 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| RFQX-CVS123-2-0343 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| SUV2_INFO 134 | None | Software | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 133 | None | Software | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_INFO 132 | None | Hardware | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 00868000 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 00930000 | None | Hardware | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-CVS123-2-0349 | None | Hardware | High complexity | 56 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-004; None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm the update chain ownership (backend/campaign vs. ECU programming) and the authenticity/integrity scheme to be applied. |
| 00930000 | SSR-SDT-002 | Hardware | High complexity | 19 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Medium | ESTIMATED | Define and code | Agree responsibility split (DIA) for the non-ECU portion. |
| RFQX-CVS123-2-0351 | None | IT / backend | High complexity | 56 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Medium | ESTIMATED | Define and code | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-CVS124-0001 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-CVS124-0002 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No supplier action - document reference / boilerplate. |
| RFQX-CVS124-0003 | None | Process / compliance | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-009; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm the DIA / responsibility (RASIC/CIA) split for each cybersecurity work product before supplier scope is fixed. |
| RFQX-CVS124-0004 | None | IT / backend | High complexity | 56 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| 4.1 | None | IT / backend | High complexity | 18 | Limited; standard implementation and verification risk. | Internal review confirms wording and scope. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Complete internal review of wording and baseline scope. |
| 4.2 | None | Cybersecurity | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No supplier action - document reference / boilerplate. |
| RFQX-CVS124-0007 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-CVS124-0008 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-CVS124-0009 | None | System | Low complexity | 8 | Limited; standard implementation and verification risk. | Internal baseline decision recorded. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Complete internal review of wording and baseline scope. |
| RFQX-CVS124-0010 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-CVS124-0011 | None | IT / backend | High complexity | 56 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-CVS124-0012 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-CVS124-0013 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| 4.3 | SSR-BOOT-001 | Software | High complexity | 32 | Responsibility gap 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 Interface | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Medium | ESTIMATED | Define and code | Agree responsibility split (DIA) for the non-ECU portion. |
| RFQX-CVS124-0015 | None | System | Low complexity | 8 | Limited; standard implementation and verification risk. | Internal baseline decision recorded. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Complete internal review of wording and baseline scope. |
| RFQX-CVS124-0016 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-CVS124-0017 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| REQ_UDS_0001 | SSR-TOOL-002 | IT / backend | High complexity | 18 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| REQ_UDS_0002 | SSR-SYS-001 | System | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0003 | None | Software | High complexity | 26 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| INFO_UDS_0001 | None | Interface | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| INFO_UDS_0002 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0004 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0005 | SSR-UPD-004 | Hardware | High complexity | 26 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0006 | None | Software | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0231 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0007 | None | Software | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0232 | SSR-UPD-004 | Hardware | High complexity | 26 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0008 | None | Cybersecurity | High complexity | 26 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0009 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0233 | SSR-UPD-004 | Hardware | High complexity | 26 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0010 | None | Software | High complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0234 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0011 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0235 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0012 | SSR-SYS-001 | System | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0013 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0014 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-CVS124-0039 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| REQ_UDS_0015 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| INFO_UDS_0003 | None | Software | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0016 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0236 | SSR-UPD-004 | Hardware | High complexity | 26 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0017 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0018 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0019 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0237 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0020 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0021 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0022 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| INFO_UDS_0039 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms it is binding. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0339 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0340 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0341 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0023 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0025 | None | Hardware | High complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0026 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0027 | SSR-HW-001 | Hardware | High complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0028 | None | Software | High complexity | 26 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0029 | SSR-UPD-001 | Software | High complexity | 26 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0030 | None | Software | High complexity | 26 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| INFO_UDS_0004 | None | Software | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0032 | None | Software | High complexity | 26 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0033 | None | Software | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0034 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| INFO_UDS_0005 | None | Cybersecurity | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| INFO_UDS_0040 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0036 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| INFO_UDS_0006 | None | Interface | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0037 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| INFO_UDS_0007 | None | Interface | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0038 | None | System | High complexity | 26 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0039 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0238 | SSR-UPD-004 | Hardware | High complexity | 26 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0040 | SSR-RBAC-001 | Cybersecurity | High complexity | 26 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | None | Unverified security control could leave a residual risk in the cybersecurity case. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0041 | None | Cybersecurity | High complexity | 26 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0042 | SSR-RBAC-001 | Cybersecurity | High complexity | 26 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | None | Unverified security control could leave a residual risk in the cybersecurity case. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0043 | SSR-RBAC-001 | Cybersecurity | High complexity | 26 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Unverified security control could leave a residual risk in the cybersecurity case. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0044 | SSR-SYS-003 | Software | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0045 | None | Cybersecurity | High complexity | 26 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| INFO_UDS_0038 | None | Software | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms it is binding. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0046 | SSR-SYS-003 | Software | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0047 | SSR-RBAC-003 | IT / backend | High complexity | 18 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| REQ_UDS_0048 | SSR-RBAC-004 | Software | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0049 | None | System | High complexity | 26 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| INFO_UDS_0008 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms it is binding. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0050 | SSR-DIAG-003 | System | High complexity | 26 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0051 | SSR-TOOL-002 | IT / backend | High complexity | 32 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| REQ_UDS_0338 | SSR-SYS-001 | System | Medium complexity | 19 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0305_1 | None | Software | High complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| INFO_UDS_0019 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0305 | None | System | Medium complexity | 19 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0337 | None | System | Medium complexity | 21 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0306_2 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0307_3 | None | Software | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0308_4 | None | IT / backend | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0309_5 | None | Software | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0310_6 | None | Software | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0311_7 | None | Software | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0312_8 | None | Software | High complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0313_9 | None | Software | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0314_10 | None | Software | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0315_11 | None | Software | High complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0306 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0316_12 | None | Software | Low complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0317_13 | None | System | Low complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0318_14 | None | IT / backend | High complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0319_15 | None | IT / backend | High complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0320_16 | None | Software | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0321_17 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0322_18 | None | Software | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0323_19 | None | IT / backend | High complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0324_20 | None | System | Low complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0325_21 | None | IT / backend | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0326_22 | None | Software | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0327_23 | None | Software | High complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0316 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0328_24 | None | Software | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0329_25 | None | Software | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0330_26 | None | Cybersecurity | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0331_27 | None | Cybersecurity | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0332_28 | None | Software | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0333_29 | None | Software | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0334_30 | None | Software | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0335_31 | None | Software | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0336_32 | None | Software | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0337_33 | None | Software | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0328 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0052 | SSR-SYS-002 | Process / compliance | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0053 | SSR-HW-001 | Hardware | High complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| INFO_UDS_0009 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0054 | SSR-SYS-001 | System | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0055 | SSR-SYS-002 | Process / compliance | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0056 | SSR-SYS-002 | Process / compliance | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0342 | SSR-RBAC-004 | Software | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0239 | None | System | High complexity | 26 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0057 | SSR-UPD-001 | Software | High complexity | 26 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| RFQX-CVS124-0138 | None | Software | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| REQ_UDS_0058 | None | Software | High complexity | 26 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0059 | SSR-UPD-001 | Software | Medium complexity | 26 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| RFQX-CVS124-0141 | None | IT / backend | High complexity | 56 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm the update chain ownership (backend/campaign vs. ECU programming) and the authenticity/integrity scheme to be applied. |
| REQ_UDS_0060 | SSR-UPD-003 | IT / backend | High complexity | 26 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RFQX-CVS124-0143 | None | Hardware | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0240 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0061 | SSR-UPD-002 | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0241 | SSR-DIAG-004 | Process / compliance | High complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0242 | SSR-SYS-002 | Process / compliance | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0243 | None | Software | Low complexity | 16 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0062 | SSR-COM-007 | Interface | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | External Interfaces | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0063 | SSR-SYS-003 | Software | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0064 | None | Cybersecurity | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0065 | SSR-HW-001 | Hardware | High complexity | 8 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| REQ_UDS_0066 | SSR-HW-001 | Hardware | High complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0067 | SSR-TOOL-002 | IT / backend | High complexity | 16 | Responsibility gap 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 Interface | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| REQ_UDS_0244 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0068 | None | Cybersecurity | High complexity | 26 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0069 | SSR-TOOL-003 | Software | High complexity | 18 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RFQX-CVS124-0158 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-CVS124-0159 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| REQ_UDS_0070 | SSR-KEY-001 | Cybersecurity | High complexity | 26 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | None | Unverified security control could leave a residual risk in the cybersecurity case. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0071 | SSR-TOOL-003 | Software | High complexity | 26 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| REQ_UDS_0072 | SSR-SYS-003 | Software | High complexity | 26 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| INFO_UDS_0010 | None | IT / backend | High complexity | 56 | Limited; standard implementation and verification risk. | Customer confirms it is binding. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0073 | None | Software | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0245 | SSR-SYS-002 | Process / compliance | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0246 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0074 | None | Software | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0075 | SSR-COM-006 | Software | High complexity | 18 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RFQX-CVS124-0169 | None | IT / backend | High complexity | 56 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| INFO_UDS_0011 | None | Software | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0076 | SSR-RBAC-001 | Cybersecurity | High complexity | 26 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| REQ_UDS_0077 | SSR-COM-002 | System | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| INFO_UDS_0012 | None | Software | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0248 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| INFO_UDS_0013 | None | Software | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms it is binding. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0078 | None | Software | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0079 | None | Software | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0080 | None | Software | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0247 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0081 | SSR-SYS-003 | Software | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| INFO_UDS_0014 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0249 | SSR-SYS-002 | Process / compliance | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0250 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0251 | None | Software | Low complexity | 16 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0343 | SSR-UPD-001 | Software | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| REQ_UDS_0344 | SSR-RBAC-001 | Cybersecurity | High complexity | 24 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | None | Unverified security control could leave a residual risk in the cybersecurity case. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0345 | None | Process / compliance | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0346 | None | Process / compliance | Low complexity | 16 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0347 | None | System | Low complexity | 16 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0348 | None | Process / compliance | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0349 | None | Process / compliance | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0082 | SSR-TOOL-003 | Software | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| REQ_UDS_0083 | SSR-BOOT-005 | Software | High complexity | 24 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| INFO_UDS_0015 | None | Software | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0084 | SSR-SYS-001 | System | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0254 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0085 | None | Software | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0086 | SSR-COM-006 | Software | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0252 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0253 | None | Software | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0087 | SSR-DIAG-005 | Hardware | High complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0255 | SSR-SYS-002 | Process / compliance | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0088 | SSR-DIAG-003 | System | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0259 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0256 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0257 | None | Software | Low complexity | 16 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0089 | SSR-DIAG-006 | Software | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0090 | None | IT / backend | High complexity | 16 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0091 | SSR-HW-001 | Hardware | High complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0092 | SSR-KEY-001 | Cybersecurity | High complexity | 24 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | None | Unverified security control could leave a residual risk in the cybersecurity case. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0093 | None | Hardware | High complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-CVS124-0212 | None | Software | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| REQ_UDS_0258 | SSR-SYS-002 | Process / compliance | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0260 | None | Software | High complexity | 26 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0261 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0262 | SSR-SYS-002 | Process / compliance | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0263 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0264 | None | Software | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0265 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0094 | None | Software | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0095 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0266 | SSR-SYS-002 | Process / compliance | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0267 | SSR-DIAG-004 | Process / compliance | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0096 | None | Software | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0097 | SSR-TOOL-002 | IT / backend | High complexity | 18 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| REQ_UDS_0268 | SSR-DIAG-004 | Process / compliance | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0098 | None | Software | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0269 | SSR-SYS-002 | Process / compliance | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0270 | SSR-DIAG-004 | Process / compliance | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0271 | SSR-DIAG-004 | Process / compliance | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0272 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0273 | SSR-DIAG-004 | Process / compliance | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0274 | SSR-DIAG-004 | Process / compliance | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0275 | SSR-DIAG-004 | Process / compliance | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0276 | SSR-DIAG-004 | Process / compliance | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0277 | SSR-DIAG-004 | Process / compliance | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| RFQX-CVS124-0237 | None | Software | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| REQ_UDS_0099 | SSR-DIAG-006 | Software | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| RFQX-CVS124-0239 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-CVS124-0240 | None | Hardware | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-CVS124-0241 | None | Interface | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; External Interfaces | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| REQ_UDS_0304 | SSR-DIAG-003 | System | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0100 | None | Software | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0101 | SSR-SYS-003 | Software | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| RFQX-CVS124-0245 | None | Software | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-CVS124-0246 | None | Hardware | High complexity | 56 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-001; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm the exact ECU designation/variant and the agreed item definition and boundary used for the risk analysis (TARA). |
| RFQX-CVS124-0247 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-CVS124-0248 | None | System | High complexity | 56 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm the update chain ownership (backend/campaign vs. ECU programming) and the authenticity/integrity scheme to be applied. |
| RFQX-CVS124-0249 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| REQ_UDS_0278 | SSR-SYS-002 | Process / compliance | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0279 | SSR-DIAG-004 | Process / compliance | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0280 | SSR-DIAG-004 | Process / compliance | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0281 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0282 | SSR-SYS-002 | Process / compliance | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0283 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0102 | SSR-DIAG-004 | Process / compliance | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0103 | None | Software | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0104 | None | Software | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0284 | SSR-SYS-002 | Process / compliance | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0285 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0286 | None | Software | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0287 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0105 | None | Software | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0106 | SSR-SYS-002 | Process / compliance | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| RFQX-CVS124-0265 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| REQ_UDS_0107 | None | Software | High complexity | 26 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0288 | SSR-SYS-002 | Process / compliance | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0289 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0290 | None | Software | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0108 | SSR-HW-001 | Hardware | High complexity | 18 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| INFO_UDS_0017 | None | Hardware | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0109 | SSR-TOOL-003 | Software | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| REQ_UDS_0110 | SSR-SDT-001 | Software | High complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0111 | SSR-TOOL-003 | Software | High complexity | 18 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| REQ_UDS_0112 | SSR-TOOL-003 | Software | High complexity | 18 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| REQ_UDS_0113 | None | Software | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0114 | None | Software | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0115 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0116 | None | Software | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0117 | None | Software | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0118 | None | Software | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0295 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0119 | None | Software | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0291 | SSR-SYS-002 | Process / compliance | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0292 | SSR-SYS-002 | Process / compliance | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0293 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0120 | None | Software | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0294 | SSR-SYS-002 | Process / compliance | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0296 | SSR-SYS-002 | Process / compliance | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0297 | SSR-SYS-002 | Process / compliance | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0298 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0299 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0300 | None | Software | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0121 | None | Software | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0122 | SSR-SYS-001 | System | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0123 | None | Software | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0124 | SSR-SYS-001 | System | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0301 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0302 | None | Software | Medium complexity | 16 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0125 | SSR-SYS-003 | Software | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0303 | None | Interface | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0126 | SSR-SYS-002 | Process / compliance | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0127 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0128 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0129 | SSR-RBAC-004 | Software | High complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0130 | SSR-RBAC-004 | Software | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| REQ_UDS_0133 | SSR-RBAC-004 | Software | High complexity | 26 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0134 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0135 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0136 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0137 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0138 | SSR-SYS-002 | Process / compliance | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0139 | SSR-SYS-003 | Software | High complexity | 26 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0140 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0141 | SSR-SYS-003 | Software | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| RFQX-CVS124-0316 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-CVS124-0317 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-CVS124-0318 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-CVS124-0319 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-CVS124-0320 | None | Hardware | High complexity | 56 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| REQ_UDS_0142 | SSR-SYS-003 | Software | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0143 | None | Software | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0144 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0145 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0146 | SSR-SYS-002 | Process / compliance | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| INFO_UDS_0018 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0147 | SSR-UPD-002 | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| RFQX-CVS124-0328 | None | System | Medium complexity | 24 | Responsibility gap 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 Interface | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm the DIA / responsibility (RASIC/CIA) split for each cybersecurity work product before supplier scope is fixed. |
| REQ_UDS_0148 | SSR-UPD-002 | System | Medium complexity | 26 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0149 | SSR-UPD-002 | System | Medium complexity | 26 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| RFQX-CVS124-0331 | None | Hardware | High complexity | 56 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| REQ_UDS_0150 | SSR-SYS-003 | Software | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0151 | SSR-SYS-001 | System | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0152 | SSR-SYS-001 | System | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0153 | None | System | Medium complexity | 26 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0154 | SSR-UPD-002 | System | Medium complexity | 26 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0155 | SSR-UPD-002 | System | Medium complexity | 26 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0156 | SSR-SYS-001 | System | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0157 | SSR-UPD-002 | System | Medium complexity | 26 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| RFQX-CVS124-0340 | None | Software | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-004; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm the update chain ownership (backend/campaign vs. ECU programming) and the authenticity/integrity scheme to be applied. |
| REQ_UDS_0158 | SSR-TOOL-003 | Software | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| INFO_UDS_0020 | None | Hardware | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0159 | SSR-BOOT-002 | Hardware | High complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| INFO_UDS_0021 | None | Hardware | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0160 | SSR-TOOL-003 | Software | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| REQ_UDS_0161 | SSR-SDT-001 | Software | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| RFQX-CVS124-0347 | None | Hardware | High complexity | 56 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| REQ_UDS_0162 | SSR-UPD-002 | System | Medium complexity | 26 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0163 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0164 | SSR-SYS-001 | System | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0165 | None | System | High complexity | 26 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SUV2_REQ 62 | SSR-SYS-003 | Software | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| SUV2_REQ 63 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0166 | SSR-BOOT-005 | Software | Medium complexity | 26 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0167 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0168 | SSR-SYS-001 | System | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| INFO_UDS_0022 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| INFO_UDS_0023 | None | Hardware | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| INFO_UDS_0024 | None | Hardware | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| INFO_UDS_0025 | None | Hardware | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0169 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0170 | SSR-DAI-006 | IT / backend | High complexity | 18 | Responsibility gap 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 Interface | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| INFO_UDS_0026 | None | Software | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0171 | SSR-TOOL-003 | Software | High complexity | 18 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| REQ_UDS_0172 | SSR-DAI-006 | IT / backend | High complexity | 18 | Responsibility gap 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 Interface | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| REQ_UDS_0173 | SSR-UPD-002 | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0174 | SSR-SYS-001 | System | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0175 | SSR-SYS-003 | Software | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0176 | SSR-DAI-007 | System | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0177 | SSR-DAI-005 | Software | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0178 | SSR-DAI-007 | System | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0179 | SSR-SYS-001 | System | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0180 | SSR-SYS-001 | System | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0181 | SSR-SYS-003 | Software | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| RFQX-CVS124-0375 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| REQ_UDS_0182 | SSR-SYS-001 | System | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| RFQX-CVS124-0377 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| INFO_UDS_0027 | None | Interface | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| INFO_UDS_0028 | None | Software | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms it is binding. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| INFO_UDS_0029 | None | IT / backend | High complexity | 56 | Limited; standard implementation and verification risk. | Customer confirms it is binding. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0183 | SSR-TOOL-002 | IT / backend | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RFQX-CVS124-0382 | None | Software | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-001; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm the exact ECU designation/variant and the agreed item definition and boundary used for the risk analysis (TARA). |
| REQ_UDS_0184 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0185 | SSR-TOOL-002 | IT / backend | High complexity | 18 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| REQ_UDS_0186 | SSR-DAI-004 | Software | High complexity | 18 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| REQ_UDS_0187 | SSR-DAI-004 | Software | High complexity | 26 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| REQ_UDS_0188 | SSR-DAI-003 | IT / backend | High complexity | 18 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| REQ_UDS_0189 | SSR-UPD-002 | System | Medium complexity | 26 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0190 | SSR-UPD-001 | Software | High complexity | 26 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| REQ_UDS_0191 | SSR-SYS-001 | System | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0192 | SSR-UPD-001 | Software | Medium complexity | 26 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0193 | SSR-UPD-002 | System | Medium complexity | 26 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| INFO_UDS_0030 | None | Software | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms it is binding. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| INFO_UDS_0031 | None | Software | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| INFO_UDS_0032 | None | Hardware | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| INFO_UDS_0033 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0194 | SSR-UPD-003 | IT / backend | High complexity | 26 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| REQ_UDS_0195 | SSR-SYS-003 | Software | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0196 | None | Hardware | High complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0197 | SSR-DIAG-003 | System | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| INFO_UDS_0034 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0198 | SSR-SYS-001 | System | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0199 | SSR-SYS-001 | System | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0200 | SSR-SYS-001 | System | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0201 | SSR-SYS-001 | System | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0202 | SSR-TOOL-002 | IT / backend | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| REQ_UDS_0203 | SSR-DIAG-003 | System | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0204 | SSR-DIAG-003 | System | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0205 | SSR-DIAG-003 | System | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0206 | SSR-SYS-001 | System | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| INFO_UDS_0035 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0207 | SSR-SYS-001 | System | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0208 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0209 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0210 | SSR-DIAG-003 | System | High complexity | 26 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0210 | SSR-DIAG-003 | System | High complexity | 26 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0211 | SSR-SYS-001 | System | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0212 | SSR-DIAG-003 | System | High complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| INFO_UDS_0036 | None | System | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0213 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0214 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0215 | None | System | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0216 | None | System | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0217 | None | System | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| INFO_UDS_0037 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0218 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0219 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0220 | None | System | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0221 | None | System | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0222 | None | System | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0223 | SSR-RBAC-001 | Cybersecurity | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| REQ_UDS_0224 | SSR-RBAC-001 | Cybersecurity | High complexity | 24 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | None | Unverified security control could leave a residual risk in the cybersecurity case. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| RFQX-CVS124-0433 | SSR-COM-004 | IT / backend | High complexity | 56 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| REQ_UDS_0225 | SSR-TOOL-004 | System | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| REQ_UDS_0226 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0227 | SSR-TOOL-002 | IT / backend | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| REQ_UDS_0228 | SSR-SYS-002 | Process / compliance | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| REQ_UDS_0229 | SSR-TOOL-004 | System | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| REQ_UDS_0230 | SSR-TOOL-004 | System | High complexity | 16 | Responsibility gap 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 Interface | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| INFO_UDS_0039 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0339 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0340 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0341 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0342 | None | System | Low complexity | 5 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0343 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0344 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0345 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0346 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0347 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0348 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0349 | None | System | Low complexity | 16 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0003 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0034 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| INFO_UDS_0040 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0036 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0037 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0045 | None | Software | Low complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0048 | None | System | High complexity | 26 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0107 | None | System | High complexity | 26 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0180 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0193 | None | System | High complexity | 26 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0045 | None | Software | Low complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0053 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0054 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| REQ_UDS_0024 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-CVS151-0001 | None | System | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No supplier action - document reference / boilerplate. |
| RFQX-CVS151-0002 | None | Process / compliance | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-009; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm the DIA / responsibility (RASIC/CIA) split for each cybersecurity work product before supplier scope is fixed. |
| RFQX-CVS151-0003 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-CVS151-0004 | None | Cybersecurity | High complexity | 56 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | OP-002; None | Unverified security control could leave a residual risk in the cybersecurity case. | Medium | ESTIMATED | Define and code | Confirm the diagnostic role model, the authorized services per role, and which party owns the diagnostic authorization policy. |
| RBAC_INFO 1 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RBAC_INFO 2 | None | Hardware | High complexity | 56 | Limited; standard implementation and verification risk. | Customer confirms it is binding. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RBAC_INFO 3 | None | Software | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RBAC_INFO 4 | None | Cybersecurity | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RBAC_INFO 5 | None | Software | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RBAC_INFO 6 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RBAC_REQ 1 | SSR-RBAC-005 | System | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| RBAC_INFO 7 | None | Cybersecurity | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RBAC_INFO 8 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RBAC_REQ 2 | SSR-TOOL-002 | IT / backend | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RBAC_INFO 9 | None | Interface | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RBAC_REQ 3 | SSR-TOOL-002 | IT / backend | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RBAC_INFO 46 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RBAC_REQ 4 | SSR-TOOL-002 | IT / backend | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RBAC_REQ 5 | SSR-RBAC-003 | IT / backend | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RBAC_INFO 10 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms it is binding. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RBAC_INFO 11 | None | Interface | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RBAC_INFO 12 | None | Cybersecurity | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RBAC_REQ 6 | SSR-TOOL-002 | IT / backend | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RBAC_INFO 13 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RBAC_INFO 14 | None | Interface | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RBAC_INFO 15 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RBAC_INFO 16 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RBAC_REQ 27 | SSR-TOOL-002 | IT / backend | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RBAC_INFO 41 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RBAC_REQ 7 | SSR-RBAC-003 | IT / backend | High complexity | 19 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RBAC_INFO 18 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RBAC_REQ 8 | SSR-TOOL-002 | IT / backend | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RBAC_REQ 9 | SSR-TOOL-002 | IT / backend | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RBAC_INFO 19 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms it is binding. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RBAC_REQ 10 | SSR-RBAC-003 | IT / backend | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RFQX-CVS151-0036 | None | IT / backend | High complexity | 56 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RBAC_REQ 11 | SSR-RBAC-003 | IT / backend | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RBAC_INFO 35 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RBAC_INFO 20 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RBAC_REQ 12 | SSR-RBAC-003 | IT / backend | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RBAC_REQ 13 | SSR-RBAC-003 | IT / backend | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RBAC_INFO 36 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RBAC_INFO 21 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RBAC_REQ 14 | SSR-TOOL-002 | IT / backend | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RBAC_REQ 15 | SSR-RBAC-001 | Cybersecurity | High complexity | 26 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RBAC_INFO 22 | None | Cybersecurity | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RBAC_INFO 23 | None | Cybersecurity | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RBAC_REQ 16 | SSR-TOOL-002 | IT / backend | High complexity | 18 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RFQX-CVS151-0049 | None | IT / backend | High complexity | 56 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm the diagnostic role model, the authorized services per role, and which party owns the diagnostic authorization policy. |
| RBAC_REQ 17 | SSR-TOOL-002 | IT / backend | High complexity | 18 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RBAC_REQ 18 | SSR-SYS-001 | System | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| RBAC_INFO 24 | None | Cybersecurity | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RBAC_REQ 19 | SSR-TOOL-002 | IT / backend | High complexity | 18 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RFQX-CVS151-0054 | None | IT / backend | High complexity | 56 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm the diagnostic role model, the authorized services per role, and which party owns the diagnostic authorization policy. |
| RBAC_REQ 20 | SSR-TOOL-002 | IT / backend | High complexity | 18 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RBAC_INFO 25 | None | Cybersecurity | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RBAC_REQ 21 | SSR-TOOL-002 | IT / backend | High complexity | 18 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RFQX-CVS151-0058 | None | IT / backend | High complexity | 56 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm the diagnostic role model, the authorized services per role, and which party owns the diagnostic authorization policy. |
| RBAC_INFO 26 | None | Cybersecurity | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RBAC_REQ 22 | SSR-KEY-001 | Cybersecurity | High complexity | 26 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RBAC_INFO 27 | None | Cybersecurity | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RBAC_REQ 23 | SSR-RBAC-003 | IT / backend | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RBAC_INFO 28 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RBAC_INFO 29 | None | Interface | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-CVS151-0065 | SSR-COM-004 | IT / backend | High complexity | 56 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RBAC_REQ 36 | SSR-KEY-001 | Cybersecurity | High complexity | 29 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RBAC_INFO 30 | None | Software | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RBAC_REQ 35 | SSR-RBAC-004 | Software | High complexity | 19 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RBAC_INFO 32 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RBAC_INFO 33 | None | Cybersecurity | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RBAC_REQ 32 | SSR-RBAC-004 | Software | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RBAC_INFO 34 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-CVS151-0073 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | No supplier action - document reference / boilerplate. |
| RBAC_REQ 33 | SSR-RBAC-003 | IT / backend | High complexity | 19 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RBAC_REQ 34 | SSR-RBAC-003 | IT / backend | High complexity | 19 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RBAC_INFO 37 | None | Software | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RBAC_INFO 38 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-CVS151-0078 | SSR-RBAC-005 | System | High complexity | 56 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| RBAC_REQ 24 | SSR-TOOL-002 | IT / backend | High complexity | 29 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RBAC_REQ 25 | SSR-TOOL-002 | IT / backend | High complexity | 19 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RBAC_REQ 26 | SSR-TOOL-002 | IT / backend | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RBAC_INFO 40 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms it is binding. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RBAC_REQ 28 | SSR-RBAC-001 | Cybersecurity | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RBAC_INFO 42 | None | IT / backend | High complexity | 56 | Limited; standard implementation and verification risk. | Customer confirms it is binding. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RBAC_REQ 29 | SSR-RBAC-004 | Software | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RBAC_REQ 30 | SSR-RBAC-003 | IT / backend | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RBAC_INFO 43 | None | IT / backend | High complexity | 56 | Limited; standard implementation and verification risk. | Customer confirms it is binding. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RBAC_REQ 31 | SSR-RBAC-003 | IT / backend | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RBAC_INFO 44 | None | IT / backend | High complexity | 56 | Limited; standard implementation and verification risk. | Customer confirms it is binding. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RBAC_INFO 45 | None | Cybersecurity | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-CVS151-0091 | None | Cybersecurity | High complexity | 56 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | OP-003; None | Unverified security control could leave a residual risk in the cybersecurity case. | Medium | ESTIMATED | Define and code | Confirm ownership and provisioning flow for keys/certificates (generation, injection, storage, renewal, revocation) between OEM and supplier. |
| RFQX-CVS151-0092 | None | Software | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-CVS151-0093 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-CVS151-0094 | None | Interface | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; External Interfaces | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-CVS154-0001 | None | Cybersecurity | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No supplier action - document reference / boilerplate. |
| RFQX-CVS154-0002 | None | Process / compliance | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-009; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm the DIA / responsibility (RASIC/CIA) split for each cybersecurity work product before supplier scope is fixed. |
| RFQX-CVS154-0003 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-CVS154-0004 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| DSC_BASE_INFO 1 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| DSC_BASE_INFO 2 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| DSC_BASE_INFO 3 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| DSC_BASE_REQ 37 | SSR-TOOL-002 | IT / backend | High complexity | 16 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| DSC_BASE_REQ 43 | SSR-TOOL-002 | IT / backend | High complexity | 16 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| DSC_BASE_REQ 29 | SSR-VV-002 | IT / backend | High complexity | 16 | Responsibility gap 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 Interface | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| DSC_BASE_REQ 30 | SSR-TOOL-002 | IT / backend | High complexity | 16 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| DSC_BASE_REQ 31 | SSR-TOOL-002 | IT / backend | High complexity | 16 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| DSC_BASE_REQ 45 | SSR-VV-002 | IT / backend | High complexity | 16 | Responsibility gap 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 Interface | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| DSC_BASE_REQ 46 | SSR-TOOL-002 | IT / backend | High complexity | 16 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| DSC_BASE_REQ 49 | SSR-TOOL-002 | IT / backend | High complexity | 16 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| DSC_BASE_REQ 26 | SSR-VV-002 | IT / backend | High complexity | 16 | Responsibility gap 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 Interface | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| DSC_BASE_INFO 44 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms it is binding. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| DSC_BASE_INFO 33 | None | IT / backend | High complexity | 56 | Limited; standard implementation and verification risk. | Customer confirms it is binding. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| DSC_BASE_INFO 4 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| DSC_BASE_INFO 38 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| DSC_BASE_REQ 5 | SSR-VV-001 | System | Medium complexity | 19 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| DSC_BASE_INFO 6 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-CVS154-0023 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| DSC_BASE_INFO 7 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-CVS154-0025 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-CVS154-0026 | None | System | High complexity | 56 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-001; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm the exact ECU designation/variant and the agreed item definition and boundary used for the risk analysis (TARA). |
| DSC_BASE_REQ 47 | SSR-TOOL-002 | IT / backend | High complexity | 16 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| DSC_BASE_INFO 9 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| DSC_BASE_REQ 39 | SSR-TOOL-002 | IT / backend | High complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| DSC_BASE_INFO 40 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| DSC_BASE_REQ 11 | SSR-SYS-001 | System | Medium complexity | 19 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| RFQX-CVS154-0032 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| DSC_BASE_INFO 17 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| DSC_BASE_REQ 41 | SSR-SYS-001 | System | Medium complexity | 19 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| DSC_BASE_REQ 42 | None | IT / backend | High complexity | 19 | Limited; standard implementation and verification risk. | Internal review confirms wording and scope. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Complete internal review of wording and baseline scope. |
| DSC_BASE_REQ 19 | SSR-COM-009 | IT / backend | High complexity | 16 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| DSC_BASE_REQ 51 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| REQ_DSC_BASE_20 | SSR-TOOL-003 | Software | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| DSC_BASE_REQ 34 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| DSC_BASE_REQ 27 | SSR-TOOL-002 | IT / backend | High complexity | 16 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| DSC_BASE_REQ 50 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| DSC_BASE_INFO 35 | None | System | High complexity | 56 | Limited; standard implementation and verification risk. | Customer confirms it is binding. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| DSC_BASE_REQ 28 | SSR-TOOL-002 | IT / backend | High complexity | 16 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| DSC_BASE_REQ 22 | SSR-KEY-001 | Cybersecurity | High complexity | 24 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | None | Unverified security control could leave a residual risk in the cybersecurity case. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| DSC_BASE_INFO 36 | None | System | High complexity | 56 | Limited; standard implementation and verification risk. | Customer confirms it is binding. | OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| DSC_BASE_REQ 48 | SSR-TOOL-002 | IT / backend | High complexity | 16 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| RFQX-CVS154-0047 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-CVS31-0001 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-CVS31-0002 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No supplier action - document reference / boilerplate. |
| RFQX-CVS31-0003 | None | Process / compliance | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-009; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm the DIA / responsibility (RASIC/CIA) split for each cybersecurity work product before supplier scope is fixed. |
| RFQX-CVS31-0004 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-CVS31-0005 | None | IT / backend | High complexity | 56 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| 1.1 | SSR-RBAC-001 | Cybersecurity | High complexity | 29 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | OEM/Customer Review Interface | Unverified security control could leave a residual risk in the cybersecurity case. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| RFQX-CVS31-0007 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-CVS31-0008 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; OEM/Customer Review Interface | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-CVS31-0009 | None | IT / backend | High complexity | 56 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-CVS31-0010 | None | IT / backend | High complexity | 56 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| AUTH_INFO 1 | None | Process / compliance | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 1 | SSR-TOOL-002 | IT / backend | High complexity | 21 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| AUTH_INFO 2 | None | Process / compliance | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 155 | SSR-RBAC-006 | Software | High complexity | 26 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RFQX-CVS31-0015 | None | Software | High complexity | 56 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm the diagnostic role model, the authorized services per role, and which party owns the diagnostic authorization policy. |
| AUTH_REQ 2 | SSR-KEY-002 | System | High complexity | 32 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| AUTH_REQ 117 | SSR-DAI-001 | Cybersecurity | High complexity | 26 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_INFO 30 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 118 | SSR-KEY-003 | IT / backend | High complexity | 26 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_INFO 24 | None | IT / backend | High complexity | 56 | Limited; standard implementation and verification risk. | Customer confirms it is binding. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 45 | SSR-DAI-001 | Cybersecurity | High complexity | 26 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_REQ 119 | SSR-TOOL-002 | IT / backend | High complexity | 26 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_INFO 27 | None | Cybersecurity | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 3 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| AUTH_REQ 4 | SSR-SYS-002 | Process / compliance | Medium complexity | 10 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| AUTH_REQ 172 | SSR-KEY-002 | System | High complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| AUTH_REQ 173 | SSR-KEY-003 | IT / backend | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_REQ 174 | SSR-KEY-003 | IT / backend | High complexity | 26 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_REQ 5 | SSR-KEY-002 | System | High complexity | 26 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| AUTH_REQ 120 | SSR-TOOL-002 | IT / backend | High complexity | 26 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_REQ 6 | SSR-TOOL-004 | System | High complexity | 26 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_INFO 143 | None | Cybersecurity | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 7 | SSR-DAI-008 | System | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| AUTH_INFO 60 | None | System | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 4 | None | Cybersecurity | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 121 | SSR-KEY-003 | IT / backend | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_REQ 122 | SSR-KEY-001 | Cybersecurity | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_REQ 123 | SSR-KEY-003 | IT / backend | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_INFO 5 | None | Cybersecurity | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 8 | SSR-SYS-001 | System | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| AUTH_REQ 116 | SSR-DAI-003 | IT / backend | High complexity | 26 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_REQ 110 | SSR-RBAC-004 | Software | High complexity | 26 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_REQ 111 | SSR-TOOL-002 | IT / backend | High complexity | 26 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_INFO 31 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 112 | SSR-TOOL-002 | IT / backend | High complexity | 24 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_REQ 113 | SSR-DAI-006 | IT / backend | High complexity | 26 | Responsibility gap 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 Interface | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_REQ 114 | SSR-COM-004 | IT / backend | High complexity | 26 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_REQ 115 | SSR-DAI-003 | IT / backend | High complexity | 26 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RFQX-CVS31-0049 | None | IT / backend | High complexity | 56 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| AUTH_INFO 141 | None | Cybersecurity | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 160 | SSR-SYS-001 | System | Medium complexity | 21 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| AUTH_INFO 142 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 3 | None | Cybersecurity | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 161 | SSR-SYS-001 | System | Medium complexity | 21 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| AUTH_INFO 140 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 162 | SSR-DAI-008 | System | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| AUTH_INFO 145 | None | System | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 124 | SSR-TOOL-002 | IT / backend | High complexity | 26 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_REQ 125 | SSR-TOOL-002 | IT / backend | High complexity | 24 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_REQ 126 | SSR-COM-004 | IT / backend | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_REQ 127 | SSR-DAI-006 | IT / backend | High complexity | 24 | Responsibility gap 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 Interface | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_REQ 128 | SSR-DAI-006 | IT / backend | High complexity | 24 | Responsibility gap 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 Interface | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_REQ 129 | SSR-TOOL-002 | IT / backend | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_INFO 11 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 159 | SSR-SYS-001 | System | Medium complexity | 21 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| AUTH_REQ 96 | SSR-RBAC-004 | Software | High complexity | 26 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| AUTH_REQ 158 | SSR-TOOL-002 | IT / backend | High complexity | 26 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_REQ 130 | SSR-TOOL-002 | IT / backend | High complexity | 18 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| AUTH_INFO 32 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 131 | SSR-COM-004 | IT / backend | High complexity | 26 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_REQ 132 | SSR-COM-004 | IT / backend | High complexity | 24 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_INFO 133 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 175 | SSR-DAI-001 | Cybersecurity | High complexity | 24 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | None | Unverified security control could leave a residual risk in the cybersecurity case. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| AUTH_REQ 176 | SSR-KEY-001 | Cybersecurity | High complexity | 24 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | None | Unverified security control could leave a residual risk in the cybersecurity case. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| AUTH_REQ 177 | SSR-KEY-001 | Cybersecurity | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_INFO 101 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 163 | SSR-KEY-002 | System | High complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| AUTH_REQ 164 | SSR-KEY-001 | Cybersecurity | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_INFO 7 | None | Cybersecurity | High complexity | 56 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer confirms it is binding. | None | Unverified security control could leave a residual risk in the cybersecurity case. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 165 | SSR-KEY-001 | Cybersecurity | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_REQ 134 | SSR-DAI-001 | Cybersecurity | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_REQ 166 | None | IT / backend | High complexity | 19 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 9 | SSR-KEY-001 | Cybersecurity | High complexity | 29 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_REQ 106 | SSR-SYS-001 | System | Medium complexity | 19 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| AUTH_INFO 25 | None | Cybersecurity | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 100 | None | Cybersecurity | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 11 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 170 | SSR-KEY-001 | Cybersecurity | High complexity | 24 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | None | Unverified security control could leave a residual risk in the cybersecurity case. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| AUTH_REQ 13 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| AUTH_INFO 8 | None | System | Low complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms it is binding. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 9 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-CVS31-0092 | None | Cybersecurity | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 14 | SSR-RBAC-003 | IT / backend | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_INFO 61 | None | Software | High complexity | 56 | Limited; standard implementation and verification risk. | Customer confirms it is binding. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 135 | SSR-RBAC-003 | IT / backend | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RFQX-CVS31-0096 | None | Cybersecurity | High complexity | 56 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm ownership and provisioning flow for keys/certificates (generation, injection, storage, renewal, revocation) between OEM and supplier. |
| AUTH_INFO 33 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 136 | SSR-RBAC-003 | IT / backend | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RFQX-CVS31-0099 | None | Cybersecurity | High complexity | 56 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm ownership and provisioning flow for keys/certificates (generation, injection, storage, renewal, revocation) between OEM and supplier. |
| AUTH_REQ 42 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| AUTH_REQ 15 | SSR-KEY-001 | Cybersecurity | High complexity | 24 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | None | Unverified security control could leave a residual risk in the cybersecurity case. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| AUTH_REQ 47 | SSR-KEY-001 | Cybersecurity | High complexity | 24 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | None | Unverified security control could leave a residual risk in the cybersecurity case. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| AUTH_REQ 95 | SSR-KEY-001 | Cybersecurity | High complexity | 24 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | None | Unverified security control could leave a residual risk in the cybersecurity case. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| AUTH_REQ 107 | SSR-SYS-001 | System | High complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| AUTH_REQ 105 | SSR-DAI-008 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| AUTH_REQ 169 | SSR-KEY-001 | Cybersecurity | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_INFO 137 | None | Cybersecurity | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 138 | None | IT / backend | High complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 143 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 139 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 156 | SSR-DIAG-006 | Software | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_INFO 134 | None | Software | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 16 | SSR-TOOL-002 | IT / backend | High complexity | 24 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_REQ 17 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 18 | None | Process / compliance | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 19 | None | System | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 20 | None | System | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 10 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 157 | SSR-DIAG-006 | Software | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_REQ 140 | SSR-TOOL-002 | IT / backend | High complexity | 24 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_REQ 141 | None | System | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 142 | None | Cybersecurity | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 144 | None | Cybersecurity | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 145 | None | Cybersecurity | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 146 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 34 | None | Cybersecurity | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 35 | None | System | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 21 | SSR-TOOL-002 | IT / backend | High complexity | 24 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_REQ 22 | None | System | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 23 | None | System | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 147 | None | Cybersecurity | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 148 | None | Cybersecurity | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 149 | SSR-TOOL-002 | IT / backend | High complexity | 24 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_REQ 150 | SSR-TOOL-002 | IT / backend | High complexity | 24 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_INFO 135 | None | Cybersecurity | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 136 | None | Cybersecurity | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 167 | SSR-KEY-002 | System | High complexity | 29 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| AUTH_REQ 168 | SSR-SYS-001 | System | High complexity | 29 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| AUTH_INFO 146 | None | Cybersecurity | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 26 | None | System | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 24 | SSR-COM-006 | Software | High complexity | 29 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_REQ 33 | SSR-SYS-001 | System | Medium complexity | 19 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| AUTH_REQ 25 | SSR-RBAC-004 | Software | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_INFO 12 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 13 | None | Process / compliance | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 109 | SSR-SYS-001 | System | High complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| AUTH_REQ 26 | SSR-TOOL-002 | IT / backend | High complexity | 24 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_REQ 27 | SSR-TOOL-002 | IT / backend | High complexity | 16 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Confirm responsibility allocation, then implement and verify. |
| AUTH_INFO 147 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 148 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 28 | SSR-TOOL-002 | IT / backend | High complexity | 24 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_REQ 29 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| AUTH_INFO 14 | None | System | Low complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms it is binding. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 38 | None | System | High complexity | 56 | Limited; standard implementation and verification risk. | Customer confirms it is binding. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 133 | SSR-SYS-001 | System | Medium complexity | 8 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Confirm responsibility allocation, then implement and verify. |
| AUTH_REQ 151 | SSR-KEY-003 | IT / backend | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_REQ 152 | SSR-COM-004 | IT / backend | High complexity | 24 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_REQ 153 | SSR-COM-004 | IT / backend | High complexity | 24 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| AUTH_INFO 36 | None | System | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 154 | SSR-SYS-001 | System | High complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| AUTH_INFO 37 | None | System | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 167 | None | System | Medium complexity | 19 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 169 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 12 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-CVS31-0165 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | No supplier action - document reference / boilerplate. |
| AUTH_REQ 4 | None | System | Medium complexity | 19 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 159 | None | System | Medium complexity | 21 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 1 | None | System | Medium complexity | 21 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 160 | None | System | Medium complexity | 21 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 2 | None | System | Medium complexity | 21 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 161 | None | System | Medium complexity | 21 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 3 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 162 | None | System | Low complexity | 5 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 5 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 163 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 6 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 164 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 7 | None | System | Low complexity | 5 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 165 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 8 | None | System | Low complexity | 5 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 166 | None | System | Medium complexity | 19 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 12 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 170 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 10 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 171 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 1 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 141 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 2 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 142 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 3 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 143 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 4 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 140 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 5 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 145 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 11 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 146 | None | System | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 135 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 136 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 167 | None | System | Low complexity | 5 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 168 | None | Cybersecurity | High complexity | 29 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 169 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 137 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 107 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 136 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 60 | None | System | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 127 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 128 | None | System | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 12 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 137 | None | IT / backend | High complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 135 | None | IT / backend | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 155 | None | System | Low complexity | 5 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 117 | None | System | Low complexity | 5 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 45 | None | System | Low complexity | 5 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 3 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 122 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 5 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 164 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 9 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 136 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 156 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 172 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 173 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 6 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 175 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 176 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 177 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 147 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 147 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 1 | None | System | Medium complexity | 21 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 155 | None | System | Low complexity | 5 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 117 | None | System | Low complexity | 5 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 24 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 45 | None | System | Low complexity | 5 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 3 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 122 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 5 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 164 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 9 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 136 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 156 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 157 | None | System | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 24 | None | System | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 171 | None | Cybersecurity | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 100 | None | Cybersecurity | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 108 | None | System | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 172 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 173 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 174 | None | Process / compliance | High complexity | 26 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 6 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 175 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 176 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_REQ 177 | None | System | Low complexity | 4 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| AUTH_INFO 101 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-CVS32-0001 | None | System | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| RFQX-CVS32-0002 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No supplier action - document reference / boilerplate. |
| RFQX-CVS32-0003 | None | Process / compliance | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-009; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm the DIA / responsibility (RASIC/CIA) split for each cybersecurity work product before supplier scope is fixed. |
| RFQX-CVS32-0004 | None | IT / backend | High complexity | 56 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| 1.1 | None | Cybersecurity | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No supplier action - document reference / boilerplate. |
| 1.2 | None | Cybersecurity | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| 1.3 | SSR-KEY-004 | Cybersecurity | High complexity | 26 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RFQX-CVS32-0008 | None | Cybersecurity | High complexity | 56 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | OP-011; None | Unverified security control could leave a residual risk in the cybersecurity case. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| SDT_REQ 1 | SSR-COM-010 | System | Medium complexity | 19 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SDT_INFO 1 | None | Software | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 2 | None | Interface | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 2 | SSR-COM-010 | System | Medium complexity | 19 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SDT_REQ 3 | None | Cybersecurity | High complexity | 29 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-CVS32-0014 | None | Cybersecurity | High complexity | 56 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm the diagnostic role model, the authorized services per role, and which party owns the diagnostic authorization policy. |
| SDT_INFO 3 | None | Software | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 4 | SSR-RBAC-007 | Cybersecurity | High complexity | 29 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RFQX-CVS32-0017 | None | System | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 4 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 5 | SSR-COM-011 | Software | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| RFQX-CVS32-0020 | None | Software | High complexity | 56 | Limited; standard implementation and verification risk. | Customer confirms responsibility allocation and implementation method. | OP-011; None | Limited; standard implementation and verification risk. | Low | BLOCKED / NEEDS CUSTOMER DECISION | Customer clarification | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. |
| SDT_INFO 5 | None | Interface | Medium complexity | 24 | Limited; standard implementation and verification risk. | Customer confirms it is binding. | External Interfaces | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 6 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 7 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 8 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 6 | SSR-COM-009 | IT / backend | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SDT_REQ 7 | SSR-COM-007 | Interface | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | External Interfaces | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SDT_REQ 8 | SSR-COM-009 | IT / backend | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SDT_REQ 9 | SSR-COM-009 | IT / backend | High complexity | 29 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SDT_REQ 10 | SSR-COM-007 | Interface | High complexity | 24 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | External Interfaces | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| SDT_REQ 11 | SSR-COM-007 | Interface | Medium complexity | 19 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | External Interfaces | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SDT_REQ 12 | SSR-COM-009 | IT / backend | High complexity | 29 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SDT_INFO 9 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 13 | SSR-COM-009 | IT / backend | High complexity | 19 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SDT_INFO 10 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 71 | None | System | Medium complexity | 19 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 9 | None | IT / backend | High complexity | 19 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 11 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 12 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 13 | None | Interface | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 14 | SSR-COM-010 | System | Medium complexity | 19 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SDT_INFO 14 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 15 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 16 | None | Interface | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 15 | SSR-COM-007 | Interface | Medium complexity | 19 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | External Interfaces | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SDT_INFO 17 | None | Cybersecurity | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 16 | SSR-COM-010 | System | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SDT_REQ 17 | SSR-COM-007 | Interface | Medium complexity | 18 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | External Interfaces | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SDT_REQ 18 | SSR-COM-009 | IT / backend | High complexity | 26 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SDT_REQ 19 | None | System | Medium complexity | 18 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 18 | None | Cybersecurity | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 20 | SSR-KEY-004 | Cybersecurity | High complexity | 26 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SDT_INFO 19 | None | Cybersecurity | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 21 | SSR-COM-010 | System | High complexity | 32 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| SDT_REQ 22 | SSR-VV-004 | IT / backend | High complexity | 32 | Responsibility gap 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 Interface | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SDT_INFO 20 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 23 | SSR-KEY-004 | Cybersecurity | High complexity | 29 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SDT_REQ 24 | SSR-RBAC-006 | Software | High complexity | 29 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| SDT_REQ 25 | SSR-COM-011 | Software | Medium complexity | 19 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SDT_REQ 26 | SSR-COM-011 | Software | High complexity | 29 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| SDT_INFO 21 | None | System | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 22 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 23 | None | Cybersecurity | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 24 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 27 | SSR-COM-011 | Software | Medium complexity | 19 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SDT_REQ 28 | SSR-KEY-004 | Cybersecurity | High complexity | 29 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SDT_REQ 29 | SSR-KEY-004 | Cybersecurity | High complexity | 29 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SDT_INFO 25 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 30 | SSR-KEY-004 | Cybersecurity | High complexity | 29 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | None | Unverified security control could leave a residual risk in the cybersecurity case. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| SDT_REQ 31 | SSR-COM-010 | System | Medium complexity | 19 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SDT_REQ 32 | SSR-COM-010 | System | Medium complexity | 19 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SDT_REQ 33 | SSR-COM-007 | Interface | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | External Interfaces | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SDT_INFO 26 | None | Interface | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 34 | SSR-DAI-009 | Cybersecurity | High complexity | 16 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | None | Unverified security control could leave a residual risk in the cybersecurity case. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SDT_REQ 35 | SSR-COM-007 | Interface | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | External Interfaces | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SDT_REQ 36 | SSR-COM-007 | Interface | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | External Interfaces | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SDT_REQ 37 | SSR-COM-007 | Interface | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | External Interfaces | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SDT_REQ 38 | SSR-COM-010 | System | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SDT_REQ 39 | SSR-COM-007 | Interface | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | External Interfaces | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SDT_REQ 41 | None | System | Low complexity | 16 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 42 | SSR-COM-009 | IT / backend | High complexity | 29 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SDT_REQ 43 | None | System | Low complexity | 16 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 44 | SSR-DAI-009 | Cybersecurity | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SDT_REQ 46 | SSR-COM-009 | IT / backend | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SDT_REQ 47 | SSR-COM-009 | IT / backend | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SDT_REQ 48 | SSR-COM-009 | IT / backend | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SDT_INFO 27 | None | Software | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 28 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-CVS32-0088 | SSR-COM-007 | Interface | Low complexity | 8 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | External Interfaces | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SDT_INFO 29 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 30 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 49 | SSR-COM-011 | Software | Medium complexity | 19 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SDT_REQ 50 | SSR-DAI-009 | Cybersecurity | High complexity | 29 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SDT_REQ 51 | SSR-DAI-009 | Cybersecurity | High complexity | 29 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SDT_INFO 49 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 52 | SSR-KEY-004 | Cybersecurity | High complexity | 29 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | None | Unverified security control could leave a residual risk in the cybersecurity case. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| SDT_REQ 91 | SSR-COM-010 | System | Medium complexity | 19 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SDT_REQ 89 | None | System | Medium complexity | 19 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 90 | None | System | Low complexity | 19 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 54 | SSR-COM-010 | System | Medium complexity | 19 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SDT_REQ 55 | SSR-COM-007 | Interface | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | External Interfaces | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SDT_REQ 56 | SSR-COM-007 | Interface | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | External Interfaces | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SDT_REQ 57 | SSR-COM-007 | Interface | Medium complexity | 19 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | External Interfaces | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SDT_REQ 58 | SSR-COM-010 | System | Medium complexity | 19 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SDT_REQ 59 | SSR-COM-007 | Interface | Medium complexity | 19 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | External Interfaces | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SDT_REQ 60 | None | System | Low complexity | 19 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 61 | SSR-COM-012 | IT / backend | High complexity | 29 | Responsibility gap 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 Interface | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SDT_REQ 62 | None | System | Low complexity | 16 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 63 | SSR-COM-009 | IT / backend | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SDT_REQ 64 | SSR-COM-009 | IT / backend | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SDT_REQ 65 | SSR-COM-009 | IT / backend | High complexity | 16 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SDT_REQ 66 | SSR-COM-007 | Interface | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | External Interfaces | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SDT_INFO 31 | None | Software | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 32 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 33 | None | Cybersecurity | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 34 | None | Software | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| RFQX-CVS32-0116 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 35 | None | Cybersecurity | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 36 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 67 | SSR-COM-009 | IT / backend | High complexity | 29 | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Customer confirms the responsibility split (DIA/RASIC) for the non-ECU portion. | None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SDT_REQ 68 | SSR-COM-013 | Cybersecurity | High complexity | 29 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SDT_REQ 69 | SSR-COM-009 | IT / backend | High complexity | 29 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SDT_REQ 70 | SSR-COM-009 | IT / backend | High complexity | 29 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SDT_REQ 71 | SSR-COM-009 | IT / backend | High complexity | 29 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SDT_REQ 88 | SSR-COM-009 | IT / backend | High complexity | 29 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SDT_REQ 72 | SSR-COM-009 | IT / backend | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SDT_REQ 73 | SSR-COM-009 | IT / backend | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SDT_INFO 37 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 74 | SSR-COM-009 | IT / backend | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SDT_INFO 38 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 75 | SSR-COM-009 | IT / backend | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SDT_REQ 76 | SSR-COM-009 | IT / backend | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SDT_INFO 39 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 77 | SSR-DAI-009 | Cybersecurity | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SDT_INFO 40 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 41 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 42 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 43 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 44 | None | Cybersecurity | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 78 | SSR-DAI-009 | Cybersecurity | High complexity | 29 | Unverified security control could leave a residual risk in the cybersecurity case. | Customer approves the proposed implementation method and responsibility allocation. | None | Unverified security control could leave a residual risk in the cybersecurity case. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Validate assumption with customer; complete mapping; implement. |
| SDT_REQ 79 | SSR-COM-010 | System | Medium complexity | 19 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SDT_REQ 80 | SSR-COM-010 | System | Medium complexity | 19 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SDT_REQ 81 | SSR-COM-010 | System | Medium complexity | 19 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SDT_REQ 82 | SSR-COM-010 | System | Medium complexity | 19 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SDT_REQ 83 | SSR-COM-010 | System | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SDT_REQ 84 | SSR-COM-010 | System | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SDT_REQ 85 | SSR-COM-010 | System | Medium complexity | 16 | Limited; standard implementation and verification risk. | Customer approves the proposed implementation method and responsibility allocation. | None | Limited; standard implementation and verification risk. | Medium | ESTIMATED | Define and code | Validate assumption with customer; complete mapping; implement. |
| SDT_REQ 86 | SSR-COM-009 | IT / backend | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SDT_INFO 45 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 46 | None | IT / backend | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 47 | None | Interface | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 87 | SSR-COM-009 | IT / backend | High complexity | 24 | Responsibility gap 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; None | Responsibility gap between OEM and supplier could leave a security control unimplemented or duplicated. | Low | ESTIMATED WITH ASSUMPTION | Define and code - assumption gated | Agree responsibility split (DIA) for the non-ECU portion. |
| SDT_REQ 7 | None | System | Low complexity | 16 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 48 | None | Interface | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 7 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 14 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 15 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 22 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 25 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 7 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 14 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 15 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 17 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 22 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 25 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 49 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 13 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 17 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 16 | None | System | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 20 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 21 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 24 | None | System | High complexity | 56 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 31 | None | System | High complexity | 29 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 34 | None | System | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 37 | None | System | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 38 | None | System | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 39 | None | System | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 41 | None | System | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 42 | None | System | High complexity | 29 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 43 | None | System | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 44 | None | System | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 48 | None | System | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 27 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 30 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 49 | None | System | High complexity | 29 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 50 | None | System | High complexity | 29 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 51 | None | System | Low complexity | 19 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 49 | None | System | Low complexity | 8 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 52 | None | System | Low complexity | 19 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 89 | None | System | Low complexity | 19 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 90 | None | System | Medium complexity | 19 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 91 | None | System | High complexity | 29 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 54 | None | System | High complexity | 29 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 57 | None | System | High complexity | 29 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 58 | None | System | High complexity | 29 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 59 | None | System | High complexity | 29 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 60 | None | System | High complexity | 29 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 61 | None | System | High complexity | 29 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 62 | None | System | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 63 | None | System | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 66 | None | System | High complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_INFO 33 | None | System | Medium complexity | 24 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 88 | None | IT / backend | High complexity | 29 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |
| SDT_REQ 88 | None | System | High complexity | 29 | Misinterpreted requirement could drive wrong design and late change cost. | Customer confirms it is binding. | None | Misinterpreted requirement could drive wrong design and late change cost. | Medium | ESTIMATED | Define and code | No action unless the customer confirms it is binding. |