Хардуер и диагностика — работен модел

Какво обхваща

• Hardware domain свързва component identity, evidence, timeline, findings, incidents, diagnostic cases, service и acceptance.
• Flow: Catalog → Evidence → Mapping → Correlation → Incident/Case → Guided diagnostics → Service/Replacement → Validation/Acceptance → Retention.
• Physical/virtual detection е важно: missing sensor/SMART/RAID/BMC във VM е evidence gap, не automatic failure.
• Normal collection е read-only; disruptive vendor tests не се auto-start-ват.

Как се работи

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

Важни правила

• Missing tool е missing evidence.
• Replacement recommendation не е automatic decision.
• Пазете old component history.