Hardware and diagnostics — working model

What it covers

• The hardware domain connects component identity, evidence, timeline, findings, incidents, diagnostic cases, service and acceptance.
• Flow: Catalogue → Evidence → Mapping → Correlation → Incident/Case → Guided diagnostics → Service/Replacement → Validation/Acceptance → Retention.
• Physical/virtual detection matters: missing sensor/SMART/RAID/BMC evidence in a VM is an evidence gap, not an automatic failure.
• Normal collection is read-only; disruptive vendor tests do not auto-start.

How to use it

1. Refresh catalogue/evidence.
2. Open component detail.
3. Check coverage/freshness.
4. Correlate incident/case.
5. Run guided steps.
6. Validate after service/replacement.

Important rules

• A missing tool is missing evidence.
• A replacement recommendation is not an automatic decision.
• Keep old component history.