Sheet BEA-03 — ITSM Manual
Visibility, CMDB & Experience
Configuration data, the Relay device bridge, problem and knowledge work, and experience reporting.
What this area covers
Service work is only as good as the context behind it. This area covers the CMDB, the device bridge to Relay, problem and knowledge management, and the reporting layer that measures what requesters actually experienced.
Operational areas in scope
| Area | What operators need from it | Why it matters |
|---|---|---|
| CMDB | Configuration items, relationships, and vendor inventory connectors | Impact assessment is guesswork without a trustworthy asset picture |
| Device bridge | Endpoint state from Relay attached to the tickets that reference those devices | Agents should see the device without opening a second product |
| Problem management | A path from recurring incidents to root cause and verified fix | Firefighting the same incident monthly is a process failure, not bad luck |
| Known-error database | Documented workarounds attached to open root causes | A known error with a workaround turns a crisis into a lookup |
| Knowledge base | Articles that deflect tickets at intake and speed up the ones that arrive | Every deflected ticket is capacity returned to the team |
| XLA scorecard and reporting | Experience measures alongside SLA compliance | An SLA can be green while requesters are miserable; the XLA notices |
What operators are actually managing
- Keep the CMDB current enough that change and incident work can rely on it.
- Use the device bridge so endpoint context arrives with the ticket, not after it.
- Turn recurring incidents into problems with an accountable owner.
- Capture knowledge at the moment of resolution, then measure what escaped capture.
- Read the XLA scorecard alongside SLA reports and act on the gap between them.
What this public manual area includes
- Problem management, the known-error database, and knowledge authoring.
- The knowledge capture loop from resolution to deflection to review.
- Reporting, dashboards, workload views, and the XLA scorecard in the administration console.
What healthy operation looks like
- Configuration data answers impact questions faster than tribal memory does.
- Recurring incidents shrink because their root causes get owned and fixed.
- Knowledge deflects tickets before they reach an agent, and the team can prove it.
- Leadership reads experience measures, not just breach counts.