RMA, 5-Why & Knowledge Base

RMA (Return Merchandise Authorization) handles the lifecycle of a returned device: receive it, diagnose it, find the root cause, fix or replace, and ship back. S3Suite's RMA module pairs each return with a 5-Why root-cause analysis and an auto-suggest from the Knowledge Base of past resolutions, so your second RMA on the same fault takes a fraction of the time of the first.

---

Concepts

---

Before you start

• Make sure your devices are in the system. RMA looks up devices by serial number. If a device was never registered through manufacturing, you need to create it first (Manufacturing → Devices).
• Populate the Knowledge Base. Auto-suggest only helps if it has past entries to suggest. Aim for one KB entry per resolved RMA in the first few months.

---

Quick start: handle your first RMA (5 minutes)

1. Create the RMA

1. Open your project
2. Go to Operations → RMA
3. Click New RMA
4. Enter the device serial number. The system auto-fills:

- Variant - Lot - Warranty status - Last-known firmware version - Field service history (if any)

1. Fill in the reported issue - what the customer said in their own words
2. Click Create

You land on the RMA detail page with the device context on the right and the 5-Why panel on the left.

2. Check the auto-suggest

The moment you create the RMA, S3Suite searches the Knowledge Base for entries with similar symptoms:

1. Look at the Similar past resolutions panel
2. Each suggestion shows the past symptom, the root cause, and the resolution
3. If you see a match, click it. The system pre-fills the 5-Why and resolution fields based on the past entry.

Tip: Even partial matches save time. A device with "won't connect to WiFi" that matches a past "won't connect to WiFi - SSID dropped from broadcast list" is a 30-second diagnosis instead of 30 minutes.

3. Run the 5-Why (if auto-suggest did not match)

1. In the 5-Why panel, type the symptom in the first row (Why 1)
2. Click into Why 2 and type the answer to "why did that happen?"
3. Continue down to Why 5 (or stop earlier if you hit the root cause)
4. The final row is the root cause

Example:

4. Save to Knowledge Base

1. After completing the 5-Why and the resolution, click Save to Knowledge Base
2. Edit the title (e.g. "Device shuts down after power outage - firmware v2.3 bug")
3. Optional: tag with categories or symptom keywords
4. Save

This entry now feeds auto-suggest on the next RMA. The Knowledge Base compounds.

5. Close the RMA

1. On the RMA detail page, change status to Resolved or Closed
2. Fill in the resolution (or accept the one pre-filled from KB)
3. Optional: link to a Revision Control commit (the firmware fix), a ticket (customer notified), or a Risk Management entry (if the root cause indicates broader risk)
4. Save

---

Workflow: mass troubleshooting (one root cause, many devices)

When the same fault affects multiple devices, do not file one RMA at a time.

1. Go to Operations → RMA
2. Click New Mass Troubleshooting Record
3. Enter the shared reported symptom
4. Add devices to the record:

- Paste a list of serial numbers, or - Filter by lot / variant / firmware version and bulk-add

1. Run the 5-Why once for the whole record
2. The resolution applies to every linked device
3. Save to Knowledge Base as a single entry

This avoids 50 copies of the same 5-Why and gives you a single trail when someone asks "how many devices were affected?"

---

Workflow: linking an RMA to a customer ticket

If the RMA started as a customer support submission, link them so the customer sees one continuous timeline.

1. Open the customer's ticket (Operations → Technical Support, or follow the email link they received)
2. Look for the Create RMA from this ticket button (only appears when the ticket has a device serial)
3. Click. S3Suite pre-fills the RMA with the customer info, device, and the ticket's first message as the reported issue.
4. Save

The RMA detail page shows a Linked ticket card; the ticket detail page shows a Linked RMA card. Either side can navigate to the other.

---

Workflow: surfacing systemic risks from RMAs

If you see the same root cause across multiple RMAs, that is a risk, not just a series of failures.

1. After the third or fourth RMA with the same root cause, open Engineering → Risk Management
2. Click New Risk
3. Title: the root cause (e.g. "Firmware v2.3 power state machine bug")
4. In Linked items, link the RMA records
5. Set severity / likelihood based on how many devices are at risk
6. Assign an owner for the firmware fix

See Risk Management for the full register workflow.

---

Reference

RMA statuses

• Open - just created, not yet diagnosed
• In progress - 5-Why or testing underway
• Awaiting parts - diagnosed, waiting on a component
• Resolved - fixed and ready to return
• Returned - sent back to the customer
• Closed - terminal state

Knowledge Base auto-suggest

• Triggered on RMA creation, based on the reported issue text plus the device's firmware version plus the variant
• Returns the top five closest matches
• "Closeness" is keyword-based (current implementation); planned upgrade to embeddings-based search
• Each suggestion shows the past RMA's symptom, root cause, and resolution; click to pre-fill the new RMA

Common pitfalls

• "My 5-Why has the same answer three rows in a row." That means you reached the root cause early. Stop. Five "why?" rows is a maximum, not a target.
• "Auto-suggest never finds anything." The Knowledge Base needs ten to twenty resolved RMAs before it becomes useful. Save every resolved RMA in the first few months even if it feels redundant.
• "Mass troubleshooting linked the wrong devices." Filters are forgiving; double-check the filter result count before bulk-adding. Removing a device from a mass record is easy but tedious.
• "The customer keeps emailing about an RMA I already closed." Make sure the linked ticket is also marked Resolved. The customer portal shows the ticket status, not the RMA status.

---

Related docs

• Operations Suite - the broader operations surface (devices, warranty, field service, OTA updates, support)
• Support and Ticketing - the customer-facing entry point that often becomes an RMA
• Knowledge Base and Diary - where resolved RMAs accumulate as reusable institutional knowledge
• Risk Management - escalate repeating RMA patterns into tracked risks