Service Oversight

Service Overview shows scoped incident distribution by current state and a recent evidence queue. The service catalogue records each service’s name, criticality, owner and current status. Together, those views help the team decide which interruption needs attention and who can answer for the affected service. The underlying incident, outage and impact records carry the case detail.

An outage entry records when a site or device stopped and when it was restored. An impact entry records whether service was delayed or unavailable and can hold a workaround procedure. An integration event retains the source system, external event identifier, receipt time, payload hash and outcome. These records provide different forms of evidence; they should be read in their own context rather than treated as interchangeable alerts.

• Service ownership. Keep each service’s owner, criticality and operating status current.
• Interruption evidence. Tie impact and outage records to the incident they describe.
• External receipts. Review integration events by source and outcome when an inbound update needs attention.

Agree which services belong in the catalogue and who may change their criticality or status. A service marked active should have an owner who can respond to an interruption. Decide when an outage record is needed and how site and device identifiers are entered. Set the rule for recording restoration time once service returns, so the outage register remains useful in review.

External sources need their own connection and receipt mapping. Agree which source owns each event identifier and who examines a rejected or failed receipt. The status of a receipt describes ingestion of that event; it does not replace the status of an incident or service request.

A shared service degrades at a site. The Incident Responder opens the service record to check ownership and criticality, then records the incident and its impact as delayed. If a device becomes unavailable, add an outage entry with its site, device and start time. The service owner can review the impact and workaround while the responder investigates. At restoration, fill in the outage end time and the incident resolution.

Separately, an external source sends an event for the same operating period. The Admin checks its receipt status and external identifier. A rejected receipt goes to the receipt queue for review. The team should be able to explain both what happened to the service and what happened to the inbound event without confusing one record for the other.

• Service Overview — Incident distribution by current state and a recent evidence queue.
• Unresolved Service Outages — Outages waiting for a restoration time.
• Rejected Integration Events — External receipts that need a source or mapping review.

Review incident response for the interruption and asset and service context for the device dependency.