# ASPICE SUP.9 Problem Resolution Management

> Elaborate ASPICE SUP.9 work products: problem resolution procedure, problem reports, and resolution/verification records for Automotive SPICE (VDA PAM 4.0).



Tags: Automotive, ASPICE, Problem Resolution


## Example Prompts

- Document the problem resolution process and defect reports for SUP.9
- Record root cause analysis and verification of resolved problems
- Maintain problem status and closure evidence for ASPICE assessment

URL: https://rakenne.app/skills/aspice-sup-problem-resolution-management/index.md

Try this skill: https://rakenne.app/a/?skill=aspice-sup-problem-resolution-management



## Overview

Elaborate ASPICE SUP.9 work products: problem resolution procedure, problem reports, and resolution/verification records for Automotive SPICE (VDA PAM 4.0).

## Getting Started

Add your source materials to the project workspace, then activate the *ASPICE SUP.9 Problem Resolution Management* skill. The agent will guide you through the process step by step.

## Example Conversation

> **You:** We need to document our problem resolution process and defect reports for SUP.9. We log bugs in Jira but don't have a formal procedure or verification of closure.
>
> **Agent:** I'll help you elaborate SUP.9 work products. I need: (1) How problems are identified (e.g. from testing, reviews, audits) and classified (severity, type); (2) How resolution and closure are done (fix, re-test, who verifies); (3) Any existing defect list to turn into problem reports with resolution and verification. I can draft a problem resolution procedure and a problem report template.
>
> **You:** We use Jira for bugs; severity is Critical/Major/Minor. We fix, re-test, and the tester closes. We have about 20 open items from integration test.
>
> **Agent:** I've created `problem-resolution-procedure.md` (identify → record → analyze → resolve → verify → close) and `problem-reports.md` with a table template (ID, description, severity, source, status, resolution, verification). I've added 20 rows from your Jira export — you can fill resolution and verification for each as they're closed. For assessment, we'll need at least: description, severity, status, and for closed items resolution summary and verification (e.g. re-test date, result). Should I add a section for root cause analysis for Critical/Major items?

## Sample Output Excerpt

Below is a representative excerpt from SUP.9 problem reports and resolution.

---

### Problem resolution procedure (excerpt)

1. **Identify and record** — Problem ID, description, work product affected, severity (Critical/Major/Minor), source (test, review, audit).
2. **Analyze** — Root cause for Critical/Major; define resolution (fix, workaround, process change).
3. **Resolve and verify** — Implement; re-test or re-review; record verifier and date; close when verified.

### Problem reports (excerpt)

| ID | Description | Severity | Source | Status | Resolution / verification |
|----|-------------|----------|--------|--------|---------------------------|
| PR-044 | Boot time 2.8 s at −40 °C (requirement 2.5 s) | Major | SYS-IT-002 | Open | — |
| PR-038 | Traceability matrix missing 2 links | Minor | Audit NC-001 | Closed | Links added; verified in review 12 Feb 2025 |

<!-- /excerpt -->

## Validation

This skill does not include extension tools. Validation is performed by following the **Validation** checklist in the skill workflow: problem resolution procedure is defined; every recorded problem has ID, description, severity, and status; resolved problems have resolution and verification records; closed problems have verification evidence.


---

Back to [Skill Library](https://rakenne.app/skills/index.md)