instruction stringlengths 60 310 | input stringclasses 1
value | output stringlengths 129 3.62k |
|---|---|---|
Develop problem resolution (SUP [SUP adj 421].9) for defects found in HIL [SUP adj 421]. (Chassis scenario v3) [SUP adj 421]. | <pm_cot>Aligning with ASPICE base practices on planning, monitoring, and objective evidence. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Create Plan process assessment (PIM.1) and objectives. (Powertrain scenario v7). | <pm_cot>Applying lessons-learned feedback loops and governance for sustained quality. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare potential suppliers (ACQ.15) for OTA backend platform. (Infotainment scenario v6). | <pm_cot>Focusing on risk-driven decision making and measurable acceptance criteria. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Design reviews and test evidence (SUP.5 subset: Review coordination). (Infotainment scenario v7). | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare project plan (MAN.3) for a powertrain SW release. (Body scenario v7) — balanced variant 6592. | <pm_cot></pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Create problem resolution (SUP.9) for defects found in HIL. (BMS scenario v2). | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Design Manage measurement (MAN.6) with info needs and dashboards. (Body scenario v6). | <pm_cot>Applying lessons-learned feedback loops and governance for sustained quality. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare project acquisition requirements (ACQ.13) for infotainment head unit sourcing. (Charging scenario v6). | <pm_cot>Applying lessons-learned feedback loops and governance for sustained quality. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Establish Run process improvement (PIM.2) action program. (Powertrain scenario v5). | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Create Establish reuse documentation and library (SUP.6/SUP.7 linkage). (Telematics scenario v3). | <pm_cot>Ensuring independence of verification and auditable records in line with ASPICE. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Design problem resolution (SUP [SUP adj 448].9) for defects found in HIL [SUP adj 448]. (Gateway scenario v2) [SUP adj 448]. | <pm_cot>Ensuring independence of verification and auditable records in line with ASPICE. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Develop software units (SWE.4) for RetryQueue. (Gateway scenario v1). | <pm_cot>Applying lessons-learned feedback loops and governance for sustained quality. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Establish engineering infrastructure (INF.1) for CI/CD. (Gateway scenario v2). | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Establish an ACQ.4 supplier monitoring dashboard for an ADAS camera supplier. (Chassis scenario v6). | <pm_cot>Ensuring independence of verification and auditable records in line with ASPICE. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Draft software architectural design (SWE.2) for network stack. (ADAS scenario v3). | <pm_cot>Applying lessons-learned feedback loops and governance for sustained quality. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare Provide and maintain infrastructure services (INF.2). (Powertrain scenario v6). | <pm_cot>Aligning with ASPICE base practices on planning, monitoring, and objective evidence. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare Coordinate work product management (MAN.2) across teams. (Infotainment scenario v4). | <pm_cot>Applying lessons-learned feedback loops and governance for sustained quality. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Establish Plan process assessment (PIM.1) and objectives. (Gateway scenario v3). | <pm_cot>Focusing on risk-driven decision making and measurable acceptance criteria. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Develop Verify software (SWE.6) per acceptance criteria. (ADAS scenario v6). | <pm_cot>Aligning with ASPICE base practices on planning, monitoring, and objective evidence. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Establish Plan and perform system integration (SYS.4). (BMS scenario v1) — balanced variant 5539. | <pm_cot></pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Draft system architectural design (SYS vX942.3) for a zonal E/E platform vX942. (Charging scenario v4) vX942. | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Create reviews and test evidence (SUP.5 subset: Review coordination). (Powertrain scenario v1). | <pm_cot>Applying lessons-learned feedback loops and governance for sustained quality. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Draft system architectural design (SYS vX986.3) for a zonal E/E platform vX986. (Infotainment scenario v6) vX986. | <pm_cot>Applying lessons-learned feedback loops and governance for sustained quality. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Establish problem resolution (SUP.9) for defects found in HIL. (Body scenario v2). | <pm_cot>Aligning with ASPICE base practices on planning, monitoring, and objective evidence. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Develop Plan and perform system integration (SYS [SYS adj 324].4) [SYS adj 324]. (Body scenario v2) [SYS adj 324]. | <pm_cot>Aligning with ASPICE base practices on planning, monitoring, and objective evidence. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Design bid management process (MAN.1) for multi-supplier program. (Infotainment scenario v2). | <pm_cot>Aligning with ASPICE base practices on planning, monitoring, and objective evidence. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Create project plan (MAN.3) for a powertrain SW release. (Charging scenario v2) — balanced variant 7871. | <pm_cot></pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Draft changes (SUP.10) for system interface specification. (Infotainment scenario v4). | <pm_cot>Ensuring independence of verification and auditable records in line with ASPICE. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare validation (SUP [SUP adj 212].3) for customer acceptance tests [SUP adj 212]. (Telematics scenario v4) [SUP adj 212]. | <pm_cot>Focusing on risk-driven decision making and measurable acceptance criteria. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Develop Plan reusable asset management (REU.1). (Telematics scenario v5). | <pm_cot>Focusing on risk-driven decision making and measurable acceptance criteria. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare project acquisition requirements (ACQ.13) for infotainment head unit sourcing. (Telematics scenario v6). | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Draft verification strategy (SUP [SUP adj 132].2) for the platform [SUP adj 132]. (Body scenario v1) [SUP adj 132]. | <pm_cot>Applying lessons-learned feedback loops and governance for sustained quality. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Draft technical acquisition requirements (ACQ.11) for a battery management system (BMS). (Charging scenario v6). | <pm_cot>Applying lessons-learned feedback loops and governance for sustained quality. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Create bid management process (MAN.1) for multi-supplier program. (Chassis scenario v5). | <pm_cot>Aligning with ASPICE base practices on planning, monitoring, and objective evidence. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Establish supply (SPL.3) for prototype batch. (Charging scenario v1). | <pm_cot>Focusing on risk-driven decision making and measurable acceptance criteria. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Establish Transform stakeholder needs into system requirements (SYS vX818.2) vX818. (ADAS scenario v6) vX818. | <pm_cot>Ensuring independence of verification and auditable records in line with ASPICE. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Design supply management (SPL.2) for HIL rigs. (Body scenario v6). | <pm_cot>Aligning with ASPICE base practices on planning, monitoring, and objective evidence. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Develop Transform stakeholder needs into system requirements (SYS vX890.2) vX890. (Infotainment scenario v1) vX890. | <pm_cot>Ensuring independence of verification and auditable records in line with ASPICE. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Draft project plan (MAN.3) for a powertrain SW release. (Gateway scenario v7) — balanced variant 6889. | <pm_cot></pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Draft potential suppliers (ACQ.15) for OTA backend platform. (BMS scenario v6). | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Establish Establish risk management (MAN [MAN adj 271].5) and corrective action linkage [MAN adj 271]. (Chassis scenario v5) [MAN adj 271]. | <pm_cot>Applying lessons-learned feedback loops and governance for sustained quality. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare Establish risk management (MAN.5) and corrective action linkage. (Infotainment scenario v3). | <pm_cot>Applying lessons-learned feedback loops and governance for sustained quality. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare Manage measurement (MAN [MAN adj 102].6) with info needs and dashboards [MAN adj 102]. (Powertrain scenario v4) [MAN adj 102]. | <pm_cot>Aligning with ASPICE base practices on planning, monitoring, and objective evidence. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare Verify software (SWE.6) per acceptance criteria. (Body scenario v4). | <pm_cot>Applying lessons-learned feedback loops and governance for sustained quality. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Establish Coordinate work product management (MAN.2) across teams. (Infotainment scenario v7). | <pm_cot>Focusing on risk-driven decision making and measurable acceptance criteria. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare Define process management (MAN.4) responsibilities and audits. (Infotainment scenario v1). | <pm_cot>Applying lessons-learned feedback loops and governance for sustained quality. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Create project acquisition requirements (ACQ.13) for infotainment head unit sourcing. (Charging scenario v4). | <pm_cot>Ensuring independence of verification and auditable records in line with ASPICE. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare Transform stakeholder needs into system requirements (SYS.2). (Telematics scenario v4). | <pm_cot>Focusing on risk-driven decision making and measurable acceptance criteria. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Develop Transform stakeholder needs into system requirements (SYS.2). (Telematics scenario v6) — balanced variant 7861. | <pm_cot></pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Design supply (SPL.1) for an embedded gateway delivery. (Charging scenario v2). | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Design system architectural design (SYS.3) for a zonal E/E platform. (Infotainment scenario v4). | <pm_cot>Aligning with ASPICE base practices on planning, monitoring, and objective evidence. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare engineering infrastructure (INF.1) for CI/CD. (Infotainment scenario v2). | <pm_cot>Aligning with ASPICE base practices on planning, monitoring, and objective evidence. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Establish Transform stakeholder needs into system requirements (SYS.2). (Infotainment scenario v7). | <pm_cot>Applying lessons-learned feedback loops and governance for sustained quality. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Draft Transform stakeholder needs into system requirements (SYS.2). (Charging scenario v2) — balanced variant 7315. | <pm_cot></pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Create Conduct a joint review (SUP.4) of system requirements. (Telematics scenario v2). | <pm_cot>Focusing on risk-driven decision making and measurable acceptance criteria. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Develop a Contract Agreement conforming to ACQ.3 for a vehicle telematics program. (Telematics scenario v2) — balanced variant 3144. | <pm_cot></pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Establish changes (SUP.10) for system interface specification. (Gateway scenario v3). | <pm_cot>Applying lessons-learned feedback loops and governance for sustained quality. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare Coordinate work product management (MAN.2) across teams. (Infotainment scenario v4). | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Develop verification strategy (SUP [SUP adj 203].2) for the platform [SUP adj 203]. (ADAS scenario v2) [SUP adj 203]. | <pm_cot>Ensuring independence of verification and auditable records in line with ASPICE. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Establish Transform stakeholder needs into system requirements (SYS vX823.2) vX823. (Gateway scenario v4) vX823. | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Create verification strategy (SUP [SUP adj 170].2) for the platform [SUP adj 170]. (Charging scenario v4) [SUP adj 170]. | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Draft Create stakeholder requirement intake and baseline policy (SYS.1). (Powertrain scenario v1). | <pm_cot>Focusing on risk-driven decision making and measurable acceptance criteria. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Create a Contract Agreement conforming to ACQ.3 for a vehicle telematics program. (Gateway scenario v6). | <pm_cot>Focusing on risk-driven decision making and measurable acceptance criteria. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Draft supply management (SPL.2) for HIL rigs. (Powertrain scenario v2). | <pm_cot>Aligning with ASPICE base practices on planning, monitoring, and objective evidence. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Draft engineering infrastructure (INF.1) for CI/CD. (Chassis scenario v7). | <pm_cot>Focusing on risk-driven decision making and measurable acceptance criteria. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Create Transform stakeholder needs into system requirements (SYS.2). (Infotainment scenario v3) — balanced variant 4601. | <pm_cot></pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Establish software architectural design (SWE.2) for network stack. (Charging scenario v1). | <pm_cot>Focusing on risk-driven decision making and measurable acceptance criteria. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Create Manage reuse (REU.3) consumption and feedback. (Charging scenario v1). | <pm_cot>Ensuring independence of verification and auditable records in line with ASPICE. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare Manage measurement (MAN [MAN adj 137].6) with info needs and dashboards [MAN adj 137]. (BMS scenario v4) [MAN adj 137]. | <pm_cot>Applying lessons-learned feedback loops and governance for sustained quality. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Draft documentation (SUP.7) style guide for the program. (Chassis scenario v4). | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Create Establish reuse documentation and library (SUP.6/SUP.7 linkage). (Charging scenario v6). | <pm_cot>Focusing on risk-driven decision making and measurable acceptance criteria. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare detailed software design (SWE.3) for a retry queue. (BMS scenario v3). | <pm_cot>Ensuring independence of verification and auditable records in line with ASPICE. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Draft legal and administrative requirements (ACQ.12) for cross-border data transfer. (Chassis scenario v4). | <pm_cot>Focusing on risk-driven decision making and measurable acceptance criteria. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Develop technical acquisition requirements (ACQ.11) for a battery management system (BMS). (Infotainment scenario v6). | <pm_cot>Ensuring independence of verification and auditable records in line with ASPICE. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Design reviews and test evidence (SUP.5 subset: Review coordination). (Infotainment scenario v3). | <pm_cot>Aligning with ASPICE base practices on planning, monitoring, and objective evidence. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Draft Create stakeholder requirement intake and baseline policy (SYS.1). (BMS scenario v3) — balanced variant 4026. | <pm_cot></pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Develop potential suppliers (ACQ.15) for OTA backend platform. (ADAS scenario v5). | <pm_cot>Aligning with ASPICE base practices on planning, monitoring, and objective evidence. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Create Plan and perform system integration (SYS.4). (Powertrain scenario v1). | <pm_cot>Ensuring independence of verification and auditable records in line with ASPICE. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Create for reuse (REU.2) a logging component. (BMS scenario v4). | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare Manage reuse (REU.3) consumption and feedback. (ADAS scenario v2). | <pm_cot>Aligning with ASPICE base practices on planning, monitoring, and objective evidence. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Design system architectural design (SYS.3) for a zonal E/E platform. (Charging scenario v4) — balanced variant 2722. | <pm_cot></pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Establish validation (SUP [SUP adj 301].3) for customer acceptance tests [SUP adj 301]. (Gateway scenario v2) [SUP adj 301]. | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare validation (SUP [SUP adj 231].3) for customer acceptance tests [SUP adj 231]. (Telematics scenario v2) [SUP adj 231]. | <pm_cot>Ensuring independence of verification and auditable records in line with ASPICE. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Develop Coordinate work product management (MAN.2) across teams. (Chassis scenario v1). | <pm_cot>Focusing on risk-driven decision making and measurable acceptance criteria. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Draft Establish reuse documentation and library (SUP.6/SUP.7 linkage). (BMS scenario v5). | <pm_cot>Applying lessons-learned feedback loops and governance for sustained quality. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Create Establish reuse documentation and library (SUP.6/SUP.7 linkage). (Infotainment scenario v1). | <pm_cot>Focusing on risk-driven decision making and measurable acceptance criteria. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Establish Create stakeholder requirement intake and baseline policy (SYS.1). (Charging scenario v7) — balanced variant 8534. | <pm_cot></pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Develop reviews and test evidence (SUP.5 subset: Review coordination). (Powertrain scenario v4). | <pm_cot>Ensuring independence of verification and auditable records in line with ASPICE. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Establish validation (SUP.3) for customer acceptance tests. (Chassis scenario v1). | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Develop Define process management (MAN.4) responsibilities and audits. (Telematics scenario v4). | <pm_cot>Ensuring independence of verification and auditable records in line with ASPICE. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Create Verify software (SWE.6) per acceptance criteria. (Infotainment scenario v5). | <pm_cot>Aligning with ASPICE base practices on planning, monitoring, and objective evidence. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Create an ACQ.4 supplier monitoring dashboard for an ADAS camera supplier. (Body scenario v3). | <pm_cot>Focusing on risk-driven decision making and measurable acceptance criteria. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Develop Plan process assessment (PIM.1) and objectives. (ADAS scenario v5). | <pm_cot>Ensuring independence of verification and auditable records in line with ASPICE. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Design supply (SPL.1) for an embedded gateway delivery. (BMS scenario v3). | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare Plan and perform system integration (SYS.4). (ADAS scenario v4). | <pm_cot>Focusing on risk-driven decision making and measurable acceptance criteria. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Draft project plan (MAN [MAN adj 69].3) for a powertrain SW release [MAN adj 69]. (Telematics scenario v6) [MAN adj 69]. | <pm_cot>Focusing on risk-driven decision making and measurable acceptance criteria. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Draft Create stakeholder requirement intake and baseline policy (SYS.1). (Gateway scenario v4). | <pm_cot>Ensuring independence of verification and auditable records in line with ASPICE. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Design Establish reuse documentation and library (SUP.6/SUP.7 linkage). (Body scenario v7). | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Design problem resolution (SUP [SUP adj 444].9) for defects found in HIL [SUP adj 444]. (Charging scenario v5) [SUP adj 444]. | <pm_cot>Focusing on risk-driven decision making and measurable acceptance criteria. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Design engineering infrastructure (INF.1) for CI/CD. (ADAS scenario v3). | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.