Assets and services

Each asset has an asset tag, optional serial number and location, a status, and a required service link. The service has its own name, criticality, status and owner. Together they give the Patch Operator enough context to select the intended equipment and give the Service Owner a way to understand why patch work matters. A patch attempt points to the asset; it can therefore be read alongside the service attached to that asset.

Asset status distinguishes in stock, Assigned, Maintenance and Retired equipment. The team should check status before planning an attempt. An assigned asset may be in active use, while a retired asset needs a different decision. The status alone does not establish whether a particular patch is installed; that outcome belongs to an attempt linked to the asset and patch.

• Equipment identity. Asset tag and serial number help staff select the right physical or virtual item.
• Service context. The required service link connects the item to criticality and a named owner.
• Lifecycle state. Asset status helps the team distinguish active work from maintenance or retirement.

Agree the source of asset tags and how the team handles a replacement device. Decide who maintains the service link when equipment moves between operational uses. Service Owners should review criticality and ownership before patch planning starts, especially where a change window depends on service importance. Imported inventory records need their asset tags and service links checked before operators create attempts against them.

For example, a service may have two assigned assets at different locations. The same patch can have a successful attempt on one and a failed attempt on the other. The service link helps the owner review both results together without collapsing them into one installation state. If a failure causes disruption, the incident record can point to the same asset and service.

Pick one assigned asset and verify its tag, location and service owner. Have the Patch Operator use that asset in a scheduled attempt and ask the Service Owner to find the result from the service context. Then choose a maintenance asset and confirm the team makes an intentional planning decision before installing. Review a retired item to ensure its old attempt history remains understandable.

Check a change involving the same service. Its scheduled window and rollback plan should be reviewed in the context of service criticality. The asset, change and attempt do different jobs: inventory identity, service decision and actual patch result. Keep each record current so the next operator can trace the chain.

• Active service assets — Find assigned and maintenance equipment with its service and location.
• My services — Review the services assigned to the current owner and their criticality.

Select an asset for patch work and review service impact.