Overview
  • 12 Dec 2024
  • 2 Minutes to read
  • PDF

Overview

  • PDF

Article summary

The role of an Analyst in creating a Work Order within an ITSM (Information Technology Service Management) application involves several key responsibilities to ensure accurate and efficient reporting of incidents or service requests. The role of an Analyst in creating a Work Order is crucial for initiating the incident management or service request process. By providing accurate information, collaborating with the IT support team, and actively participating in the resolution process, Analysts contribute to efficient IT service delivery and overall organizational productivity.

The following flowchart provides insights into Work Order functionality:

IT Service Management Process Flow with Work Order

The following information is the Description of the above Flowchart Diagram:

This diagram illustrates the interconnected processes involved in IT service management, including service requests, changes, incidents, and work orders. The flow starts with various initiations such as service requests by users or analysts, change requests, incidents reported by end users or analysts, and work orders created by analysts. Each process follows a fulfillment or execution path and concludes with either resolution or closure. Key components include decision points and potential linking between different processes.

IT Service Management Operational Procedures

Begin with any process initiation such as Service Request, Change, Incident, or Work Order.

Service Request Procedure

  1. End User or Analyst creates a Service Request through the Service Catalog.

  2. Fulfillment Request is processed by creating a Work Order.

  3. Complete the Work Order and resolve the Service Request.

  4. End the event.

Change Procedure

  1. End User or Analyst creates a Change Request or Change Record.

  2. Fulfill the Change Request by creating a Work Order.

  3. Execute and complete the Work Order and close the Change Record.

  4. End the event.

Incident Procedure

  1. End User or Analyst logs an Incident.

  2. Request Fulfillment is initiated by creating a Work Order.

  3. Complete the Work Order and resolve the Incident.

  4. End the event.

Work Order Procedure

  1. Analyst creates a Work Order.

  2. Execute the Work Order.

  3. Complete the Work Order.

  4. Close the Work Order.

  5. End the event.

Linking Procedures

Link the Work Order to Service Request, Incident, Change or another Work Order as required.

Use Case

Solution

Amy a new employee has onboarded Novatech Company and HR has initiated the onboarding process through a Service Request. In the middle of the process there is a request fulfillment of Laptop allocation and the asset is not in stock at the current location.

Maxwell the Analyst creates a Work Order with Urgency as High and Priority as P2. The Work Order is assigned to the Asset Team to review and procure the Asset at the earliest.


Was this article helpful?

What's Next
Changing your password will log you out immediately. Use the new password to log back in.
First name must have atleast 2 characters. Numbers and special characters are not allowed.
Last name must have atleast 1 characters. Numbers and special characters are not allowed.
Enter a valid email
Enter a valid password
Your profile has been successfully updated.