Helpdesk Userguide
Helpdesk Userguide
5
User’s Guide
June 2003
Part No: HD-550-UG-01
Copyright 2003 BMC Software, Inc. All rights reserved.
Remedy, the Remedy logo, all other Remedy product or service names, BMC Software, the BMC Software
logos, and all other BMC Software product or service names, are registered trademarks or trademarks of
BMC Software, Inc. All other trademarks belong to their respective companies.
Contacting Remedy
If you need technical support for this product, or would like to request documentation for a product for
which you are licensed, contact Remedy Customer Support by email at [email protected]. If you have
comments or suggestions about this documentation, contact Information Development by email at
[email protected].
This edition applies to version 5.5 of the licensed program.
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Related Remedy documents . . . . . . . . . . . . . . . . . . . . . . 10
Contents ! 3
Remedy Help Desk 5.5
4 "Contents
User’s Guide
Contents ! 5
Remedy Help Desk 5.5
6 "Contents
User’s Guide
Contents ! 7
Remedy Help Desk 5.5
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
8 "Contents
Preface
The Remedy Help Desk 5.5 User’s Guide describes how to use the Remedy®
Help Desk 5.5 application. Remedy Help Desk is one of four Remedy IT
Service Management applications. The others are Remedy® Asset
Management, Remedy® Change Management, and Remedy® Service Level
Agreements.
Audience
This guide is intended for the requesters who use Remedy Help Desk to
request assistance or services, the IT professionals who use Remedy Help
Desk to respond to those requests, and the managers who oversee the
operations of the IT organization. More specifically, IT professionals include:
! Frontline and backline support technicians, who use the application to
create new requests for help or services.
! Support staff and managers, who use the application to resolve help desk
cases and change requests; create asset records; and view relationships
among help desk cases, change requests, and asset records in a networked
environment.
! Managers, who monitor the daily operations of the IT organization, and
use the application to track the support staff’s performance on resolving
help desk cases, and manage requests that are escalated, or requests to be
reassigned.
Preface ! 9
Remedy Help Desk 5.5
Remedy Service Level Agreements Procedures for using the Remedy Everyone PDF
User’s Guide Service Level Agreements
SLA-550-UG-01 application; includes new features
overview.
Remedy Approval Server Guide for Procedures for installing and Everyone PDF
User and Administrators administering the Approval
ARAS-510-UAG-01 Server, connecting an AR System
system application to the
Approval Server, setting up
approval processes and rules, and
approving requests.
Remedy IT Service Management Procedures for installing and Administrators Print and PDF
Installation and Configuration configuring the four
Guide Remedy IT Service Management
ITSM-550-ICG-01 applications: Help Desk, Change
Management, Asset
Management, and Service Level
Agreements.
Remedy IT Service Management Procedures for using the Remedy Everyone Help link
Online Help Help Desk, Change Management,
Asset Management, Service Level
Agreements, nd Configuration
Manager.
Action Request System Concepts Overview of the AR System Everyone Print and PDF
Guide architecture and features with in-
AR-510-CNTG-01 depth examples; includes
information about other Remedy
products.
10 "Preface
User’s Guide
12 "Preface
Chapter
The following topics introduce you to the Remedy Help Desk application
and to the business model on which it is based.
! “About Remedy Help Desk” on page 14
! “What’s New in Remedy Help Desk” on page 15
! “Remedy Help Desk business models” on page 16
! “Using Remedy Help Desk” on page 19
! “Other Remedy applications” on page 23
Requester role
Requesters who need technical support can contact the support organization
by telephone, email, and by submitting requests directly into the Remedy
Help Desk application on their desktops through either the Windows client
or the web.
Requesters can also request services that are planned by support staff.
Support role
Support staff members provide services to their customers, such as helping
to resolve problems and implementing change requests. To do this, support
staff members work with help desk cases and change requests. When a person
or group is assigned to a help desk case or a change request, a member of the
support staff accepts responsibility for the help desk case or change request
until it is either resolved or reassigned.
As support staff members work on help desk cases and change requests, they
can access asset inventory information that enables them to resolve help desk
cases and change requests. For example, a support staff member might need
a user’s asset configuration information to help troubleshoot the user’s issue.
The staff member can verify when an asset was last updated. This
information might be applicable to the cause for the case.
Manager role
Managers oversee the operation of the IT organization. This role includes
performing daily management activities (such as handling escalations and
approving solutions) and tracking performance measurements for support
staff, based on requesters’ completed surveys.
Managers can run reports on help desk cases, on change requests and tasks,
and asset inventory records. These reports enable them to plan resources and
to identify trends in the types of upcoming cases, change requests and tasks,
and asset records that warrant further investigation.
Administrator role
The application administrator oversees the operation of the Remedy Help
Desk application and all of its modules. Administrators have full and
unlimited access to the application and are responsible for configuring data
in applications to contain custom entries such as:
! Categorizations
! Locations
! People
! Groups
! Skills
For information about the administrator’s role and tasks, see the
Remedy IT Service Management Installation and Configuration Guide.
The following sections describe the activities you can perform with the three
modules within each role.
Common features
Many features are common across the Help Desk, Change Tasking, and Asset
Inventory modules. These include shared resource management features and
common management tools in each module.
Resource management
All Remedy Help Desk modules share the following resource management
functions:
! Common databases of people and groups—These databases store
requester information and information about the support staff groups
and individuals.
! Automatic group assignment—The Help Desk and Change Tasking
modules automatically assign new cases, change requests, or tasks to
support staff members or groups based on categorization, location,
availability, and the corresponding responsibilities associated with the
support staff members or groups.
! Master work schedule—This schedule defines the IT organization’s
business hours and holiday schedule; for example, for use in escalations.
Management tools
All Remedy Help Desk modules provide the following management tools:
! Management view table—From the IT Service Management Console,
managers have convenient access to escalated requests, reassignment
requests, solutions awaiting approval, and urgent requests.
! Integration between Help Desk, Change Tasking, and Asset Inventory—
Managers and support staff can track related cases, change requests, and
asset records within their organization.
! Integration with Crystal Reports—Managers and support staff can
generate and view a variety of predefined summary and detail reports
through the Crystal Reports engine.
! Automatic escalation—Managers are notified of cases or change requests
open beyond a predefined length of time. The information includes the
severity of the case or change request and who requested it.
! Preferences—Support staff and managers can customize the actions for
their modules. For example, they can specify what form appears when they
begin creating a request.
The procedures in the following sections describe the tasks you can perform.
4 Click Login.
A new window appears, prompting you to select the Requester Console.
2 In the Urgency field, select the urgency level of this request. Options are Low,
Medium, High, and Urgent.
3 In the Summary field, select a predefined summary by clicking the arrow to
the right of the field, or enter your own brief summary.
If one or more solutions are available based on what you enter in the
Summary field, they are listed in the Possible Solutions table. If a listed
solution appears to meet your needs, you can use that solution to resolve the
case yourself. For more information, see “Resolving help desk cases on your
own” on page 33.
4 The summary you choose also determines whether the Requested Date field
is displayed. If it appears, it will be in the upper right area of the form. Enter
the date by which you need the request fulfilled, or click the button and select
the date from the calendar that appears.
5 In the Details field, enter a more detailed description about the request.
For example, when creating a help desk case, describe the steps you took
before the problem occurred.
6 Click Save to submit the request.
A message is displayed that specifies the individual or group from the support
staff who are assigned to the request.
7 Click OK to dismiss the message.
Another message reports that the request has been submitted.
The prefix of the request ID number indicates whether a help desk case or a
change request was created:
! HD indicates a help desk case.
! CHG indicates a change request.
8 Click OK to dismiss the message.
If the solution appears to meet your needs, you can use it to resolve the case
without the assistance of the support staff, as outlined in step 7.
6 Click Close to return to the Possible Solutions table in the New Request form.
7 If you decide to use a solution:
a Select the solution from the list, and click Use Solution.
A message reports that the request will be marked as Resolved when the
request is saved.
b Click OK.
c Save the request.
A message reports that the case has been submitted.
8 If you decide not to use a solution, enter the appropriate information for the
case, and click Save to submit it, as described in “Creating new requests” on
page 31.
You can view status details and other information for the request:
! The top region of the request form provides a general description of the
case, the case type, status, and escalation information.
! The Requester Information tab displays data about the requester. The
Source field specifies how the request was originated—by the requester,
by phone, by email, or from the web.
When you are finished viewing the details of the request, click Close to return
to the Remedy IT Service Management Console.
Modifying a request
You can modify a request only if you created it, or if a support staff member
created it with you as the requester. You cannot modify requests submitted
by others. In addition, you can modify only those fields to which you have
write access, such as the description. If you try to make changes to a field to
which you do not have access, a message informs you that you do not have
access permissions for that field.
Printing a request
You can print an image of a request in its form, or you can print a report of
the data in the request.
If you are not satisfied with the resolution, you can reopen the request. The
request’s status changes to Assigned, and the assignee is notified.
If you do not close or reopen the request, it will be closed automatically after
the time interval specified by the administrator. For example, your
application might be configured to close resolved requests automatically
after 15 days.
You can modify only those requests you have created, or those created by
support staff with you as a requester. In addition, your administrator must
verify that the AR System server is configured to enable you to modify
requests without a write license.
! For change requests, the Confirm Resolution is in the lower right portion
of the form.
The Status field is changed automatically to Close when you modify the
request.
4 Click Close to return to the Remedy IT Service Management Console.
5 Click Save.
If there are no closed help desk cases, a message reports that you have no
surveys to fill out.
If one or more resolved help desk case have automatically changed to
Closed, or if a support staff member has closed one or more help desk
cases, a list of cases is displayed. Select a case, and click Respond. The
Survey form is displayed.
If you cannot access the survey, contact your administrator.
2 In the Survey form, enter or select a number (1 to 10) in each of the Rating
fields to indicate your degree of satisfaction. Typically, 1 is the lowest rating
and 10 is the highest.
In Windows, you can use the spinner buttons (the up and down arrow
buttons to the right of the Ratings fields) to increase or decrease the rating
number in the field.
3 Optionally, enter any comments in the Comments field.
4 Click Save.
3 If the Detailed Description field does not fully display the text, click the
ellipses button (...).
If the message contains an attachment, you can view it or save it to disk.
Using reminders
Reminders enable you to create notes for yourself and others. You can send
them by email or by AR System Alert, and you can specify when they will be
sent.
You can create generic reminders, or you can create reminders that are
associated with a specific request. For example, you can send yourself a note
about a specific help desk case to remind yourself to follow up on the
problem.
3 In the Link to Request ID field, enter the request ID with which you want to
associate the reminder.
If you opened the Reminders dialog box from within a request, this field is
automatically filled in with the appropriate request ID. You can delete the
request ID if you do not want to associate the reminder with this request.
4 In the Form field, enter the form name with which you want to associate the
reminder. This indicates whether the reminder pertains to a help desk case or
a change request.
If you opened the Reminders dialog box from within a request, this field is
automatically filled in with the appropriate form name. You can delete the
form name if you do not want to associate the reminder with this form.
5 Select one of the following notification methods from the Notification field:
! Alert sends the reminder through AR System Alert. You must fill in the AR
Login field to use this notification method.
! Email sends the reminder by email. You must fill in the Email field to use
this notification method.
! User Default sends the reminder based on the notification method
specified in the user’s profile.
Using reminders ! 45
Remedy Help Desk 5.5
6 By default, the Time field contains the current date and time. Change this to
the time that you want the system to send the reminder. You can enter the
time, or click the button next to the field and select the time from the
calendar that appears.
7 In the Notify option fields, select Individual or Group.
8 In the Person or Group field, enter the name of the person or group you want
to notify.
If you do not know the name, you can perform a search. For more
information about searching for a person’s record, see “Searching for a
person’s or group’s record” on page 48.
9 To view more detailed information about the person or group, click Profile.
The Person Information or Group Information dialog box is displayed. You
cannot make changes in this dialog box. When you have finished reviewing
it, click Close.
10 In the Subject field, enter information about the reminder.
The information in this field appears in the subject line if the reminder is sent
by email.
11 Enter the reminder message in the Message field.
Note: Do not enter anything in the Log field. This field records the subject
line and text of the reminder when it is sent.
12 Click Save.
The reminder will be sent at the time you specified.
2 In the Show Reminders field, select the set of reminders that you want to
view. Options are All, Pending, and Sent.
The reminders are displayed in the table.
3 Select a reminder, and click View.
The Reminder Details dialog box is displayed.
4 Update the reminder as needed, and click Save.
Note: If the reminder you selected was already sent, it is not saved. You will
need to create a new reminder.
Using reminders ! 47
Remedy Help Desk 5.5
1 In the Create Reminders tab, select the appropriate topic in the Notify field.
2 Place the cursor in the Person or Group field, and press Enter.
The top portion of the form provides general information about the group
or person. The tabs in the bottom portion of the form provide additional
contact, pager, address, and cost center information.
In Windows, you can also right-click anywhere in the table and select an
option from the menu.
! Refresh Table loads the latest data into the table. The administrator can set
a limit on how many records are loaded into the table. The status bar of
the main window indicates how many records are loaded.
! Refresh All in Table loads the latest data into the table and overrides any
limitations the administrator may have set on how many records can be
returned. Note that if a large number of records are returned, your server’s
performance may be slower.
! Clear Table removes the table data. To view any new data, click in the
table.
If necessary, use the scroll bar at the right to scroll through the entries in the
table.
To view the details of a request in the table, select the request, and click View.
Note: Requests processed using the Help Desk module are referred to as help
desk cases. Change Tasking requests are referred to as change requests. Asset
inventory requests are referred to as asset records. When referring to help
desk cases, change requests, and asset records in general, they are called
requests.
Using the Remedy Help Desk Support application, support staff can perform
the following tasks:
! Create, update, and resolve help desk cases and change requests
! Search for and view assigned help desk cases and change requests
! Create and look up potential solutions to help desk cases
! Create change tasks
! Create asset and component records
! Relate help desk cases, change requests, and assets
! Track requester information
! Create and send reminder messages to groups or people
! Create and view bulletin board messages
! Set personal preferences
! Generate reports
Change requests
A change request is a request for a planned activity implemented by the
support staff. Changes can affect an individual, a group of people, or an
entire organization. Change requests often comprise many activities that are
identified as change tasks.
Change tasks
A change request can involve multiple change tasks that must be
coordinated. The change supervisor assigns these tasks to task implementors.
For example, the task of installing new word processors for an entire
organization might involve:
! Verifying that everyone has the necessary hardware and software installed.
! Ordering the software.
! Performing the actual installation.
Each change task can be tracked and monitored separately from the other
change tasks. For example, different task implementors can be assigned to
work on different tasks, and the task work logs contain information relevant
to the task. The overall change request monitors progress of the tasks.
For example, if you are a change supervisor who has received a request to
install new word processing software for the Sales department, you can log
the change request using either of the following methods:
! You can track the change request as an individual item. You might use this
approach if your organization is small and each change supervisor is
responsible for the entire change request.
! You can create multiple change tasks for a change request if your
organization is large or cross-functional and support staff members have
more specialized responsibilities. For instance, under the software
installation change request, you could specify two separate change tasks:
one task to purchase the software, and one task to install it.
If a change task involves work to be done by an outside vendor, you can also
specify the vendor information using the Work Order field on the Change
Tasking form. Selecting Yes in this field enables a Work Order tab, in which
you can enter address and contact information for the vendor doing the
work.
Change supervisor
After a change request is created by a requester or a frontline support staff
member, the request is automatically assigned to the appropriate change
group or supervisor, based on the organization’s support staff groupings.
Supervisors are notified of changes assigned to them by email, paging, or
AR System Alert.
A change request is resolved when all of the tasks are closed. The requester is
then notified that the change request is resolved.
Task implementors
Task implementors are support staff members who perform the tasks
associated with a change request.
When a change supervisor assigns change tasks, the task implementors are
notified of tasks assigned to them by email, paging, or by AR System Alert.
After a task is assigned, task implementors can log their progress as they
complete the task.
Levels of assets
The Asset Inventory module provides two levels of assets:
! Main asset (an asset record)
! Asset component (a component record)
Main asset
You can track an asset through a single asset record, or you can create a
record for the main asset with component records. For example, you could
have a workstation with a monitor and an internal hard disk drive installed.
You could inventory the entire workstation as one asset.
Asset component
An asset component is a subset of a main asset. For example, if you have a
workstation with a monitor and an internal hard disk drive, you could
inventory the workstation as the main asset, and the monitor and disk drive
as components of the main asset.
The following procedures outline how to access and use the Remedy IT
Service Management Console in the support role.
You can now work on your requests as a member of the support staff.
In the Assigned Requests table, the first characters in the request ID indicate
the type of request:
! HD identifies Help Desk cases.
! CHG identifies change requests.
! TSK identifies change tasks.
4 Click Login.
A dialog box appears, prompting you to select a console.
5 Select Support Console.
6 The Remedy IT Service Management Console is displayed.
Other
! Reports
! Reminders
! Preferences
! Help
! Logout (web only)
New Request
Click New Request to create a new request. The form that opens depends on
how you have set your New Request Action preferences. See “Setting
personal preferences and options” on page 66 for more information.
Search Task
Select Search Task to search for existing change tasks.
Track Assets
Select the Track Assets to display the Track Asset Information dialog box,
from which you can create and search for assets and components.
Reports
Select Reports to generate predefined reports on help desk cases, change
requests, and asset records. You can view reports with the built-in
Crystal Reports viewer. For more information about reporting, see
“Working with reports” on page 191.
Reminders
Select Reminders to create and display reminders. Reminders are sent by
email or via AR System Alert.
Preferences
Select Preferences to select options for specifying the form that will open
when you create or search for a request, and for specifying paging criteria (if
your application is configured for paging).
Help
Select Help to display online help.
2 Click Profile.
" To set New Request and Search for Request Action preferences:
1 From the Remedy IT Service Management Console, select Preferences.
The Setup Personal Preference dialog box appears. The General tab is
displayed by default.
2 In the New Request Action field, choose one of the following options. The
option you choose determines what form is displayed when you click New
Request on the Remedy IT Service Management Console:
! Open Front Line Support Dialog—A generic New Request form opens.
You can use this form to submit both help desk cases and change requests.
It has fewer fields to fill in than the New Help Desk Case and New Change
Request forms, and it can be used by frontline support staff to quickly log
callers’ requests of either type.
! Open Help Desk Module—A New Help Desk Case form opens. This
option is useful if you work only with help desk cases and do not usually
work with change requests.
! Open Change Tasking Module—A New Change Request form opens.
This option is useful if you work only with change requests as a change
supervisor or as a change implementor, and do not usually work with help
desk cases.
! Open Selection Dialog—A selection dialog box opens. You can choose to
open either a New Help Desk Case or New Change Request form. This
option is useful if you regularly work with both help desk cases and change
requests.
3 In the Search For Request Action field, choose one of the following options.
The option you choose determines what form is displayed when you click
Search for Request on the Remedy IT Service Management Console:
! Open Help Desk Module—A Search Help Desk Cases form is displayed.
This option is useful if you work only with help desk cases and do not
usually work with change requests.
! Open Change Tasking Module—A Search Change Requests form is
displayed. This option is useful if you work only with change requests as a
change supervisor or change implementor and do not usually work with
help desk cases.
! Open a Selection Dialog—A selection dialog box is displayed. The dialog
box presents the choice to open either the Help Desk module or the
Change Tasking module. This option is useful if you regularly work with
both help desk cases and change requests.
4 Click Save.
A message reports that the preference has been saved.
5 When you have finished setting preferences, click Close.
4 Under When to Send Page, select an option to specify when you will be
notified:
! Always? notifies you whenever a help desk case or change request is
assigned to you, regardless of priority.
! For Escalated Calls? notifies you whenever a help desk case or change
request is assigned to you and has been escalated.
! For Hotlists? notifies you whenever a VIP creates a request that is assigned
to you.
5 If you have selected For Escalated Calls? or for Hotlists?, specify the
minimum priority a request must have for you to be paged. For example, if
you set the priority to Medium, you will be paged for all requests with
priority Medium or higher.
6 Click the Change Tasking tab, and select the Paging Type and Paging Criteria
options for the Change Tasking module.
The Paging Type and Paging Criteria options are the same as for the Help
Desk module, described in the previous steps.
7 Click Save.
A message reports that the preference has been saved.
8 Click OK to dismiss the message.
9 When you have finished setting preferences, click Close.
If you are using the Remedy IT Service Management Console, or if you are
using the web, the default form view is already set for you. If you do not use
the Remedy IT Service Management console and you access forms directly in
the AR System User Tool, you can set the default form view in Options dialog
box.
Use the following procedure to set the default form view if you access forms
directly in the AR System User Tool instead of through the Remedy IT
Service Management Console. This procedure applies to Windows only. For
detailed information about customizing other options, refer to AR System
User Tool Help.
3 In the Default Form View field, enter the name of view that you want to
appear when the application is started:
If the message incudes an attachment, you can view the attachment and save
it. For more information, see “Viewing and saving attachments in Bulletin
Board messages.”
2 When you are finished viewing the message, click Close.
3 Click Close to close the Bulletin Board, if applicable.
Using reminders
Reminders enable you to create notes for yourself and others. You can send
them by email or by way of AR System Alert, and you can specify when they
will be sent.
You can create generic reminders, or you can create reminders that are
associated with a specific request. For example, you can send yourself a note
about a help desk case to remind yourself to follow up on the case.
You can modify or delete only reminders that you have created.
3 To associate the reminder with a specific request, enter the request ID with
which you want to associate the reminder.
If you opened the Reminders dialog box from within a request, this field is
automatically filled in with the appropriate request ID. You can delete the
field ID if you do not want to associate the reminder with this request.
4 In the Form field, enter the form name with which you want to associate the
reminder. This indicates that the reminder pertains to a help desk case or a
change request.
If you opened the Reminders dialog box from within a request, this field is
automatically filled in with the appropriate form name. You can delete the
form name if you do not want to associate the reminder with this form.
5 Select one of the following notification methods from the Notification field:
! Notifier sends the reminder through AR System Alert. You must fill in the
AR Login field to use this notification method.
! Email sends the reminder by email. You must fill in the Email field to use
this notification method.
! User Default sends the reminder based on the notification method
specified by the administrator for that user.
6 By default, the Time field contains the current date and time. Change this to
the time that you want the system to send the reminder. You can enter a time,
or click the button next to the field and select the time from the calendar that
is displayed. To have the reminder sent immediately, enter $TIMESTAMP$.
7 In the Notify option fields, select Individual or Group.
8 Enter the name of the person or group that you want to notify in the
Recipient field.
If you do not know the name, you can perform a search:
a Position the cursor in the field, and press Enter.
The Search People or Search Group dialog box is displayed.
b Enter the search criteria in the appropriate fields.
c Click Search.
If people or groups matching the search criteria exist, their records are
listed in the table.
d In the table, select the person or group that you want to notify, and click
OK.
Using reminders ! 77
Remedy Help Desk 5.5
The fields in the Create Reminder tab are filled in with that person’s or
group’s information.
9 To view more detailed information about the person or group that you have
selected, click Profile.
The Person Information or Group Information form is displayed. You
cannot make changes in this form. When you have finished reviewing it, click
Close.
10 In the Subject field, enter information about the reminder.
11 In the Message field, enter the reminder message.
Note: Do not enter anything in the Log field. This field records the subject
line and message of the reminder when it is sent.
12 Click Save.
13 Click Close to close the Reminders dialog box.
The reminder will be sent at the time you specified.
Using reminders ! 79
Remedy Help Desk 5.5
In Windows, you can also right-click anywhere in the table and select an
option from the menu.
! Refresh Table loads the latest data into the table. The administrator can set
a limit on how many records are loaded into the table. The status bar of
the main window indicates how many records are loaded.
! Refresh All in Table loads the latest data into the table and overrides any
limitations the administrator may have set on how many records can be
returned. Note that if many records are returned, your server’s
performance may be slower.
! Clear Table removes the table data. To view any new data, click in the
table.
If necessary, use the scroll bar at the right to scroll through the entries in the
table.
To view the details of a request in the table, select the request, and click View.
2 To reverse the sort order within that column, click the column header again.
2 In the Summary field, select an existing summary for the request, or enter a
description of the issue or request.
If the contents of the Summary field match a value predefined by the
administrator, the Detailed Description, Category, Type, and Item fields are
filled in automatically. You can accept these values, or change them.
If the Solution Available! button becomes enabled, possible solutions are
available in the database for the case. For more information, see “To search
for possible solutions when creating a new case in the Generic New Request
form:” on page 104.
3 In the Description field, enter a description of the request.
" To create a new help desk case in a Help Desk Case form:
1 On the Remedy IT Service Management Console, click New Request.
The Help Desk Case form is displayed.
2 In the Summary field, select an existing summary for the request, or enter
your own description.
If the contents of the Summary field match a value predefined by the
administrator, the Detailed Description, Category, Type, and Item fields are
filled in automatically. You can accept these values, or change them.
! Category—The menu items that you can choose are determined by your
administrator. The category field is the broadest categorization of the case.
For example, case categories could include Hardware, Software, or
Network.
! Type—The menu items that you can choose are determined by your
administrator and the value you selected for the Category field. The Type
field identifies the case with more precision. For example, case types could
include Printers, Servers, or Workstations.
! Item—The menu items that you can choose are determined by your
administrator and the values you selected for the Category and Type fields.
The Item field is the most detailed of the categorization fields. For
example, case items could include product, model, or component names.
3 In the Description field, enter a description of the case.
16 In the Submitted By field, enter the name of the person who reported the
case, if different from the person actually submitting the request. For
example, a user might have reported the problem by submitting a help desk
ticket, in which case the user is also the requester. If the user reported the
problem by way of phone or email, the person who took down the
information and submitted the ticket on the user’s behalf is the requester.
17 In the Urgency field, select the urgency of the case.
The following steps are optional. To skip them, go to step 21.
18 Click the Solutions tab, and look for possible solutions. For more
information about solutions, see “To search for possible solutions when
working in the Help Desk Case form:” on page 106.
19 Click the Related Items tab to relate other items to this case.
For more information about related items, see “Working with related items”
on page 139.
20 Click the Problem Management tab to organize information about this case.
1 In the Requester Information tab of the form, click in the Login or Name
field, and enter any information you know about the individual you are
looking for, or leave the field blank.
2 Without moving the cursor from the field, press Enter.
The Search People dialog box is displayed, listing any matching records.
While creating a new request, you might find that the requester does not yet
have a record in the database. If no record exists for the requester, you can
create one using the Person Information form.
4 Optionally, fill in the other fields, including fields on the other tabs.
! The Pager tab shows information about software and parameters for
paging equipment, and contact information for this requester.
! The Address tab shows the requester’s mailing address.
! The Financials tab shows the cost accounting and cost center information
associated with the requester. The Accounting Code and cost center data
is configured by the administrator initially, but can be modified by
support staff.
5 Click Save.
A message reports that the new requester entry was created.
When a case is assigned to you, you can be notified by pager (if you have set
paging preferences), email, or notifications sent to AR System Alert. The
notification method depends on how your system is configured.
For more information about AR System Alert, see the AR System User Tool
Help.
Note: If the Category, Type, or Item information for a case is changed, and
Auto-Reassignment is enabled, the case might be reassigned automatically
to another member of the support staff. When the case is reassigned, both
the new and old assignee are notified.
When you perform a search for a case, the form that is displayed depends on
what you selected in the Search For Request field. See “Setting New Request
and Search for Request Action preferences” on page 68 for more
information. The following procedure assumes that you selected the Open
Selection Dialog option as the default Search For Request Action preference.
You can use this bar to specify complex search criteria. For detailed
information about using the advanced search bar, see AR System User Tool
Help. To access AR System User Tool Help, choose Help > Contents and
Index.
4 Click Search.
The requests matching the search criteria are displayed in the Results pane.
5 To view the details of a help desk case, click on the item in the list.
The case is displayed in the Details pane.
5 Click Search.
6 Your group’s open cases will be listed in the table below the Help Desk Case
form.
7 To view the details of a case, select it, and click View.
5 Click Search.
6 Your open cases will be listed in the table below the Help Desk Case form.
7 To view the details of a case, select it, and click View.
For example, you create a help desk case for a requester who has not received
external email for the past hour. Because this might be a more widespread
problem, you decide to look for possible duplicate cases. You look for a
recent case that might be reporting the same problem.
When you check the case details of a recent case, you discover that a case
submitted by another requester also reports the external email problem. In
this situation, you would mark the most recent case as a duplicate of the
original case.
Once you mark the case as a duplicate, you cannot update it. When the
original case is resolved, the duplicate is automatically resolved.
If you have erroneously marked a case as duplicate, you can remove the
duplicate case. This enables you to update and resolve the original case.
5 To determine whether a case is a duplicate, select the entry, and click View.
The Help Desk Case form is displayed, showing the details of the case.
The case is added to the Current Duplicate Cases list. If no duplicate cases
existed before, a new Current Duplicate Cases table is displayed.
! Click Mark Selected Case as Original to make the selected request the
original of the current case.
The case is marked as the original, and added to the Current Original Case
list. The request that you have open is marked as a duplicate, and the
upper region of the form displays the message “This is a duplicate case.”
9 Click the Activity tab, and update the Work Log.
10 If the case status in Work in Progress, update the time spent on the case.
11 Click Save.
The request appears in the Modify Help Desk Case form. The note in the
upper region of the form identifies it as a duplicate case.
5 To review the original case to verify that the two cases are not duplicates, click
View.
6 The Help Desk Case form is displayed.
7 Review the case.
8 Click Close.
9 If the two cases are not duplicates, click Remove Duplicate.
A message reports that your current case will be removed as a duplicate.
10 Click OK to dismiss the message.
11 Click Save.
You can now continue working on the case.
Solutions are made available when the Category, Type, and Item fields of a
help desk case match the Category, Type, and Item fields of an existing
solution.
" To search for possible solutions when creating a new case in the Generic
New Request form:
1 On the Remedy IT Service Management Console, click New Request.
The generic New Request form is displayed.
2 In the Summary field, select a predefined summary.
If a solution is available based on what you enter in the Summary field, the
Solution Available! button is enabled.
4 To view more information about a listed solution, select the solution, and
click View.
The Solution Details form is displayed.
If the solution appears to meet your needs, you can use the solution to resolve
the case, as outlined in step 6.
5 Click Close to return to the solutions list in the Available Solutions dialog
box.
6 If you decide to use a solution:
a Select the solution and click Use Solution.
A message reports that using this solution will resolve the request.
b Click OK.
A dialog box reports that the requester has been notified of the case’s
resolution, and that you have been notified of the case.
If you decide not to use a solution, click Close in the Available Solutions
dialog box.
" To search for possible solutions when working in the Help Desk Case form:
1 Create a new help desk case as described in “To create a new help desk case
in a Help Desk Case form:” on page 87, or search for and open an existing
case as described in “To search for a help desk case:” on page 98.
2 Make sure that you have entered valid values in the Category, Type, and Item
fields of the Help Desk Case form.
3 Click the Solutions tab.
4 Click List Possible Solutions.
The Solution dialog box is displayed, with a list of possible solutions if any
are available.
Note: The solutions listed might not necessarily be the appropriate solutions
for your case. Always review a solution to make sure that it is suitable for
the case.
If none of the solutions are suitable, you can search for solutions by changing
the Category, Type and Item fields, or clearing the fields and searching by
Keyword. If you find a solution that has different Category, Type, and Item
fields than your case, you must change the Category, Type, and Item fields
for the case.
8 If you have selected a solution, you can resolve the case:
a Update the Work Log field in the Activity tab.
b In the Status field, select Resolved.
c Click Save.
A message reports that the requester has been notified of the case’s
resolution.
9 Click OK to dismiss the message.
For example, several help desk cases have been submitted about insufficient
memory, and a change request has already been created to upgrade
everyone’s memory. The help desk cases can be related to the change request.
The asset could also be related to the change request for the memory.
When working with a help desk case, you can relate it to other cases, to
change requests, or to asset records:
! Relating help desk cases to other help desk cases—When you work with a
help desk case, you might need to create related cases that address similar
issues. A set of related cases can result from many issues reported to the
help desk by one requester at one time. A set of related cases can also result
from a single problem that encompasses several issues, which span
multiple, second-level support technicians.
! Relating help desk cases to change requests—When you work with a help
desk case, you might need to work with a related change request. For
example, if a change request for a server upgrade results in connection
problems for the people affected by the change, you can relate their help
desk cases to the server upgrade change request as you open the cases.
! Relating help desk cases to assets—When you work with a help desk case,
you might need to work with a related asset record. For example, if you are
working on a help desk case involving a monitor, you might need to assign
another monitor temporarily. You might want to relate the help desk case
to the monitor to supplement the asset’s service record.
If no related items exist for the request, the tab displays the message “No
records related to this case were found.”
4 To view a related request, select it, and click View.
5 The request is displayed.
6 When you have finished creating the new request, click Save.
A message reports that you have created a new request. Another message tells
you that the two requests have been related.
7 Click OK to close each dialog box.
The form for the new request closes.
8 If the newly related item does not appear in the Related Items table, refresh
the table manually by clicking the Refresh button.
9 Click Save.
3 In the Search for Existing Record to Relate region, select a request type from
the Record Type field.
4 Click Search.
The Search and Relate dialog box is displayed, listing the requests according
to the value in the Search with the Same field.
5 To change the search, select another value in the Search with the Same field,
or click the Advanced tab to enter additional search criteria.
6 Click Search.
The Search Results list shows the requests matching the search criteria.
7 To view more information about a request, select it, and click View.
The request’s form is displayed, showing the details of the request.
8 Click Close.
9 To relate a request, select it, and click Relate.
A message reports that the request has been related.
10 Click Save to save the case to which you were relating the other request.
If the requester does not close or reopen the case, the Help Desk module
automatically changes the status to Closed (after a predefined period of
time), and sets the Closure Code to Automatically Closed.
The response time to change the status depends on how the Remedy Help
Desk administrator configured the application module.
Note: If a help desk case has a Case Type of Problem, you must be a member
of the Problem Management group to close the case.
Disruptions can also occur without the user being aware of them. For
example, although deficiencies in data processing or faults in data
communication facilities might not be noticeable to users, they indicate
faults in the organization’s IT infrastructure.
! Problems are more serious issues that interfere with the effective
functioning of the organization. A problem is frequently manifested in a
number of related incidents and can typically be traced to an underlying
cause. Problem control focuses on establishing the cause of the problem
and eliminating it, thereby resolving the problem and preventing
additional incidents. Incidents that cannot be solved by the Help Desk
support staff should be designated as problems in the Problem
Management tab, by changing the type in the Case Type field to Problem.
! Known Errors are problems that have had their root cause identified.
After the root cause of the problem is identified and verified, it can be
reclassified as a Known Error by selecting Yes in the Known Error field.
Errors can become known while analyzing the problem, as well as from the
information about known errors provided by suppliers. For example,
software is frequently shipped with release notes that detail the known
bugs in the application.
1 One or more help desk cases are created. By default, they are given a case type
of Incident.
2 The underlying problem of the incidents is defined, and its root cause is
identified. If a specific case most clearly identifies the underlying problem, its
Case Type is changed from Incident to Problem. Other cases can now be
related to this problem.
3 In the Problem Management tab, the problem manager (or any other
member of the Problem Management group) marks the problem as Root
Cause Identified (RFC) by selecting RC Identified from the Known Error
Status menu.
4 Other staff members verify the root cause. The problem manager (or any
other member of the Problem Management group) marks the problem as
Root Cause Verified (RCV) by selecting RC Verified from the Known Error
Status menu.
As you work through the case to identify possible causes of the stated
problem, you might find other cases that have some similarities to the case
you are working on. You can then specify those cases as related incidents.
You can now select other cases as related incidents to this problem.
4 Select the case you want related to the current problem, and click Mark as
Incident.
The selected case is displayed in the Current Incidents table. The Incident
Count field is updated automatically to reflect the total number of related
incidents.
5 Click Save.
Unrelating incidents
If a related incident appears not to be relevant to a problem, you can unrelate
it.
The Change Tasking module of the Remedy Help Desk Support application
enables innovative IT support organizations to take preventive measures and
stay ahead of technology as computing needs change.
This section explains the processes of managing change requests by using the
Remedy IT Service Management Console of the Remedy Help Desk
application. The following topics are covered:
! “Working with change requests in the Change Tasking module” on
page 120
! “Creating new requests” on page 121
! “Working with change tasking as a change supervisor” on page 132
! “Working with Change Tasking as a task implementor” on page 155
When the change request or task is assigned, support staff members can log
their progress as they complete tasks associated with the request. When a
support staff member changes a request state to resolved, the system notifies
the requester that the request is resolved.
! The system notifies the requester that the change request has been
resolved.
! Once the requester is notified of the change of status, they can close the
change request by setting the Confirm Resolution to Closed. If the
requester does not close the change request, the request closes
automatically after a specified time.
The form that is displayed when you begin creating a new request depends
on the personal preferences you have set. For information about setting
preferences, see “Setting personal preferences and options” on page 66.
2 In the Summary field, select a predefined summary from the menu, or enter
a brief summary of the request.
If you select a predefined summary, the Description, Category, Type, and
Item fields are filled in automatically.
3 In the Description field, enter a description of the request.
If you selected a predefined summary, a brief description is automatically
entered into this field. You can add to or replace this text.
4 If you did not select a predefined summary, make the appropriate selections
from the Category, Type, and Item fields:
! In the Category field, select the appropriate category for the request.
! In the Type field, select the appropriate type within the selected category.
! In the Item field, select the appropriate item within the selected type.
When you save the request, the Change ID field will be filled in automatically
with the ID number of the request.
5 In the Login+ field, type the requester’s name and press Enter.
If the requester already has been entered in the People database, the Phone,
Office, VIP Status, Region, Site, and Department fields are filled in
automatically.
If these fields were not filled in automatically, or if you want to change them,
enter appropriate information. If you change them, you will be asked
whether you want to update the requester’s user profile.
If the requester has not yet been entered in the database, the Search People
dialog box is displayed. You can use it to search the database for records. For
more information, see “Searching for a requester” on page 127.
If you cannot find the person, you can create a record for them in the
database. For more information, see “Creating a requester record” on
page 129.
6 In the Urgency field, select the urgency level of the request.
7 If the requester has other open requests, or has assets assigned, they will be
listed in the Requester’s Assets and Requester’s Open Requests tables. To
view one of these entries, select it, and click Details.
8 Click Save to create the request and submit it to the database.
To have the New Change Request form appear when you start creating a new
request, you might need to set your personal preferences to Open Change
Tasking Module in the New Request Action field. See “Setting New Request
and Search for Request Action preferences” on page 68 for more
information. The following procedure assumes that you selected the Open
Change Tasking Module option as the New Request Action preference.
2 In the Summary field, select a predefined summary from the menu, or type
in a description of the change.
If you choose a predefined summary, the Category, Type, and Item fields are
filled in automatically.
3 In the Description field, enter a detailed description of the change request.
4 If you did not select a predefined summary, fill in the Category, Type, and
Item fields:
a In the Category field, select the appropriate category for the change. The
menu items you can choose are determined by your administrator. The
category field is the broadest categorization of the change request. For
example, categories could include Hardware, Software, or Network.
b In the Type field, select the appropriate type for the change. The menu
items you can choose are determined by your administrator and the value
you selected for the Category field. The Type field identifies the request
with more precision. For example, types could include Printers, Servers,
or Workstations.
c In the Item field, select the appropriate item for the change. The menu
items you can choose are determined by your administrator and the values
you selected for the Category and Type fields. The Item field is the most
detailed of the categorization fields. For example, items could include
product type, model number, or component names.
The options listed in the Item menu depend on the value entered in the
Type field.
When you save the change request, the Change ID field will be filled in
automatically with the ID number of the change request.
5 In the Service field, select a type of service for this change request.
The selections available depend on how your administrator has configured
this menu for the service types pertinent to your organization. For example,
the menu might be configured to show specific types of warranties.
6 Select the Priority to identify the importance of this change request, from the
standpoint of the support person.
7 Select the Urgency to indicate the importance that the requester assigns to
this change request.
8 In the Status field, accept the default status of New.
You select a Closure Code when the change request is complete, or the
application will close the request automatically after a specified time
following resolution of the request. Your administrator specifies this
automatic closure time.
The Pending field will be filled in whenever the resolution of the request is
dependent upon an external action.
9 The Approval Status field will be filled in by the change approver once work
has begun on the change request. For now, you can leave this field blank.
Note: The Auto-Reassign checkbox can be used later, if the request needs to
be modified. You can check this box if you want the system to reassign the
request automatically to another person when the Category, Type, or Item
is changed. Assignments are determined by the categorization and
location of the change request.
Usually, the Group and Supervisor fields in the Support Information region
will be filled in automatically when you save the change request, according to
the application administrator’s definitions. However, you can enter
information in them.
The Modified By, Modified, and Created fields are filled in by the system and
cannot be changed.
13 In the Requested Date field, enter the date by which the requester needs to
have the change implemented.
14 Click the Assessment tab, and enter the dates by which you want the change
request started and completed.
7 To make changes, update the appropriate fields and click Save. For
information about filling in requester information, see “Creating a requester
record” on page 129.
8 Click Close.
9 Click OK to close the Search People dialog box.
While creating a new request, you might find that the requester does not yet
have a record in the database. If this is the case, you must create a record for
the requester. You can do this in the Person Information form. You can
access this form while you are creating the request.
4 Click Yes.
The Person Information form is displayed.
6 Optionally, fill in the other fields, including fields on the Pager and Address
tabs.
7 Click Save.
A message reports that the entry was created.
3 From the Alert List window, select a request, and double-click it.
The request is displayed.
The change supervisor must make sure that the assignment is correct and
accept the change request. If the assignment is not correct, the change
supervisor can reassign the request to someone in the group, or send a
reassignment request to the manager, asking that the change be reassigned to
another supervisor outside the group.
If a request is assigned to your group but not to an individual, you can assign
the request to yourself by selecting your name in the Supervisor menu.
b In the dialog box that is displayed, select the file to be attached, and choose
Open.
In the web, use the To field to select the attachment pool to which you
want the attachment added.
The file is displayed in the Attachments field.
7 Click the Activity tab, and enter relevant information in the Work Log field.
8 Click Save.
A message reports that the change request has been assigned.
If you cannot accept an assigned change request, you can reassign the request
to another change supervisor. You can reassign it to someone in your group
by using the Supervisor menu list. To assign a change request to someone
outside of your group, you must have your manager reassign the change
request.
When you ask that a change request be reassigned, your manager is notified
of the reassignment request. If the manager reassigns the request to another
supervisor, you and the other supervisor are notified that the change request
has been reassigned. Until then, you remain assigned to the request.
3 Click Save.
A message reports who has been notified of the reassignment.
To have the Search Change Requests form appear, you may need to set your
personal preferences and select the Open Change Tasking Module option in
the Search For Request Action field. See “Setting New Request and Search for
Request Action preferences” on page 68 for more information. The following
procedure assumes that you selected the Open Change Tasking Module
option as the default Search For Request Action preference.
In the web, the matching requests are listed in a table at the bottom of the
form.
4 To view the details of another change request, click on the request in the list.
The change request is displayed.
3 In the Work Log field, enter any important information about the change
request progress.
4 Click Save.
The following example illustrates a situation where you would want to relate
help desk cases with a change request. Several users have called in with
problems about having insufficient memory to run an application. A change
request for upgrading everyone’s memory has already been created and is
pending implementation. In this situation, the help desk cases can be related
to the change request. The change request, in turn, can also be related to the
asset record for the memory.
You can relate change requests to each other, to assets, or to help desk cases:
! Relating change requests to other change requests—By creating
relationships between change requests, you can work with multiple
change requests at the same time.
For example, the operations department submits a change request to have
their email software upgraded. While supervising the change request, you
notice that most of the department computers do not have enough
memory to run the new email software. You open a related change request
for the department to have a memory upgrade.
3 From the Show menu, choose the related requests that you want to view:
! All Related Items shows all related change requests, asset records, and help
desk cases.
! Related Assets shows only the related asset records.
! Related Change Requests shows only the related change requests.
! Related Help Desk Cases shows only the related help desk cases.
All specified requests are displayed in the Related Items table.
If no related items exist for the request, the tab displays the message: “No
records were found related to this change request.”
4 To view a related request, select it, and click View.
The request is displayed.
6 When you have finished creating the new request, click Save.
A message reports that you have created a new request. Another message tells
you that the two requests have been related.
5 In the Search with the Same field, select another value if you want to change
the search.
To refine the search criteria, click the Advanced tab and enter more specific
search criteria.
6 Click Search.
The Search Results list shows the requests matching the search criteria.
7 To view more information about a request, select it, and click View.
8 Click Close.
9 To relate a request, select it, and click Relate.
A message reports that the request has been related.
10 Click Close to save the change request to which you were relating the other
request.
You can create new tasks for a change request. You can also add predefined
tasks to a change request. Predefined tasks are a set of tasks that comprise a
change request. For example, the predefined tasks for Upgrade Memory are
“Get memory hardware asset from inventory” and “Install memory.” When
you create predefined tasks, the tasks are automatically related to the change
request.
The Remedy Help Desk administrator predefines tasks when configuring the
Change Tasking module. For information about creating predefined tasks,
see the Remedy IT Service Management Installation and Configuration Guide.
A change request can consist of several tasks. You can open each task, assign
the task to a support staff member, and change the Plans and Planned Dates
as needed.
For example, to solve a requester’s disk space problem, you might create a
change request to upgrade the requester’s disk drive. You could add these
predefined tasks:
! Order drive
! Back up data
! Format new drive
! Reinstall software
! Restore data on new machine
7 To add a single task to the change request, select the task, and click Add
Selected Task. To add all tasks to the change request, click Add All Tasks.
A message reports that the tasks have been added.
8 Click Close.
The selected tasks appear in the Tasks for Change Request table.
3 Select the task you want to cancel, and click Cancel Task.
The Task Work Log dialog box is displayed.
4 In the Work Log field, enter a reason for canceling the task.
5 Click OK.
The task status changes to Closed.
10 If the vendor uses confirmation codes for work orders, enter the vendor’s
confirmation code for the work order.
11 Click Save.
c In the Contact Details field, enter the applicable contact specifics, such as
phone number, email address, or pager information. If you selected email
as the notification method, you must enter an email address for the
contact in the Email field.
d In the Contact Address tab, enter mailing address information for the
contact.
When you assign the change task, the assignee is automatically notified. The
change task is listed in the Assigned Requests list in the Remedy IT Service
Management Console, along with any other change requests.
If you reassign the change task, the previous and new assignees are
automatically notified of the changed assignment. If you deny the
reassignment, the current assignee is informed that the assignment has not
changed and the request was denied.
The tasks associated with the change request are listed in the Tasks for
Change Request table.
3 Select the task that you want to reassign, and click View.
The task is displayed.
4 Approve or reject the reassignment request. To reassign the change task:
a Select No from the Request Reassignment field.
b Select a new staff member from the Implementor menu list.
If you decide to deny the request, select No from the Request Reassignment
field.
5 Click Save.
6 Click Close.
Note: A change request is automatically resolved only when all of its tasks are
closed. Automatic resolution does not occur when any of the tasks are
cancelled.
When a change supervisor assigns change tasks, the task implementors are
notified of tasks assigned to them by email, paging, or AR System Alert. After
a task is assigned, task implementors can log their progress as they complete
the task. When all of the tasks related to a change request are closed, the
change supervisor and requester are notified that the change request is
resolved.
This section explains the Support view of the Change Tasking module and
the actions you can perform as a task implementor.
2 Update the Work Log field with information about the progress you have
made on the task.
3 In the Status field, choose WorkInProgress.
4 Optionally, click the Assessment tab, and enter planning information in the
Plans field.
5 In the Implementor field, select your name.
6 Click Save.
If you cannot accept an assigned task, you can reassign it to someone in your
group, or ask your change supervisor to assign it to someone else outside of
your group. When the change supervisor reassigns the task, you and the
other task implementor are notified that the task has been reassigned.
3 In the Assessment tab, update the Work Log field with information about
your progress.
4 Click Save.
5 Click Close.
Closing tasks
When you have completed a change task, you are ready to close it. When all
of the tasks that comprise a change request are closed, the change request is
automatically assigned a status of Resolved. The change supervisor and the
requester are notified when the change request is resolved.
The Asset Inventory module of the Remedy Help Desk Support application
provides you with a quick and convenient method of tracking your
company’s IT assets. Use Asset Inventory to create asset records and related
component records.
Remedy Help Desk administrators customize the Asset Inventory module for
the organization’s use. The Remedy IT Service Management Installation and
Configuration Guide describes these customization tasks.
The following topic areas provide information about using the Asset
Inventory module to create and manage asset records and asset components.
! “Working with assets” on page 160
! “Working with asset components” on page 166
! “Working with related items” on page 172
You can also relate help desk cases and change requests to asset records.
3 Fill in all required fields. Required fields are shown in boldface type:
! ID—Type a unique alphanumeric value in the ID field.
! Name—Enter a descriptive name for the asset.
! Status—Select a value, or accept the default value of Ordered.
! Category—Select a category. The values you can choose are determined
by the administrator.
! Type—Select a type. The values you can choose are determined by the
category you chose, and by the administrator.
! Item—Select an item. The values you can choose are determined by the
type you chose, and by the administrator.
The owners, users, or managers related to this asset are listed in the table. If
there are none, a message appears above the table stating that no owners,
users, or managers were found for the asset.
3 To view the record in the table, select the record, and click View.
The record is displayed in the Person Information form.
3 Click Add.
The Select Type dialog box appears.
9 Click Save.
10 Click Close to close the Asset Information form.
3 Fill in all the required fields, shown in bold font on the form:
! ID—Enter a unique alphanumeric value in the ID field.
! Status—Select a value. If you choose Relate to Main Asset, you can relate
the component to an existing asset.
! Category—Select a category. The values you can choose are determined
by the administrator.
! Type—Select a type. The values you can choose are determined by the
category you chose, and by the administrator.
! Item—Select an item. The values you can choose are determined by the
type you chose, and by the administrator.
c Click OK.
The asset ID appears in the field.
7 Fill in the remaining fields in the General tab:
! Install Date—Enter the component’s installation date, if applicable.
! Part Number—Enter the component’s part number, if applicable.
! Version—Enter the component’s version number, if applicable.
! Licenses—Enter the number of licenses available for the component, if
applicable.
! Notes—Enter any relevant comments about the asset. When the
component record is saved, your notes will be added to the audit trail.
4 Fill in the fields, as described in “To create an asset component from the
Remedy IT Service Management Console:” on page 166.
The Main Asset ID field automatically contains the ID of the asset from
which you are creating the component. You cannot change this entry.
5 When you are finished, click Save.
6 Click Close to close the form.
The component that you have created is listed in the Components tab of the
asset record.
4 Select the search criteria by selecting values for the Category, Type, and Item
fields.
5 Click Search.
The Search Results table displays the list of possible matches.
6 To perform another search with different criteria, click Clear Fields, select the
new criteria, and click Search.
7 Click Close to close the form.
You can relate assets to each other, to change requests, or to help desk cases:
! Relating assets to other assets—When you work with an asset, you might
need to work with a related asset. For example, you might have a printer
to which many computers are connected. You could create relationships
between the asset records of the printer and the computers connected to
it, which could help you quickly determine who has access to the printer.
! Relating assets to change requests—When you work with an asset record,
you might need to work with a related change request. For example, if a
change request requires ordering an asset, you can relate the asset to the
change request when you receive the asset.
! Relating assets to help desk cases—When you work with an asset record,
you might need to work with a related help desk case. For example, if the
solution to a help desk case is to add more memory to a workstation, you
may need to relate the help desk case (there is not enough memory) to the
asset record for the workstation (purchasing additional memory).
3 From the Show menu, choose the related requests that you want to view:
! All Related Items shows all related asset records, change requests, and help
desk cases.
! Related Assets shows only the related asset records.
! Related Change Requests shows only the related change requests.
! Related Help Desk Cases shows only the related help desk cases.
All specified requests are displayed in the Related Items table.
If no related items exist for the request, a message appears above the table
stating that no related items were found.
4 To view a related request, select it, and click View.
The request is displayed in its form.
6 When you have finished creating the new request, click Save.
A message reports that you have created a new request. Another message tells
you that the two requests have been related.
7 Click OK to close each dialog box.
The form for the new request closes.
8 If the related item does not appear in the Related Items table, refresh the table
manually by clicking the Refresh button.
9 Click Save to save the changes.
The Search and Relate dialog box is displayed, listing the requests according
to the value in the Search with the Same field.
5 In the Search with the Same field, select another value if you want to change
the search. Or, to refine the search criteria, click the Advanced tab and enter
more specific search criteria.
6 Click Search.
The Search Results list shows the requests matching the search criteria.
7 To view more information about a request, select it, and click Details.
The request is displayed.
8 Click Close.
9 To relate a request, select it, and click Relate.
A message reports that the request has been related.
10 Click Save to save the asset record.
Managers can run reports on help desk cases, on change requests, and on
asset inventory. These reports enable managers to plan resources and to
identify trends in the types of upcoming cases, change requests and tasks, and
assets that warrant further investigation. Managers can also view reports
based on customer satisfaction feedback on help desk cases and change
requests.
Note: The Remedy Help Desk Management application includes all the
functionality of the Remedy Help Desk Support application and its three
modules. Managers can perform all the tasks that the support staff can
perform using the Remedy Help Desk Support application—set the same
preferences, use reminders, and perform many other functions. The
following sections, therefore, cover only those activities that managers can
do in addition to the support tasks. For instructions about providing
support tasks, see the following sections:
" To access the Remedy Help Desk Management application from a browser:
1 From a browser, enter the following URL:
http://<web_server>:<port>/arsys/apps/default/<ar_server>/ITSMHD/
RemedyManager_Administrator.jsp
The Login window is displayed.
2 Enter your AR System user name and password.
3 Click Login.
4 The IT Service Management Console for the Management application is
displayed.
Other
! Reports
! Reminders
! Preferences
! Help
! Logout (web only)
New Request
Click New Request to create a new request. The form that opens depends on
how you have set your New Request Action preference. See “Setting personal
preferences and options” on page 66 for more information.
Search Task
Select Search Task to search for existing change tasks.
Track Assets
Select the Track Assets to display the Track Asset Information dialog box,
from which you can create and search for assets and components.
Reports
Select Reporting to generate predefined reports on help desk cases, change
requests, and asset records. You can view reports with the built-in Crystal
Reports viewer. For more information about reporting, see Chapter 8,
“Working with reports.”
Reminders
Select Reminders to create and display reminders.
Help
Select Help to display online help for the Support role.
Approving solutions
When a support staff member proposes a solution for a help desk case, you
are notified of the solution requiring approval. You can then review the
solution for completeness and accuracy, and you can approve or reject it.
When you approve it, the solution becomes available to support staff and
requesters for general use.
3 To change the solution, edit the Summary and Description fields as needed.
4 Make the appropriate selection in the Status field.
Handling escalations
When escalations are enabled, Help Desk cases and change requests are
automatically escalated as soon as escalation criteria are met. Escalation
criteria are set by the Help Desk administrator. For example, a case could be
escalated if it is not marked a Work in Progress within a certain time period.
When an escalation occurs, you are notified. Strategies for dealing with
escalations differ among organizations, but can include the following
actions:
! Reassigning the escalated request to another support staff member
! Contacting the requester for more information about the request
Use the following procedure to escalate a change request or help desk case.
5 Click Save.
A message reports that the original support staff member and the newly
assigned staff member have both been notified of the reassignment.
Reviewing surveys
When a requester’s help desk case is resolved by the support staff, the
requester is notified. The requester then can close the case.
After closing a resolved case, the requester is prompted to fill out a survey
about how the case was handled. You can access and review all completed
surveys.
For information about the various reports and for instructions on generating
reports, see “Working with reports” on page 191.
For information about using the Bulletin Board, see “Using the Bulletin
Board” on page 72.
Using reminders
Reminders enable you to create notes for yourself and others. You can send
them by email or by AR System Alert, and you can specify when they will be
sent.
For information about using reminders, see “Using reminders” on page 76.
For detailed information about creating Help Desk cases and change
requests, see “Creating a new help desk case” on page 86 and “Creating a new
change request” on page 123.
For detailed information about searching for help desk cases and change
requests, see “Searching for help desk cases” on page 98 and “Searching for
requests” on page 136.
For detailed information about using the Asset Inventory module, see
“Working with the Asset Inventory Module as Support” on page 159.
Generating reports
The following sections provide instructions for generating predefined
reports, and for creating reports with qualifications you specify.
Before you can view and print predefined reports, you must have a report
server selected. For information about specifying a report server, see “To
specify a report server for viewing and printing reports:” on page 39.
a In the first column (Field <n>), select a field on which you want to search.
b In the second column (Operand), select an operator; for example, = (the
equal sign) for matching entries.
c In the third column (Value), enter a value by which you want to search.
For example, to find all Help Desk cases assigned to Bob Backline, enter
Bob Backline as the value.
d Repeat these steps to refine the search further.
You can also use the advanced search bar to specify a qualification.
e Click the Advanced Qualification button.
The Advanced Qualification Builder dialog box is displayed.
f In the Qualification field, enter the criteria for the report data you want.
You can enter the qualification manually, or use buttons and selection lists
to build your qualification. The selections you make appear in the
Qualification field.
g Select Save.
h The search criteria you selected appear in the Qualification field of the
Report Console.
Predefined reports
Predefined reports enable you to quickly generate information about:
! assets and asset components
! change requests and change tasks
! help desk cases, customer satisfaction surveys, and solutions.
The following sections describe the predefined reports that are available for
each module.
Asset information
The following reports provide information about assets and asset
components.
Change information
The following reports provide information about change request and change
task activity.
Help Desk
The following reports provide information about help desk cases, case
activity, satisfaction surveys, and solutions.
Glossary ! 207
Remedy Help Desk 5.5
208 "Glossary
User’s Guide
! 209
Remedy Help Desk 5.5
210 "Glossary
User’s Guide
! 211
Remedy Help Desk 5.5
212 "Glossary
User’s Guide
! 213
Remedy Help Desk 5.5
214 "Glossary
User’s Guide
! 215
Remedy Help Desk 5.5
216 "Glossary
User’s Guide
! 217
Remedy Help Desk 5.5
incident keyword
Any even that is not part of the standard A variable whose value is defined by the
operation of a service and that causes, or AR System. For example, $USER$ represents
may cause, an interruption to or reduction the name of the user that is currently logged
in the quality of that service. See also in. Keywords can be used in defining
Problem Management. qualifications for searches, search menus,
Information Technology Infrastructure Library workflow, and macros; or for specifying a
(ITIL) value in the Set Fields action for active links,
A reference library organizations can use to filters, and escalations.
improve the way they use IT. knowledge base
integer data type A repository that stores reusable solutions
The data type used for fields that contain to customer product problems in an easy-
numeric values between –2147483647 and to-retrieve format.
2147483647. The range for a field can be known error
limited by the AR System administrator. A condition identified by successful
inventory diagnosis of the root cause of a problem
The quantity of assets available. when it is confirmed that a configuration
item is at fault.
ISO currency code
See currency code. legacy system
A system in which a company or
ITIL
organization has already invested
See Information Technology Infrastructure
considerable time and money.
Library (ITIL).
license
IT director
See fixed license, floating license, FTS license,
A person responsible for technological
read license, write license.
direction and procurement strategy. Works
with lines of business managers to Lifecycle Asset Management
determine future hardware and software Managing the life of an asset from its
requirements. purchase, deployment, and disposal.
IT Services applications location
See Remedy IT Service Management A configurable component composed of a
region, a site, and a department. Locations
join form
are used by the auto-assignment
A type of form that contains information
functionality.
from two or more AR System forms.
Although join forms function similar to macro
regular AR System forms in most respects, A set of operations recorded for later
they do not store independent data. Join execution. Macros are useful for
forms point to the data stored on the two automating frequently used or complex
AR System forms that were used to create search operations.
the join form.
218 "Glossary
User’s Guide
! 219
Remedy Help Desk 5.5
notification permission
A message sent to a user via workflow. The property setting that enables
Notification can be in the form of an alert, AR System administrators to control who
email message, or other method using can view and change individual fields of a
integrations. form. Administrators also set permissions
operator for forms and active links. Permissions are
One of a number of functions that enable defined for each access control group. See
you to define advanced searches or build also access control, group, user.
qualifications. plug-in
option group An auxiliary program that works with the
See selection data type. AR System server to enhance its capability.
A plug-in is a dynamically linked library
packing list (DLL) on Microsoft platforms and a shared
A set of associated server objects that can be object on UNIX platforms. The plug-in
viewed as a work space in the server window service loads the plug-in at runtime.
or used in external utilities.
plug-in service
page field A server that loads plug-ins. The plug-in
A type of field that groups related fields and service is a companion server to the AR
includes tabs to label those groups. System server that loads the ARDBC,
page holder field AREA, or filter API plug-ins at runtime.
A field that contains one or more page fields preference server
and allows these grouped fields to be An AR System server that stores user
displayed one set at a time in a given area of preferences centrally in one or more
the screen. preference forms.
Parent/Child contract
Problem Management
A parent, or main, contract that has other The process of identifying, diagnosing, and
children, or subcontracts, associated with it. recording the root causes of incidents to
peer tasks prevent problems from reoccurring.
Dependent change tasks that can be prompt bar
completed simultaneously. See also In the AR System User Tool, the part of a
dependent change tasks. main window that displays instructions or
peer-to-peer relevant information to the user.
Devices that are on the same level in an property
organization’s network (for example, two An attribute that is defined. For example,
workstations). See also network topology. the properties of a field include its data type,
physical characteristics (such as length),
and whether it is required or optional.
220 "Glossary
User’s Guide
! 221
Remedy Help Desk 5.5
222 "Glossary
User’s Guide
! 223
Remedy Help Desk 5.5
224 "Glossary
User’s Guide
! 225
Remedy Help Desk 5.5
226 "Glossary
User’s Guide
work space
A subset of all objects on the server
displayed in AR System Administrator. This
subset of server objects is defined in a
packing list.
write license
A license that allows a user to modify and
save data in existing requests as field and
form permission settings allow. See also
fixed license, floating license, read license.
XML Schema or XML Schema Definition (XSD)
Provides a means for defining the structure,
content, and semantics of XML documents.
! 227
Remedy Help Desk 5.5
228 "Glossary
Index
A main assets 59
accepting overview for support 58
assigned cases 96 relationship definitions 59
assigned change requests 133 reporting and monitoring 60
assigned change tasks 155 working with as support 159
adding assets
attachments 75 asset components 59
contact information for work order 151 creating and tracking as management 190
name to User Name list 27 creating owner or user for 164
owner, user, or manager for an asset 164 creating records 160
servers 27 main assets 59
tasks to change requests 144 modifying records 165
administrator role 18 relating new request to 174
applications searching for as support 162
configuring 18 working with as support 160
Remedy Asset Management 23 assigning tasks 152
Remedy Change Management 23 assignment
Remedy Service Level Agreements 23 accepting cases 96
approving solutions 181 accepting change requests 133
AR System Alert 44, 45, 77, 95, 132 accepting change tasks 155
asset components group notification of 132
creating 166 individual notification of 132
linking to assets 170 attachments
searching for 169 adding to Bulletin Board messages 75
working with 166 viewing and saving 73
Asset Information reports 196 audience, for this manual 9
Asset Inventory module autoassignment 94
asset components 59 Auto-fill feature 30
features 21 Automatic reassignment 15
levels of assets 59
Index ! 229
Remedy Help Desk 5.5
230 "Index
User’s Guide
F K
features known errors 114
Asset Inventory module 21
Index ! 231
Remedy Help Desk 5.5
L individual 132
linking asset components to assets 170 of case assignment by AR System Alert 95
logging in of case assignment by email 95
as first-time user 27 of change assignment by AR System Alert 132
as requester 27 of change assignment by email 133
Authentication field 29
to a specific server 27 O
online help 30
M options
management advanced 71
approving solutions 181 setting personal preferences and 66
creating and tracking assets 190 overview
creating requests 190 Asset Inventory module for support 58
handling escalations 186 assignment of cases 94
handling reassignments 183 Change Tasking module for support 56
includes functionality of support 178 Help Desk module for support 55
list of tasks 177
opening the application 178 P
reviewing surveys 188 paging information 50, 65
searching for requests 190 paging type 69
tools 22 person record,searching 48
using reminders 189 personal preferences
using the Bulletin Board 189 changing your personal record 66
using the Remedy IT Service Management setting advanced options 71
Console 179 setting for support 66
working with Remedy Help Desk 178 setting new and search request forms 68
working with reports 189 setting paging preferences 69
management role 18, 178 plus sign in field labels 30
Manager View menu, using 181 potential duplicates 101
manual, audience for 9 potential incidents 117
modifying potential solutions 19
asset records 165 predefined reports
Bulletin Board messages 75 asset information 196
change tasks 157 generating 192
existing requests 138 help desk 201
reminders as requester 46 Report Console 192
reminders as support 78 using 196
requester information as support 94 predefined tasks, creating 146
requester record as support 131 printing
tasks within change request 147 report on demand for a request 39
requests 38
N table data 51, 81
new features 15 Problem Management
notification designating a help desk case as a problem 116
group 132 known errors 115
232 "Index
User’s Guide
Index ! 233
Remedy Help Desk 5.5
234 "Index
User’s Guide
Index ! 235
Remedy Help Desk 5.5
V
viewing
assigned change tasks 157
associated tasks for change request 147
attachments in Bulletin Board messages 73
Bulletin Board messages as requester 43
closed cases 16
reminders as requester 46
reminders as support 78
requests related to assets 172
requests related to change request 140
requests related to help desk case 109
your group’s open cases 98
your group’s open change requests 137
your open cases 99
your open change requests 137
W
Web Services 15
web views 15
work log 102
work order
adding or removing contact information 151
description of 15
task as 148
updating company information 149
updating contact information 150
work order tab 145
236 "Index