Assets and receipts

An asset has a tag, serial number, location, current state and service link. An incident can point to the asset it affects. That link helps the investigator move from a customer-facing interruption to the relevant equipment or managed item. The asset record is a practical operating reference: Assigned and Maintenance mean different things when the team is looking for a cause, and Retired equipment should not be chosen casually for a new issue.

The service owner and incident coordinator should agree what an asset represents in this operation. A physical appliance, a managed endpoint or a logical service item may each be useful, but the tag must identify one actual working record. Keep serial number and location current enough for an on-duty investigator to find the item. An incident summary should still describe the customer effect; the asset link supplies supporting context.

• Inventory context. Tag and locate the item connected to a service.
• Incident reference. Link the affected asset when opening an interruption.
• Receipt review. Inspect provider, external event identifier, time and outcome.

Decide who maintains asset state and when Assigned becomes Maintenance or Retired. Define how new assets are registered so two similar tags cannot confuse incident response. Choose which external events should create integration receipts and which provider identifiers the team will retain. Receipt status has Received, Applied, Rejected and Failed values; agree who reviews exceptions and where the underlying provider event can be inspected.

An integration receipt is evidence of an event’s handling outcome. It does not by itself say that a public update was approved or delivered to a customer. When a receipt fails, the administrator needs the provider and external event identifier to investigate without guessing from a generic error label. A payload hash helps compare repeated or disputed deliveries during that investigation.

An alert points to a gateway associated with the customer portal. The coordinator opens an incident and links the gateway asset. The asset record shows its location and that it is Assigned to the relevant service. The investigator can check the gateway while the service owner reviews the public component state. If the gateway is taken out for repair, the asset state can become Maintenance without treating that as the incident’s resolution.

If a provider event is connected, the admin reads its receipt, provider name, external event identifier and received time. If the receipt is Failed, the admin investigates the original event and checks whether a later receipt was Applied. The incident coordinator still bases the incident’s status and resolution time on the actual service behavior. This separates an integration outcome from the customer effect it may have reported.

• Asset register — Find an item by tag, location, state and service.
• Open incidents — Find the incident that identifies the affected asset.
• Receipts needing attention — Review rejected and failed provider events.

Begin with incident response and review integration receipt handling. Agree on external event sources in integrations.