This documentation supports the 25.1 version of BMC Helix ITSM: Service Desk.To view an earlier version, select the version from the Product version menu.

Resolving an incident with an emergency change request


This user scenario describes how to resolve an incident request with an emergency change request. Incident Management and BMC Helix ITSM: Change Management must be installed to follow this user scenario.

Scenario

  1. Joe Unser, a Calbro Services benefits agent, cannot access the local area network. He contacts the Calbro Service desk, and Francie Stafford, a service desk analyst, creates an incident request.
  2. The incident request is assigned to Ian Plyment, a specialist in the support group assigned to Joe's company. Ian determines that Joe's data port is broken, and an emergency change is required to restore Joe's service.
  3. Ian contacts Allen Allbrook, the owner of the service, to let him know that an emergency change is required. Allen assesses the risk and authorizes Ian to perform the work.
  4. Ian then replaces Joe's data port and documents his actions in the incident request. Ian verifies with Joe that he can now access the local area network.
  5. Ian closes the incident request and notifies Mary Mann, the change coordinator, of the emergency change so she can register the change. This ensures everyone can see what was changed, should the emergency change cause other incidents to occur. It also ensures that BMC Helix CMDB is updated.

Workflow

The following table describes the typical steps involved in this user scenario:

User

Actions

Explanation

Reference

Service desk customer

The customer contacts the service desk.

Joe cannot access the local area network.

NA

Service desk analyst

Francie Stafford receives Joe's call and creates a new incident request record from the applicable template.

Specialist

Ian Plyment, a specialist investigates Joe's incident request and determines that his data port is broken. The fix requires an emergency change.

Specialist

After the change is implemented and verified, Ian closes the incident request and asks Mary Mann, the change coordinator, to register a change for this emergency change.

Change coordinator

From Joe's incident ticket, Mary creates the emergency change request from the incident request,

This step saves time, ensures accuracy and relates the incident with the change request.

To register an incident request

  1. On the Incident console, the service desk analyst, Francie registers the incident request record.
  2. Francie uses Incident Matching to search for a solution.
  3. When Francie does not find a solution, she completes the incident request registration and saves the record.
  4. The incident request is assigned to an assignment group as specified in the template.

To accept the assignment

  1. On the Incident console, Ian searches for incident requests that are assigned to his support group.
  2. Ian opens the Joe's incident request and assigns it to himself. In the work details, the specialist specifies that the incident request is being handled according to the emergency change protocol.
  3. Ian contacts Allen Allbrook, the owner of the affected service, to tell him this incident request requires an emergency change. 
  4. In the Work Detail tab of the incident request, Ian notes that he contacted Allen.
  5. Allen analyzes the risk and impact of the emergency change request and then authorizes Ian to implement the emergency change.

To resolve incident and register a change

  1. Ian implements the change and records all work in the incident request.
  2. He contacts the customer to verify that the affected service has been restored.
  3. Ian closes the incident request and asks Mary Mann, the change coordinator, to register a change request for this emergency change.
    By registering a change request, all stakeholders can keep a track of what was changed in case the emergency change causes incidents to occur. This action also makes sure that Allen, the service owner, is informed and BMC Helix CMDB is updated.

To create an emergency change

  1. From the Incident form, Mary creates a change request. 
  2. From the Quick Actions area, Mary clicks the arrow beside Create Related Request and selects Infrastructure Change.
    This opens the Change Request form and copies information from the incident request record to the change request record.
    A relationship is created between the change and the incident. 

Result

Joe can access the local area network. 

Benefits

  • The incident is recorded to help service desk analysts resolve similar incidents.
  • All actions pertaining to the emergency change are added in the incident request, in case any issues occur. This helps all stakeholders keep a track of the changes done for incident resolution.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*