1. Data Center Management
  2. Features
  3. Service and asset context
Feature · Service and asset context

Service and asset context

Connect service ownership, equipment, location and operating state.

OverviewIncident intake
Data Center Management · Service and asset context

Incident intake

Investigating waits for the service manager

New
SummaryPriorityServiceAssetAssigned toOpened at
SMM-265LowSRV-5870ASS-4763016 Oct
SMM-654MediumSRV-1279ASS-5737011 Oct
SMM-766HighSRV-8508ASS-1011713 Oct
SMM-370CriticalSRV-1546ASS-8298725 Oct
SMM-870LowSRV-6556ASS-7377113 Oct
6 of 6 records
SMM-265Incidents · INC-92420
Low
ServiceSRV-5870
AssetASS-47630
Opened at16 Oct
Example screen with sample data

What you can do

Know what a piece of equipment supports

Begin with the service that operations is responsible for. The Service Manager records its name, owner, criticality and current state. The Asset Manager then attaches each equipment record to the service and gives it a stable tag, serial number where available, location and state. When a technician opens an incident, the same service and asset links show what work is affected. They also provide context when a rack observation is entered for that asset.

A location is useful only when the team agrees how it is written. One operator may use a room and row; another may use a site code. Pick the convention before importing equipment so that two spellings do not split the working inventory. Keep the tag stable when equipment changes state. Retiring an asset should not erase the incident history that names it.

How the work is organized

The Service Manager owns service context; the Asset Manager keeps the equipment register current.

  • Service ownership. A named person is linked to each service record.
  • Equipment identity. The asset tag stays with the equipment through its operating states.
  • Affected work. Incident records link the service and asset involved in the response.

What to agree during setup

Decide who may change a service’s criticality, when a service enters maintenance and how retired services are kept for history. Agree on asset tag format and the meaning of each asset state. Decide how location text maps to the rack code used in a rack position. Import people and services before attaching assets so that required references can be checked immediately.

Check the handoff on an actual case

A technician receives a report about a service in maintenance. The Service Manager confirms the service owner and its criticality. The Asset Manager finds the tagged equipment at its recorded location and confirms that it is assigned, rather than in stock. The Incident Coordinator creates an incident linked to that service and asset. The next responder sees the same equipment identity in the incident and can inspect its rack position before going to the floor.

Rehearse the awkward case as well: a replacement asset has a new tag but the old serial number was copied by mistake. Resolve the equipment identity before moving the incident to the new asset. Keep both records traceable to the service.

What your team sees

  • Asset inventory — Equipment grouped by operating state, with tag, location and service.
  • Open incidents — Current disruptions linked to the affected equipment.
  • Rack positions — Recorded rack code and power for the selected asset.

What it keeps track of

Data model
Services
Services for data center operations.
Assets
Assets for data center operations.
People
People for data center operations.
Incidents
Incidents for data center operations.
Rack positions
Rack Positions for data center operations.

Who uses it

Permissions
Service Manager
, Asset Manager, Incident Coordinator, Service Technician.
The manager owns the service; the asset manager maintains equipment identity.

Set up Data Center Management your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started