BMC Change Management 8 1 - User Guide

BMC Software Confidential
BMC Change Management 8.1
Using
Date:
01-Nov-2013 17:48
URL:
https://docs.bmc.com/docs/display/change81/Using
Using
Table of Contents
1 Accessing the interface _________________________________________________________________ 13
1.1
To log in and access the BMC Remedy ITSM Suite applications _______________________________ 13
2 Navigating the interface ________________________________________________________________ 14

2.1 Best Practice and Classic views _______________________________________________________ 14
2.1.1
Benefits of Best Practice view in BMC Change Management ____________________________ 15
2.1.2 Benefits of Best Practice view in the Release Management module _______________________ 21
2.1.3 Best Practice view - Change Request form _________________________________________ 25
2.1.4 Best Practice view - Release Request form _________________________________________ 27
2.1.5 Classic view - Change Request form ______________________________________________ 29
2.1.6 Classic view - Release Request form ______________________________________________ 30
2.2 IT Home page ____________________________________________________________________ 31
2.2.1 IT Home page and its functional areas ____________________________________________ 32
2.2.2 Configuring the IT Home page __________________________________________________ 34
2.2.3 Customizing and using the IT Home page video _____________________________________ 35
2.3 Navigating consoles, forms, and modules _______________________________________________ 35
2.3.1 What happens to data as I move back and forth on the breadcrumb trail? _________________ 37
2.3.2 How does the breadcrumb trail behave with forms in Search mode? _____________________ 37
2.3.3 Can I force a second window to open? ____________________________________________ 38
2.3.4 Which consoles, forms, and modules open in a new window? __________________________ 38
2.4 User interface standards for field labels _________________________________________________ 39
2.5 Icons used in the interface __________________________________________________________ 39
2.6 Using the Change Management Console and the Change form ______________________________ 40
2.6.1 Change Management console functional areas ______________________________________ 41
2.6.2 Company and Console View ____________________________________________________ 44
2.6.3 Change form functional areas ___________________________________________________ 45
2.7 Using the Release Management console and the Release form _______________________________ 48
2.7.1
Release Management console functional areas ______________________________________ 48
2.7.2 Release form functional areas ___________________________________________________ 52

2.7.3 Activity form functional areas ___________________________________________________ 54
2.8 Using the Change Management Dashboard ______________________________________________ 56
2.8.1 To use the Change Management Dashboard ________________________________________ 56
2.9 Tooltip data shown in consoles _______________________________________________________ 58
2.10 Tooltip data shown in Change Calendar ________________________________________________ 58
2.11 Working with the Requester console ___________________________________________________ 59
2.11.1 Requester Console users _______________________________________________________ 59
2.11.2 Requester console users _______________________________________________________ 60
2.11.3 Integration between Requester console and BMC Change Management __________________ 61
2.12 Working with the Overview console ___________________________________________________ 61
Page 2 of 452
Using
2.12.1 Overview console functional areas _______________________________________________ 62

2.12.2 Console List table ____________________________________________________________ 64
2.12.3 Selecting status values ________________________________________________________ 65
3 Using Global search ___________________________________________________________________ 67
3.1 To use Global search _______________________________________________________________ 67
3.2 Limitation _______________________________________________________________________ 68
3.3 Special characters and boolean expressions in Global search ________________________________ 68
3.4 Global search indexed fields _________________________________________________________ 69
3.4.1 Activity form indexed fields _____________________________________________________ 70
3.4.2 Help Desk form indexed fields ___________________________________________________ 70
3.4.3 Infrastructure Change form indexed fields _________________________________________ 72
3.4.4 Known Error form indexed fields _________________________________________________ 73
3.4.5 Problem Investigation form indexed fields _________________________________________ 74
3.4.6 Release form indexed fields _____________________________________________________ 75
3.4.7 Solution Database form indexed fields ____________________________________________ 76
3.4.8 Task form indexed fields _______________________________________________________ 77
3.4.9 Work Order form indexed fields _________________________________________________ 78
4 Viewing your profile ___________________________________________________________________ 80
4.1 To modify your profile ______________________________________________________________ 80
5 Using BMC Change Management _________________________________________________________ 81
5.1 Initiate stage - Creating change requests ________________________________________________ 81
5.1.1
Creating a change request at the initiate stage - Best Practice view ______________________ 83
5.1.2 Creating a change request at the Initiate stage - Classic view ___________________________ 86
5.1.3 Creating emergency change requests _____________________________________________ 91
5.1.4 Creating a change request from Atrium Impact Simulator ______________________________ 91
5.1.5 Creating change requests as rollbacks ____________________________________________ 93
5.1.6 Associating custom process flows to a change template ______________________________ 94
5.1.7
Selecting change templates ____________________________________________________ 94
5.1.8 Impact, urgency, and priority criteria _____________________________________________ 96

5.2 Adding information to the change request ______________________________________________ 97
5.2.1 Adding Requester information __________________________________________________ 97
5.2.2 Adding classification information ________________________________________________ 99
5.2.3 Adding vendor information ____________________________________________________ 101
5.2.4 Recording the change activities ________________________________________________ 102
5.2.5 Modifying change requests - Additional information you can enter _____________________ 105
5.3 Review and Authorize stage - Risk and impact analysis ____________________________________ 107
5.3.1 Risk assessment ____________________________________________________________ 109
5.3.2 Specifying risk level at the Review and Authorize stage _______________________________ 110
5.3.3 Computing risk levels ________________________________________________________ 110
5.3.4 Risk Recalculation ___________________________________________________________ 112
5.3.5 Planning dependencies for change requests _______________________________________ 112
5.4 Plan and Schedule stage - Planning the change request ___________________________________ 113
5.4.1 Planning the change request at the Plan and Schedule stage ___________________________ 115
Page 3 of 452
Using
5.4.2 Detecting CI collisions between change requests ___________________________________ 118

5.5 Approvals - Approving change requests ________________________________________________ 121
5.5.1 Handling approvals for emergency change requests _________________________________ 124
5.5.2 Adding approvers ___________________________________________________________ 124
5.5.3 Approving changes using Approval Central ________________________________________ 131
5.5.4 Working with BMC Change Management as an approver _____________________________ 133
5.5.5 Viewing approvers for a change request __________________________________________ 135
5.5.6 Resubmitting a rejected request ________________________________________________ 136
5.5.7 Approving or rejecting requests _________________________________________________ 137
5.5.8 Understanding the change management approval process ____________________________ 138
5.5.9 Viewing change requests awaiting approval _______________________________________ 139
5.5.10 Approval processes provided out-of-the-box for BMC Change Management ______________ 139
5.5.11 Multiple approvers and multiple approval levels ____________________________________ 142
5.5.12 Approving or rejecting requests via email _________________________________________ 143
5.6 Implement stage - Implementing the change ___________________________________________ 146
5.6.1 Identifying change requests as rollbacks __________________________________________ 148
5.6.2 Implementing a change request ________________________________________________ 149
5.6.3 Implement stage - Working on task assignments ___________________________________ 149
5.6.4 Implement stage - Working with tasks ___________________________________________ 150
5.7 Closed stage - Completing change requests ____________________________________________ 151
5.7.1
Closing a change request _____________________________________________________ 154
5.8 Monitoring the progress of a change request ____________________________________________ 155

5.8.1 To view the progress of a change request when using the Best Practice view ______________ 155
5.8.2 To view the progress of a change request when using the Classic view ___________________ 156
5.8.3 Monitoring associated tasks ___________________________________________________ 156
5.8.4 Viewing and updating affected areas _____________________________________________ 157
5.8.5 Viewing the audit log _________________________________________________________ 157
5.8.6 Tracking efforts for a change request ____________________________________________ 158
5.8.7 Tracking the time spent working on change requests ________________________________ 160
5.9 Copying change requests ___________________________________________________________ 161
5.9.1 To copy a change request _____________________________________________________ 161
5.9.2 Copying tasks from another change request _______________________________________ 162
5.10 Working with related change requests _________________________________________________ 163
5.10.1 Assigning sequence numbers to dependent change requests __________________________ 164
5.10.2 Creating related change requests _______________________________________________ 165
5.10.3 Relating change requests _____________________________________________________ 166
5.10.4 Removing a related change request _____________________________________________ 166
5.10.5 Viewing change dependencies _________________________________________________ 166
5.11 Working with change request assignments _____________________________________________ 167
5.11.1 Automatically assigning changes ________________________________________________ 168
5.11.2 Receiving notifications of change request assignments _______________________________ 168
5.11.3 Viewing assigned changes _____________________________________________________ 169
5.11.4 Assigning change requests ____________________________________________________ 170
Page 4 of 452
Using
5.11.5 Assigning changes to change implementers _______________________________________ 171

5.11.6 Reassigning change requests ___________________________________________________ 172
5.11.7 Working with reassignment requests _____________________________________________ 173
5.12 Using phases with change requests ___________________________________________________ 173
5.12.1 To use phases with change requests _____________________________________________ 174
5.12.2 Change task status transitions __________________________________________________ 174
5.13 Managing CIs ____________________________________________________________________ 175
5.13.1 Working with related configuration items _________________________________________ 176
5.13.2 Searching for CIs from the Change Management console _____________________________ 178
5.13.3 Creating a CI _______________________________________________________________ 178
5.13.4 Managing inventory _________________________________________________________ 183
6 Using Release Management ____________________________________________________________ 188
6.1 Initiate milestone - Creating release requests ___________________________________________ 188
6.1.1
Creating a release request at the initiate milestone - Best Practice view __________________ 190
6.1.2 Creating a release request at the initiate milestone - Classic view _______________________ 193
6.1.3 Specifying the business justification _____________________________________________ 196
6.1.4 Selecting release templates ____________________________________________________ 198
6.1.5 Creating a manifest __________________________________________________________ 200
6.2 Recording the release activities ______________________________________________________ 204
6.2.1 To add or modify work information to a release request when using the Best Practice view ___ 205
6.2.2 To add or modify work information to a release request when using the Classic view ________ 205
6.3 Planning milestone - Planning and scheduling the release request ___________________________ 206
6.3.1 To plan and schedule the release request _________________________________________ 207
6.3.2 Scheduling releases __________________________________________________________ 210
6.4 Managing release management approvals ______________________________________________ 213
6.4.1 Approval processes provided out-of-the-box for Release Management __________________ 213
6.4.2 Understanding the release management approval process ____________________________ 214
6.4.3 Working with release request approvals __________________________________________ 215
6.5 Build milestone - Building a controlled environment for the release __________________________ 216
6.5.1 To build the release __________________________________________________________ 218
6.6 Test milestone - Testing the release __________________________________________________ 218
6.6.1 To test the release __________________________________________________________ 220
6.7 Deployment milestone - Rolling out the release to the business _____________________________ 220
6.7.1 To deploy the release to the business ____________________________________________ 221
6.8 Close Down milestone - Completing release requests _____________________________________ 222
6.8.1 To close down the release ____________________________________________________ 223
6.8.2 To cancel a release __________________________________________________________ 223
6.9 Working with release manifests ______________________________________________________ 224
6.9.1 Related topics ______________________________________________________________ 225
6.9.2 Using Quick Actions on changes and activities _____________________________________ 225
6.9.3 Performing other functions with related release requests _____________________________ 225
6.10 Working with release activities ______________________________________________________ 226
6.10.1 Working on activities ________________________________________________________ 228
Page 5 of 452
Using
6.10.2 Working with activities as an activity assignee ______________________________________ 228

6.10.3 Creating activity task groups and tasks ___________________________________________ 229
6.10.4 Entering activity work information ______________________________________________ 231
6.10.5 Closing the activity __________________________________________________________ 232
6.10.6 Planning financial information for activities ________________________________________ 232
6.10.7 Planning activity dates _______________________________________________________ 233
6.10.8 Creating activities - basic steps _________________________________________________ 234
6.10.9 Working with activity assignments ______________________________________________ 235
6.10.10Selecting activity templates ___________________________________________________ 239
6.10.11Activity statuses ____________________________________________________________ 239
6.10.12Release task status transitions __________________________________________________ 241
6.11 Working with release request financial information - Rolling up costs _________________________ 243
6.11.1 To roll up costs _____________________________________________________________ 243
6.12 Working with release request assignments _____________________________________________ 245
6.12.1 Reassigning release requests ___________________________________________________ 247
6.12.2 Automatically assigning release requests _________________________________________ 248
6.12.3 Assigning release requests ____________________________________________________ 248
6.12.4 Receiving notifications of release request assignments _______________________________ 249
6.12.5 Updating assignment availability ________________________________________________ 249
6.13 Sending release or activity notifications ________________________________________________ 250
6.14 Monitoring the progress of a release request ____________________________________________ 250
6.14.1 To view the progress of a release request when using the Best Practice view ______________ 251
6.14.2 To view the progress of a release request when using the Classic view ___________________ 252
6.14.3 Managing release effort logs ___________________________________________________ 252
6.14.4 Tracking efforts for a release record _____________________________________________ 253
6.15 Modifying release requests _________________________________________________________ 253
6.15.1 Moving the release forward ____________________________________________________ 254
6.15.2 Performing additional functions from the Process Flow Status bar ______________________ 255
7 Working with relationships _____________________________________________________________ 256
7.1 Leveraging the power of relationships (video) ___________________________________________ 257
7.2 Related request types for BMC Change Management and Release Management _________________ 258
7.3 CI relationship types ______________________________________________________________ 260
7.4 Defining relationships _____________________________________________________________ 261
7.4.1 To define a relationship when using the Best Practice view ____________________________ 261
7.4.2 To define relationships when using the Classic view _________________________________ 262
7.5 Searching for request types and establishing the relationship type ___________________________ 264
7.5.1
To search for request types and establish the relationship type _________________________ 264
7.6 Working with release relationships ___________________________________________________ 265

7.7 Viewing the impact of CIs on change requests __________________________________________ 267
7.7.1
To view impact of CIs on change requests ________________________________________ 268
7.8 Copying relationships _____________________________________________________________ 270

7.8.1 To copy relationships ________________________________________________________ 270
7.9 Viewing relationships ______________________________________________________________ 271
Page 6 of 452
Using
7.9.1 To view relationships _________________________________________________________ 271

7.10 Performing additional functions with relationships _______________________________________ 272
7.11 Relating CIs to alternate datasets _____________________________________________________ 273
7.11.1 To relate CIs from alternate datasets _____________________________________________ 274
7.12 Creating CI unavailability ___________________________________________________________ 275
7.12.1 Relating unavailable CIs and changes ____________________________________________ 275
7.12.2 Defining new CI unavailability for a record - alternative method ________________________ 277
7.13 Performing additional functions with CI unavailability _____________________________________ 280
7.14 Working with related incidents ______________________________________________________ 281
7.14.1 To define an incident related to a change request ___________________________________ 281
7.14.2 To relate an incident to a change request _________________________________________ 281
7.14.3 To unrelate an incident from a change request _____________________________________ 281
7.15 Responding to task reassignments as a change coordinator ________________________________ 281
7.15.1 To respond to task reassignment requests as change coordinator ______________________ 282
7.16 Using Quick Actions on relationships _________________________________________________ 282
7.16.1 To use quick actions _________________________________________________________ 283
8 Working with broadcasts _______________________________________________________________ 285
8.1 Creating broadcast messages _______________________________________________________ 285
8.1.1
To create a broadcast message _________________________________________________ 285
8.2 Viewing and managing broadcasts ___________________________________________________ 287

8.2.1 To manage broadcast messages ________________________________________________ 287
8.3 Limiting the number of broadcasts ___________________________________________________ 287
8.3.1 To limit the number of messages _______________________________________________ 288
8.4 Controlling the timing of broadcast pop-up messages ____________________________________ 288
8.4.1 To set the timing of pop-up messages ___________________________________________ 288
9 Working with records _________________________________________________________________ 289
9.1 Creating a requester record _________________________________________________________ 289
9.1.1
To define a requester record ___________________________________________________ 289
9.2 Working with requester records _____________________________________________________ 290

9.3 Modifying records ________________________________________________________________ 290
9.3.1 To modify a record __________________________________________________________ 290
9.4 Printing records __________________________________________________________________ 291
9.4.1 To print a record ____________________________________________________________ 291
10 Working with costs ___________________________________________________________________ 292
10.1 Costing process workflow __________________________________________________________ 292
10.2 Costing limitations _______________________________________________________________ 293
10.3 Adding and viewing costs __________________________________________________________ 294
10.3.1 To add or view a cost to a change request ________________________________________ 294
10.4 Calculating the costs of a change request ______________________________________________ 295
10.4.1 To modify a cost ____________________________________________________________ 296
10.5 Using autocost estimates __________________________________________________________ 296
10.5.1 To use autocost estimates ____________________________________________________ 296
10.6 Allocating costs to CIs _____________________________________________________________ 297
Page 7 of 452
Using
10.6.1 To allocate costs to configuration items __________________________________________ 297

11 Working with tasks ___________________________________________________________________ 299
11.1 Working with BMC Change Management as a task implementer _____________________________ 299
11.2 Relation of task statuses to change statuses ____________________________________________ 301
11.3 Creating automatic tasks ___________________________________________________________ 304
11.3.1 To use automatic tasks in a change request _______________________________________ 304
11.4 Relating ad hoc tasks to change requests ______________________________________________ 305
11.4.1 To relate an ad hoc task to a change request ______________________________________ 305
11.5 Relating predefined task group or task templates to a change request ________________________ 306
11.5.1 To add predefined task group and task templates to a change _________________________ 306
11.6 Sequence number in task groups and tasks _____________________________________________ 307
11.7 The Dates tab ___________________________________________________________________ 307
11.8 Managing tasks __________________________________________________________________ 308
11.8.1 Modify a task _______________________________________________________________ 308
11.8.2 Close a task _______________________________________________________________ 309
11.8.3 Cancel a task ______________________________________________________________ 309
11.8.4 Add financial information to a task ______________________________________________ 309
11.9 Adding work information to a task ____________________________________________________ 310
11.9.1 To add work information to a task _______________________________________________ 310
11.10Tracking time for tasks ____________________________________________________________ 310
11.10.1To track task time ___________________________________________________________ 310
11.11Working with task assignments ______________________________________________________ 311
11.11.1 To reassign a task ___________________________________________________________ 311
11.11.2To view tasks assigned to you __________________________________________________ 311
11.11.3To view tasks assigned to your group ____________________________________________ 312
11.11.4To assign a task _____________________________________________________________ 312
11.11.5To assign all tasks in a change requests ___________________________________________ 312
11.12Working on assigned tasks __________________________________________________________ 312
11.12.1To work on tasks assigned to you _______________________________________________ 312
11.13Viewing tasks and task groups _______________________________________________________ 313
11.13.1To view task groups and tasks __________________________________________________ 313
11.14Processing Configuration Management tasks ___________________________________________ 314
11.14.1Policy-based tasks ___________________________________________________________ 314
11.14.2Deployment-based tasks ______________________________________________________ 314
11.14.3Verification-based tasks ______________________________________________________ 314
11.15Using CCM tasks _________________________________________________________________ 315
11.15.1To use CCM tasks to install software and verify compliance ___________________________ 316
11.15.2Best practice CCM task templates and templates ___________________________________ 319
12 Working with reports __________________________________________________________________ 321
12.1 Generating a standard report ________________________________________________________ 321
12.1.1 To generate a report without qualifications ________________________________________ 322
12.1.2 Using the web based reporting console to create and run adhoc reports (video) ___________ 322
12.1.3 Related topics ______________________________________________________________ 323
Page 8 of 452
Using
12.2 Using qualifications to generate a report _______________________________________________ 323

12.2.1 To use qualifications to generate a report _________________________________________ 323
12.3 Using advanced qualifications to generate a report _______________________________________ 324
12.3.1 To generate a report by using advanced qualifications _______________________________ 324
12.4 BMC Change Management predefined reports __________________________________________ 325
12.5 Release Management predefined reports ______________________________________________ 329
13 Using reminders _____________________________________________________________________ 331
13.1 Creating and viewing reminders _____________________________________________________ 331
13.1.1 To view and create reminders __________________________________________________ 331
13.2 Modifying and deleting reminders ____________________________________________________ 332
13.2.1 To modify or delete reminders _________________________________________________ 332
14 Using flashboards ____________________________________________________________________ 333
14.1 Using the KPI flashboards __________________________________________________________ 333
14.1.1 Related topic _______________________________________________________________ 334
14.1.2 Opening the KPI flashboards ___________________________________________________ 334
14.1.3 BMC Change Management KPIs ________________________________________________ 334
14.1.4 BMC Change Management KPI flashboard variables _________________________________ 335
14.1.5 Release Management KPIs ____________________________________________________ 336
14.1.6 Release Management KPI flashboard variables _____________________________________ 336
14.2 Using ROI flashboards _____________________________________________________________ 337
14.2.1 Related topics ______________________________________________________________ 338
14.2.2 Opening the ROI flashboards __________________________________________________ 338
14.2.3 Configuring parameters for the ROI flashboard _____________________________________ 339
14.2.4 Active variables _____________________________________________________________ 340
14.3 Viewing and displaying data ________________________________________________________ 340
15 Using search ________________________________________________________________________ 343
15.1 Managing custom searches _________________________________________________________ 344
15.1.1 To define a custom search ____________________________________________________ 344
15.1.2 To edit or delete a custom search filter ___________________________________________ 345
15.2 Searching all records ______________________________________________________________ 345
15.2.1 To search all records _________________________________________________________ 345
15.3 Searching all change request records from a Hub server ___________________________________ 346
15.3.1 To search all records _________________________________________________________ 346
16 Using social collaboration ______________________________________________________________ 348
16.1 Chat integration _________________________________________________________________ 348
16.2 RSS feeds ______________________________________________________________________ 348
16.3 Twitter integration _______________________________________________________________ 349
16.4 Where to go from here ____________________________________________________________ 349
16.5 Related topics ___________________________________________________________________ 349
16.6 Using chat ______________________________________________________________________ 349
16.6.1 Related topic ______________________________________________________________ 350
16.6.2 Initiating a chat conversation __________________________________________________ 350
16.6.3 Adding BMC Remedy AR System users who are not present in the Friends list _____________ 354
Page 9 of 452
Using
16.7 Subscribing to RSS feeds ___________________________________________________________ 356

16.7.1 To subscribe to RSS feeds _____________________________________________________ 357
16.8 Receiving BMC Remedy ITSM broadcasts on Twitter ______________________________________ 357
16.8.1 To follow ITSM notifications on Twitter __________________________________________ 358
17 Using BMC Atrium Service Context _______________________________________________________ 359
17.1 To open the Service Context Summary window from a console _____________________________ 360
17.2 To open the Service Context Summary window from the record ____________________________ 360
17.3 Interpreting the information ________________________________________________________ 361
17.4 Related topic ____________________________________________________________________ 361
18 Using the Calendar ___________________________________________________________________ 362
18.1 What's new in the 8.1.00 calendar ____________________________________________________ 363
18.1.1 Additional Change Calendar views ______________________________________________ 363
18.1.2 Additional time duration options ________________________________________________ 364
18.1.3 Quick actions for calendar entries ______________________________________________ 364
18.1.4 View event details ___________________________________________________________ 364
18.1.5 Visual representation of collisions _______________________________________________ 365
18.1.6 Impact analysis _____________________________________________________________ 365
18.1.7 Configurable color schemes for change and release requests __________________________ 365
18.1.8 Display of CI outages ________________________________________________________ 365
18.2 Locating 8.0 features in the new calendar ______________________________________________ 365
18.2.1 Filters in the left pane ________________________________________________________ 365
18.2.2 Saved filters and quick filters ___________________________________________________ 366
18.2.3 Main calendar view __________________________________________________________ 367
18.2.4 Change Calendar administration options _________________________________________ 367
18.3 Calendar functional areas __________________________________________________________ 368
18.3.1 Filters & Queries ____________________________________________________________ 369
18.3.2 Time durations _____________________________________________________________ 371
18.3.3 Legend ___________________________________________________________________ 371
18.3.4 Event InfoTips ______________________________________________________________ 372
18.3.5 Details flyout pane __________________________________________________________ 372
18.3.6 Right-click menu commands __________________________________________________ 372
18.3.7 Drag-and-drop events _______________________________________________________ 373
18.3.8 Menu icons ________________________________________________________________ 373
18.4 Change Calendar views ____________________________________________________________ 374
18.4.1 Calendar view ______________________________________________________________ 374
18.4.2 Eventlist view ______________________________________________________________ 376
18.4.3 Timeline view ______________________________________________________________ 378
18.5 Using the date picker on the Change Calendar __________________________________________ 380
18.6 Creating user-defined queries in the Change Calendar ____________________________________ 380
18.6.1 To create or modify a user-defined query _________________________________________ 381
18.7 Exporting events to the ICS file ______________________________________________________ 382
18.8 Example of using Change Calendar ___________________________________________________ 382
19 TMS templates ______________________________________________________________________ 383
Page 10 of 452
Using
19.1 Task templates __________________________________________________________________ 384

19.1.1 Creating a task template ______________________________________________________ 386
19.1.2 Example of creating task templates with a workflow _________________________________ 392
19.2 Task group templates _____________________________________________________________ 397
19.2.1 Basic task group templates - Sequencing type _____________________________________ 398
19.2.2 Advanced task group template - Standard type _____________________________________ 401
19.3 Variable templates ________________________________________________________________ 410
19.3.1 Creating variable templates ____________________________________________________ 412
19.4 Predefined task group and task templates ______________________________________________ 413
20 Registering time segments _____________________________________________________________ 415
20.1 Understanding server time, time zones, and time segments _________________________________ 415
20.2 Registering time segments for CIs - Creating a blackout schedule ____________________________ 416
20.2.1 Defining time segments for CIs _________________________________________________ 417
20.2.2 Viewing CI relationships ______________________________________________________ 418
20.2.3 Viewing CI time segments _____________________________________________________ 419
20.2.4 Relating CI time segments _____________________________________________________ 419
20.2.5 Removing CI time segments ___________________________________________________ 419
20.3 Registering unique business events and operational categorizations __________________________ 420
20.3.1 To create and register a time segment for a business event or an operational category ______ 420
20.3.2 Searching for business time or operational time segments ____________________________ 421
20.3.3 Viewing and removing time segments ___________________________________________ 422
20.3.4 Relating time segments _______________________________________________________ 423
20.4 Using Schedule Assist to search for available times _______________________________________ 423
20.4.1 To search available times for change requests _____________________________________ 424
21 Change notifications __________________________________________________________________ 429
21.1 Notifications by groups ____________________________________________________________ 429
21.2 Notifications by roles _____________________________________________________________ 430
22 Sending pages and email messages _______________________________________________________ 431
22.1 Sending email ___________________________________________________________________ 431
22.1.1 To send an email message _____________________________________________________ 431
22.2 Paging a person or on-call group ____________________________________________________ 432
22.2.1 To page a person or an on-call group ____________________________________________ 432
23 Managing SLM service targets ___________________________________________________________ 434
24 Enabling the Change Implementer support group assignment __________________________________ 435
24.1 To enable the Change Implementer support group assignment _____________________________ 435
25 Index ______________________________________________________________________________ 436
Page 11 of 452
Using
This section describes how to complete tasks that are associated with the user goals for BMC Change
Management.
Accessing the interface (see page 13)
Navigating the interface (see page 14)
Using Global search (see page 67)
Viewing your profile (see page 80)
Using BMC Change Management (see page 81)
Using Release Management (see page 188)
Working with relationships (https://docs.bmc.com/docs/display/change81/Working+with+relationships)
Working with broadcasts (https://docs.bmc.com/docs/display/change81/Working+with+broadcasts)
Working with records (https://docs.bmc.com/docs/display/change81/Working+with+records)
Working with costs (see page 292)
Working with tasks (see page 299)
Working with reports (https://docs.bmc.com/docs/display/change81/Working+with+reports)
Using reminders (see page 331)
Using flashboards (https://docs.bmc.com/docs/display/change81/Using+flashboards)
Using search (https://docs.bmc.com/docs/display/change81/Using+search)
Using social collaboration (https://docs.bmc.com/docs/display/change81/Using+social+collaboration)
Using BMC Atrium Service Context (see page 359)
Using the Calendar (see page 362)
TMS templates (https://docs.bmc.com/docs/display/change81/TMS+templates)
Registering time segments (see page 415)
Change notifications (see page 429)
Sending pages and email messages (see page 431)
Managing SLM service targets (see page 434)
Enabling the Change Implementer support group assignment (see page 435)
Page 12 of 452
Using
1 Accessing the interface

This topic describes how to start the BMC Remedy IT Service Management suite of applications from your
browser.
1.1 To log in and access the BMC Remedy ITSM Suite

applications
1. Type the following URL into your browser:
http://<webServer>:<port>/arsys/shared/login.jsp
<webServer>: Fully qualified name of the BMC Remedy Mid Tier system, specified in the format
server_name.company.com.
<port>: (Optional) Port number (required if the web server is not on the default port)
2. In the User Name and Password fields of the Welcome page, enter your user name and password.
3. Click Login. The IT Home Page (https://docs.bmc.com/docs/display/itsm81/IT+Home+page) opens.
Note
The IT Home page opens by default, however, system administrators can configure another home
page (https://docs.bmc.com/docs/display/ars81/Configuring+home+page+preferences) to open, instead.
Page 13 of 452
Using
2 Navigating the interface

This section provides the following information:
Best Practice and Classic views (see page 14)
IT Home page (see page 31)
Navigating consoles, forms, and modules (see page 35)
User interface standards for field labels (see page 39)
Icons used in the interface (see page 39)
Using the Change Management Console and the Change form (see page 40)
Using the Release Management console and the Release form (see page 48)
Using the Change Management Dashboard (see page 56)
Tooltip data shown in consoles (see page 58)
Tooltip data shown in Change Calendar (see page 58)
Working with the Requester console (see page 59)
Working with the Overview console (see page 61)
2.1 Best Practice and Classic views

BMC Remedy ITSM provides both a Best Practice view and a Classic view for key forms.
The Best Practice view is an improved version of the form. In this view, the fields most commonly used are
immediately visible. You can access less frequently used functionality from the tabbed sections of the form or
from the links in the navigation pane. For example on the Incident request form, the Templates field is included in
the Best Practice view to encourage the use of templates.
The Classic view is a view of the form similar to the view provided in earlier releases. This view is provided for
customers who are upgrading from earlier versions of BMC Remedy ITSM applications and who have not yet
adopted the Best Practice view. You can configure many of the BMC IT Service Management (ITSM) suite
applications for either the Best Practice view or the original Classic view. You perform the view configuration at
the application, group, or individual user level.
This section explains why Best Practice views were developed (
https://docs.bmc.com/docs/display/itsm81/Development+of+Best+Practice+views), outlines the benefits of using (
https://docs.bmc.com/docs/display/itsm81/Benefits+of+Best+Practice+views) them, and provides some
recommendations (https://docs.bmc.com/docs/display/itsm81/Best+Practice+and+Classic+view+recommendations) for

deploying them.
Best Practice views are available for the following applications and modules in the BMC Remedy ITSM Suite:
Change request
Page 14 of 452
Using
Incident request
Known error
Problem investigation
Release request
Work Order
For information about the benefits of Best Practice view in each application, see Benefits of Best Practice views (
https://docs.bmc.com/docs/display/itsm81/Benefits+of+Best+Practice+views).
Note
If a procedure description in the documentation differs depending on the view, both methods are
described. Instructions for the Best Practice view are provided first.
Note
The Virtualization Lifecycle Management view is the same as the Best Practice View, and all additional
features provided for the VLM view were incorporated in BMC Change Management 7.6.04.
2.1.1 Benefits of Best Practice view in BMC Change Management

The following table describes the benefits of the Best Practice view in BMC Change Management.
Note
In the table that follows, the Navigation pane links are not mentioned if they are available from the
Navigation pane in both views, even if the link is accessed from a different group on the Navigation
pane.
Benefits to the Best Practice view of the Change Infrastructure form

Feature
Classic view
Best Practice view
Benefits
Page 15 of 452
Using
Feature
Classic view
Best Practice view
Benefits
Assignment
Fields on
Fields on Main view:
Key information for managing change requests includes knowing which
Coordinator Group
group and which person is responsible for coordinating the change until it is
closed.
Assignment tab:
Support Company
Support
Organization
Support Group
Name
Tooltip
displaying
organizational
structure
Change
Assignee
Tooltip
displaying
Name, Email,
Telephone
and Site
Set
Assignment
using
Change
Location
Several fields on
Requester tab
Type ahead
Menu button enables
selection of group
using organizational
structure
Tooltip displaying
organizational
structure
Change Coordinator
Type ahead
Tooltip displaying
Name, Email,
Telephone, and Site
Best practice recommends that that the change coordinator is the same
person who creates the change request. This is why these fields are
automatically completed with the submitter's information if that person has
the functional role of Change Coordinator or Change Manager.
If you leave the fields blank, the Assignment rules determine the field values
after the submission.
Key change request management information includes knowing where the

change is coordinated from. The application also uses this field to determine
Change Location
access rights for multitenancy implementations.
Type ahead
Tooltip
This field shows the
lowest level of
location information
of the change
coordinator.
Page 16 of 452
Using
Feature
Classic view
Best Practice view
Benefits
Service
Field on Main view:
Field on Main view:
This field was moved to the Main view, because the information it contains is
Service
Service
considered key information.
Type ahead
Field label link opens
the Service CI
View Business Service
icon allows you to
display configuration
details of the
selected service
Service context
widget can be
launched to display
essential status
information about
the selected service
Template
Available on the
Field on Main view:
Navigation pane
under Quick links
Template
Out-of-the-box, the Service field is a required field. This ensures that service
awareness is used for routing purposes and metrics can be tracked by the
selected Service. However, you can configure the field to not be required.
Note: The only services that you can select are the ones that the customer is
entitled to see. Entitlement is based on a Used By relationship with the
Service and the customer, or the organization to which the customer
belongs.
Adding the Template field to the Main view encourages the use of templates
and enables you to search and report on the changes created by template.
Type ahead
Searchable
Notes
Field on
Classification tab:
Field on Main view:
The Notes field contains key change information.
Notes
Notes
Class
Field on
Classification tab:
Field on Main view:
The Class field contains key change information.
Class
Note: Standard value was introduced in both views for release 7.6.00 of the
BMC Remedy ITSM suite.
Change Timing
Target Date
(introduced in
BMC Remedy
ITSM suite
7.6.00)
Field on Dates tab:
Field on Main view:
The Target Date is part of the key change information.
Target Date
Target Date
The Target Date is the date by when the change must be completed,
according to the applicable service level targets. Alternatively, the target
date can be a date that is agreed to on an ad hoc basis, per change.
Change Type
Available on Main
view
No longer available
This field is not used by the majority of customers, so it was removed from
the view. Background processes always set the field value to Change, for
workflow purposes.
Page 17 of 452
Using
Feature
Classic view
Best Practice view
Benefits
Requested By
Field on Requester
Fields no longer available
Best practice recommends that you review the related incident requests or
tab:
known errors, or both, to determine who requested the change, because the
change could have been requested by multiple people.
Support Company
First Name
Middle Name
Last Name
Phone Number
Organization
Department
Support
Organization
Support Group
Name
Requested For
Field on Requester
Available as a link under
Non-essential information that is used infrequently is moved to other areas,
tab:
Quick Actions
which provides a more streamlined application.
First Name
Last Name
Change
Manager
Work Info
Best practice is to review the related incident requests or known errors, or

both, to determine the request originators.
Fields on
Assignment tab:
Fields on Main view (Work

Detail tab):
Support Company
Support
Organization
Support Group
Name
Change Manager
Set Assignment
using
Manager Group
Change Manager
Table on Work Info

tab
Fields and table on Work

Detail tab (shown initially):
The Manager Group and Change Manager fields contain key change
information.
The "Set assignment

using" feature can be
accessed using the
button to the right of
the Manager Group
field.
Key change request information includes Work Info entries.
Notes
First attachment
Additional fields
hidden in More
Details expand area:
Work Info type
2nd and 3rd
attachments
Locked
View Access
Approval
Table on Approvers
tab
Table on Main view (Work

Detail tab)
The Approvers table contains key change information.
Page 18 of 452
Using
Feature
Classic view
Best Practice view
Benefits
Time Spent
Fields on
Fields on Date/System tab:
The fields were moved but kept in the view.
Assignment tab:
Start Time
Start Time
Time Spent (min)
Time Spent (min)

Total Time Spent (min)
Total Time Spent

(min)
Change
Implementer
Fields on
Assignment tab:
Fields no longer displayed
These fields are used when the change has no tasks associated with it. The
recommended best practice is to always coordinate the implementation of a
change using tasks. This is why these fields are not considered essential.
Support Company
Support
Organization
Support Group
Name
Change
Implementer
Set Implementer
using
Operational
Categorization
Fields on
Classification tab:
Tier 1
Tier 2
Tier 3
Fields available for quick

selection using the Select
Operational link under
Quick Actions (introduced
in BMC Remedy ITSM
suite7.6.00).
Customers can view all
operational and product
categorization values using
the Categorization links.
Product
Categorization
Fields on
Classification tab:
Tier 1
Tier 2
Tier 3
Product Name
Model/Version
Manufacturer
Fields on Categorization tab

(if configured to be
displayed):
Tier 1
Tier 2
Tier 3
Product Name
Model/Version
Manufacturer
Research suggested that most BMC customers use the operational

categorization fields only sporadically. This means that even when the fields
are completed, they cannot be used for reporting, because they are not
consistently completed.
Based on this, access to the fields was moved to a tab, which you configure
to appear or be hidden, according to your organization's needs.
Note: You can specify the operational categorization values for each
template.
These fields were moved to the Navigation pane, because using the CMDB is
a better way to perform grouping, trending, and assignment. This, and
wanting to reduce the registration time of new incident request records,
means that now the product categorization is automatically completed
based on the product categorization of the related service.
Type-ahead available
for all fields.
Auto-complete and
prefill available for
Product Name
Page 19 of 452
Using
Feature
Classic view
Best Practice view
Benefits
Classification
Fields on
Key information for change requests includes the fields that were moved to
Change Reason
the Main view.

The Lead Time, Business Justification, Change Environment, and
Classification tab:
Timing Reason
Lead Time
Change Reason
Business
Justification
Change
Environment
Sequence
Notes
Performance Rating fields are not displayed on the Best Practice view;
research showed the majority of customers are not using these fields for
Field on Date/System
tab:
Timing Reason
Field on the
Relationships tab:
Sequence
reporting or for change resolution.
Performance Rating
Notes
The other
fields are
shown in
other rows in
the table.
Financials
Available as the
Financial tab

Links
Nonessential information is moved to other areas, providing a more

streamlined application.
Dates
The Date fields are

on the Date tab
The Date fields are on the

Date/System tab, with the
The two date fields were not considered essential for change resolution or
reporting.
exception of RFC Date and

In Production Date
Next Stage
Not available
The Next Stage button was

introduced in the Best
This button was added to increase efficiency.
Practice view
Read-only
When the user does
When the user does not
behavior
not have modify

access, all fields are
have modify access, the

following message is
disabled and
read-only
displayed at the top of the

form:
The change aids simplification and enhances performance.
You do not have permission

to modify this ticket.
The fields are not disabled
or read-only, but the user
will not be able to save any
modifications
Page 20 of 452
Using
Feature
Classic view
Best Practice view
Benefits
Vendor
Fields on Vendor
Fields on Main view (Work
The overall number of fields displayed for Vendor assignment has been
tab:
Detail tab):
reduced, and the key fields were moved to the Main view. This was done
because they are part of the key information that should be immediately
Vendor Company
Vendor
Vendor Group
Vendor Ticket Number
available when reviewing an incident.
Organization
Vendor Group
Additional information can be registered and reviewed in Work Info.
Vendor First Name

Vendor Last Name
Vendor Phone
Vendor Email
Vendor Assignment
Status
Vendor Ticket
Number
Reported to Vendor
Date
Vendor Responded
Date
Vendor Resolved
Date
2.1.2 Benefits of Best Practice view in the Release Management module

The following table describes the benefits of the Best Practice view in the Release Management module of BMC
Change Management.
Note
In the table that follows, the Navigation pane links are not mentioned if they are available from the
Navigation pane in both views, even if the link is accessed from a different group on the Navigation
pane.
Benefits to the Best Practice view of the Release Management form

Feature
Classic view
Best Practice view
Benefits
Page 21 of 452
Using
Feature
Classic view
Best Practice view
Benefits
Assignment
Fields on
Key information for managing release requests includes knowing which
Coordinator Group
group and which person is responsible for coordinating the release until it is
closed.
Assignment tab:
Support Company
Support
Organization
Support Group
Name
Tooltip
displaying
organizational
structure
Release
coordinator
Tooltip
displaying
Name, Email,
Telephone
and Site.
Set
Assignment
using
Release
Location
Several fields on
Requester tab
Type ahead
Menu button enables
selection of group
using organizational
structure
Tooltip displaying
organizational
structure
Release Coordinator
Type ahead
Tooltip displaying
Name, Email,
Telephone, and Site
Best practice recommends that that the release coordinator is the same
person who creates the release request. This is why these fields are
automatically completed with the submitter's information if that person has
the functional role of Release Coordinator.
If you leave the fields blank, the Assignment rules determine the field values
after the submission.
Key release management information includes knowing where the release is

coordinated from. The application also uses this field to determine access
Release Location
rights for multitenancy implementations.
Type ahead
Tooltip
This field shows the
lowest level of
location information
of the release
coordinator.
Page 22 of 452
Using
Feature
Classic view
Best Practice view
Benefits
Service
Field on Main view:
Field on Main view:
This field was moved to the Main view, because the information it contains is
Service
Service
considered key information.
Type ahead
Field label link opens
the Service CI
View Business Service
icon allows you to
display configuration
details of the
selected service
Service context
widget, which can be
launched to display
essential status info
about the selected
service
Template
Available on the
Field on Main view:
Navigation pane
under Quick links
Template
Out-of-the-box, the Service field is a required field. This ensures that service
awareness is used for routing purposes and metrics can be tracked by the
selected Service. However, you can configure the field to not be required.
Adding the Template field to the Main view encourages the use of templates
and enables you to search and report on the changes created by template.
Type ahead
Searchable
Notes
Field on
Classification tab:
Field on Main view:
The Notes field contains key release information.
Notes
Notes
Business
Justification
Field on
Classification tab:
Field on Main view:
The Business Justification field contains key release information.
Business Justification
Business
Justification
Target Date
(introduced in
release 7.6.00
of BMC
Remedy ITSM
Suite)
Required
Field on Dates tab:
Field on Main view:
The Target Date is part of the key release information.
Target Date
Target Date
The Target Date is the date by when the release must be completed,
according to the applicable service level targets. Alternatively, the target
date can be a date that is agreed to on an ad hoc basis, for each release.
Page 23 of 452
Using
Feature
Classic view
Best Practice view
Benefits
Work Info
Table on Work Info
Fields and table on Work
Key release information includes Work Info entries.
tab
Detail tab (shown initially):

Notes
First attachment
Additional fields hidden in
More Details expand area:
Work Info type
2nd and 3rd attachments
Locked
View Access
Release Type
Field on
Classification tab
Field on Main view
The Release Type is used to identify the type of release that is being handled.
Requester
Requester fields are

on the General tab
Fields not available
Best practice recommends that you review the related incident requests or
known errors, or both, to determine who requested the release. The release
could have been requested by multiple people.
Time Spent
Fields on
Assignment tab:
Field on Date/System tab:
The Cumulative Efforts field was added in preparation for the automatic
roll-up of time tracked in related activities and changes.
Cumulative Efforts
Time Spent for
Activities (min)
Total Time Spent for
Changes (min)
Approval
Table on Approvers
tab
Table on Main view (Work

Detail tab)
The Approvers table contains key release information.
Operational
Categorization
Fields on
Classification tab:
Fields available for quick

selection using the Select
Operational link under
Quick Actions (introduced
in BMC Remedy ITSM suite
7.6.00)
Customers can view all
operational and product
categorization values using
the Categorization links.
Research suggested that most BMC customers use the operational

categorization fields only sporadically. This means that even when the fields
are completed, they cannot be used for reporting, because they are not
consistently completed.
Tier 1
Tier 2
Tier 3
Based on this, access to the fields was moved to a tab, which you configure
to appear or be hidden, according to your organization's needs.
Note: You can specify the operational categorization values for each
template.
Page 24 of 452
Using
Feature
Classic view
Best Practice view
Benefits
Product
Fields on
Fields on Categorization tab
These fields were moved to the Navigation pane, because using the CMDB is
Categorization
Classification tab:
(if configured to be
displayed):
a better way to perform grouping, trending, and assignment. This, and

wanting to reduce the registration time of new incident request records,
Tier 1
Tier 2
Tier 3
Product Name
Model/Version
Manufacturer
Tier 1
Tier 2
Tier 3
Product Name
Model/Version
Manufacturer
Type-ahead available
for all fields.
Auto-complete and
prefill available for
Product Name
means that now the product categorization is automatically completed

based on the product categorization of the related service.
Financials
Available on the
Financial tab

Links
Nonessential information is moved to other areas, providing a more

streamlined application.
Dates
Fields on the Dates

tab
Fields on the Date/System

tab with the exception of
The two date fields are not considered essential for the release resolution or
for reporting purposes.
Actual Start Date and Actual

End Date
Next Stage
Not available
The Next Stage button was

introduced in the Best
These buttons were added to increase efficiency.
Practice view.
Read-only
When you do not
When you do not have
behavior
have modify access,

all fields are disabled
modify access, the

following message is
and read-only.
displayed at the top of the

form:
This aids with simplification and enhances performance.
You do not have permission

to modify this ticket.
The fields are not disabled
or read-only, but you
cannot save any
modifications.
2.1.3 Best Practice view - Change Request form

The Best Practice view is an improved version of the Change Request form. In this view, the fields most
commonly used for creating change requests are immediately visible. You can access additional, less frequently
used functionality from the tabbed sections of the form or from the links in the Navigation pane.
The following list outlines Best Practice view features:
Page 25 of 452
Using
Coordinator Group field The Coordinator Group and the Change Coordinator field replace the Change
Assignee fields. Use the Coordinator Group field to select a support group. The support groups that appear
in the menu each have at least one member with a Change Coordinator functional role. From the
Coordinator Group menu, you select the company, the organization, and then the support group. Only the
selected support group name appears in the Coordinator Group field. You can type only a few characters
and press Enter. If a unique match is found, the field is populated with the value or a list of coordinator
groups is displayed from which you can select a value, if multiple matches are found.
Change Coordinator field Use the Change Coordinator field to select a Change Coordinator for the
change request. The people whose names appear on this menu belong to the support group selected in
the Coordinator Group field and have a Change Coordinator functional role. You can type only a few
characters and press Enter. If a unique match is found, the field is populated or a list of change coordinator
belonging to the selected coordinator group is displayed from which you can select a value, if multiple
matches are found.
Service field The Service field relates business service configuration items (CIs) to the change request at
the time it is created.
Template field The Template field encourages the use of templates. For information about the benefits
of using templates and how to select a template for a change request, see Selecting change templates (see
page 94).
Class field The Class field now behaves as the Change Timing field. It specifies the relative urgency of the
change, so that the approvers can assess its magnitude.
Page 26 of 452
Using
Recommendation
The Best Practice view is recommended for all BMC Change Management users, regardless of their role.
For information about BMC Change Management roles, see User roles in the change request lifecycle (
https://docs.bmc.com/docs/display/change81/User+roles+in+the+change+request+lifecycle).
The following figure illustrates the Best Practice view.

Change Request form Best Practice view
2.1.4 Best Practice view - Release Request form

The Best Practice view is an improved version of the Release Management form. In this view, the fields most
commonly used for creating release requests are immediately visible. You can access additional, less frequently
used functionality from the tabbed sections of the form or from the links in the navigation pane.
The following list outlines Best Practice view features:
Page 27 of 452
Using
Coordinator Group field Use the Coordinator Group field to select a support group. The support groups
that appear in the menu each have at least one member with a Release Coordinator functional role. From
the Coordinator Group menu, you select the company, the organization, and then the support group. Only
the selected support group name appears in the Coordinator Group field. You can type only a few
characters and press Enter. If a unique match is found, the field is populated with the value or a list of
coordinator groups is displayed from which you can select a value, if multiple matches are found.
Release Coordinator field Use the Release Coordinator field to select a Release Coordinator. The people
whose names appear on this menu belong to the support group selected in the Coordinator Group field
and have a Release Coordinator functional role. You can type only a few characters and press Enter. If a
unique match is found, the field is populated or if multiple matches are found a list of release coordinators
belonging to the selected coordinator group is displayed from which you can select a value.
Service field The Service field relates business service configuration items (CIs) to the release at the time
it is created.
Template field The Template field encourages the use of templates. For information about the benefits
of using templates and how to select a template for a release request, see Selecting release templates (see
page 198).
Business Justification field The Business Justification field indicates the business reason for the release
request. It specifies the importance of the release so that the approvers can assess its magnitude.
Page 28 of 452
Using
Recommendation
The Best Practice view is recommended for all Release Management users, regardless of their role.
The following figure illustrates the Best Practice view.
Release Request form Best Practice view
2.1.5 Classic view - Change Request form

The Classic view is the Change Management Console as it appeared in previous releases of BMC Change
Management. This view is provided for customers who are upgrading from earlier versions of BMC Change
Management and who are not yet ready to adopt the Best Practice view.
The following changes have been made to the classic view:
The Change Assignee field has been replaced with Coordinator Group and Change Coordinator fields.
The Change Manager fields have been changed to Manager Group and Change Manager fields.
Page 29 of 452
Using
The Change Timing field has been renamed to Class field. It specifies the relative urgency of the change, so
that the approvers can assess its magnitude. This field can be found on the Classification tab of the change
request.
The following figure illustrates the Classic view.
Change Request form Classic view
2.1.6 Classic view - Release Request form

The Classic view is the Release Management console as it appeared in previous releases of Release Management.
This view is provided for customers who are upgrading from earlier versions of Release Management and who are
not yet ready to adopt the Best Practice view.
A new functional role, Release Coordinator, was introduced in BMC Change Management version 7.6.00. The
following fields corresponding to this role were added to the classic view:
Coordinator Group
Release Coordinator
These fields replaced the Release Manager field on the Assignment tab in the Release Request form.
Page 30 of 452
Using
The following figure illustrates the Classic view.

Release Request form Classic view
2.2 IT Home page

When you start the BMC Remedy IT Service Management Suite, the IT Home page displays the Overview console
by default. However, you can set up what you want to see on the IT Home page. If you are a system
administrator, you can configure the page for all users. Otherwise, you can configure your own user ID to see
your views.
This topic provides the following information:
IT Home page and its functional areas (see page 32)
Configuring the IT Home page (see page 34)
To add or delete panels (see page 34)
To configure panels (see page 34)
To expand and collapse panels (see page 35)
To restore a default IT Home page view (see page 35)
To hide or show the navigation pane (see page 35)
Page 31 of 452
Using
Customizing and using the IT Home page video (see page 35)
The following figure illustrates the functional areas of the IT Home page.
2.2.1 IT Home page and its functional areas

The following table describes each of the functional areas of the IT Home page.
Functional
area
Purpose
Home page header

Logout
Click Logout to exit the application.
Breadcrumb
bar
The breadcrumb bar helps you keep track of the records you are viewing and helps with navigation. For more information about
breadcrumbs, refer to Navigating consoles, forms, and modules (
https://docs.bmc.com/docs/display/itsm81/Navigating+consoles%2C+forms%2C+and+modules).
Global search
Type in a word or a phrase in the search area, and the application will search across multiple forms for records that match your
input. For more information about global search, refer to Using Global search (
https://docs.bmc.com/docs/display/itsm81/Using+Global+search).
Navigation pane
Page 32 of 452
Using
Functional
area
Purpose
Application
menu
Depending on your permissions and other installed applications, the following links are displayed. Use them to open consoles for
applications as well as consoles for other features.
Quick Links
AR System Administration
AR System Sample Application
Administrator Console
Analytics
Asset Management
Atrium Core
Atrium Integrator
Change Management
Change Management Dashboard
Contract Management
Data Management
Foundation Elements
Incident Management
Knowledge Management
Problem Management
Process Designer
Product Catalog
Release Management
Requester Console
Return On Investment
Service Level Management
Service Request Management
Task Management
Virtual Agent
Note: When you run your mouse over the applications, you see a second menu. You can select one of those options to go
directly to a form. For example, roll over Change Management and select Change/Release Calendar. The Calendar screen
appears.
Configuration
Use these buttons to configure your panel display.
Buttons
Overview
console
Company
and View By
These fields combine to provide a way to indicate the company name and the assigned-to categories filtering the records in the
Console List table.
Refresh
This button refreshes the data in the table.
Preferences
This button allows you to set preferences for the console list table. You can remove columns, set refresh intervals, reset and save
your preferences.
Console List
table
This table lists the different types of requests.
Page 33 of 452
Using
2.2.2 Configuring the IT Home page

You can configure the IT Home page to display information of your choice. For example, Bob Baxter is the
Manager for payroll at Calbro Services. He likes to keep track of all potential problems, changes, and incidents
pertaining to his department. He also tracks software license contracts so that he knows which ones are about to
expire. Bob configures his panels to display all the information he is looking for, as follows:
Asset Management > Contracts About to Expire in 90 Days
Change Management > All Open Changes with Extensive Impact
Incident Management > All Open Incidents with Extensive Impact
Problem Management > All Open Problems by Status and Priority
To add or delete panels

You can specify how many panels to display on your IT Home page up to a maximum of four panels.
1. In the IT Home page, click the
button.
Four panels appear.

2. To delete a panel, click the
button on the panel.
To configure panels
You can select what to display on your IT Home page.
Note
You can configure your panels only with options for which you have permissions.
1. In the panel, click the Show list and run your cursor over the list of options.
2. From the list of work areas for each option, select the one to display (for example, Asset Management >
Software Certificates).
The panel displays your selection.
3. Repeat steps 1 and 2 for your other panels.
To change display on a panel, click the
4. Click the
button to display the Show list, and make another selection.
button to save your IT Home page.
A dialog box confirms that your customized layout has been saved.
5. Click OK.
When you next log on, you will see your saved IT Home page.
Page 34 of 452
Using
To expand and collapse panels

1. In the panel, click the
button.
The panel collapses.

2. In the panel, click the
button.
The panel expands to its original size.
To restore a default IT Home page view

1. In the IT Home page, click the
button.
A dialog box informs you that the default layout for this page will be brought back.
2. Click OK to proceed or Cancel to retain your current layout.
If you click OK, the panels on the IT Home page disappear and the Overview Console is displayed.
To hide or show the navigation pane

In the IT Home page, click the Applications button to hide or show the navigation pane.
2.2.3 Customizing and using the IT Home page video

Disclaimer
Although the concepts and procedures presented in this video are correct, the user interfaces shown are
not current.
View video on YouTube (http://www.youtube.com/watch?v=66vLUiy10go)
(http://www.youtube.com/watch?v=66vLUiy10go)
2.3 Navigating consoles, forms, and modules

This topic describes how to navigate around BMC Remedy ITSM consoles, forms, and modules:
What happens to data as I move back and forth on the breadcrumb trail? (see page 37)
How does the breadcrumb trail behave with forms in Search mode? (see page 37)
Can I force a second window to open? (see page 38)
Which consoles, forms, and modules open in a new window? (see page 38)
Page 35 of 452
Using
In most cases, when you open consoles, forms, and modules from the IT Home page, they open inside the IT
Home page view. Similarly, if you open a form from a console, the form replaces the console in the view.
Note
If you are working in a hub and spoke environment and open a spoke server record from the hub server,
the spoke server record opens in its own window. Each subsequent spoke server record that you open
from a hub server also opens in its own window. You can open as many spoke server windows as
necessary.
Be aware that opening a spoke server record on a hub server can take a little longer than it does to open
records in environments that are not configured for the Hub and Spoke capability. This is because the
hub server must first determine which spoke server to connect to and then open the record in separate
browser window.
If you open a related record from a form, the related record opens in the view that was occupied by the form. For
example, if you are working with a problem investigation (the "parent" record) and from the parent record you
open a related incident request, the incident request replaces the parent record in the view. If you then open a
change request from the incident request, the change request replaces the incident request in the view, and so
on. To help you keep track of the records you are viewing and to help with navigation, there is a breadcrumb bar
across the top of the view field.
Note
Not all of the consoles, forms, and modules open in the view area. For example, the BMC Remedy AR
System Approval Central module opens in a new window. When a console, module, or form opens in a
window, it is not added to the breadcrumb bar.
The breadcrumb bar contains links to the records that you opened from the parent record. When you open a
record, the breadcrumb trail expands along the breadcrumb bar to the right, with the new link. If there are more
than six links in the breadcrumb trail, arrows appear at one or both ends of the bar that let you scroll back and
forward on the bar to see links not currently in the view.
The first link in the breadcrumb trail indicates the place from which you started. It can be a console or a form. For
example, if you open a change request record directly from the IT Home page, the first link in the breadcrumb
trail takes you to the change request.
Page 36 of 452
Using
The last link corresponds to the record currently in the view. If you open a link to the left of the record currently
in view, the system truncates the breadcrumb trail to that link. The history is retained, however, so you can use
the back and forward arrows in the navigation controls to move through the bar one record at a time. There is
also a history of your most recently viewed records, which you can use to move directly to a record. Click the
down arrow to open the history list.
Note
The Forward button is only visible after you move back down the breadcrumb bar by opening a link to a
record that you previously viewed.
The breadcrumb navigation buttons and bar
If you are viewing a record from the middle of the breadcrumb trail and then branch off to another parent-type
record, the system removes the forward breadcrumb trail from the point where you branched off and starts a
new history from there, using the new parent-type record as the starting point. For example: You open a problem
investigation, then open a related incident request, and from the incident request you open a related change
request. If you go back to the incident request record and then open a second problem investigation, the
breadcrumb bar no longer contains a link to the change request. The breadcrumb trail now shows the original
problem investigation, the incident request, and the second problem investigation. It then shows any related
records that you subsequently open from the second problem investigation.
When you close the parent record, the system removes the breadcrumb history.
2.3.1 What happens to data as I move back and forth on the breadcrumb
trail?
If you are entering information into a record and open another record from the breadcrumb trail, the system
prompts you to save the work, if you have not done so. If you do not save the information, the system does not
preserve it on the record and you must re-enter it later.
If someone updates a record on your breadcrumb trail that is not currently in the view, those changes are visible
to you when you open the record again.
2.3.2 How does the breadcrumb trail behave with forms in Search mode?
If you run a search from a form that is in Search mode, the last entry in the breadcrumb trail is the name of the
form.
When you open a record from the search results table, that record does not appear in the breadcrumb trail.
However, if you drill down through that record to open other related records, those related records will appear in
the breadcrumb trail.
Page 37 of 452
Using
To return to the originating record, use the history list.
Note
All of the records that you open from a form in Search mode are added to the history list.
To return to the results table, click the name of the form in the breadcrumb trail.
2.3.3 Can I force a second window to open?

If you press the Shift key and then double-click a record entry in any table, the record opens in a second window.
Also, if you hold the Shift key and click a link, button, and so on, the form or dialog box associated with the link or
button opens in another window.
Note
If there is a record in the history list that you want to open in a second window, press the Shift key and
then double-click the entry.
If you are working in a new record that has not yet been saved and open a new child type record (task, activity, CI,
and so on), the system will open a new window automatically to accommodate the new child record. This
prevents the information in the new, unsaved parent record from being lost.
2.3.4 Which consoles, forms, and modules open in a new window?

Not all of the consoles, forms, and modules open in the IT Home page's view. The consoles, forms, and modules
in the following list open in a new window. If you open one of these from the IT Home page, any unsaved
changes to the IT Home page are lost.
Tip
Before you open any of the following consoles, forms, or modules, save the changes to the IT Home
page that you want to keep.
BMC Action Request System Administrator

Application Administration
BMC Service Level Management
Analytics
Service Management Process Model
Page 38 of 452
Using
2.4 User interface standards for field labels

On BMC Remedy ITSM forms, field labels provide data entry hints.
The following table lists the significance of field-label formats and special characters.
Significance of field labels for data entry
Field-label format
or special
characters
Significance for data entry
Bold label
followed by an
asterisk (*)
Field is required to submit and update the form.
Field label not

bolded
Field is optional.
Italicized label
System-generated value for this field. Typically this field is read-only for the user.
Label followed by
Additional functionality is associated with this field. Typically, you access this functionality by pressing Enter. For example, you
might press Enter in a field to access a search dialog box or to perform a search based on the value typed into the field.
If a field label followed by a plus sign is also bolded, the field is required. Otherwise, the field is optional.
a plus sign
Note: If you leave the field blank when you attempt to submit the form, the field is highlighted with a red border.
2.5 Icons used in the interface

This table describes the icons used on the consoles and in the Best Practice view of the application interface.
Icon descriptions
Icon
Description
Detail Displays detailed information about the field's content. For example, if you click the Detail icon associated with the Customer
field, the People form appears with information about the customer whose name appears in the field.
Search Searches for field contents. This icon is associated with fields that have the ability to open a search dialog box or form.
Explore CI Opens the BMC Atrium Explorer for the CIs selected in the Service and CI fields.
Clear field contents Clears the contents of the field and allows you to make another selection. It does not delete the record.
Page 39 of 452
Using
2.6 Using the Change Management Console and the Change

form
The Change Management console is the primary interface for change managers, and for support staff, especially
change coordinators. It provides a dedicated workspace for managing and working on change requests. It
provides quick access to the information you need and to the procedures that you perform most often. This
console is designed for change managers who work with BMC Change Management daily and do not want to
view other BMC Remedy ITSM applications. This console enables change managers and change coordinators to
use BMC Change Management to plan their days more effectively.
The Change Management console shows the most important details associated with changes requests, for
example, tasks associated with changes, work information, and important broadcasts.
Change Management console
The roles of change manager and change coordinator display the same console, but with different options. The
change management console optimizes your visual work space so that you can track changes quickly and
efficiently.
Page 40 of 452
Using
Note
You can configure the IT Home Page to display the Change Management console. The change console
provides the Company and View By filters only and by default is configured to display only Open change
records.
The section provides the following information:

Change Management console functional areas (
https://docs.bmc.com/docs/display/change81/Change+Management+console+functional+areas)
Company and Console View (see page 44)

Change form functional areas (see page 45)
2.6.1 Change Management console functional areas

Various functions are available in the Change Management console depending on your permissions. These
functions provide quick ways to go to different areas in BMC Change Management and to perform other
functions.
The following table describes what you can do in each of the functional areas:
Change Management Console functional areas
Functional
area
Purpose
Change
Management
Console
header
Search
The Global search feature lets you search across multiple forms for records that match a key term.
Page 41 of 452
Using
Functional
area
Purpose
Show
Filter By
This area contains the following fields: Show, Filter By, and Search. These fields combine to provide a way that you can filter the
change records in the Changes table.
Magnifying
glass icon
The Show field has a menu from which you select the basic criteria by which you want to filter the contents of the Change table,
Role
More filters
the menu choices include:

Submitted by me All change requests created by you.
All All change requests, regardless of who created them.
Assigned to me All change requests assigned to you.
Assigned to my group All change requests assigned to a specific support group of which you are a member. If you select
this, you are prompted to select the support group.
Assigned to all my groups All change requests assigned to all of the support groups of which you are a member.
The Filter By field places conditions on the basic criteria that you choose in the Show field. This helps you manage the
number of records returned by the Show field. If you select Assigned to me in the Show field and All Open > All Priorities
from the Filter By field, then the Changes table contains all open change records, regardless of their priority, that are
assigned to you.
The Magnifying glass icon opens a dialog box from which you can edit, save, and delete custom searches. Saved custom
searches appear in the My Searches node of the Defined Searches list. For more information about Manage My Searches, see
Creating a custom search (see page 344).
The Role field allows you to select a Role and based on the role you select, the Changes table displays all records assigned to
the users with the selected role. The Count table displays the count based on the options selected in the Show and Role field.
Note: The Role field is unavailable if you select All or Submitted By Me from the Show menu.
More filters provides a way for you to further filter the contents of the Changes table. If you still have a large number of
records after using the Filter By field, click Advanced to open a dialog box that contains fields in which you can indicate even
more precise information, such as product or operational categories.
For example, using the advanced field you can add the product category Hardware to the filter. When added to the Show and
Filter by fields, the Changes table now contains all open hardware changes, regardless of their priority, that are assigned to
you. A check box appears in the More filters label to indicate when a filter from this area is active.
Navigation
pane
View
Broadcast, or
New
Broadcast
Click this link to open the broadcast dialog box, from where you can view, create, modify, and delete broadcasts.
Counts
Displays Open, Waiting Approval, In Progress, and Pending metrics that are calculated when the console opens.
When there are unread broadcasts, this area displays the
icon followed by the number of new broadcasts.
For more information on broadcasting messages, see Working with broadcasts (

https://docs.bmc.com/docs/display/change81/Working+with+broadcasts).
Note: The count of Open requests and the actual number of requests displayed in the Changes table may vary because change
requests with Draft status are also displayed in the change table when viewing Open requests. However, when calculating the total
count of Open records, the number of change requests with status Draft are not included.
Page 42 of 452
Using
Functional
area
Purpose
Functions
Use the links in this area to do the following actions:

New Change Opens the Change form in New mode. For information, see Initiate stage - Creating change requests (see
page 81).
Search Change Opens a search form that Lets you search for change records according to the criteria that you supply. For
more information, see Using search (https://docs.bmc.com/docs/display/change81/Using+search).
Atrium Impact Simulator Opens Atrium Impact Simulator. For more information, see Atrium Impact Simulator analysis for
change requests (https://docs.bmc.com/docs/display/change81/Atrium+Impact+Simulator+analysis+for+change+requests).
View Calendar Opens the calendar. For information, see Using the Change Calendar (see page 41).
My Profile Lets you set your profile. For more information, see Viewing your profile (see page 80).
Application Preferences Lets you set your application preferences and options. This function is also available from the BMC
Change Management console. For more information, see Setting application preferences and options (
https://docs.bmc.com/docs/display/change81/Setting+application+preferences+and+options).
Reports Opens the Reporting Console. For information, see Working with reports (
https://docs.bmc.com/docs/display/change81/Working+with+reports).
Manage CIs For information, see Managing configuration items (see page 175).
Manage Inventory Opens the Inventory Management screen, if you have Asset Management application. For information,
see Managing inventory locations (see page 186).
If you are logged on as a Change Manager, the following options are also displayed:
Configuration Manager Opens BMC Configuration Manager console (if the integration is enabled). For more
information, see Using the BMC BladeLogic Client Automation Configuration Manager (
https://docs.bmc.com/docs/display/change81/Using+the+BMC+BladeLogic+Client+Automation+Configuration+Manager).
Surveys Lets you select a survey. To enable surveys, they must defined for your company and the option must be
selected.
KPIs Displays the KPI flashboards available. Select to view the KPI flashboard. The flashboards that appear represent,
in graphical format:
Total Open Changes Filters by Priority, Categorization, or Impact
Changes Pending Filters by Categorization
Change Risk Filters by Categorization, Impact, or Support Group
Time Segments Search, select, or create the following time segments:
Create Business Event
Create Op. Category Location
Modify Business Event
Modify Op. Category Location
Configuration Item (CI)
For more information, see Registering time segments (see page 415).
Applications
This area contains links to other BMC applications, consoles, and modules. The contents of this area depend on what other
applications and so on are installed. Click the double greater-than sign to open or close this panel.
Changes table
The Changes table displays high-level details about the change records that match the criteria specified in the Company and
Assigned To fields, or that were found by the most recently completed search. The CRQ prefix identifies the change requests. You
can filter the requests in the table by using the Show and Filter By fields.
Create
Opens the New Change form so you can create a new change request record.
Create for
Company
(Hub and
Spoke
environments)
Opens the New Change form so you can create a new change request record, after asking you to identify the company that you are
creating the change request record for. The record is created and submitted on the spoke server in which the company you
identified is defined.
View
Opens the change request record selected in the table.

In a Hub and Spoke environment, when you click View, you open a record directly from the spoke server.
Page 43 of 452
Using
Functional
area
Purpose
Print
Displays the details of the change request record selected in the table as a report.
Process
Opens the detailed SMPM change management process diagram, if the full SMPM application is installed. Otherwise, it opens a
Overview
high-level diagram of the change management process.
Service
Opens the Service Context summary view for the record selected in the Changes table.
Context
Details and
Displays details or related tasks of the record selected in the Changes table.
Tasks
Change
When selected, contains detailed read-only information about the record selected in the Changes table. To see Details when the
Details
Tasks table is showing, click Show Details.
Work Info
Shows activity associated with the change.

The Work Info area enables change coordinators to view or define actions performed or information gathered about a change
request. For example, you can define a work information entry that documents the installation and back-out procedures for a
change.
You can perform the following actions in this area:
Create Create a new activity
View Displays details of the selected activity
Report Displays a report of the Change Work Info history
Show Tasks
When selected, lets you view tasks associated with the record that is selected in the Changes table. To see Tasks when Details is
showing, click Show Tasks.
2.6.2 Company and Console View

The Company and Console View shows changes that are assigned to you or to the support groups you belong to.
The Company field is typically left blank if you support only one company. If you support multiple
companies and you wish to view only the tickets for one company, select the appropriate company from
the attached menu. Otherwise, you will view all tickets for all companies you support.
The Console View provides options to look at work assigned specifically to you or to your support groups.
When you select an option, a search is performed.
You can change the table by using the Company and Console Views at the upper-right corner of the console.
Select the following options to filter out which requests you see.
Option
Description
Company
Shows requests for a particular company. This field is especially useful in a multitenancy environment.
Personal
Shows the requests that are assigned to you
Selected
Groups
Shows the requests that are assigned to your support group
Page 44 of 452
Using
Option
Description
All My
Shows the requests that are assigned to all support groups that you belong to. If you belong to more than one support group, the
Groups
requests for all those groups are shown.

You can view requests and refresh the items that appear in the table. For more information about viewing and refreshing requests, see
Using search (https://docs.bmc.com/docs/display/change81/Using+search).
2.6.3 Change form functional areas

The Change form is used to request a change and track the progress from the Initiate stage to the Closed stage.
This form also shows the impact that the change has on the organization. The Change form is used to relate tasks
to different support groups. You can relate the change to configuration items that are being modified.
Change form and its functional areas (Best Practice view)
Change form and its functional areas (Classic view)
Page 45 of 452
Using
Before you begin creating or modifying information in the Change form, you should understand the information
relationships in the different areas of this form. The Change form provides an example of the level of integration
that can occur between the various modules in BMC Remedy ITSM, such as a change request that occurs due to
an incident, a change to a configuration item, or a known error correction as a result of problem investigation.
Tip
As you work with the forms and dialog boxes, you might see a plus sign (+) included in a field label. You
can type part of the information in these fields and press Enter. If an exact match is found, the field is
automatically completed. If a selection list appears, double-click the item to put in the field. Using
auto-fill fields and lists is faster, more consistent, and more accurate than typing the information.
Note
You might see additional links in the navigation pane for applications that are installed in addition to
BMC Change Management.
The Change form has the following functional areas:

Change form functional areas
Page 46 of 452
Using
Form area
Function
Change
form header
Breadcrumb
A navigation aid that contains links to related records that you opened from the current release record.
bar
Breadcrumb
navigation
controls
Back button Takes you back one link in the breadcrumb trail.
Forward button Takes you forward one link in the breadcrumb trail. The Forward button is only visible if you have returned
to a record on the breadcrumb trail that you previously viewed.
Drop-down menu Contains links to all the records that you viewed from the current release record, including records that
are not currently visible in breadcrumb trail.
Home icon Takes you to the IT Home page.
Process
Flow Status
bar
Click the change stages in the Process Flow Status bar to move through the change request lifecycle from the Initiate stage to the
Closed stage.
View
Broadcasts
Opens the View Broadcasts dialog box. For information, see Working with broadcasts (
https://docs.bmc.com/docs/display/change81/Working+with+broadcasts)
Navigation
pane
Functions
Allows you to perform the following actions:

Copy Change Activated only in Modify mode. For information, see Copying change requests (see page 161).
View Risk Report Opens Risk Report. For information, see Review and Authorize stage - Risk and impact analysis (see page
107)
Note: This option is not available when you are creating the change.
Impacted Areas Opens Impacted Areas Update dialog box. For more information, see Viewing affected areas
Collision Detection Determines if there are other change requests scheduled to work on the same CI during the same
blackout schedule. For information, see Detecting CI collisions between change requests (
https://docs.bmc.com/docs/display/change81/Detecting+CI+collisions+between+change+requests).
Manage CIs Allows you to manage CIs.
Email System For information, see Sending email (see page 431).
More
Allows you to perform the following actions:

Financials Opens the Financials dialog box where you can add costing related information. For more information, see Adding
and viewing costs (see page 294).
View Audit Log For information, see Viewing the audit log.
Reminders For information, see Using reminders (see page 331).
Paging System For information, see Paging a person or on-call group (see page 432).
Modify Operational Category Location Searches, selects, modifies, and deletes operational category locations.
Time Segments - Business Events Searches, selects, and creates for business event time segments. For information, see
Registering unique business events and operational categorizations (see page 420).
Page 47 of 452
Using
2.7 Using the Release Management console and the Release

form
This section contains information about getting started with Release Management, including using the Release
Management console.
Release Management console functional areas (
https://docs.bmc.com/docs/display/change81/Release+Management+console+functional+areas)
Release form functional areas (see page 52)

Activity form functional areas (see page 54)
The following sections described for the Change Management console are also applicable to the Release
Management console:
IT Home page (see page 31)
Navigating consoles, forms, and modules (see page 35)
Using Global search (see page 67)
User interface standards for field labels (see page 39)
Icons used in the interface (see page 39)
2.7.1 Release Management console functional areas

The Release Management console provides a dedicated workspace for managing release requests. This console
provides quick access to the information you need and to the procedures that you perform most often. This
console optimizes your visual work space so that you can track releases quickly and efficiently. illustrates the
functional areas of the Release console.
Release Management console and its functional areas
Page 48 of 452
Using
The Release Management console lets you see the most important details associated with release requests (for
example, change requests and activities linked to releases, tasks allocated to release requests, work information,
and important broadcasts). It is designed to give you quick access to the information and procedures that you
need daily so that you do not have to open other BMC Remedy ITSM applications. Finally, if you point your cursor
over the Release ID, tooltip information is displayed. For more information, see Tooltip data shown in consoles
(see page 58).
The following table describes what you can do in each of the functional areas.
Release console functional areas
Functional
area
Purpose
Console tab
Displays releases and related changes and activities.
Release
Management
Console
header
Refresh icon
Updates the console with the latest information.
Search
Page 49 of 452
Using
Functional
area
Purpose
Show
Filter By
This area contains the following fields: Show, Filter By and Search. These fields combine to provide a way that you can filter the
release records in the Releases table.
Magnifying
glass icon
The Show field has a menu from which you select the basic criteria by which you want to filter the contents of the Releases table, the
More filters
menu choices include:

Submitted by me All release requests created by you.
All - All release requests, regardless of who created them.
Assigned to me All release requests assigned to you.
Assigned to my group All release requests assigned to a specific support group of which you are a member. If you select
this, you are prompted to select the support group.
Assigned to all my groups All release requests assigned to all of the support groups of which you are a member.
The Filter By field places conditions on the basic criteria that you choose in the Show field. This helps you manage the number
of records returned by the Show field. If you select Assigned to me in the Show field and All Open > All Priorities from the Filter
By field, then the Releases table contains all open release records, regardless of their priority, that are assigned to you.
The Magnifying glass icon opens a dialog box from which you can edit, save, and delete custom searches. Saved custom
searches appear in the My Searches node of the Defined Searches list. For more information about Manage My Searches, see
"Creating a custom search".
More filters provides a way for you to further filter the contents of the Releases table. If you still have a large number of
records after using the Filter By field, click Advanced to open a dialog box that contains fields in which you can indicate even
more precise information, such as product or operational categories. For example, using the advanced field you can add the
product category Hardware to the filter. When added to the Show and Filter by fields, the Releases table now contains all open
hardware releases, regardless of their priority, that are assigned to you. A check box appears in the More filters label to
indicate when a filter from this area is active.
Navigation
pane
View
Broadcast,
or New
Broadcast
Click this link to open the broadcast dialog box, from where you can view, create, modify, and delete broadcasts.
When there are unread broadcasts, this area displays the
icon followed by the number of new messages and the message New
Broadcast. When there are new broadcasts, the area also turns red. For more information on broadcasting messages, see Working
with broadcasts (https://docs.bmc.com/docs/display/change81/Working+with+broadcasts).
Note: If you open the Release Management console with no new broadcasts, but the View Broadcast link is red, open the Application
Preferences dialog box and make sure that a Console View preference has been selected. See Viewing your profile (see page 80) for
information about how to view and select Console View preferences.
Milestones
Displays Plan, Build, Test, and Deploy milestone metrics that are calculated when the console opens.
Page 50 of 452
Using
Functional
area
Purpose
Functions

New Release Opens the Release form in New mode. For information, see Initiate milestone - Creating release requests (see
page 188).
Search Release Opens the Release form in Search mode. For more information, see Using search (
https://docs.bmc.com/docs/display/change81/Using+search).
My Profile Sets your personal profile. See Viewing your profile (see page 80).
Application Preferences Sets your program preferences and options. This function is also available from the Release
Management console. See Setting application preferences (
https://docs.bmc.com/docs/display/change81/Setting+application+preferences).
Reminders Opens the Reminders dialog box. For information, see Using reminders (see page 331).
Reports Opens the Reporting Console. For information, see Working with reports (
https://docs.bmc.com/docs/display/itsm80/Working+with+reports).
KPIs Displays the KPI flashboards available. Select to view flashboards. The flashboards that appear represent, in graphical
format:
Process KPIs View KPI flashboards
Total Open Releases Filters by Service or Priority
Total Pending Approval Filters by Service, Impact, or Business Justification
Total By Risk Filters by Service, Impact, or Milestone
View Calendar Opens the calendar. For information, see Using the Change Calendar (see page 48).
Time Segments Create, modify, or search the following time segments:
Business Event
Operational Category Location
Configuration Item (CI)
For information, see Registering time segments. (see page 415)
Applications
This area contains links to other BMC applications, consoles, and modules. The contents of this area depend on what other
applications and so on are installed. Click the double greater-than sign to open or close this panel.
Releases
table
The Releases table displays high-level details about the release records that match the criteria specified in the Company and
Assigned To fields, or that were found by the most recently completed search. The RLM prefix identifies the release requests. You
can filter the requests in the table by using the Show and Filter By fields.
Create
Opens the New Release form so you can create a new release request record.
View
Opens the release request record selected in the Releases table.
Print
Prints the details of the release request record selected in the Releases table.
Process
Overview
Opens the detailed SMPM release management process diagram, if the full SMPM application is installed. Otherwise, it opens a
high-level diagram of the release management process.
Service
Context
Opens the Service Context summary view for the record selected in the Releases table.
Show
Details/Hide
Details
When selected, displays the work information table with details about the record selected in the Releases table. It also displays the
Create and View links to create or view release activities from the Release Management Console.
For more information, see Recording Release Activities (https://docs.bmc.com/docs/display/change81/Recording+the+release+activities).
Changes and
Activities
Create
Opens the New Change or Activity form so you can create a new record.
Page 51 of 452
Using
Functional
area
Purpose
View
Opens the record selected in the Releases table.
Print
Displays details of the release request record selected in the Releases table as a report.
Show
Details/Hide
Displays the work information and tasks table with records selected in the Changes and Activities table. You can create or view
release work information on the Work Info tab. You can view tasks on the Tasks tab.
Details
2.7.2 Release form functional areas

The Release form is used to request a release and track the progress from initiation to completion. This form also
shows the impact that the release has to the organization. The Release form is used to assign tasks to different
support groups, and you can associate the release to configuration items that are being modified.
Release form and its functional areas (Best Practice view)
Release form and its functional areas (Classic view)
Page 52 of 452
Using
Before you begin searching, creating, or modifying information in the Release form, you must understand the
information relationships involved in the different areas of this form. First, you must create assignment mappings
to assign a release to a Release Management support group, to an individual, or to both. An individual in the
Release Management group must assume the role of Release Coordinator. For information about functional roles
and assignment mappings, see Functional roles and extended application access (
https://docs.bmc.com/docs/display/itsm80/Functional+roles+and+extended+application+access) and Mapping
assignments (https://docs.bmc.com/docs/display/itsm80/Mapping+assignments).
The Release form provides an excellent example of the level of integration that can occur between the various
modules available among the BMC Remedy ITSM suite as a release request can occur due to an incident, a
change to a configuration item, or a known error correction as a result of problem investigation.
You might see additional links appear in the navigation pane for applications that are installed in addition to BMC
Change Management.
The Release form has the following functional areas:
Release form functional areas
Page 53 of 452
Using
Form area
Function
Release
form header
Breadcrumb
A navigation aid that contains links to related records that you opened from the current release record.
bar
Breadcrumb
navigation
controls
Back button Takes you back one link in the breadcrumb trail
Forward button Takes you forward one link in the breadcrumb trail. The Forward button is only visible if you have returned
to a record on the breadcrumb trail that you previously viewed.
Drop-down menu Contains links to all the records that you viewed from the current release record, including records that
are not currently visible in breadcrumb trail
Home icon Takes you to the IT Home page
Process
Flow Status
bar
Click the milestones in the Process Flow Status bar to steps you through the release request lifecycle from the Initiate milestone to
the Close Down milestone.
View
Opens the View Broadcasts dialog box. For information, see Working with broadcasts (
Broadcasts
Navigation
pane
Functions
Performs the following actions:

Copy Release Activated only in Modify mode.
Collision Detection Determines if there are other requests scheduled to work on the same CI during the same blackout
schedule. For information, see Detecting CI collisions between change requests (
Financials Opens the Financials dialog box where you can add costing related information. For more information, see
Adding and viewing costs (see page 294).
Note: This option is not available when you are creating the release request.
Email System For information, see Sending email (see page 431).
Modify Business Events - Searches, selects, modifies, and deletes business events. For information, see Registering unique
business events and operational categorizations (see page 420).
Time Segments Business Event - Searches, selects, and creates time segments for business events. For information, see
Registering unique business events and operational categorizations (see page 420).
Time Segments - Configuration Item (CI) Searches, selects, and creates time segments for Configuration Items. For
information, see Registering time segments for CIs - Creating a blackout schedule (see page 416).
2.7.3 Activity form functional areas

Release Management provides basic facilities for assignment, status, work information, and task management.
The Activity form is used to manage a release and track its progress from initiation to completion. The Activity
form is also used to assign tasks to different support groups.
Release Activity form
Page 54 of 452
Using
You use the Activity form to add a set of activities to a release request. You can track release states and requester
information, relate and assign tasks, and enter work log information. For more information, see Working with
release activities (see page 226).
Note
Any other links that are displayed in the navigation pane are determined by the applications that are
installed in addition to Release Management.
The Activity form has the following functional areas:

Activity form functional areas
Form area
Function
Navigation
pane
Quick Links

View Broadcasts Opens the View Broadcasts dialog box. For more information, see Working with broadcasts (
Select Template Selects any templates made available for your support group. For information, see Selecting activity
templates (see page 239).
Page 55 of 452
Using
Form area
Function
Functions

Paging System For information, see Sending pages and email messages (see page 431).
View Audit Log For information, see Viewing the audit log (see page 157).
Note: This option is not available when you are creating the activity.
Consoles
Opens other installed BMC Remedy IT Service Management consoles

Release Console Opens the Release Management console
Reports Opens the Reporting console. For information, see Working with reports (
https://docs.bmc.com/docs/display/itsm80/Working+with+reports).
Other
functionality
Save
Saves the form contents
Print
Displays a report of the form contents that can be printed
2.8 Using the Change Management Dashboard

The Change Management Dashboard provides flashboards containing key metrics associated with changes
occurring in the organization. This dashboard enables the organization to make sure that change-related
activities are meeting identified goals.
For more information on the Change Management Dashboard, see Change Management Dashboard (
https://docs.bmc.com/docs/display/change81/Change+Management+Dashboard)
2.8.1 To use the Change Management Dashboard

1. On the IT Home page, click the Change Management Dashboard link.
2. On the Change Management Dashboard, enter a start time and end time for the Flashboard data to view.
3. In the change statistics area, define how you want the flashboards to appear:
Overall Health Choose one of the following settings:
Flashboard name
Metric
Change Success Rate
Successful closed change requests by Status Reason
Changes by Priority
Open change requests by 'Priority' and 'Categorization Tier 1'
Changes by
Timing/Category
Closed change requests by 'Change Timing' and 'Categorization Tier 1'
Changes by
Timing/Group
Closed change requests by 'Change Timing' and 'Support Group Name'
Changes Successful
Page 56 of 452
Using
Flashboard name
Metric
Change requests with Status = Closed & Status Reason = Successful grouped by 'Support Group Name'
and 'Categorization Tier 1'
Changes Unsuccessful
Change requests with Status = Closed & Status Reason = Unsuccessful grouped by 'Support Group Name'
and 'Categorization Tier 1'
Financials Choose one of the following settings:

Flashboard name
Metric
Change Cost Variance
Not applicable
Changes by Cost/Category
Average cost of closed changes by Category
Changes by Cost/Department
Average cost of closed changes by Department
Customer Data Choose one of the following settings:

Flashboard name
Metric
Change Requests by
Change requests by Organization and Company
Changes By Business Justification
Closed change requests by Business Justification
Operational Efficiency Choose one of the following settings:

Flashboard name
Metric
Change End Date Variance
Closed change requests by Category/Company versus closed emergency change requests by

Category/Company
Change Start Date Variance
Closed change requests by Group/Company versus closed emergency change requests by

Group/Company
Change Status
Open change requests by change request Status and Support Group
Changes by Impact
Closed change requests by Impact and Category
Changes by Performance
Rating
Closed change requests by Performance Rating and Group
Changes Completed
Completed change requests by actual End Date and Category
Changes Rolled Back
Closed, backed-out change requests by Group and Category
4. (Optional) Click Refresh to refresh the flashboards, including the date criteria (Start Date and End Date)
specified, and show the change request data that matches the qualifications.
5. Click Set Defaults to open the User View dialog box, where you can save the flashboards which
automatically appear when the Change Management Dashboard form opens.
The list for each Flashboard category shows the available flashboards. In the Duration field, you can select
a time period to show data for the last 7, 30, or 90 days.
6. Click Save.
Page 57 of 452
Using
2.9 Tooltip data shown in consoles

To reduce the clutter on the Consoles, tooltips in the Change Management and Release Management consoles
display additional data that is not directly available to users. Point your mouse over the Change ID or Release ID,
and the tooltip appears. Tooltips display the Change or Release ID, Impact, Priority, and so on.
Tooltip displayed in console
2.10 Tooltip data shown in Change Calendar

To reduce the clutter on the Consoles, tooltips in the Change Calendar display additional data that is not directly
available to users. Point your mouse over the Summary, and the tooltip appears. Tooltips displayed the Change or
Release ID, scheduled dates, and so on.
Tooltip displayed in Calendar
Page 58 of 452
Using
2.11 Working with the Requester console

For organizations that do not install BMC Service Request Management, the Requester console is an interface for
users to create and view their requests.From the Requester console, users can create a request that is submitted
to BMC Change Management or BMC Incident Management. Depending on how the application is configured,
the console might display incident requests and change requests entered on the user's behalf by support staff, in
addition to the requests that the user created. Users can also view requests and respond to a survey after the
request has been resolved.
Requester console users are typically employees who need assistance from the IT support staff to implement a
change or resolve an incident. However, the user might not be an employee. Non-employees can also be users
because non-registered users can also submit service requests.
Traditionally, after a user made a telephone call to a central help desk, a support staff member logged the
request. BMC Incident Management and BMC Change Management provide user self-provisioning. Using the
Requester console, users can submit, track, and (in some cases) resolve their own requests. BMC Change
Management and BMC Incident Management are preconfigured to work with the Requester console. However,
an organization can decide to make the Requester console unavailable.
Note
BMC Service Request Management, when it is installed, replaces the Requester console. For more
information, see Service Request Management (https://docs.bmc.com/docs/display/srm81/Home).
2.11.1 Requester Console users

Users of the Requester Console are usually employees who need assistance from the IT support staff. The user or
requester is typically an employee in the organization who must have a change implemented or an incident
resolved. But any member of your organization can be a requester.
Page 59 of 452
Using
However, the user might not be an employee. Non-employees can also be requesters, since non-registered users
can also submit service requests. Traditionally, after a requester made a telephone call to a central help desk, a
support staff member logged the request.
BMC Service Desk: Incident Management and BMC Change Management provide user self-provisioning. Using
the Requester Console, requesters can submit, track, and (in some cases) resolve their own requests, and, as a
result, improve the overall efficiency.
BMC Change Management and BMC Service Desk: Incident Management are preconfigured to work with the
Requester Console. However, an organization can set an option to make the Requester Console unavailable.The
Requester Console is the primary interface for requesters to define and view their requests. From the Requester
Console, you can define a request that is submitted to BMC Change Management or BMC Service Desk: Incident
Management. You can also view requests and respond to a survey after the request has been resolved.
The following figure illustrates the key areas on the Requester Console.
Requester Console key areas
2.11.2 Requester console users

Users of the Requester console are usually employees who need assistance from the IT support staff. The user or
requester is typically an employee in the organization who must have a change implemented or an incident
resolved. But any member of your organization can be a requester.
However, the user might not be an employee. Non-employees can also be requesters, since non-registered users
can also submit service requests. Traditionally, after a requester made a telephone call to a central help desk, a
support staff member logged the request.
BMC Incident Management and BMC Change Management provide user self-provisioning. Using the Requester
console, requesters can submit, track, and (in some cases) resolve their own requests, and, as a result, improve
the overall efficiency.
BMC Change Management and BMC Incident Management are pre-configured to work with the Requester
console. However, an organization can set an option to make the Requester console unavailable.The Requester
console is the primary interface for requesters to define and view their requests. From the Requester console, you
can define a request that is submitted to BMC Change Management or BMC Incident Management. You can also
view requests and respond to a survey after the request has been resolved.
The following figure illustrates the key areas on the Requester console.
Requester console key areas
Page 60 of 452
Using
2.11.3 Integration between Requester console and BMC Change

Management
The Requester console provides the front-end user interface into the BMC Change Management application. The
integration:
Generates change requests
Updates change information using the work info record
Includes an interface back from the change to the request that is stored in the Requester console
Updates the status to the appropriate status of the request, and makes work info entries visible
The Requester console interacts with BMC Change Management using the BMC Change Management interface
forms.
2.12 Working with the Overview console

The information in this section is for people who fulfill one or more of the following support roles:
Problem coordinators
Page 61 of 452
Using
Service desk analysts

Specialists
Group coordinators
On-duty managers
Overview console functional areas (
https://docs.bmc.com/docs/display/itsm81/Overview+console+functional+areas)
Selecting status values (https://docs.bmc.com/docs/display/itsm81/Selecting+status+values)

Console List table (https://docs.bmc.com/docs/display/itsm81/Console+List+table)
Use the Overview console if you must respond to, manage, or track individual or group work assignments from a
variety of sources. For example, if your company runs the full BMC Remedy ITSM suite, either you or the group
you manage might receive work assignments from BMC Asset Management, BMC Incident Management, BMC
Problem Management, and BMC Change Management. From the Overview console, you can quickly get
information about all your work assignments and perform the procedures that you use most often.
The Overview console provides a view of work assigned across multiple applications. The implementation of the
Overview console uses a BMC Remedy AR System ARDBC plug-in to provide a consolidated view of all assigned
work from data sources in multiple applications without using replication of data or complex SQL views that
bypass APIs.The plug-in architecture is data driven. Configuration forms define how the plug-in is set, including
which forms to query, which fields to map to the table field, and an ARDBC form that performs the query.
As you work with the forms and dialog boxes associated with this console, you might see a plus sign
included
in a field label. You can type part of the information next to these fields and press ENTER. If an exact match is
located, the program automatically completes the field. If a selection list appears, double-click the item you want
to put in the field. Using auto-fill fields and lists is faster, more consistent, and more accurate than typing the
information.
2.12.1 Overview console functional areas

This section illustrates the functional areas of the Overview console and describes what you can do in each of the
functional areas.
Overview console functional areas
Functional area
Purpose
Overview
Console header
Search
Show/Company
Page 62 of 452
Using
Functional area
Purpose
This area contains the following fields: Show and Company. These fields combine to provide a way that you can filter the
records in the console table.
The Show field provides a filter by which you can manage the contents of the Console List table. The choices are:
Submitted By Me Shows all records submitted by you.
Assigned To Me Shows all records assigned to you.
Assigned To My Selected Groups Asks you to select one of the groups to which you belong, and then displays the
records assigned to that group.
Assigned To All My Groups Displays the records assigned to or requested for all of the support groups to which you
belong.
The Company field restricts the criteria that you choose in the Show field for the selected company. This helps you
manage the number of records returned by the Show field.
Refresh
Refreshes the data in the tables.

Note: Refresh does not appear in the Overview console when it is used in the IT Home page.
Navigation pane
View Broadcast,
or New
Opens the broadcast dialog box, from where you can view, create, modify, and delete broadcasts
Broadcast
When there are unread broadcast messages, this area displays a message: New Broadcasts, followed by the number of new
messages. When there are new broadcast messages, the area also turns red.
Note: If you open the Overview console with no new broadcast messages, but the View Broadcast link is red, open the
Application Preferences dialog box and make sure that a Console View preference has been selected.
Functions

Select Status Values See only those records in a certain state, which you specify from the Select Status Values dialog
box. See Selecting status values (https://docs.bmc.com/docs/display/itsm81/Selecting+status+values).
My Profile Set your profile.
Application Preferences Set your program preferences and options. This function is also available from the
application console.
IT Home Page
Use this link to open the IT Home Page.
ROI Console
Use this link to open the Return on Investment (ROI) console.
CMDB
Use this link to open the BMC Atrium CMDB.
Console List
panel
View
Displays a form containing detailed information about the selected record in the Console List table.
In a Hub and Spoke environment, when you click View, you open a record directly from the spoke server.
Create
Creates a new record.
Create for
Company
On a hub server in a Hub and Spoke environment, creates a record after asking you to select a company from a list of
operating companies. The record is created and submitted on the spoke server where the company is defined.
Print
Displays a report of the record contents that can be printed.
Service Context
Page 63 of 452
Using
Functional area
Purpose
Opens the Service Context Summary view for the record selected in the console table. For more information about Service
Context, see Using BMC Atrium Service Context (https://docs.bmc.com/docs/display/itsm81/Using+BMC+Atrium+Service+Context).
Note: The Service Context icon is only available on the Overview console when you open the Overview console from the
Applications list.
Search for
Ticket
Opens a dialog box from which you can select the type of ticket you are searching for. After you select the type of record
from the menu, click the Select button to open a search form specific to the type of ticket you are searching for.
Note: To see activity records and CI unavailability records, you must search for those tickets, because these records are not
displayed in the Console List table.
Preferences
Using Preferences, you can control the appearance of the Console List table. For example, you can add or remove a column.
Console List
table
Lists the different types of requests. See Console List table (https://docs.bmc.com/docs/display/itsm81/Console+List+table).
2.12.2 Console List table

The Console List table lists different types of requests. The types of requests that you can choose from depend on
the applications that are installed.
The table lists the following fields:
Field name
Description
Request ID
ID of the request. The prefix identifies each type of request. See the prefix descriptions in the following table.
Parent Request ID
ID of the parent request from which the current request was created, if applicable.
Request Type
Type of the request. Request types include:

Incident
Problem Investigation
Known Error
Change
Release
Work Order
Summary
Short description of the request
Service
Service CI related to the request
Status
Current status of the request
Priority
Priority of the request
Assignee Group
Support group to which the request assignee belongs to
Assignee
User name of the user to who the request is assigned.

BMC Change Management - Change Manager
Release Management - Release Coordinator
BMC Service Request Management - Request Manager
Page 64 of 452
Using
Field name
Description
BMC Service Desk - Assignee
A specific prefix identifies each type of request:

Prefix
Description
CRQ
Identifies change requests. To view and define change requests, BMC Change Management must be installed.
RLM
Identifies release requests. To view and define release requests, BMC Change Management must be installed.
TAS
Identifies tasks.
SDB
Identifies solution database entries. To view and define solution entries, BMC Service Desk must be installed.
INC
Identifies incidents. To view and define incidents, BMC Service Desk must be installed.
PBI
Identifies problems. To view and define problems, BMC Service Desk must be installed.
PKE
Identifies known errors. To view and define known errors, BMC Service Desk must be installed.
PR
Identifies purchase requisitions. To view and define purchase requisitions, BMC Asset Management must be installed.
You can also change the table's contents by using the Show and Company filters at the top of the console:
Show Shows records that either are assigned to you or to your support groups.
Submitted By Me All change requests created by you.
All All change requests, regardless of who created them.
Assigned To Me All change requests assigned to you.
Assigned To My Selected Group All change requests assigned to a specific support group of which
you are a member. If you select this, you are prompted to select the support group.
Assigned To All My Groups All change requests assigned to all of the support groups of which you
are a member.
Company Shows records that are created for the selected company.
If there are more entries than the system can show in the table, use the arrow keys at the right top corner of the
table to scroll through the table.
2.12.3 Selecting status values

You can use the Select Status Values dialog box to filter the requests that appear in the Overview console based
on their status.
To select status values

1. From the Navigation pane, choose Functions > Select Status Values.
2. In the Select Status Values dialog box, select the status values for each category from the lists, then click
OK to close the dialog box.
3.
Page 65 of 452
Using
3. If the Assigned Work table does not refresh with the filtered records, click Refresh to reload the table's
contents.
Page 66 of 452
Using
3 Using Global search

If you have BMC Knowledge Management installed, you can use the Global search feature in any of the BMC
Remedy ITSM application consoles.
Global search searches across multiple forms for records that match a word or phrase that you type in the search
area.
Note
Global search results include information only from the forms that you have permission to access.
That is, you need permission to access an application to have its records appear in the search
results.
The Global search does not include BMC Asset Management CI's .

To use Global search (see page 67)
Limitation (see page 68)
Special characters and boolean expressions in Global search (see page 68)
3.1 To use Global search

1. In the text field to the right of the breadcrumb bar, type your search string and then click the Search icon.
Global search
2. Locate the record you want in the search results table and double-click it.
The record opens in the viewing area and the system updates the breadcrumb trail with an entry for the
record you opened.
Note
As you drill down through the record, each record you open is also added to the breadcrumb trail.
If you want to maintain the contents of the search results table to view later, do not change the
text in the Search field. If you do, when you click the Search icon to return to the search results
Page 67 of 452
Using
table, the search feature will execute a new search based on the changed content of the Search
field.
3. To return to the search results table, click the Search icon again.
3.2 Limitation
Global search results might include external files that have been registered as knowledge base items. If the search
conditions are fulfilled by XML or HTML files that have been registered in this way, the Global Search Results
screen appears distorted due to the tags that are used in XML and HTML files. Additionally, the Advanced search
link on the search results screen becomes unresponsive.
Asset CIs are not included in the Global Search.
3.3 Special characters and boolean expressions in Global

search
Global search uses Full Text Search (FTS) to find the search strings in requests and other records. Some
characters are used to control the search criteria, as indicated in the following table.
Special characters and their results
Special
character
Results
Example search
string
"
Performs a phrase search on the terms enclosed in double-quotation marks (")
"firewall
blocked"
Example results
firewall
blocked her
access
firewall
blocking my
access
Find requests that contain any of the specified words

firewall,
blocking
"firewall,
blocking"
firewall
blocks
access
firewall will
block access
firewall is
not working
try blocking
his access
%fire%
backfire
file
Page 68 of 452
Using
Special
character
Results
Example search
string
Example results
Wildcard to extend the search
firewall
Note: You do not need to use a wildcard to extend the search for word stems, such as "ed," "s",
and "ing," because word stems are automatically included.
Note
Searches that start with a wildcard character are not as efficient as searches that use an exact phrase or
a trailing wildcard. For example, searching for the term "%block" is less efficient than searching for either
"block" or "block%".
You can use use boolean expressions in your search. Boolean operators include parentheses (), AND, OR, and
NOT. The boolean operators must be specified in upper case; otherwise, they are treated as search strings.
Boolean operators and their results
Boolean
operator
Results
Example search string
AND
Find requests that contain all of the specified words and

phrases
firewall AND blocking
Example results
firewall blocks access

firewall will block access
OR
Find requests that contain any of the specified words and

phrases
firewall OR blocking
NOT
Exclude the specified word or phrase
firewall NOT blocking
()
group expressions
firewall AND (block,

allow)
firewall blocks access

firewall will block access
firewall is not working
try blocking his access
firewall is not working
firewall blocking access

set up firewall to allow
access
Global search results reflect both the search terms and the configuration of full text search. Configurable options
that affect search results include case sensitivity, the list of ignored words, thesaurus, and stemming. For more
information about full text search, see Enabling full text search (
https://docs.bmc.com/docs/display/ars81/Enabling+full+text+search).
3.4 Global search indexed fields

Page 69 of 452
Using
This section provides a list of the fields on each form that are indexed for use by Global search. The information in
these fields can be found by Global search.The following topics are provided:
Activity form indexed fields (see page 70)
Help Desk form indexed fields (see page 70)
Infrastructure Change form indexed fields (see page 72)
Known Error form indexed fields (see page 73)
Problem Investigation form indexed fields (see page 74)
Release form indexed fields (see page 75)
Solution Database form indexed fields (see page 76)
Task form indexed fields (see page 77)
Work Order form indexed fields (see page 78)
3.4.1 Activity form indexed fields

The following is a list of the fields on the Activity form (AAS:Activity) that are indexed for use by Global search.
Field
Field ID
Activity ID
1000000182
Assignee
1000003230
Assignee Support Company
1000003228
Assignee Support Group
1000003229
Assignee Support Organization
1000003227
Company
1000000001
Notes
1000000151
Region
200000012
Request ID
10000006
Site
260000001
Site Group
200000007
Summary
1000000000
z2TF Work Log Description
301389926
z2TH WorkLog
301389923
3.4.2 Help Desk form indexed fields

The following is a list of the fields on the Help Desk form (HPD:Help Desk) that are indexed for use by Global
search.
Page 70 of 452
Using
Field
Field ID
Assigned Group
1000000217
Assigned Support Company
1000000251
Assigned Support Organization
1000000014
Catagorization Tier 3
1000000065
Categorization Tier 1
1000000063
1000000064
Closed Date
1000000564
Company
1000000082
Contact Last Name
1000005782
Customer Last Name
1000000018
Detailed Description
1000000151
Incident Number
1000000161
Manufacturer
240001003
Owner
1000000715
Owner Group
1000000422
Owner Support Company
1000000426
Owner Support Organization
1000000342
Product Categorization Tier 1
200000003
200000004
200000005
Product Model/Version
240001005
Product Name
240001002
Region
200000012
Reported Date
1000000560
Resolution
1000000156
Service
303497300
Service Request ID
301572100
Site
260000001
Site Group
200000007
Summary
1000000000
Page 71 of 452
Using
Field
Field ID
301394446
z2TH HPD Worklog
301389614
3.4.3 Infrastructure Change form indexed fields

The following is a list of the fields on the Infrastructure Change form (CHG:Infrastructure Change) that are
indexed for use by Global search.
Field
Field ID
1000000063
1000000064
1000000065
Change Coordinator
1000003230
Change Coordinator Group
1000003229
Change Coordinator Support Company
1000003228
Change Coordinator Support Organization
1000003227
Change Manager
1000000403
Change Manager Group
1000000015
Change Manager Support Company
1000000251
Change Manager Support Organization
1000000014
Company
1000000001
Customer Last Name
1000003298
1000000151
Infrastructure Change ID
1000000182
Manufacturer
1000002270
1000001270
1000001271
1000001272
1000002269
Product Name
1000002268
Region
200000012
Service
303497300
Page 72 of 452
Using
Field
Field ID
Service Request ID
301572100
Site
260000001
Site Group
200000007
Summary
1000000000
Vendor fields
301389926
z2TH Worklog
301389923
3.4.4 Known Error form indexed fields

The following is a list of the fields on the Known Error form (PBM:Known Error) that are indexed for use by Global
search.
Field
Field ID
Assigend Group
1000000217
Assigned Group Pblm Mgr
1000000837
1000000251
1000000014
Assignee
1000000218
1000000063
1000000064
1000000065
Company
1000000001
1000000151
Known Error ID
1000000979
Manufacturer
240001003
200000003
200000004
200000005
240001005
Product Name
240001002
Service
303497300
Page 73 of 452
Using
Field
Field ID
Summary
1000000000
Support Company Pblm Mgr
1000000834
Support Organization Pblm Mgr
1000000835
Tempoarary Workaround
1000000855
Vendor Name
1000000396
301389897
z2TH PBM Worklog
301389875
3.4.5 Problem Investigation form indexed fields

The following is a list of the fields on the Problem Investigation form (PBM:Problem Investigation) that are
indexed for use by Global search.
Field
Field ID
Assigend Group
1000000217
Assigned Group Pblm Mgr
1000000837
1000000251
1000000014
Assignee
1000000218
1000000063
1000000064
1000000065
Company
1000000001
1000000151
Manufacturer
240001003
Problem Investigation ID
1000000232
200000003
200000004
200000005
240001005
Product Name
240001002
Region
200000012
Page 74 of 452
Using
Field
Field ID
Service
303497300
Site
260000001
Site Group
200000007
Summary
1000000000
Support Company Pblm Mgr
1000000834
Support Organization Pblm Mgr
1000000835
Temporary Workaround
1000000855
Vendor Name
1000000396
301389897
z2TH PBM Worklog
301389875
3.4.6 Release form indexed fields

The following is a list of the fields on the Release form (RMS:Release) that are indexed for use by Global search.
Field
Field ID
1000000063
1000000064
1000000065
Company
1000000001
1000000151
Manufacturer
1000002270
1000001270
1000001271
1000001272
1000002269
Product Name
1000002268
Region
200000012
Release Coordinator Group
1000000015
Release Coordinator
1000000403
Release Coordinator Support Company
1000000251
Release Coordinator Support Organization
1000000014
Page 75 of 452
Using
Field
Field ID
Release ID
303489800
Service
303497300
Site
260000001
Site Group
200000007
Summary
1000000000
Vendor fields
301389926
z2TH Worklog
301389923
3.4.7 Solution Database form indexed fields

The following is a list of the fields on the Solution Database form (PBM:Solution Database) that are indexed for
use by Global search.
Field
Field ID
Abstract
1000000000
Assigend Group
1000000217
1000000251
1000000014
Assignee
1000000218
1000000063
1000000064
1000000065
Company
1000000001
Department
200000006
Manufacturer
240001003
Organization
1000000010
200000003
200000004
200000005
240001005
Product Name
240001002
Page 76 of 452
Using
Field
Field ID
Region
200000012
Searchable
1000001469
Site
260000001
Site Group
200000007
Solution
1000001203
Solution Database ID
1000001204
Summary
1000001202
301389897
z2TH PBM Worklog
301389875
3.4.8 Task form indexed fields

The following is a list of the fields on the Task form (TMS:Task) that are indexed for use by Global search.
Field
Field ID
Assignee
10010413
Assignee Support Company
1000000251
Assignee Support Group
10002506
Assignee Support Organization
1000000014
Catagorization Tier 3
1000000065
1000000063
1000000064
Company
1000000001
Customer Last Name
1000003298
Manufacturer
1000002270
Name
10007000
Notes
10000101
1000001270
1000001271
1000001272
1000002269
Product Name
1000002268
Page 77 of 452
Using
Field
Field ID
Region
200000012
Request ID
10000006
Site
260000001
Site Group
200000007
Summary
Task ID
z2TF_WorkInfoSummary
10000547
z2TH_Worklog
10000523
3.4.9 Work Order form indexed fields

The following is a list of the fields on the Work Order form (WOI:WorkOrder) that are indexed for use by Global
search.
Field
Field ID
1000000063
1000000064
1000000065
Company
1000000001
Customer Last Name
1000003298
1000000151
Manufacturer
1000002270
1000001270
1000001271
1000001272
1000002269
Product Name
1000002268
Region
200000012
Request Assignee
1000003230
Request Assignee Support Organization
1000003227
Request Assignee Support Company
1000003228
Request Assignee Support Group
1000003229
Page 78 of 452
Using
Field
Field ID
Request Manager
1000000403
Request Manager Group
1000000015
Request Manager Support Company
1000000251
Request Manager Support Organization
1000000014
Service
200000020
Service Request ID
301572100
Site
260000001
Site Group
200000007
Summary
1000000000
Work Order ID
1000000182
301389926
z2TH WorkLog
301389923
Page 79 of 452
Using
4 Viewing your profile

You can view and modify your personal profile. When you click My Profile, the People (Search) form appears.
In this form, you can perform the following actions:
Update company information such as organization, business, and home address
View permissions
For detailed information about the People form, see People information (
https://docs.bmc.com/docs/display/itsm81/People+information).
4.1 To modify your profile

1. To open your profile, from the navigation pane in the application console, choose Functions > My Profile.
2. On the People form, update the information at the top of the form, or click the tab corresponding to the
area in which you want to change the profile information.
Make your changes by selecting from the various lists that are available.
Page 80 of 452
Using
5 Using BMC Change Management

This section describes how to create and manage change requests.
The following topics are discussed:
Initiate stage - Creating change requests (see page 81)
Adding information to the change request (see page 97)
Review and Authorize stage - Risk and impact analysis (see page 107)
Plan and Schedule stage - Planning the change request (see page 113)
Approvals - Approving change requests (see page 121)
Implement stage - Implementing the change (see page 146)
Closed stage - Completing change requests (see page 151)
Monitoring the progress of a change request (see page 155)
Copying change requests (see page 161)
Working with related change requests (see page 163)
Working with change request assignments (see page 167)
Using phases with change requests (see page 173)
Managing CIs (see page 175)
5.1 Initiate stage - Creating change requests

Changes start at the Initiate stage of the change request lifecycle. Most change requests are generated from a
incident, problem investigation, an RFC proposed by Problem Management, or a known error. When change
requests are generated by any of these records, some information is copied from the record. For example, when a
change request is generated from an incident, the Description, Impact and Urgency, and the Product and Service
Categorization fields are copied to the change request. The Requester Information defaults to the user initiating
the change request.
Note
Change requests created from another BMC Remedy ITSM application like Incident or Service Request
Management are created in Request for Authorization status.
Creating change requests
Page 81 of 452
Using
In addition, BMC Change Management enables any user with Change Submit permissions to enter change
requests. Change managers (and change coordinators) can enter and resolve change requests quickly with the
option to define and relate items before saving the change request.
How you create a change request depends on which view of the BMC Change Management application you use,
Classic View or Best Practice View.
For instructions, see the following topics:
Creating a change request at the initiate stage - Best Practice view (see page 83)
Page 82 of 452
Using
Creating a change request at the Initiate stage - Classic view (see page 86)
Creating emergency change requests (see page 91)
Creating a change request from Atrium Impact Simulator (see page 91)
Creating change requests as rollbacks (see page 93)
Associating custom process flows to a change template (see page 94)
Selecting change templates (see page 94)
Impact, urgency, and priority criteria (see page 96)
5.1.1 Creating a change request at the initiate stage - Best Practice view
The section describes how to create a change request at the Initiate stage when using the Best Practice view of
To create a change request

1. On the Change Management console, click Create or Create for Company (in a Hub and Spoke
environment).
If you are working in a Hub and Spoke environment, you are asked to identify the company you are
creating the record for. Select the company from the drop down list, then click Create. The Change form
opens on the spoke server of the company you chose. Continue with the rest of this procedure.
Note
The record that you create for the selected company is created and submitted on the spoke server
where the company is defined.
In the Initiate stage, the change request initially appears in Draft status. The change request has not yet
been submitted to the Change Management process.
2. Use the following fields to specify the change coordinator:
Coordinator Group Specify the group of people with the Infrastructure Change Coordinator
functional role. This list is populated with groups that have at least one user with a Infrastructure
Change Coordinator functional role.
Change Coordinator Specify the user responsible for the change. The list is populated with people
with the Change Coordinator functional role and who are included in the Coordinator Group
selected. |
3. From the Service field, select the business service configuration item (CI) that relates to the change request
that you are creating.
The Servicefield relates business service configuration items (CIs) to the change request at the time it is
created. Business service CIs are related either to the customer directly or to the customer's company,
organization, or department.
Page 83 of 452
Using
Note
The business service CI is not a physical CI (such as a printer or a router); it is a logical CI. In this
context, a logical CI is a business service that can be provided from one business, or organization
within a business, to another. Service CIs can include customer support, employee provisioning,
web farms, storage, and so on. When business service CIs are created and made available on the
Service field menu, they are related either to a customer directly or to the customer's company,
organization, or department. If you need to have a new business service CI added to the Service
field menu, you must notify a system administrator with Asset Administrator privileges.
4. (Optional) Select a template to complete part of the change request.

Change templates are especially useful in any change request that follows well-defined methods for
specific and repeated requirements.
The template is attached to the change request. The custom process flow associated with the change
template applies to the change request. A new Work Info record is created that includes a textual
representation of the change process flow. In the process flow bar, the options for next and back are
changed to reflect the process flow.
Note
If you start to enter fields in the change request and then select a change template, the change
template overwrites any field values that are already present in the change request, including any
relationships or tasks included with the change request.
5. (Optional) Enter a date in the Target Date field.

The target date is the date by when the change must be completed, according to the applicable service
level target. Alternatively, the target date can be a date that is agreed to on an ad hoc basis, per change.
The target date cannot be set to a date earlier than the current date, except for Latent changes.
6. Complete the following fields:
Field
name
Description
Summary
Provide a brief description of the change.
Class
Specify the relative urgency of the change, so that the approvers can assess its magnitude.
Note: The Class field can be used to categorize a change based the approval process. Each Class can be mapped to a different
approval process, which will drive the status transitions that can be defined as per the organization's requirement.
You have the following options:
Standard indicates a change (for example, a computer upgrade) that is typically preapproved and requires only approval
by the change manager. Standard changes follow the out-of-box change process defined as per ITIL specifications. This
configuration is not provided out of box.
Page 84 of 452
Using
Field
name
Description
Emergency indicates a change that resolves an incident or problem deemed critical to business continuity and for which
a workaround is not sufficient.
You must configure the Approval Process to follow for Emergency changes.
Expedited indicates that a change has an enterprise-wide impact with an associated risk. If you select Expedited, you
must also select the Timing Reason (for example, Known error correction).
You must configure the Approval Process to follow for Expedited changes.
Latent indicates a change that has already been performed (for example, if a task implementer is assigned to replace the
hard drive on a computer and then decides to upgrade the memory while the computer is open). Latent timing
automatically sets the request status to Completed after you save the change request. The Target Date for a latent
change can be earlier than the current date.
This out of box configuration of latent changes cannot be changed.
Normal indicates a change that must follow the complete change management process. Normal changes are often
categorized according to risk and impact to the organization (for example, minor change low risk and impact,
significant change medium risk and impact, and major change high risk and impact). By definition a normal change
will proceed through all steps of the change management process and those that are categorized as medium or high risk
will be reviewed by the Change Advisory Board (CAB).
The default value is Normal. Out of box a change follows this process.
No Impact indicates a change that has no impact on the infrastructure and requires no approval.
By default, No Impact changes follow the Business Approval - No Impact phase and move to the Scheduled status. Use
this process for preapproved no impact changes where the change is automatically scheduled after the approval phase is
complete.
For more information on approval processes provided out of the box, see Approval processes provided out-of-the-box
for Change Management (
https://docs.bmc.com/docs/display/change80/Approval+processes+provided+out-of-the-box+for+Release+Management) .
Impact
Specify the extent to which the change affects the business. The default value is 4-Minor/Localized. Impact is often directly
related to the extent to which the service has degraded from agreed service levels. Impact can be measured by the number of
people affected, the criticality of the system affected, and the loss of revenue as a result of the service degradation or
disruption.
For detailed information about Impact, see Impact, urgency, and priority criteria (
https://docs.bmc.com/docs/display/change80/Impact%2C+urgency%2C+and+priority+criteria).
Urgency
Specify a value that indicates the importance of the change request, and reflects how quickly a change must be implemented,
or the time available to reduce the impact of the change on the business. The default value of the Urgency field is Low.
Use the following factors to determine Impact and Urgency:
Number of customers affected by associated Incidents
Duration and scope of the service disruption
Availability of a solution or workaround
The type of service being disrupted, usually based on the CI involved
Awareness of the future impact on the business
For detailed information about Urgency, see Impact, urgency, and priority criteria (
Priority
Specify the importance that you (as support staff) assign to the change request.
Priority indicates the relative order in which to address the changes. It is influenced by considerations of risk and resource
availability, but is primarily driven by the combination of Urgency and Impact. The default value of the Priority field is Low.
For detailed information about Priority, see Impact, urgency, and priority criteria (
Risk
Level
The system automatically performs the risk assessment for the change request in the Risk Level field. The risk level is used as a
criterion to determine required approvals. The default risk level is Level 1, which is the lowest level. The highest risk level is Level
5.
Page 85 of 452
Using
Field
name
Description
Risk assessment involves computing the total risk based on risk related questions and the derived risk factors. For more
information, see Computing risk levels (see page 110).
7. In the Initiate stage of the Process Flow Status bar, click the arrow and choose Next Stage.
8. Review the information in the Change Initiation dialog box, and then click Save.
9. By default, a new Work Info record is created that includes a textual representation of the default change
process flow.
The newly created change is assigned to the appropriate group based on the predefined assignment routing. If
there is no appropriate assignment routing, you are prompted to assign the change request manually.
5.1.2 Creating a change request at the Initiate stage - Classic view

This section describes how to create a change request at the Initiate stage when using the Classic View of BMC
Change Management.
To create a change request at the Initiate stage

1. From the IT Home Page, open the BMC Change Management application.
For more information, see IT Home page (see page 31).
2. On the Change Management console, click Create or Create for Company (in a Hub and Spoke
environment).
If you are working in a Hub and Spoke environment, you are asked to identify the company you are
creating the record for. Select the company from the drop down list, then click Create. The Change form
opens on the spoke server of the company you chose. Continue with the rest of this procedure.
Note
The record that you create for the selected company is created and submitted on the spoke server
where the company is defined.
In the Initiate stage, the change request initially appears in Draft status. The change request has not yet
been submitted to the Change Management process.
3. To enter details about the company and user for which the change request is created, in the Requested for
area, press Enter on the Last Name field search for the appropriate user. The Change Locationcan, by
default, be updated to the selected user's location.
Notes
Page 86 of 452
Using
If you create a new change from the Incident or Problem console, the change appears in
Request for Authorization status because the reason for creating the change is already
known. This information has been entered by the Incident or Problem before the new
change is created.
After they are updated, the Requested for fields cannot be modified.
By default, the Requested By fields are autopopulated with the details of the user who creates the change
after the change request is submitted, if the user creating the change does not specify these details. If this
user is not associated to a support group, the Support Company is set to the Location Company of the
user. If this user is associated to a support group, the Support Company, Support Organization, and
Support Group is set to the user's default Support Group.
You can modify the Requested By fields, if required. The Support Company field list is based on the user
selected in the Last Namefield of the Requested By information.
If the selected user does not belong to the support staff group all companies are listed similar to
Change Location companies.
If the selected user belongs to the support staff group this list is restricted to his Support Group
companies.
4. From the Service field, select the business service configuration item (CI) that relates to the change request
that you are creating. The Servicefield relates business service configuration items (CIs) to the change
request at the time it is created. Business service CIs are related either to the customer directly or to the
customer's company, organization, or department.
Note
This field lists the CIs created under the Logical Entity > Business Service category. The business
service CI is not a physical CI (such as a printer or a router); it is a logical CI. In this context, a
logical CI is a business service that can be provided from one business, or organization within a
business, to another. Service CIs can include customer support, employee provisioning, web
farms, storage, and so on. When business service CIs are created and made available to the
Selecting a business service CI automatically performs the following actions:

Relates the business service CI to the change request as a Related to association type when the
release is submitted. After it is established, you cannot remove the association created between the
release request and the business service CI from the Relationships tab. However, you can select
another service from the Service field when the change request is in Modify mode.
Populates the Product Categorization of the change request based on the categorization of the
business service CI. You can modify the Product Categorization values later.
5.
Page 87 of 452
Using
5. (Optional but recommended) Select a template to complete part of the change request.
Change templates are especially useful in any change request that follows well-defined methods for
specific and repeated requirements. Change templates can do more than prepopulate fields; they can also
include CIs and tasks with the change request. BMC provides change templates for virtual machines that
include standard tasks with the change request. For more information, see Selecting change templates (see
page 94).
The template is attached to the change request. The custom process flow associated with the change
template applies to the change request. A new Work Info record is created that includes a textual
representation of the change process flow. In the process flow bar, the options for next and back are
changed to reflect the process flow.
Note
If you start to enter fields in the change request and then select a change template, the change
template overwrites any field values that are already present in the change request, including any
relationships or tasks included with the change request.
6. In the Initiate stage of the Process Flow Status bar, click the arrow and choose Next Stage.
The two tabs in the Change Initiation dialog box prompt you to enter required and optional information.
7. Enter the following information in the Required Information tab of the Change Initiation dialog box.
Field
Description
Summary
Briefly describe the change.
Class
Specify the relative urgency of the change, so that the approvers can assess its magnitude.
You have the following options:
Standard indicates a change (for example, a computer upgrade) that is typically preapproved and requires only
approval by the change manager. Standard changes follow the out-of-box change process defined as per ITIL
specifications. This configuration is not provided out of box.
Emergency indicates a change that resolves an incident or problem deemed critical to business continuity and for
which a workaround is not sufficient.
You must configure the Approval Process to follow for Emergency changes.
Expedited indicates that a change has an enterprise-wide impact with an associated risk. If you select Expedited, you
must also select the Timing Reason (for example, Known error correction).
You must configure the Approval Process to follow for Expedited changes.
Latent indicates a change that has already been performed (for example, if a task implementer is assigned to replace
the hard drive on a computer and then decides to upgrade the memory while the computer is open). Latent timing
automatically sets the request status to Completed after you save the change request. The Target Date for a latent
change can be earlier than the current date.
This out-of-the-box configuration of latent changes cannot be changed.
Normal indicates a change that must follow the complete change management process. Normal changes are often
categorized according to risk and impact to the organization (for example, minor change low risk and impact,
significant change medium risk and impact, and major change high risk and impact). By definition a normal change
will proceed through all steps of the change management process and those that are categorized as medium or high
risk will be reviewed by the Change Advisory Board (CAB).
The default value is Normal. Out of box a change follows this process.
No Impact indicates a change that has no impact on the infrastructure and requires no approval.
By default, No Impact changes follow the Business Approval - No Impact phase and move to the Scheduled status. Use
Page 88 of 452
Using
Field
Description
this process for preapproved no impact changes where the change is automatically scheduled after the approval phase
is complete.
For more information on approval processes provided out of the box, see Approval processes provided out-of-the-box
for Change Management (see page 213).
Impact
Reflects the extent to which the change affects the business.

The default value is 4-Minor/Localized. Impact is often directly related to the extent to which the service has degraded from
agreed service levels. Impact can be measured by the number of people affected, the criticality of the system affected, and
the loss of revenue as a result of the service degradation or disruption.
For detailed information about Impact, see Impact, urgency, and priority criteria (see page 96).
Urgency
Defines the importance the requester assigns to the change request and reflects how quickly a change must be
implemented, or the time available to reduce the impact of the change on the business. The default value of the Urgency
field is Low.
Number of customers affected by associated Incidents
For detailed information about Urgency, see Impact, urgency, and priority criteria (see page 96).
Priority
Identifies the importance you (as support staff) assign to the change request.
Priority indicates the relative order in which to address the changes. It is influenced by considerations of risk and resource
availability, but is primarily driven by the combination of Urgency and Impact. The default value of the Priority field is Low.\
For detailed information about Priority, see Impact, urgency, and priority criteria (see page 96).
Risk Level
Defines the relative risk associated with the change, from 5 (highest risk) to 1 (lowest risk).
The default value is Risk Level 1. The Risk Level is used as a criterion to determine required approvals.
You can click the Risk Info icon to compute the risk level for the request. For more information, see Review and Authorize
stage - Risk and impact analysis (see page 107).
Coordinator
Group
Defines the groups of people with the Change Coordinator functional role.
Note: If the user creating the change has the functional role of a Change Coordinator, the Coordinator Group, Change
Coordinator, and Change location fields are auto filled with the user's details.
Change
Coordinator
Defines the user responsible for the change. The list is populated with people with the Change Coordinator functional role
and included in the Coordinator Group selected.
Note: The Change Coordinator field is found on the Assignment tab.
Change
location
Location of the company defined for the user requesting the change. Information for this field is related to the Requested By
information provided for the change.
Note: The Change location details are found on the Assignment tab of the Change form.
Change
Type
Categorizes the request according to your organization's change type definitions. This value does not have any associated
workflow.
Project Change requests that are part of larger scale changes, and usually consist of multiple change requests
related to each other
Page 89 of 452
Using
Field
Description
Change A simple stand-alone change activity
Release Prior to the introduction of the Release Management module in BMC Change Management 7.5.00, this
option was used to classify a change request as a release request. After a release request has been established,
subsequent change records can be related as children or peer requests.
Asset Configuration Change request related to an asset configuration
Asset Management Change request related to managing an asset
Asset Lease Change request related to an asset lease
Asset Maintenance Change request related to maintenance of an asset
Purchase Requisition Change request related to a purchase requisition
Depending on which applications are installed, you might see other options.
Note: Asset type options only apply when BMC Asset Management is installed. It is used for integrations and workflow
between BMC Asset Management and BMC Change Management applications.
8. Click the Optional Information tab, and then enter the following information.
Field
Description
Operational
Operational values are data-driven and are defined by the application administrator (for example, Tier 1 is Install, Tier
Categorization
2 is Server, and Tier 3 is Hard Drive).
Product
Product values are data-driven and are defined by the application administrator (for example, Tier 1 is Hardware, Tier
Categorization
2 is Disk Device, and Tier 3 is Disk Array).
Product Name
Product Name is data-driven and are defined by the application administrator (for example, Dell).
Model/Version
Model/Version is data-driven and are defined by the application administrator (for example, PowerEdge).
Model/Manufacturer
Manufacturer is the auto filled with the manufacturer defined for the selected Product.
9. Click Saveon the Change Initiation dialog box to generate the change request.
Tip
After you become familiar with Change Management functionality, you can bypass the Change
Initiation dialog box and enter the required information directly into the Change form.
The Initiate Change dialog box automatically closes. You return to the New Change form, and the
newly-created change is assigned to the appropriate group based on the predefined assignment routing.
If there was no appropriate assignment routing, you must manually assign the change request. For more
information, see Working with change request assignments (see page 167).
Note
Most change requests must be approved before they move to the Review & Authorize stage. For
more information, see Handling approvals for emergency change requests (see page 124).
10.
Page 90 of 452
Using
10. Click Save.

By default, a new Work Info record is created that includes a textual representation of the default change
process flow.
5.1.3 Creating emergency change requests

An emergency change is implemented when there is an Incident that requires a change. Depending on how your
application administrator has configured the BMC Change Management application, emergency change requests
bypass the normal approval process. When you create an Emergency change the new approval process phase will
be used, bypassing the normal change states. For example, if emergency requests are configured to bypass the
Review approval stage, the change is not held up waiting for approvals, but is automatically approved. The
request skips to the next stage in its lifecycle.
Warning
Your application administrator must configure the approval process that bypasses the normal approval
process for emergency change requests. For more information, see Bypassing the approval process for
emergency changes (
https://docs.bmc.com/docs/display/change81/Bypassing+the+approval+process+for+emergency+changes).
Note
Previously, Problem records could not be related to Emergency change requests. You can now relate
Problem records to the emergency change.
To create emergency change requests

1. As a manual step, make sure that an open incident refers to this change request.
2. Create a new change request as described in Initiate stage - Creating change requests (see page 81) or
Creating a change request at the initiate stage - Best Practice view (see page 83).
3. Select Emergency from the Class field.
The following message is displayed:
Make sure an open incident references this change. (ARWARN 1440110)
4. Enter the required information for the change record, and then click Save.
5. Add the related Incident or Problem requests in the Relationship tab of the record.
5.1.4 Creating a change request from Atrium Impact Simulator

This section describes the procedure to perform an impact simulation for CIs and create a new change request
related to this analysis using the Atrium Impact Simulator.
Page 91 of 452
Using
To create a change request from Atrium Impact Simulator

1. On the Change Management console, choose Functions > Atrium Impact Simulator.
The following figure illustrates the functional areas of the BMC Atrium Impact Simulator console. For more
information on the BMC Atrium Impact Simulator console, see Atrium Impact Simulator interface (
https://docs.bmc.com/docs/display/ac80/Atrium+Impact+Simulator+interface) in the BMC Atrium Core
documentation.
The following table describes what you can do in each of the functional areas:
BMC Atrium Impact Simulator console functional areas
Functional
area
Description
CIs for
Simulation
CIs for
Simulation
table
The left column of this table contains the Set CIs State for Simulation field. Use this field to assign an impact state to the CI
selected in the table.
Add CI
Click to search for one or more CIs to add to the table.
Remove CI
Click to remove the selected CI from the table.
Page 92 of 452
Using
Functional
area
Description
Simulate
Impact
Click to run an impact simulation for the CIs in the table.
Results
Results in
Shows the results of a simulation as a topology, including any impact relationships between the CIs. An icon on each CI
Topology
image represents the predicted impact state for each CI, based on the simulation criteria.
Results in
Shows the results of a simulation as a table. The Predicted Status column indicates the expected impact for each CI. To list
Table
only impacted service CIs, click Show Services. To list all impacted CIs, click Show All Results.
Save
Save the simulation. Saved simulations can be loaded and compared.
Simulation
Here you choose the source CIs to include in a simulation. You can select one or several CIs, each with
their own simulated impact state.
2. Click Add CIto search for and select CIs to add to the change request.
a. In the Query window, run a query to return the CIs that you wish to include in a simulation.
b. In the results list, select one or more CIs to include in your simulation.
c. In the CIs for Simulation section, select a CI, and then select an impact state in the Set CIs State for
Simulation field.
d. Repeat this step until every CI in the CIs for Simulation section has the impact state you want to
simulate.
3. Click Simulate Impact to run an impact simulation for the CIs in the table.
You can view the results of the simulation on the Results in Table and Results in Topology tabs. You can
filter the CIs by severity level or other options provided by the Atrium Impact Simulator.
4. To save the simulation, complete the following steps:
a. Click Save Simulation.
b. In the dialog box, enter a name for the simulation.
c. Provide a description of the simulation, such as its purpose, and the source CIs used in the
simulation.
d. Click OK.
5. To create a new change request, choose Relate to New> Change Request.
The Change form opens. The CIs from the Atrium Impact Simulator are related to the request in the
Relationship tab. Work information is created for the change request, along with a simulation .csv file
attached.
For more information, see Working with relationships (
https://docs.bmc.com/docs/display/change81/Working+with+relationships).
6. Enter the remaining information to create the request.

7. Save your work when you are finished.
5.1.5 Creating change requests as rollbacks
Page 93 of 452
Using
You should create a back-out plan for restoring the IT infrastructure to its initial situation. If the actions
associated with a change request need to be reversed, support staff and managers can create a change request
for the system that needs to be rolled back. This means that impacted systems need to be restored to their
previous status before the change request was implemented.
To identify a change request as a rollback

1. Create a new change request.
2. Create a related task to implement the rollback for this change request.
For more information, see Implement stage - Working with tasks (see page 150).
3. Use one of the following options to add a work info record to enter information about why you are rolling
back the change request :
When using the Best Practice view
When using the Classic view
Update the fields on the Work Detail tab.
Update the fields on the Work Info tab.
4. Close the task.

5. Complete the change request.
5.1.6 Associating custom process flows to a change template

You can create and modify custom process flows, which determine the change lifecycle. You must associate the
custom process flow with the appropriate change template or templates. Then when the change coordinator
selects the template on the change request form, the custom process flow applies to the change request.
To associate a custom process flow with a change template

1. From the Application Administration Console, click the Custom Configuration tab.
2. From the Application Settings list, choose Change Management > Template > Template, and then click
Open.
3. Either search for and open an existing change template, or create a new change template.
4. Click the Process Flow tab.
5. In the Change Process Flow field, select the custom process flow.
The Status Transition field displays a textual representation of the status flow transitions.
6. Click Save.
5.1.7 Selecting change templates

The Change Template function enables you to select any templates for your support group. Use change
templates to quickly and efficiently create standard change requests with a minimum of mouse clicks and key
strokes. Change templates are useful in any change request that follows well-defined methods for specific and
repeated requirements for example, Installs, Moves, and Add Changes (IMAC). Change templates are most
helpful to new and occasional BMC Change Management users.
Page 94 of 452
Using
To select templates
1. Create or open a change request.
2. Perform one of the following actions:
To attach a change template click the template field on the

change form.
To attach a change template click Quick Links > Select Template on the left
navigation pane.
Note
The change template can be applied in the Draft state, that is, while creating the change request.
3. On the Change Template Selection dialog box, click View to examine the contents of a change template.
The template appears in read-only mode. Viewing a template enables you to see its relationship, its task
and task group templates, and other important features.
Note
You cannot create, modify, or delete change templates in the BMC Change Management
application; you can only view them. You must use the Application Administration console to
create, modify, or delete change templates. Besides change managers, users with Infrastructure
Change Master and Change Config permissions can create, modify, and delete change templates.
Any member of your support group can modify change templates for that group. For more
information, see Creating templates (https://docs.bmc.com/docs/display/itsm81/Creating+templates).
4. Select a template and click OK.

The contents of the template are applied to the change request. The change template overwrites
any field values that are already present in the change request, including any relationships or tasks
included with the change request.
The value of the Notes field value from template is appended to existing value.
NULL values in the template will overwrite existing values, except for the following fields:
Summary
Change Timing
Change Type
Impact
Priority
Location Company
Product Cat Tier1
Region
Page 95 of 452
Using
Risk Level
Service+
Urgency
Change Environment
Lead Time
Change Reason
5.1.8 Impact, urgency, and priority criteria

Impact is a measure of the effect of an incident, problem, or change on business processes. Impact is often based
on how service levels will be affected.
Urgency is a measure of how long it will be until an incident, problem, or change has a significant business
impact. For example, a high impact incident may have low urgency if the impact will not affect the business until
the end of the financial year.
Priority is a category that identifies the relative importance of an incident, problem, or change. Priority is based on
impact and urgency, and it identifies required times for actions to be taken. Impact and urgency are used to
assign priority.
Impact criteria (see page 96)
Urgency criteria (see page 97)
Priority criteria (see page 97)
Impact criteria
The following table lists the criteria for determining the impact of a change and the approval actions needed to
address the impact:
Impact
Description
Extensive
There is significant business service impact because multiple customers are affected by the change. Considerable human and technical
resources are needed. Management is involved in the decision process. The RFC must be discussed in the Change Advisory Board (CAB)
meeting and approved by the Change Manager. The Change Manager seeks advice on change authorization and planning.
Significant
There is clear service impact because at least one customer is affected by the change. The RFC must be discussed in the CAB meeting
and approved by the Change Manager. The Change Manager seeks advice on authorization and planning.
Moderate
There is little impact on current services because no customers are affected as a result of the change. The Change Manager can
authorize this RFC.
Minor
The change can be executed without prior approval from the Change Manager because no customers are affected by the change.
Impact is further categorized by the following factors:

Scope Widespread, large, limited, or local
Number of customers affected More than one, one, or none
Page 96 of 452
Using
Urgency criteria
The following table lists the criteria for determining the urgency of a change:
Urgency
Action needed
Critical
The change is immediately necessary to prevent severe business impact. Change approval is needed by the CAB or Emergency
Committee (CAB/E-CAB).
High
The change is needed as soon as possible because of potentially damaging service impact.
Medium
The change will solve irritating problems or repair missing functionality. This change can be scheduled.
Low
The change will lead to improvements, changes in workflow, or configuration. This change can be scheduled.
Priority criteria
Priority identifies the RFC importance by correlating impact and urgency, as shown in the following table:
Urgency
Impact
Critical
High
Medium
Low
Extensive
Significant
Moderate
Minor
For example, if the impact is Extensive, and the urgency is Critical, the priority is 1.
5.2 Adding information to the change request

This section describes how to add additional information to your change request.
Adding Requester information (see page 97)
Adding classification information (see page 99)
Adding vendor information (see page 101)
Recording the change activities (https://docs.bmc.com/docs/display/change81/Recording+the+change+activities)
Modifying change requests - Additional information you can enter (see page 105)
5.2.1 Adding Requester information

Enter additional information about the requester on the Change form as needed.
Page 97 of 452
Using
To enter requester information using the Best Practice view (see page 98)
To enter requester information using the Classic view (see page 98)
Note
Requested for information can be modified only when the change is in the Initiate stage.
By default, the Requested By fields are auto-populated with the details of the user who creates the change after
the change request is submitted. If this user is not associated to a support group, the Support Company is set to
the Location Company of the user. If this user is associated to a support group, the Support Company, Support
Organization, and Support Group is set to the user's default Support Group.
You can modify the Requested By fields, if required. The Support Company field list is based on the user selected
in the Last Name field of the Requested By information.
If the selected user does not belong to the support staff group all companies are listed similar to Change
Location companies.
If the selected user belongs to the support staff group this list is restricted to his Support Group companies.
To enter requester information using the Best Practice view

1. Open the change request.
2. Choose Quick Actions > Requested for.
3. Enter information about the requester in the Requested For dialog box.
The Requested For information provides details about the company, user details, organization and
department for which the request has been created.
4. Click OK.
5. Click Save.
To enter requester information using the Classic view

2. Click the Requester tab on the Change form.
3. Modify information as needed in the required fields on the Requester tab (for example, Support Company,
First Name, and Last Name).
This information is supplied automatically, based on your logon. The Support Company is the organization
or group to which the change request is assigned.
Tip
Page 98 of 452
Using
Type a letter or name into fields with a plus sign (+) on the field label, and press Enter to
automatically fill the field. If multiple choices exist, a selection list or dialog box appears, to help
you enter a name. Otherwise, you receive a prompt if the letter or person is not found.
4. Enter information about the requester in the Requested For dialog box.
5. Enter information into the required Change Location Company field.
The Change Location Company field is especially important in a multitenancy environment. In this field,
you can specify the company, department, or other group that controls access to the change request.
6. (Optional) After you respond to the change requester, click the
icon.
The Requester Contacted icon is used to record if the requester has been contacted about the change
request. This data is useful when service providers are organizing their work queue. If you click the
Requester Contacted icon, the hidden Requester Contacted field is set to Yes when you save your changes.
The Requester Contacted icon now appears in Yes
mode.
If the change was generated from a service request, workflow in the BMC Change Management application
sets the SLA Responded field on the Service Requests form to Yes.
Note
This field is applicable only if the SLM application is installed.
7. Click Save.
8. The Requested for fields provide details of the company and user for which the change request is created.
To enter this information, search for the appropriate user based on the last name field. The Change
Location can, by default, be update to the selected user's location.
5.2.2 Adding classification information

Classification information is used to describe the business justification of a request (for example, Sarbanes-Oxley
requirements) and show which products and services are affected by the request. This information can be helpful
when the request goes through the approval process.
To enter classification information when using the Best Practice view

1. On the Change form, click the Categorization tab.
2. Enter the following information:
Field
Description
Class
Define the urgency of the change (for example, Normal). For more information, see Creating a change request at the initiate
stage - Best Practice view (see page 83).
Page 99 of 452
2.
Using
Field
Description
Change
Define the business reason for implementing the change request.
Reason
Available options include:
- Upgrade
- New functionality
- Maintenance
- Upgrade
- Other
If the request needs to go through the approval process, change reason information can be helpful.
3. Choose Links > Categorizations and enter the following information:

Field
Description
Operational Categorization
Operational categorization is based on a three-tier hierarchy that is configured in the Operational Catalog.
Product Categorization
Product categorization is based on a five-tier hierarchy that is configured in your Product Catalog.
4. Click Save.
To enter classification information when using the Classic view

1. On the Change form, click the Classification tab.
2. Enter the following information:
Field
Description
Class
Define the urgency of the change (for example, Normal). For more information, see Creating a change request at the
Initiate stage - Classic View (see page 86).
Timing Reason
Define the reason for creating a change request with a Timing of Expedited (for example, Insufficient lead-time). For more
information, see Plan and Schedule stage - Planning the change request (see page 113).
Lead Time
Define the amount of time that you need to prepare for a change implementation.
The system adds Lead Time to the Submit date to determine the Earliest Start date and time. For example, if the Submit
date is 5/18/2010 1:50:29 A.M. and you type 8 in the Lead Time field, the system determines that the Earliest Start Date is
5/18/2010 9:50:29 A.M.
Note: The Lead Time field is available only from the Classification tab of BMC Change Management Classic view.
Change
Reason
Define the business reason for implementing the change request. Available options include:
- Upgrade
- New functionality
- Maintenance
- Upgrade
- Other
If the request needs to go through the approval process, change reason information can be helpful.
Business
Justification
Tracks the business reason for request.

Page 100 of 452
Using
Field
Description
- Corporate Strategic
- Business Unit Strategic
- Maintenance
- Defect
- Upgrade
- Enhancement
- Customer Commitment
- Sarbanes-Oxley
Note: Select an option based on the classification defined by your company.
Change
Define the environment where the change will be implemented.
Environment
- Upgrade
- New functionality
- Maintenance
- Upgrade
- Other
This field is useful when mapping approvers and for reporting purposes. An approver can be mapped for a selected
environment.
Sequence
Define whether you want the change request to take place in a particular order relative to other change requests. For
more information, see Planning dependencies for change requests (see page 112).
Performance
Rating
Rate the work done by support staff or the manager in completing the change request.
Note: Do not enter information into the Performance Rating field when you are creating a change request. The manager
of the support staff assigned to the change request typically enters this rating after the change request reaches the
Completed status. For more information, see Closed stage - Completing change requests (see page 151).
Notes
Define a more detailed description of the change request.
Operational
Categorization
Operational categorization is based on a three-tier hierarchy that is configured in the Operational Catalog.
Product
Categorization
Product categorization is based on a five-tier hierarchy that is configured in your Product Catalog.
3. Click Save.
5.2.3 Adding vendor information

A vendor is a third-party company that provides services that might be required to complete a request. Vendors
can use their own tracking systems to create and manage tickets for these services.
The Vendor Management feature of BMC Change Management enables users to maintain details of the vendor
and the vendor ticket within a change request to track a vendor's involvement in a change. Users can extract the
vendor details from change requests for reporting purposes using the custom reports feature.
Page 101 of 452
Using
For more information on generating custom reports, see Creating reports (

https://docs.bmc.com/docs/display/ars8000/Creating+reports) in the BMC Remedy Mid Tier documentation.
Note
When you create a change request from an existing incident or problem request, vendor information in
the related request is not automatically copied to the change request created.
To enter vendor information when using the Best Practice view

2. On the change form select the vendor group from the Vendor Group field.
3. If the vendor's ticket number is available, enter this information in the Vendor Ticket Number field.
4. Click Save.
To enter vendor information when using the Classic view

2. Click the Vendor tab and enter the following information:
Field
Description
Vendor Information
Enter the name, organization, and vendor group of the vendor.
Vendor Contact
Enter information about the designated contact person for the vendor company.
Vendor Ticket Information
Enter details of the vendor's ticket.

Details include:
If the change request has been assigned to a vendor
Vendor ticket number
Date when the service was requested from the vendor
Date when the vendor responded to the service request
Date when the vendor completed the requested service
3. Click Save.
5.2.4 Recording the change activities

You might need to modify a change request with work history entries that you add during its lifecycle, in order to
document activities performed or information gathered. For example, you can track a change request's progress
by recording the steps that you took to implement it in the work history.
You might want to add work information about the following activities:
General Information Notes about the record. For example, you might want to add a note that a
particular CI was deployed, and include the date.
Page 102 of 452
Using
Planning Notes about a plan to implement a global change throughout your organization.
Implementation Installation and back-out procedures for the change.
Costing and Charging Additional information about the cost of the current CI, incident, change, and so
on. For example, you might want to add a note that the cost of maintaining a CI was split between two cost
centers, or that the cost to implement a change was under budget.
Any user with change related permissions User, Master, Viewer, or Submitter can add or modify work info
from the Change console or the change request in Modify mode. However, only users with Change Master
permissions can add work info to closed Change requests.
Note
In the Classic view user with Infrastructure Change Submit permissions can add, but cannot
modify work info.
If you are using the Best Practice view, you can view multiple work info entries at the same time
by clicking the History icon. When you click this icon, the system displays a pop-up window with
the Notes field entries arranged with the most recent entry at the top (a date and time stamp is
also visible with each entry).
If your user ID has Infrastructure Change Viewer permissions, you can add and modify Work Info
entries, however, you cannot create or modify change requests.
Use the following procedures to add work information about activities performed for the current change request.
To add or modify work information in a change request when using the Best Practice view (see page 103)
To add work information to a change request when using the Classic view (see page 105)
To add or modify work information in a change request when using the Best
Practice view
2. To add new work information, under the Add Work Info details section on the Work Detail tab, enter the
following information:
Notes Enter the details of your work information record.
Attachment Click
to add any attachments related to the work information. You can add up to
three files.
3. Click Advanced to select the work information type and add any additional attachments.
a. From the Work Info Type list, select the type of work information to add.
b. In the Attachment fields, add any additional attachments required for the work information. You can
add up to three files.
c. From the Locked list, select Yes or No to lock the log.
Page 103 of 452
Using
c.
Warning
If you select Yes, you cannot modify the work log after you save it. A locked work log can
only be modified by a user with the functional role of a Infrastructure Change Master.
d. From the View Access list, specify the level of access to the work entry:
Select Internal if you want only users with application permissions for BMC Change
Management to see the entry.
Select Public if you want everyone with access to the system to see the entry, including
requesters.
Note
The information in this note applies to environments that also run BMC Service
Request Management.
When a work note is created in a change request that originated from the BMC
Service Request Management console and is marked as Public, the work note also
appears in the request's activity log in the Request Entry console of BMC Service
Request Management. If the work note is updated, the original work note remains in
the request's activity log, but the updated information is placed in a new entry in the
request's activity log.
If the work note in the incident request is updated and the Assignee marks it as
Internal, the original work note remains in the request's activity log, but the updated
information is not displayed.
4. When you finish updating the change request, under Add Work Info, click Save.
The Save operation adds your entry to the work history.
5. To view or update the entries in the work information, select the work info record and click view
6. Under the Edit Work Info section:

a. Update the required fields.
b. To remove an attachment, click delete
for that attachment.
c. Click Save.
7. To view a report of selected activities that you performed against this request, select the records from the
work info table and click report
8. To view the history of when and by whom each of the work information was added, click history
9. Click Save.
Page 104 of 452
Using
To add work information to a change request when using the Classic view
1. Open the Change request.
2. On the Work Info tab click Create.
3. From the Work Info Type list, select the type of work information to add.
4. From the Source list, select the source of this information.
Information sources can include email, system assignment, or the web.
5. Enter the details of your work information record in the Summary and Details or Notes fields.
6. To add an attachment to the record, right-click in the attachment table, and then choose Add.
7. From the Locked list, select Yes or No to lock the log.
Warning
If you select Yes, you cannot modify the work log after you save it. A locked work log can only be
modified by a user with the functional role of a Infrastructure Change Master.
8. From the View Access list, specify the level of access to the work entry:
Select Internal if you want only users with application permissions for BMC Change Management to
see the entry.
Select Public if you want everyone with access to the system to see the entry, including requesters.
9. When you finish updating the change request, click Save.
The Save operation adds your entry to the work history. The Show field enables you to filter specific work
entries based on the type of activity that appears in the table.
10. To view a report of selected activities that you performed against this request, select the records from the
work info table and click Report.
11. To view the history of when and by whom the work information was added, click History.
12. To view or update all entries in the work information, click View.
In the Change Work Info dialog box, select the work info record you want to change, update the required
fields, and then click Save.
Note
When you return to the request, refresh the Work Info table to see all the modified records.
13. Click Save.
5.2.5 Modifying change requests - Additional information you can enter
Page 105 of 452
Using
As you track and supervise a change request, you move it from one stage to another (for example, from Initiate to
Review and Authorize). When you choose different stages, messages alert you if you need to complete more
fields in the request.
Note
A request should follow the stages in the recommended lifecycle of a change request, as described in
Change request lifecycle (https://docs.bmc.com/docs/display/change81/Change+request+lifecycle). Manually
setting the status values can disrupt the lifecycle in which you enter information about and resolve the
change request.
To modify change requests

1. Use one of the following methods to locate the change request:
On the Change Management console, select the change request from the Assigned Change table,
and click View.
Search for the change request.
2. On the Change form, make the appropriate changes.
3. Use the Process Flow Status area to move the change request from one status to the next, as shown in the
following figure:
If you need to suspend work temporarily on the change request you are working on, select Enter Pending
and an appropriate status reason (for example, Manager Intervention) from the Process Flow Status menu.
When you are ready to continue work on the change request, select Resume from the Process Flow Status
menu.
Note
The Change Manager or Change Coordinator can resume a pending change request.
Page 106 of 452
Using
Otherwise, the Status field is updated automatically during the Process Flow.
4. (Optional) Perform the following actions:
Action
For more information
Add a task to the change request.
See Implement stage - Working with tasks (see page 150).
Modify the change request assignments.
See Working with change request assignments (see page 167).
Relate a CI or some other object to the change
See Working with relationships (
request.
Modify the start and end dates of the change
See Plan and Schedule stage - Planning the change request (see page 113).
request.
5. Click Save.
5.3 Review and Authorize stage - Risk and impact analysis

No change to the IT infrastructure is without risk. Therefore, your change requests should minimize the severity
of any impact and disruption. They also should be successful at the first attempt. The change manager is
responsible for planning and scheduling change requests, which includes assessing their risk and impact. During
the Review & Authorize stage, the change manager should estimate the impact by using the risk assessment
functionality.
Reviewing and authorizing change requests
Page 107 of 452
Using
Note
You reach the Review & Authorize stage only if an approver is mapped to the Business Approval phase. If
no approvers are mapped to the Business Approval phase, the request moves to the Planning in Progress
status. You should then perform risk and impact analysis during the Plan & Schedule stage. For more
information, see Plan and Schedule stage - Planning the change request (see page 113).
When you are working on a change request, you use the Change form to describe the change and to show which
products and services are affected by the change. Before you can submit a change, you must define the Change
Type, Impact, Risk Level, and Urgency.
Page 108 of 452
Using
You also specify the Class of the change on the Change form.
You also must use the Classification tab to specify the Class of the change.
Selecting these values automatically determines the Risk Level and Lead Time for the change.
For more information and instructions, see the following topics:
Risk assessment (see page 109)
Specifying risk level at the Review and Authorize stage (see page 110)
Computing risk levels (see page 110)
Risk Recalculation (see page 112)
Planning dependencies for change requests (see page 112)
5.3.1 Risk assessment

Risk assessment helps you achieve greater productivity by combining qualitative and quantitative criteria for
assessing the risk level associated with a change. You can raise the accuracy of the changes by assessing risks
with a consistent and standard process. The end output is a Change Risk Report, which can provide a key decision
in change planning.
Recommendation
No matter how well-planned or tested a change might be, you must consider the possibility that your
change can create disruptions elsewhere in the IT infrastructure. Do not approve any change request
that does not explicitly plan for the possibility of failure. For more information, see Creating change
requests as rollbacks (see page 93).
When approvers review a proposed change request, they want to see an analysis of potential risks and the impact
of the change request.
During the planning phase, assess the risk of your change request. Risks can include the number of people
affected, financial concerns, loss of productivity due to system or network downtime, resource allocation, and
seasonal considerations, such as vacations, holidays, and weather. Impact analysis needs to be based on how
many people are affected by the proposed change, and where those people are located. Here you can select the
anticipated risk that this proposed change has, from 5 (highest risk) to 1 (lowest risk).
You can also compute the risk of a change request. Risk factors can include a set of questions used to calculate
the risk value. During configuration, your application administrator defines a set of questions that apply to a
specific company, to the operational categorization of a change request, or globally to all change requests, and a
weight for each question. For example, your application administrator can define a set of questions that apply
only to change requests regarding decommissioning virtual machines, if those change requests are identified by
operational categorization.
Page 109 of 452
Using
The support staff assigned to each change request provides the risk value and probability for each question as it
pertains to their specific request. The system calculates the total risk and saves the value in the Risk Level field of
the Change form.
Finally, you can view a report of the total impact of your risk changes.
The Change form includes the following fields for risk management:
Risk Level Enter the anticipated risk that this proposed change has, from 5 (highest risk) to 1 (lowest risk).
Impact Determine the impact of this change based on the number of affected users.
Performance Rating When using the Classic view, in the Classification tab, rate the work done by support
staff or the manager in completing the change request. Usually, the manager of the support staff assigned
to the change request enters this rating after the change request is closed. This field is not displayed in the
Best Practice view.
Note
To configure the risk levels, see Configuring risk assessment (
https://docs.bmc.com/docs/display/change81/Configuring+risk+assessment).
5.3.2 Specifying risk level at the Review and Authorize stage

This section describes how to define a risk level for a change.
To specify the risk level at the Review and Authorize stage

2. Use the Process Flow Status bar to move the change request to the Review & Authorize stage.
3. In the Risk Level field on the Change form, select the appropriate level of risk for the change request, and
then click Save.
The range of risk runs from Lowest Risk Level 1 to Highest Risk Level 5. Alternatively, you can use the risk
value computed based on your answers to a series of predefined questions (as described in the Computing
risk levels (see page 110) section) or a derived risk factor, if configured (as described in the Configuring risk
assessment (https://docs.bmc.com/docs/display/change81/Configuring+risk+assessment)). Risk value can be
computed based on a combination of predefined questions and derived risk factors.
5.3.3 Computing risk levels

To support best practices for the risk assessment process for change requests, you can have the system compute
the risk level.
Page 110 of 452
Using
For more information about how risk assessment is computed, see Configuring risk assessment (
https://docs.bmc.com/docs/display/change81/Configuring+risk+assessment).
To compute risk levels

1. Open the change request in the Change form.
2. Click the Risk Level icon
3. In the Risk Assessment Questions dialog box, answer the questions, and then click Save.
These risk questions are defined and created by the application administrator with support and guidance
from the Change Manager. They might be specific to the company or to the operational categorization of
the change request.
Note
If you change the operational categorization of the change request and click the Risk Level icon,
the questions are kept to provide traceability/audit of the lifecycle of the request.
4. Save the change request.

5. To view and print a report of the risk assessment, click View Risk Report.
Choose Links > View Risk Report in the left frame of the Change
form.
Choose Advanced > View Risk Report in the left frame of the Change
form.
The Change Risk Report dialog box displays the summary, which includes the questions and responses, the
derived factors, if applicable, and the Aggregate Risk Value. The derived factors section includes the
change impact, change priority, CI impact, and CI priority. The Aggregate Risk Value is calculated based on
the risk questions and responses and the derived factors.
Notes
The Aggregate Risk Value does not directly reflect the risk level that you manually entered.
For more information about how the aggregate risk value is calculated, see Sample rating
calculation (https://docs.bmc.com/docs/display/change81/Sample+rating+calculation).
The Change Risk Report includes values of all questions and responses provided during the
life cycle of the change. For example, if you change the operational categorization of the
change request, click the Risk Level icon and provide a set of responses, these questions
and responses are included in the risk report to maintain an audit of the lifecycle of the
change.
Page 111 of 452
Using
5.3.4 Risk Recalculation

Risks can be configured within a change template and are applied when the template is used to create a change.
Additionally, risk calculations can be configured on the Risk Factor Configuration form. Configuring risk factors
overrides any risks set in the change template.
In certain scenarios, risks are recalculated due to configuration conflicts. For example, when the user uses a
change template that has a risk value defined, the risk level for the change is set to this value. If at some point this
change is reassigned to a user for whom risk settings have been configured, risk is recalculated based on the
configuration defined. The value defined in the change template is overwritten and the following error message is
displayed:
The system has computed a new value for Risk level. To use this computed value, clear
the value in the Risk Level field and press Save. ARNOTE 48140
To configure risk within a change template, select Administrator Console > Application Administration Console >
Custom Configuration > Change Management > Template > Template and define a risk level.
To configure risk calculations on the Risk Factor Configuration form, select Administrator Console > Application
Administration Console > Custom Configuration > Change Management > Risk Factors > Change Risk Selection
and define risk calculation factors.
For more information about configuring change risk calculation, see Risk assessment (see page 109).
5.3.5 Planning dependencies for change requests

When planning how to implement a series of change requests, determine in what order, if any, they must be
completed. To set dependencies, you assign a sequence number to each request. Requests with a lower
sequence number must be completed before those with higher numbers can be completed; otherwise, you are
notified by a warning message (by default). More than one request can have the same sequence number; requests
with the same sequence number are considered peers. For example, a request with the sequence number 3 can
be completed only after all requests with sequence numbers 1 and 2 are completed. Peer requests can be
completed in any order among themselves.
To implement sequence numbers in requests, see Assigning sequence numbers to dependent change requests
(see page 164).
Note
Your application administrator can configure the level of enforcement of the change dependency rules.
For example, BMC Change Management can be configured so that users see an error, not just a warning,
if they complete requests out of sequence. For more information, see Configuring change rules (
https://docs.bmc.com/docs/display/change81/Configuring+change+rules).
Page 112 of 452
Using
A change request can include multiple tasks. When a change request is scheduled, the first task is activated and
set to Assigned. When the last task is completed and its status is set to Closed, the request is Completed.
To implement sequence numbers for tasks, see Sequence number in task groups and tasks (see page 307).
5.4 Plan and Schedule stage - Planning the change request

In the Plan & Schedule stage, the change manager (or change coordinator) plans a forward schedule of changes
(or FSC). This includes planning all the requests approved for implementation, setting target dates, and estimating
the risks and costs involved. When you have finished planning the request, and have supplied all the information
that the approvers require to review the request, you can submit it to the approval process.
Planning and scheduling change requests
Page 113 of 452
Using
Plan for the following important details:

Set the request's status to Planning, and specify the planned dates.
Estimate the time that the project will take.
Estimate any applicable down time associated with the request.
Register an available or unavailable time segment to perform the request.
Assess the risks and impact of the request.
Specify the business justification for the request if necessary.
Define the tasks.
Page 114 of 452
Using
Calculate the costs associated with the request.

Submit the request for approval.
Approvers require all this planning information to decide whether to approve or reject the change request.
See the following topics for instructions:
Planning the change request at the Plan and Schedule stage (see page 115)
Detecting CI collisions between change requests (
https://docs.bmc.com/docs/display/change81/Detecting+CI+collisions+between+change+requests)
5.4.1 Planning the change request at the Plan and Schedule stage
1. Open the Change Calendar.
a. Open the Change request.
b. Perform one of the following actions:
Choose Quick Action > View Calendar.
Choose Quick Links > View Calendar.
c. On the Change Calendar, select how many days' worth of change requests and business events to
show.
For more information, see Using the Change Calendar (
https://docs.bmc.com/docs/display/change80/Using+the+Change+Calendar).
d. View requests as needed.

e. Select the requests and business events for a specific day.
f. Close the Change Calendar when you are finished.
For more information, see Using the Change Calendar (
https://docs.bmc.com/docs/display/change80/Using+the+Change+Calendar).
2. Register available or unavailable time segments for your business event, operational categorization, or CI.
For more information, see:
Registering time segments (see page 415)
Registering unique business events and operational categorizations (see page 420)
Registering time segments for CIs - Creating a blackout schedule (see page 416)
3. Use the Process Flow Status bar to move the request to Planning in Progress status in the Plan & Schedule
stage.
Click the Date/System tab.
Click the Dates tab.
5. When planning a change request, use the Date/System or the Dates tab to track the requested, scheduled,
and actual start and end dates of changes.
Page 115 of 452
5.
Using
When using the Best

Practice view
The Earliest Start Date is

determined by the Submit
The Earliest Start Date is determined by the Lead Time field (in the Classification tab) for the change request.
If it is not already specified, the Requested Start Date is automatically set to the Earliest Start Date.
Date.
For example, User A works for a Support Group SG1 for which working hours (shift) are defined as 9:00
A.M. to 6:00 P.M. PST.
When user A creates a change after 6:00 P.M. PST, the Earliest Start Date for that change is calculated
considering the working hours of the Manager Group. Therefore, the Earliest Start Dateshows the 9:00
A.M. the next morning considering Lead Time =0 (in the Classic view). If the user is in different time zone,
that offset is automatically considered.
Note
When adding dates:
If the change status is not Draft, the Class (on the Change form when using the Best
Practice view and in the Classification Tab when using the Classic view) is automatically set
to Expedited with a warning when the Requested Date is earlier than the Earliest Start Date.
When the Class is changed to Expedited, you are prompted to select a Timing Reason.
The Actual Start Date and Actual End Date fields of the change request are populated
depending on the tasks defined in the Implementation phase of the change. The Actual
Start Date is populated when the first task of the phase is activated and the Actual End Date
is populated when the last task of the phase is either closed, completed, or cancelled.
When the Actual Start Date or Actual End Date is earlier than the Submit Date a warning
message is displayed. The message states that the change must be a Latent change for the
Actual Start Date to be earlier than the Submit Date is displayed and the value in the Actual
Start Date field is cleared. This behavior is displayed irrespective of the status of the change
request.
Recommendation
If many tasks are required for the request you are planning, it might be best to create the tasks
before you enter the dates. The Task Dates table displays the task dates and times to help you
determine the start and end dates of the change request. For more information, see Implement
stage - Working with tasks (see page 150).
6. (Optional) Use the Schedule Assist utility to search for available times for the change request.
For more information, see Using Schedule Assist to search for available times (see page 423).
7.
Page 116 of 452
Using
7. In the Change Dates region of the form, provide dates for the Scheduled Start Date and Scheduled End
Date fields.
If the new dates fall outside the range of the task's Scheduled Dates, changes to the Scheduled Dates (both
Start and End) can result in notifications being sent to task implementers.
Note
The Scheduled Start Date and Scheduled End Date fields are required when moving a change
status beyond Planning in Progress.
However, for no impact changes, or changes that follow a custom process flow that skips the
Planning in Progress stage, you are prompted to enter the Scheduled Start Date and Scheduled
End Date fields when you save the change or move the change to the next stage from the Draft
stage.
8. (Optional) Review the RFC Date information.

This field contains the date and time information at which the change was requested.
9. If the change request did not pass through the Review & Authorize stage, assess the risks and impact of the
change request.
You can compute the risk level of the change. For more information, see Computing risk levels (see page
110).
10. When using the Classic view, click the Classification tab, and then select a Business Justification.
The Classification tab is used to describe the business justification of the request (for example,
Sarbanes-Oxley requirements) and show which products and services are affected by the request. This
information can be helpful when the request goes through the approval process. For more information, see
Adding classification information (see page 99).
11. (Optional) Use the Process Flow Status bar to relate a CI to the change request, as shown in the following
figure:
When the CI Relationships Search dialog box appears, you can search for a CI and then relate it to the
request. For more information, see Working with related configuration items (see page 176).
12.
Page 117 of 452
Using
12. (Optional) Click the Tasks tab.

You can plan and create the tasks that make up the change request. For more information, see Implement
stage - Working with tasks (see page 150).
13. (Optional) Perform one of the following actions to calculate the costs associated with the change request:
Choose Links > Financials.
Click the Financials tab.
For more information, see Adding and viewing costs (see page 294).
14. Click Save.
15. Click Next Stage in the Process Flow Status bar to move the change request forward.
When the change request reaches Scheduled For Approval status, it must be approved to move forward.
For more information, see Approval processes provided out-of-the-box (see page 213).
5.4.2 Detecting CI collisions between change requests

The Collision Detection tool (under the Functions menu) determines if there are other change requests scheduled
to work on the same CI during the same scheduled time, and helps you manage and resolve these potentially
harmful conflicting change requests. For Release Management, Collision Detection is run against the changes in
the release manifest, not the changes related to the release in the Relationships tab. Collision Detection does not
apply to release activities in the release manifest.
Note
The Collision Detection tool works a little differently with Release Management than with BMC Change
Management. The Collision Detection link does not turn red when a collision is detected. Also, you fix
collisions in the Manifest tab of the release form.
CI collisions detected with change requests
Page 118 of 452
Using
The Collision Detection tool consists of two sections:

The Include Collision State section at the top lets you include (or exclude) change requests that have
alreadyrun through Collision Detection. The following collision states are detected:
Collision
state values
Description
None Found
The change request has been checked for collisions and none were found (green). When running Collision Detection from a
release, changes with no scheduled start or end dates will have a collision state of None Found.
Note: Used primarily with Release Management.
Detected
Collision detected for the listed CI (red).
Ignored
You ignore the collision (purple).
Investigating
You are investigating the collision (orange).
Resolved
You have taken action on the collision (blue).
(clear)
Collision detection has not been run against this change request.
Note: Used primarily with Release Management.
N/A
Used only for Activities in the manifest table. Collision Detection does not apply to Activities.
The Change Requests with Identified Collisions section at the bottom identifies the current CI collisions for
the change request. It lists the CI affected, the change request ID, the scheduled start and end dates, and
the ID and scheduled start and end dates of the change request causing the conflict.
The first time that you run the Collision Detection tool, it shows you only the current collisions in the change
relationship or release manifest. After that when you open the Collision Detection tool only new collisions are
shown, if you maintained the default settings (none of the Include Collision State fields are selected). Previously
Page 119 of 452
Using
detected collisions that need corrective action are not listed. You must select the Include Collision State fields
and then click Identify Collisions to see all CI collisions that need corrective action.
To detect CI collisions between change requests

1. Open the request.
2. Click the Relationships tab on the change form or the Manifest tab on the release form.
3. Choose one of the following options:
For Change Requests Functions > Collision Detection
For Release Requests Functions > Collision Detection
The Collision Detection dialog box appears. By default, none of the options are selected and all
current collisions are displayed.
In the Include Collision State section, choose to include or exclude the collision states (for example,
Detected) when you run the tool. For example, if Detected is selected, then any records that were
previously flagged as Detected are included in the collision detection the next time the tool is run. If
you clear Detected, then these records are excluded from collision detection.
Note
If the status of none of the colliding change requests is Detected or Investigating, or if the
colliding change request is not pending collision detection, the collision detection link for
the change is not shown in red.
4. Select or clear collision states as needed, and then click Identify Collisions.
The table displays the collision state of each change request included in the request.
5. To fix the CI collision:
a. Change the collision state from Detected to Resolved.
b. Close the Collision Detection dialog box.
c. Save and close the request.
Collision states are not saved to the database until you save the request.
d. Open the change request.
e. Run Collision Detection again from the request to determine which CIs are causing the collision.
f. Click the Dates tab of the request.
g. Enter a new Scheduled Start Date and Scheduled End Date which does not overlap with the
detected CI collisions.
h. Save and close the request.
i. Open the request and run the Collision Detection tool one more time from the request to make sure
that no other collisions are detected.
Make sure all the Include Collision States options are cleared before you click Identify Collisions.
j. Save and close the Collision Detection tool.
6. Save the request.
Page 120 of 452
Using
5.5 Approvals - Approving change requests

Within the lifecycle of the change request, approvals might be required. There are several approval phases
possible, which vary depending on how your organization configures and implements the possible changes.
Some changes bypass the approval process altogether. The application administrator determines which change
requests require approval, what kind of approval process the change requests must undergo, and who the
approvers are. Support staff and management can add more approvers to the list.
Tip
The SMPM process model specifies that the best practice is to include an approval after the risk and
impact analysis of a change request.
For more information, see Adding approvers (see page 124).

Approving changes
Page 121 of 452
Using
Submit the change request for approval after you have completed planning the change request and provided all
the information that the approvers require to review the change request.
When the change request requires an approval move to the next stage, the word Approval is displayed on the
Process Status Flow bar. You must approve, cancel, put on hold, or reject the approval from the approval table.
You can configure the approval settings to require one or all approvers. For more information on configuration
options, see Defining roles (https://docs.bmc.com/docs/display/ars8000/Defining+roles) in the BMC Remedy AR
System Approval Server documentation.
It is important to understand that the change manager (or change coordinator) controls the overall progress of a
change request. Change managers submit the requests for approval and monitor the approval process. As a
manager, you might be required to review change requests for approval. You review change requests and provide
approval through BMC Change Management.
Page 122 of 452
Using
The approvers and the approval phase are viewable on the change form.
The approvers and the approval phase are viewable on the Approvers tab.
Approvers are notified when a change request requires their approval. If an approval is reassigned, the new
approver is notified. After reviewing the change request, approvers can approve it, reject it, or put it on hold if
more information is required. When an approver approves the change request, the change request is refreshed
and the updated approval status is displayed in the Approval table on the change form.
In BMC Change Management version 8.1.00, if configured, approvers can approve or reject change requests via
email. For more information on approvals using email, see Approving or rejecting requests via email (see page
143).
When the change request is in the Approval phase, the following fields cannot be modified:
Services CI
Impact
Urgency
Priority
Risk Level
Status
Class
Change Location
Change Manager details
Change Coordinator
Relationships
Operation Categorization
Financial Information
Any Date fields
An approver might not have have access to the BMC Change Management application to approve a change
request. If the approver's access permission does not allow access the change request, he can use BMC Remedy
AR System Approval Central to approve change requests. For more information on approving change requests
from the Approval Central, see Approving changes using Approval Central (see page 131).
Note
If no approvers are mapped to an approval phase, or the phase is configured for a self-approval, the
change request is refreshed after the approval is complete.
Page 123 of 452
Using
If a technical error occurs when the request is sent for an approval, the change request moves to the Pending
status with a status reason as Approval Error. The change user can restart the change request so that it can be
sent for approval again.
The change request is refreshed when no approvers are found for an approval phase or when an approver
approves the change request.
See the following procedures:
For information about reviewing proposed change requests and providing or denying approval, see
Handling approvals for emergency change requests (see page 124).
For information about reviewing the approval process, see Working with BMC Change Management as an
approver (see page 133).
For information about adding approvers, see Adding approvers (see page 124).
5.5.1 Handling approvals for emergency change requests

Depending on how the application administrator has configured the application, change requests that have been
designated as emergencies can be allowed to bypass the approval process even if they normally require approval.
In this case, the emergency change request is not held up waiting for approvals. For more information, see
Creating emergency change requests (see page 91).
Following are possible configurations for handling approvals for emergency change requests:
The application administrator can configure emergency change requests to bypass the normal change
states and approval process. To configure a new approval process for emergency changes, the application
administrator must create a new approval process for your company. As a result, when a change manager
or change coordinator creates a change and selects Emergency in the Class (Timing) field, the new
approval process phase is then used. For more information, see Bypassing the approval process for
emergency changes (
https://docs.bmc.com/docs/display/change81/Bypassing+the+approval+process+for+emergency+changes).
The change manager or the change coordinator can choose to add approvers to the process. The Approval
Status field is set to Approval Required.
If the change manager assigns approvers, the approval process proceeds as usual.
If the change manager does not assign approvers, the Approval Status is set to Approved, and the
change request can be implemented.
If the change request is designated as an emergency and your organization uses the Change Management
Chain approval process, the manager of the Requested For user (in the Requester tab) is the first approver
in the management chain. If the Requested For fields are empty, the emergency approval process is
bypassed. Change managers can add more approvers if appropriate. They cannot delete approvers.
5.5.2 Adding approvers

You can create additional approvers on an ad hoc basis. The following rules apply:
Page 124 of 452
Using
You can add Support Groups or Individuals as approvers.

Group approval requests are sent only to group members with the Infrastructure Change Approver role.
If an individual approver is needed, only people defined within the People form can be chosen as
approvers.
Note
The ability to add someone as an approver is restricted, based on the permissions of the user adding an
approver. If the person adding signatures cannot see the person based on row-level access, they cannot
add them as an approver. But anyone with a record in the People form can become an approver if the
assigner has access to that information.
There are slight differences between ad hoc approvals and the typical approval processes configured by the
application administrator.
If you add an ad hoc approver (for example, Bob Baxter) and an approver mapping does not exist, the
approval server immediately generates an approval signature for the ad hoc approver and Bob is notified
that he must approve the change request. The change request cannot move past the next approval phase
until Bob (the ad hoc approver) approves the request.
If you add an ad hoc approver (for example, Bob Baxter) at the Draft status and an approver mapping
already exists (for example, Mary Mann for the Review phase), the approval server immediately generates
an approval signature for the ad hoc approver and Bob is notified that he must approve the change
request. The change request cannot move past the next approval phase until both Bob (the ad hoc
approver) and Mary (the mapped approver) approve the request.
If the request is already at the Review phase and you add an ad hoc approver where an approver mapping
already exists (for example, Mary Mann), the approval server generates two approval signatures-one for
Bob (the ad hoc approver) and one for Mary (the mapped approver). Also, Bob is notified that he must
approve the change request. The change request cannot move past the next approval phase until both Bob
(the ad hoc approver) and Mary (the mapped approver) approve the request.
For more information about the relationship between approver mappings and approval process configuration
records, see the following topics:
Approval mappings (https://docs.bmc.com/docs/display/change81/Approval+mappings)
Configuring approvals (https://docs.bmc.com/docs/display/change81/Configuring+approvals)
The following topics provide instructions for adding approvers:
Adding additional approvers (see page 126)
Adding alternate approvers (see page 126)
Acting as an alternate approver (see page 127)
Adding non-approval notifications (see page 128)
Page 125 of 452
Using
Viewing and removing non-approver notifications (see page 130)
Adding additional approvers

This section describes the procedure to create additional approvers on an ad hoc basis for a change request.
To add approvers
2. Advance through the states of your change request until you reach an approval stage.
3. Click the Approvers tab.
The Approvers table shows the list of approvers generated for the change request. Their signature is
required for approval. You might need to refresh the table to see the lists. The list contains the following
information:
Approval Status Indicates status of work on the change
Approvers Indicates the names of the approvers
Name Indicates either the individual's full name or the support group name
Alternate Signature Appears when someone other than the original signature owner has approved
or rejected the change
4. Click Add.
5. On the Add Approver dialog box, select an individual, or a group to add.
6. Enter the name of one or more individuals or groups.
7. (Optional) To search for an individual, enter a name or initial in the Full Name+ field, and press Enter.
8. Click Save.
You might have to refresh the table field to see all approvers.
9. Click Save.
The approver is notified that they must review the change request.
Adding alternate approvers

Sometimes an approver might be unavailable because of a scheduled vacation or business event. For that period
of time, the approver should designate an alternate approver because change requests still require approval.
From the People form, you can set up one or more people to approve change requests that are pending your
approval, for example, to add the change manager or change coordinator as an alternate approver.
Note
You can configure alternate approvers only for yourself.
Page 126 of 452
Using
To add alternate approvers for people

1. Open the People form.
2. Search for yourself.
3. Select your record, then click the Alternate Approvers tab.
4. Click Update Alternate Approvers.
The Alternate Approvers form appears.
5. To locate the alternate approver, click Search.
6. In the People Search form, select the alternate approver, then click Select.
7. Select the start date and the end date.
8. In the Notify Alternate field, select whether to notify the alternate approver.
9. In the Covering field, select whether this will be an alternate for all approvals or only for a specific process.
10. If you selected Specific Process in the Covering field, select the applicable process in the Process field.
11. Click Add.
Acting as an alternate approver

If you are acting as an alternate approver of a change request, you have the same signature authority as the
approver for whom you are serving. Your authority as an alternate approver exists for a specific time period, and
for the designated approval process or processes.
To act as an alternate approver

1. Open the Approval Console.
2. From the Action Menu, click Search My Approvals.
Entering information to act as an alternate approver
3. In the Acting As field, select Alternate.

4. In the User field, type the name of the user for whom you are acting as the alternate.
You must enter that user's exact AR System logon name.
5. Select the approval process.
6. Verify that the Approval Status field is set to Pending.
7.
Page 127 of 452
Using
7. Click Search.
The Approval Requests table is populated with the pending requests for the user for whom you are acting
as alternate, instead of your own pending requests.
Adding non-approval notifications

The change manager can notify additional individuals or groups that are not approvers about the approval. These
notifications are non-appoval notifications.
To add non-approver notifications

4. Click View Notifications.
The Non-Approver Notifications dialog box appears. You can select the type of notification you want to
add. The options are:
Individual
Group
5. To add an individual:
a. Select Individual in the Notification For field.
Adding an individual notification
Page 128 of 452
Using
b. Enter the individual's first or last name.

You can enter a last name (or partial last name) and then press Enter to bring up the People Search
form.
c. Click Add to create the notification.
The individual's name, approval phase for the notification, and its status appears in the table.
6. To add a group:
a. Select Group in the Notification For field.
Adding a group notification
Page 129 of 452
Using
b. Specify the support company, organization, and group name.

c. Click Add to create the notification.
The group name, approval phase, and its status (for example, Pending) appears in the table.
Note
Notifications are sent to all users present in the selected Support Group. In previous
releases, notification was sent only to users with the Functional role of Infrastructure
Change Approver.
7. Use the Status field to toggle between viewing Pending and Notified notifications.
8. Delete the notifications, if needed.
9. Close the Non-Approver Notifications dialog box when you are finished.
Viewing and removing non-approver notifications

You can view or remove notifications for non-approver associated with a change.
To view notifications
2.
Page 130 of 452
Using
4. Click View Notifications.
The Non-Approver Notifications dialog box appears.
Non-Approver Notifications dialog box
To delete a non-approver notification

1. In the Status field, select Pending (default) or Notified.
The figure above shows that a notification has been sent to a user about an approval for the Business
Approval phase of a change request.
2. Select the notification to remove and click Delete.
A warning appears, verifying that you want to delete the selected notification.
3. Click Yes to delete the selected notification.
The notification is removed from the table.
4. Close the Non-Approver Notifications dialog box when you are finished.
5.5.3 Approving changes using Approval Central

Page 131 of 452
Using
You can use BMC Remedy AR System Approval Central to approve change requests. This is especially important if
your current access permission does not allow you to access the change request. Not all approvers have access
to the BMC Change Management application through their home pages, yet still have the role to approve change
requests before they can move forward.
Note
You must have appropriate permissions to modify a change request to view the change request and
approve it. For more information on roles and permissions, see User permissions (
https://docs.bmc.com/docs/display/itsm80/User+permissions) in the BMC IT Service Management
documentation.
To approve changes using Approval Central

1. Log in to the AR System server as the approver.
2. Open Approval Central.
Using Approval Central to approve change requests
Approval Central displays all pending change requests that are assigned to you. If there are many requests,
you can filter them by using the fields in the Search Criteria area.
Page 132 of 452
Using
Note
Click the Source ID to view details of the change request.
3. Approve, reject, hold, reassign, or view the change request.

After you approve the change request, it no longer is displayed in the Approval Requests table. The
appropriate approvers are notified of any reassigned approvals.
Note
If approvers need more information about a change request, they can view the request details and add a
question in the approval activity log. Their signature is on hold while they are waiting for the information
and the status is set to More Information.
5.5.4 Working with BMC Change Management as an approver

BMC Change Management integrates fully with the BMC Remedy Approval Server for business, technical, and
financial approvals.
An approver must:
Be defined in the ITSM Foundational People form
Be assigned an appropriate application permissions. For example, Infrastructure Change Viewer is sufficient
for a user who only needs to approve a request through the Approval Central.
Have a BMC Remedy Action Request System Read license.
Have the functional role of Infrastructure Change Approver
Additionally, the server must have the appropriate BMC Remedy ITSM application license.
Note
The BMC Change Management application ships with defined approval processes. Most companies
should not have to define additional approval processes. However, you can use the Approval Process
Configuration form to define additional approval processes for your company. For more information, see
Approval processes provided out-of-the-box for BMC Change Management (see page 139).
In BMC Change Management application administrators can define an approval process in which a series of
people must review and approve a proposed change request or release request. Only after all approvals are
granted can the change request or release request be moved to the next status. A change request goes through
several phases as it progresses through its lifecycle. Approvers are responsible for reviewing their assigned
change requests, and for approving or rejecting them. Approvers are configured by the application administrator
Page 133 of 452
Using
and are responsible for change requests with a specific categorization and location.The application administrator
also determines which types of change requests need approval, and what type of approval process they
require.As the change request moves from one status to another, the default workflow on the change request
queries the approval server to find out which approval process to use, and then executes it.
For example, when a change request moves from the Draft status into the Review phase (shown in the following
figure), the Approval Server checks the Review approval process. If the application administrator mapped an
approver to the Review process, the change request must be approved before it moves to the next stage. Also,
the Class and Timing Reason fields are locked by workflow. You cannot make modifications to the values set in
these fields until the change request is approved and it moves to the next status in its lifecycle.
Change request going through Review Approval in the Review & Authorize stage
The Approve option is enabled in the Process Flow bar when a change request is sent for Approval.
Page 134 of 452
Using
Approval option enabled
When the user clicks the approve option the change request is approved and it moves to the next status in its
lifecycle. In case of an auto-approval (no approver is assigned), the change form is refreshed to show the updated
Change status after approval.
Note
The Approve option is displayed to all users, even if the user is not an approver for that change request.
If a user, who not an approver for that change request clicks the approve option the following error
message is displayed:
You are not currently defined as an alternate for any user and you are not on
the Approvers list for this approval. (ARERR 45802).
The change manager or change coordinator controls the overall progression of a change request, and can
perform approvals at several points in the change life cycle. For change requests in the Request for Change status
with no approvers, the change manager and the change coordinator can move the change forward to Planning In
Progress, cancel it, or send it back to the requester by assigning it a status of Draft. After a change is planned and
built, the change request is set to a status of Scheduled for Review. Once again, the change manager or change
coordinator has the opportunity to review change plans, schedules, and so on, before moving the change to the
Implementation Approval phase.The following people perform the approval process:
Approver
Responsibility
Application
administrator
Selects the approval process, and if necessary, modifies the approval rules. Configures the approval mappings. For more
information, see Approval mappings (https://docs.bmc.com/docs/display/change81/Approval+mappings).
Change manager
(or change
coordinator)
Monitors the approval process to make sure that it proceeds as expected. The change manager also determines which types
of change requests need approval, and in some cases, selects the approvers.
Change approvers
Reviews the change request and approve or reject it. If approvers need more information about a change request, they can
request it. Their signature is put on hold while they are waiting for the information and the status is set to More Information.
Requester
Checks the status of the change request and follows the approval process throughout its cycle.
5.5.5 Viewing approvers for a change request

In the Approvers table on the Work Detail tab of the Infrastructure Change form, you can see the approvers for
the change request.
Page 135 of 452
Using
Initially, the Approvers table displays all pending reviewers for the current approval phase. The Show list provides
filters so that you can display all approvers or a subset of approvers. The following filters are provided:
Filter
Description
Pending
Displays approvers whose approval is pending
Approved
Displays approvers who have already approved the change request
Rejected
Displays approvers who have already rejected the change request
Hold
Displays approvers who have put the approval of the change request on hold
More
Displays approvers who have requested for more information to approve the change request
Information
Cancelled
Displays approvals that were cancelled
Error
Displays approvals that encountered errors
Closed
Displays approvals that have been closed
Future
Approvers
Displays approvers for future stages of the change request, regardless of whether you have configured an approval phase or not. This
filter is useful when a change request must go through multiple approval phases.
Tip: To see which approvers are required for a specific future phase, view the future approvers and sort on the process column.
All
Approvers
Displays all approvers for all stages of the change request in approval phases have been configured. This list including approvers who
have already approved or rejected the change request
For each approver, the Approvers table displays the following information:
The approval status, such as Approved or Pending
Note
The value of the approver Self indicates that the request submitter has the required authority to
approve the change request and does not require any additional approvers to take action. This
request is considered to be a self-approved request.
A self approval rule is defined in the approval process for this option.
The approver's logon ID and name

The approval process, such as Change Level-Review
5.5.6 Resubmitting a rejected request

If an approver rejects a proposed change request, the approval process is stopped. The Approval Status is set to
Rejected. You can resubmit the request for approval.
Page 136 of 452
Using
To resubmit a rejected request

1. Open the request record.
2. From the process flow bar, at the stage the request was rejected, select Restart.
The request status is set to Pending Approval for the stage at which it was rejected.
Note
When an approver rejects a request, all signature lines associated with the request are closed. If
this request is restarted, any ad hoc approver assigned to the request will have to be added again.
Any tasks associated to the change request are not affected when the change is rejected and can
be resumed when the change request is resumed.
When approving the request after it was restarted, users can enter details for restarting the request in the
Work Info.
Click the Work Details tab and enter details in the Notes field.
Click the Work Info tab and enter details in the Details field.
4. Save your changes.
5.5.7 Approving or rejecting requests

When you finish planning the request, and have supplied all the information that the approvers require to review
the request, you can submit the request for approval.
When a request requires an approval, its approvers are notified. Notifications are sent according to the method
specified in the Notifications tab of the approver's record in the People form. Approvers receive an email with
details of the request and approve and reject options if email based approvals are enabled.
For more information on email based approvals, see Approving or rejecting requests via email (see page 143).
On the request, the word Approval is displayed on the Process Status Flow area. The request must approved,
canceled, or rejected from the Approval table on the change request or the Approval Server for it to move to the
next defined status.
If the request is approved:
An approval signature is generated and the request moves to the next valid status or the status defined in
the Approved field of the Approval Process Mapping.
If the request is rejected:
It moves to the status defined in the Rejected field of the Approval Process Mapping. When the change
Page 137 of 452
Using
request is rejected all pending approval signatures are closed.

A rejected request can be resumed or canceled. If the reason for rejecting the request can be resolved, the
Change Manager, Change Coordinator or Release Coordinator can take the necessary action and resume
the request. Otherwise, the request can be canceled. Tasks associated to the change request are not
affected when a change is rejected.
If the request is resumed, all approval signatures are regenerated, and approved signatures stay as
approved. Tasks associated and can also be resumed.
For more information on resubmitting rejected change requests, see Resubmitting a rejected request (see
page 136).
For a change request, the request moves to the Pending status with a status reason as Approval Error when:
A technical error occurs when the request is sent for an approval.
An Ad Hoc change is defined, and the Change Manager for the Change Requester in not defined.
Approval is mapped to a Group and no valid approver is found within the Group.
Change Approval Chain has been configured and an approver cannot be found.
The change user can restart the change so that it can be sent for approval again.
Note
For more information, see Handling approvals for emergency change requests (see page 124) and
Working with BMC Change Management as an approver (see page 133).
5.5.8 Understanding the change management approval process

After a change is planned and scheduled, the change request is set to a status of Scheduled for Review. The
change manager or change coordinator has the opportunity to review change plans, schedules, and so on, before
moving the change to the Implementation Approval phase.
When a request is in the Approval phase, the following fields within the change record cannot be modified:
Services CI
Impact
Urgency
Priority
Risk Level
Status
Class
Change Location
Page 138 of 452
Using
Change Manager details

Change Coordinator
Relationships
Operation Categorization
Financial Information
Any Date fields
To access functions involving Approvers, perform the following action:
Use the Work Detail tab on the Change form.
Use the Approvers tab on the Change form.
The following buttons in the Change form control functions involving approvers:
Button
Action
Opens the APR:Non-ApprovalNotifications form so that you can view notifications in either Pending or Notified status. Notifications are
listed in the table on the form. For more information, see Viewing and removing non-approver notifications (see page 130).
Note: The same forms allows you to add notifications for the change.
Creates a new individual or group to approve the change. For more information, see Adding approvers (see page 124).
Allows an approver or a change manager or coordinator defined as alternate approvers, to approve the change request. This button is
enabled only if the user is a valid approver for the record. For more information, see Adding alternate approvers (see page 126).
Allows an approver or a change manager or coordinator defined as alternate approvers, to reject the change request. This button is
enabled only if the user is a valid approver for the record. For more information, see Adding alternate approvers (see page 126).
5.5.9 Viewing change requests awaiting approval

You can view a list of all change requests that are awaiting approval.
To view change requests awaiting approval

1. In the Change Management console, under Counts in the left navigation pane, click Waiting Approval.
The Changes table shows the change requests waiting approval.
2. Select the change request to review, and then click View.
The approver can approve or reject the change request the Change Request form, or request further
information.
5.5.10 Approval processes provided out-of-the-box for BMC Change

Management
Page 139 of 452
Using
BMC Change Management ships with default approval processes designed out-of-the-box for global use. These
best practice approval processes are already defined for you by default. These processes specify which status
occurs next if a request is approved or rejected, or if no approvers are defined.
Preconfigured approval processes for BMC Change Management
Approval
Definition
Process (phase)
Review
In the Initiate stage, the out-of-the-box behavior for change requests is that when their Status moves out of Draft status into
Request For Authorization status, the Review approval phase starts.
If the change request is approved, the request moves to the Business Approval phase and its Status becomes Request For
Change.
If the change request is rejected, its Status changes to Rejected.
If there are no approvers defined for the request (that is, if no approvers are mapped to the Review approval phase), its
Status changes to Request For Change and requires the change manager or the change coordinator to move the request
forward.
If the Class of the change is Latent, it moves to the Completed status.
Business
Approval - No
Impact
The Change Ad Hoc approval process is used in the No Impact Business Approval phase with the Change Manager logon as the
first approver. By default, this Ad Hoc approval process applies only to changes with a Class setting of No Impact. No approver
mapping is required to be configured for this phase.
When the change moves through the process flow and Change Manager approves the change in the Business Approval - No
Impact phase, it then moves to the Scheduled status. You use this process for preapproved No Impact changes where the change
is automatically scheduled after the approval phase is satisfied.
If the change is approved, it moves to the Scheduled status.
If the request is cancelled, it moves to the Cancelled status.
If the request is rejected, its status changes to Rejected.
Business
The Review & Authorize stage focuses on risk assessment and impact analysis. The Business Approval Phase starts when the
Approval
change request is placed in Request for Change status. The Business Approval phase requires that the business case for the
change be approved before it can move forward.
If the change is approved, it moves to the Planning in Progress status.
If no approvers are mapped to the Business Approval phase, the change moves to the Planning in Progress status and
requires the change manager or change coordinator to move the change forward.
If the request is cancelled, it moves to the Cancelled status.
Implementation
Approval
In the Plan & Schedule stage, the out-of-the-box behavior for change requests is that the Implementation Approval phase starts
when their Status moves into Scheduled For Approval status. At this phase, the system notifies you that the change must be
approved before it can be implemented.
If the change request is approved, its Status becomes Scheduled.
If there are no approvers defined for the change (that is, if no approvers are mapped to the Implementation approval
phase), its Status changes to Scheduled.
Close Down
Approval
In the Implement stage, the out-of-the-box behavior for change requests is that the Close Down approval phase starts when their
Status moves into Completed status (with a status reason of Final Review Required). At this phase, the system notifies you that the
request must be approved before it can be closed down.
Page 140 of 452
Using
Approval
Process (phase)
Definition
If the change request is approved, its Status Reason becomes Final Review Complete. You can then move the request to the
Closed stage.
If there are no approvers defined for the change (that is, if no approvers are mapped to the Close Down approval phase), its
Status is Completed. You can then move the request to the Closed stage.
Approval Administrators can globally approve or reject the change request. This may be required if approvers are not
available or the CAB makes a decision the requires an urgent approval or rejection of a change request. If the change is
globally approved or rejected, the approval status is changed to Closed.
The read-only Next or Current Approval Phase field displays what approval phase the change is in during its life
cycle. The Approvers tab also displays the following important information:
Approval status
Signatures of groups and individuals who must approve the change request
Alternate approvers
Approvals can be generated automatically, based on information captured on the change request. They can also
be generated manually on an ad hoc basis.
Change form Approvers tab
Page 141 of 452
Using
If needed, the application administrator can configure the change request approval workflow according to your
organization's business model. This determines which change requests require approval and what kind of
approval process they undergo.
5.5.11 Multiple approvers and multiple approval levels

There can be more than one level of approval, and there can be several approvers on each level. At least one
approver on each level must approve the change request before it can be reviewed by the next level of approvers.
Approvers can review the actions of previous approvers by viewing their comments and the approval audit trail.
Notes
This information in also applicable for the Release Management module.

You can configure the approval process to have one or all approvers on each level approve the
change request before the change can be reviewed by the next level of approvers. Modify the If
Page 142 of 452
Using
Multiple Approvers setting to configure this option. For information about modifying the If
Multiple Approvers setting, see Defining roles (
https://docs.bmc.com/docs/display/ars8000/Defining+roles).
The application administrator can also configure the change management chain (parent-child) approval process.
If the change is configured for the management chain approval process, the requester's manager is notified.
If the change is approved by all approvers, the approval process is complete and the change moves to the next
status. If the change is rejected by any approver, the change is stopped. The change manager or change
coordinator can then cancel the change or update it and resubmit it for approval.
Approving the change request can complete the approval or trigger the next step in the approval process. If there
are several levels of approvers, your approval can send the approval request to the next approver or if you deny
the request the approval process is completed, regardless of whether more approvers are defined.An approval
signature cannot be modified after the request has been rejected, and the approval process is finished. If the
change request is to be implemented, the change manager must first restart the approval process.
For additional information see the following topics in the BMC Remedy Action Request System Approval Server
documentation:
Creating signatures for multiple approvers (
https://docs.bmc.com/docs/display/ars8000/Creating+signatures+for+multiple+approvers)
Working with request details (https://docs.bmc.com/docs/display/ars8000/Working+with+request+details)

Creating new approval requests (https://docs.bmc.com/docs/display/ars8000/Creating+new+approval+requests)
Defining roles (https://docs.bmc.com/docs/display/ars8000/Defining+roles)
5.5.12 Approving or rejecting requests via email

Starting with Version 8.1.00, you can approve requests via email. When email-based approvals are enabled, an
email notification is sent the individuals who have approval authority for the request. Those people either can
approve or reject the request directly from the email notification.
Notes
If the approval process requires a password or requires that rejection of a request includes a business
justification, you cannot use email-based approvals. If this is the case, you must approve the request
from Approval Central.
Approval email notifications are also sent out to any alternate approvers defined for the process.
However, if the approver adds an alternate approver after the email has been sent, the alternate
approver will not receive the email.
Page 143 of 452
Using
The following figures show examples of approval emails. Instructions for approving and rejecting requests via
email (see page 145) are provided after the figures.
Email for a change request approval
Email for a service request approval
Page 144 of 452
Using
Note
The Server Timezone Offset displays the time zone offset information where the BMC Remedy AR
System server is located.
To approve or reject a request via email

1. In the approval email that you receive, click the request ID link to view the details of the request. However,
this is not applicable for service requests.
2. Click Approve or Reject.
An email formatted with your approval or rejection reply is displayed.
3. Send the email without modifying the text.
Warning
Page 145 of 452
3.
Using
Do not modify the content followed by the #DO NOT MODIFY FOLLOWING TEXT# text in the
email.
You are notified of the success of the approval or rejection by email, as shown in the following figure:
If you attempt to approve or reject a request that is in a state that cannot be changed (approved, rejected, closed,
or canceled), you receive an approval error notification email, as shown in the following figure:
If you receive a Approval Error Notification, click Launch Approval Central to view the status of the request.
5.6 Implement stage - Implementing the change
Page 146 of 452
Using
At the Implement stage, change coordinators take over responsibility for working on the change request. Change
coordinators are support staff members with specialized abilities who handle the details of the change request.
Change coordinators frequently exercise lead responsibilities based on factors such as location, skill set,
troubleshooting skills, difficulty of the change request, and company (if you are a service provider). In large
companies, the change manager would be responsible for the overall change such as scheduling, but the change
coordinator would perform the day-to-day management of the change request process, for example, building
and reviewing change plans, managing the change implementer, making sure that the change proceeds in a
timely fashion, and so on.
Implementing change requests
The responsibilities of a change coordinator include the following tasks:
Page 147 of 452
Using
Gathering appropriate information based on the type of change being investigated.

Associating related CIs, incidents, and services to the change request.
Providing status updates to requesters.
Reviewing change plans and schedules - Planning activities include scheduling the change request,
assessing risk and impact, creating plans, defining and sequencing the tasks needed to accomplish the
change request, and scheduling people and resources for each task.
Reviewing all completed tasks. In the Implement stage, at least one task related to the change request is in
progress.
Conducting post-implementation reviews to validate the results of the change request.
Determining requester satisfaction with change request.
The change request remains at the Implement stage until all tasks are completed, all required approvals are
granted, and reviewers verify that the change was implemented.
For more information about procedures frequently used by change coordinators, see the following links:
Tracking efforts for a change request (see page 158)
Working with relationships (https://docs.bmc.com/docs/display/change81/Working+with+relationships)
The following topics provide more information about implementing changes:
Identifying change requests as rollbacks (see page 148)
Implementing a change request (see page 149)
Implement stage - Working on task assignments (see page 149)
Implement stage - Working with tasks (see page 150)
5.6.1 Identifying change requests as rollbacks

If the actions associated with a change request need to be reversed, your support staff and managers can identify
the request as needing to be rolled back. This means that impacted systems need to be restored to their previous
state before the change request was implemented. The status of a change request must be Implementation In
Progress for you to identify it as a rollback.
The known error is the result of an incident review request of incident request records associated with a specific
CI. The change is initiated by the known error that identifies the problem's root cause and indicates to the change
coordinator that a rollback is required.
For more information about incident request reviews, see Incident request review process (
https://docs.bmc.com/docs/display/servicedesk80/Incident+request+review+process).
To identify a change request as a rollback

2. Use the Process Flow Status bar to move the change request to Implement stage.
3.
Page 148 of 452
Using
3. Make sure the Status field is set to Implementation In Progress.

4. Set the Status Reason field to In Rollback.
5. Create a related task to implement the rollback for this change request.
6. Roll back the change request.
7. Use one of the following options to add a work info record to enter information about why you are rolling
back the change request :
Update the fields on the Work Detail tab.
Update the fields on the Work Info tab.
8. Move the change request to Completed or Closed status.

Changes in value to the Status field are tracked in the audit trail.
9. Click Save.
5.6.2 Implementing a change request

This section describes the procedure to implement a change request.
To implement the change request

2. Use the Process Flow Status bar to move the change request to Implement stage.
3. To modify the change request assignments, do one of the following:
Click the Work Detail tab.
Click the Assignment tab.
For information, see Working with change request assignments (see page 167).
4. Click the Relationships tab.
Define the relationship of the change request to other change requests, CIs, LDAP objects, storage
locations, and so on. For information, see Working with relationships (
5. Click the Tasks tab.

a. Create the tasks necessary to implement the change request. For information, see Implement stage Working with tasks (see page 150).
b. Assign the tasks to the appropriate task implementers. For information, see Working with BMC
Change Management as a task implementer (see page 299).
c. Reassign tasks as necessary. For information, see Responding to task reassignments as a change
coordinator (see page 281).
5.6.3 Implement stage - Working on task assignments

Following the recommended life cycle of a change request, the status of a task should be in Scheduled before
you accept the task. You cannot start working on a task until the change request reaches the Implement stage.
Page 149 of 452
Using
For more information, see User roles in the change request lifecycle (
https://docs.bmc.com/docs/display/change81/User+roles+in+the+change+request+lifecycle).
You receive notification of assigned tasks by BMC Remedy Alert, email, and so on. You can also use the Overview
Console or the Change Management Console to view all tasks assigned to you. The table list includes a column
that shows the assignee of the task. Tasks are identified by the TAS prefix. To access the Change Management
console, the task implementer must have Infrastructure Change Master, Infrastructure Change User,
Infrastructure Change Submit, or (at a minimum) Infrastructure Change Viewer permissions.
Note
Tasks do not support functional roles; they have their own permission model. BMC Change Management
maps its groups into the relevant task computed groups for access. For this reason, users with
Infrastructure Change Viewer permission cannot update the task assigned to them from the parent
change request. To work on a task with Infrastructure Change Viewer permission, you must also be
assigned a functional role (for example, Infrastructure Change Coordinator) and you must open the task
from the Change Management console.
5.6.4 Implement stage - Working with tasks

In the Implement stage of the request, the change coordinator (or change manager) reviews all the tasks that are
needed to complete the change request. Generally, change requests are divided into smaller units, called tasks.
They are then assigned to task implementers who complete the tasks. When you plan a change request,
determine whether you can divide it into separate tasks.
Note
For more information on task implementers, see Working with BMC Change Management as a task
implementer (see page 299).
If you create a change request and then do not save it before you close it, the tasks you created do not
exist because there is no parent change request.
The Tasks tab shows the tasks that must be performed to complete the change. You can use task groups to
manage changes with many tasks, each having its own schedule, task implementer, and plan. For less complex
changes, tasks are optional. A single change can have an any number of tasks.
Creating and assigning tasks
Page 150 of 452
Using
After a task is assigned to a support group or an individual, the assignee receives notifications to perform the
various task activities based on the change process.
Note
For less complex changes, tasks are optional. If no tasks are created, the change is assigned to a Change
Implementer. The Change Implementer field is applicable only when using the Classic view.
5.7 Closed stage - Completing change requests

Page 151 of 452
Using
In the Closed stage of the change request's lifecycle, the change manager reviews all the implemented changes
to make sure that each objective was met. A request cannot be closed until all tasks are closed. When all the tasks
related to a request are closed due to success, cancellation, or failure, the requester and the change manager are
notified that the change is resolved.
Note
Change requests can be closed by users with the functional role of a Change Manager or Change
Coordinator.
In this final stage, the process of closing the change request varies based on whether the request requires Close
Down approval:
If no approval is required, the requester can set the request to Closed after confirming that the request was
resolved to his or her satisfaction. If the requester does not close the change request within the allowed
response time of it being resolved, the request is closed automatically after a specified period of time. The
Status Reason for the request indicates that the request was automatically closed.
The allowed response time depends on how the application administrator configured the BMC Remedy
Change Management application. The default is 10 days. If the requester is not satisfied with the change
request, the requester can reopen it. The change manager is notified that the request is reopened, and
must respond.
If the request requires Close Down approval, the change request moves to the Completed status with the
status reason Final Review Pending. The approvers approve it and moves the change to the status Final
Review Completed. When moved to the next stage, the change request is set to status Closed with a status
reason of Successful. After IT and the business unit (BU) have completed the review, no further activities
are performed on this request.
Closing change requests
Page 152 of 452
Using
To reach Closed status, you must enter actual start and end dates. You must also enter a performance rating from
1 (the worst rating) to 5 (the best rating) for the entire change process. You should consider all aspects of the
change request's performance. This includes looking at how the change manager performed, how well things
went with this operational Category Type and Item (CTI), and any other risk factors. The performance rating
stored on the request is then used, in combination with previous historical ratings, to compute an overall
performance for each of the risk factors.The performance history of a change manager becomes more
meaningful as more changes are accomplished. The performance rating is an average of the performance of the
assigned manager or the chosen operational CTI. This in turn helps a more accurate risk assessment to be
performed on new requests.
Note
Page 153 of 452
Using
Performance ratings for requests are not rolled into the average performance until the request is Closed.
A request in Completed status does not have the performance rating averaged into the overall rating yet.
When a change request fixes a known error, the owner of the known error is notified, so that its status can be
updated.
5.7.1 Closing a change request

This topic describes how to close a change request.
Note
After a change request is closed, it cannot be reopened.
Additionally, after the change is closed, users with Change Master permissions can update information
within the change record. They cannot, however, update the following fields:
Class
Status
Any date fields
They also cannot add new tasks or ad hoc approvers.
To close change requests

2. Use the Process Flow Status bar to move the request forward to Completed status. The Change Closure
dialog box appears.
3. Click the Dates tab.
4. Review the Completed Date information. This field is automatically set to the current date and time when
the status of the request is set to Completed.
5. Enter the Actual Start Date and Actual End Date of the request.
6. Enter the In Production Date information. Use this field to specify the date and time at which the request
was taken into production.
7. Click the Categorization tab (Best Practice view) or Classification tab (Classic view).
8. In the Performance Rating field, rate the work done by support staff or the manager in completing the
request. This performance value is a combined consideration of all derived factors on a request, ranging
from 1 (the lowest rating) to 5 (the highest rating).
9. Add the status reason and work information.
10. Click Save.
Page 154 of 452
Using
5.8 Monitoring the progress of a change request

As the change request is being planned, you can follow its progress by viewing the Work Info details. For example,
during its Implementation stage, you can follow the progress of the tasks in the request as they are being
completed.
To view the progress of a change request when using the Best Practice view (see page 155)
To view the progress of a change request when using the Classic view (see page 156)
5.8.1 To view the progress of a change request when using the Best
Practice view
1. Open the change request. The Change form provides information about the status, potential risks, and
whether it is escalated.
The left frame of the change form displays the details about who is assigned to the change request as the
change coordinator.
2. View progress details of the change request by clicking the appropriate tab:
Tab
Description
Work Detail
View information about each step in the process in the work information history area.
View who is assigned to the change request as change manager.
Review the current stage in the approval process for the change request, including the next approval phase.
Note: The Work Detail tab is displayed when you open the Change form.
Tasks
View the progress of the tasks associated with the change request.
Relationships
View all the related change requests, dependent change requests, related CIs, and so on.
Date/System
View the dates related to the change, time spent on the change and details of the change submitter.
SLM
Review the agreed-upon service targets for the request. This tab is visible only if the BMC Service Level Management
application is installed.
3. View additional details by clicking the appropriate links:

Link
Description
Quick Action >

Requested For
View for whom the change request was created. When the change request was created, the change request was
automatically assigned to the appropriate support staff group or person.
Links >
Categorization
View the timing of the change request and its categorizations.
Links > Financials
View information relating to cost types, total costs, and the total costs in a specific currency.
4. Close the Change form.
Page 155 of 452
Using
5.8.2 To view the progress of a change request when using the Classic view
1. Open the change request. The Change form provides information about the status, potential risks, and
whether it is escalated.
2. View progress details of the change request by clicking the appropriate tab:
Tab
Description
Requester
View for whom the change was requested and who is assigned to the request. When the change request was created, it was
Classification
View the timing of the change request and its categorizations.
Work Info
Tasks
View the progress of the tasks associated with the change request.
Assignments
View who is assigned to the change request as change manager, change coordinator, or change implementer.
Relationships
View all the related change requests, dependent change requests, related CIs, and so on.
Approvers
Review the current stage in the approval process for the change request, including the next approval phase.
SLM
Financials
Dates
View the planned dates.
3. Close the Change form.
5.8.3 Monitoring associated tasks

As change manager or change coordinator, you must keep track of the change request to which you have been
assigned. This includes monitoring tasks associated with the change request.
To view a task associated with a change request

3. All the tasks for that change request are listed.
4. To view details about a task, select the task in the list and click View.
5. In the work history on the Work Info tab of the Task form, you can view information about each step in the
process. You can also view work information for each task in the Work Info of the Selected Task table on
the Change form.
6. If you modified the task, click Save.
Page 156 of 452
Using
5.8.4 Viewing and updating affected areas

The Impacted Areas dialog box shows which companies, sites, and organizations are affected by the change. By
default, the information entered in the Change Location on the Requester tab is automatically entered as one of
the Impacted Areas. Use the Impacted Areas dialog box to define approvals for the change request.
Note
Impacted Areas, which automatically defaults to the change location, must be specified to generate
automatic approval requests.
To view or add affected areas

1. Open a change request.
2. Do one of the following:
From the left navigation pane, choose Links > Impacted Areas.
From the left navigation pane, choose Advanced > Impacted Areas.
3. To add a new impacted area, on the Impacted Areas dialog box, complete the required fields and enter any
other information, as needed.
4. Click Add.
You can add as many impacted areas as necessary for a particular change.
5. To delete an impacted areas that you have previously chosen, select it from the table and click Delete.
6. Click Close.
The additional impacted areas are added to the change request.
5.8.5 Viewing the audit log

Viewing audit logs enables you to view field and notification audits against the request. When certain fields are
changed, when the status is changed, or when system notifications are sent, an audit entry is generated to track
the modification. The Login ID of the individual making the change appears next to the audit entry.
Note
The View Audit Log function is not available until you create and display the request.
To filter the information shown, you can select the Audit Type to view (for example, All, Change Coordinator, or
Priority).
Page 157 of 452
Using
To view audit logs

1. Open the change request, from which to view the log.
From the left navigation pane, choose Links > View Audit Log.
From the left navigation pane, choose Functions > View Audit Log.
3. (Optional) Use the Audit Type list to filter out audit log entries.
4. Click the Notification Audit tab to view notification audit entries against the request.
The audit trail displays all the notifications that were generated.
5. Select a notification audit entry, and then click View.
5.8.6 Tracking efforts for a change request

When working with assignments, you can record time spent on a change request. The Track Effort log shows a
list of all individuals who worked on the change during its life cycle.
Note
Entries in the effort log are not system-generated, so you must enter them manually. The list is not in
chronological order.
Page 158 of 452
Using
To track efforts
2. On the Date/System tab, click Update Effort Log.
3. Fill in the Select an Assignee fields.
This information is required to select the individual for whom the effort log is being generated.
4. Fill in the Select Effort Classification fields.
Select an Assessment Type, Phase, and Area. This information is required to show what kind of effort is
being logged, for example, implementation activity.
5. Click Add, and then click Close.
6. Fill in the Enter Effort Time Spent fields.
Enter the number of hours and minutes you worked on the change. This information records where the
time was spent.
Note
As needed, you can adjust the time spent in the Update Assignee Effort Duration section. For
information, see Responding to task reassignments as a change coordinator (see page 281).
Managing the effort log

In addition to creating a track effort log entry, you can modify or delete an effort log. You can also update the
assignee effort duration in the effort log.
Note
You must be the change manager or the change coordinator to modify the effort time.
To modify the effort log

1. From the change request, choose Functions > Track Effort.
2. To delete the effort log, select an entry and click delete.
3. To update assignee effort duration, select the entry and enter the time spent in hours or minutes.
4. To modify the effort log, select a record from the table and click View.
5. Update any of the assessment type information and the time spent.
6. Click Save.
Page 159 of 452
Using
5.8.7 Tracking the time spent working on change requests

You can track the time spent working on a change request after it has been fully assigned. The Support Company,
Support Organization, Support Group, and Change Coordinator must be set before you can use the Start Clock
and Stop Clock buttons.
There are three ways to track the time spent working on a request:
Method
Description
Use the Start Clock and
Time is calculated based on when you click the Start Clock and Stop Clock buttons. For instructions, see To track the time
Stop Clock buttons
spent on a change request using the Start Clock and Stop Clock buttons (see page 160).
Manually enter in the
You can enter the time directly into the Time Spent field. For instructions, see To manually track the time spent on a
time
change request (see page 160).
Create an effort log
With the Update Assignment Log button, you can create an entry in the effort log. For instructions, see Tracking efforts
for a change request (see page 158).
To track the time spent on a change request using the Start Clock and Stop Clock
buttons
1. Open the change request and do one of the following:
2. Click Start Clock.

The current date and time are appear in the read-only Start Time field.
3. To close the Change form while working on the request, make sure to save the request first.
4. To stop tracking the time, click the Stop Clock button. You must repeat steps 1 and 2 first if you closed the
Change form.
5. Update the assignment log, as needed, and then click Save.
You can use the start and stop clock buttons as many times as you like. Each successive time, the new time
is added to the value already in the Total Time Spent field.
To manually track the time spent on a change request

1. Open the change request and do one of the following:
2. In the editable Time Spent field, enter the number of minutes.

3. Enter information in the effort log, using the Update Assignment Log button, and then click Save.
The time you entered is added to the value in the Total Time Spent field.
Page 160 of 452
Using
5.9 Copying change requests

The Copy Change function is available on the Change form only when it is in Modify mode. This function enables
you to copy a request into a new change request. When using the copy function, you have options to include
different sections of the original change request, for example, Requested For Customer, Impacted Areas,
CI/Component Relationships, Related Changes, or Work Info with attachments.
The following fields are filled with information from the change from which you are copying: Summary, Change
Type, Class, Timing Reason, Impact, Urgency, Priority, Risk Level, Lead Time, Environment, Reason For Change,
and Notes. You can change the information in these fields to reflect the new change. You are also presented with
different sections of the change that you can copy.
Note
Users with Change viewer and Change submitter permissions cannot copy a change request.
5.9.1 To copy a change request

1. From the left navigation pane on the Change form, choose Functions > Copy Change.
2. On the Copy Infrastructure Change dialog box, click the sections to include in the new request.
Depending on the options that you select, the following information is copied to the new change request:
Option
Copied information
Copy Requested
For Customer
All information from the Requested For dialog.
Copy Impacted
Areas
All the impacted areas information that is displayed in the Impacted Areas dialog is copied. For more information see,
Viewing and updating affected areas (see page 157).
Copy
CI/Component
Relationships
All CIs or Components from the Relationship tab.
Copy Tasks
You will be prompted to enter additional information. For more details, see Copying tasks from another change
request (see page 162).
Copy Related
Changes
All related change requests. Related Infrastructure Change Requests with a Dependent relationship type will be
converted to Related To relationships.
To keep the dependent relationship, in the Relationship tab, search for the dependent change request, make a new
dependent relationship and delete the Related To relationship that were copied.
Copy Work Info

(with attachments)
All Work Info, including attachments.
Page 161 of 452
Using
Note
Task Phase settings of the original change is also copied to the new change.
3. Make any modifications to the new request you are creating (for example, changing its priority or timing).
4. Click Start Copy.
The copy function can take several minutes to process.
After the change is copied, the Change form opens in New mode with the newly copied change
information in a Draft status. You now can modify and submit the new request.
5. Save the new copy of the request.
Note
A copied change request is not automatically submitted.
5.9.2 Copying tasks from another change request

The Copy Change function enables you to copy a request into a new change request. When using the copy
function, you have the option to copy the tasks associated with the original change request.
change-rules_62667_516.gif
To copy tasks from another change request

1. From the left navigation pane on the Change form, choose Functions > Copy Change.
2. On the Copy Infrastructure Change dialog box, select Copy Tasks.
3. On the Copy Tasks dialog box, you can select the tasks that you want to exclude from copying. You can
select the tasks either by status (Cancelled, and Failed) or by type (Manual, and Automatic).
4. Select the related task information that you want to copy, and then click OK.
5. Depending on the options that you select, the following information is copied to the new change request:
Option
Copied information
Location Information with

Attachments
The following information from the General tab related to Task Location and the Task Attachments,
except Command field:
Company
Region
Site Group
Site
Address
All related attachments
Requester Information
The following information from the Requester tab:
Page 162 of 452
Using
Option
Copied information
Requester Company
First Name
Middle Name
Last Name
Phone Number
Organization
Department
Support Organization
Support Group Name
Work Info with Attachments
All information on the Work Info tab including any attachments
Relationships
All information from the Relationships tab
Dates
The following information from the Dates tab is copied:

Schedule start date
Schedule end date
Financials
The following information from the Financials tab:

Calculation Unit type
Budget Estimated Total Time
6. (optional) Enter values in the following fields under Tasks Details to be overwritten in all copied Tasks:
a. Specify a value in the Summary field.
If you specify a summary value, the Summary field of all the new copied tasks uses this value.
Otherwise, the Summary field of all the new copied tasks uses the values of the source tasks.
b. Select the Priority of the task.
c. You can enter notes in the Notes field.
7. Click Start Copy.
Note
It can take several minutes for the copy process to be completed.
All tasks and child tasks related to that task are copied. After the change is copied, the Change form opens
in New mode with the newly copied change information in a Draft status. Any tasks that are copied are in
Staged status. You now can modify and submit the new request.
8. Save the new copy of the request.
Note
A copied change request is not automatically submitted.
5.10 Working with related change requests

Page 163 of 452
Using
This section describes the following topics:

Assigning sequence numbers to dependent change requests (see page 164)
Creating related change requests (see page 165)
Relating change requests (see page 166)
Removing a related change request (see page 166)
Viewing change dependencies (see page 166)
5.10.1 Assigning sequence numbers to dependent change requests

When you create change requests with relationship as dependent, you should specify the sequence in which
change requests are to be completed. When you specify a sequence for the dependent change requests, you
must complete a change request with the sequence number 0 before you can start a change request with the
sequence number 1.
In the following example, you have two related change requests-the change request to update the I/O device
software has Dependent relationships to two other change requests.
Note
You cannot assign sequence numbers to release requests. To add sequence numbers to tasks, see
Assigning a sequence number to task groups and tasks (see page 164).
To define a dependent change request

1. Open the change request to upgrade the operating system, and then click the Relationships tab.
2. Select the Dependent change request from the Relationships table.
The default sequence number for the dependent change request is 0.
3. Click View.
4. In the dependent change request, do one of the following:
Click the Relationships tab.
Click the Classification tab.
5. In the Sequence field, enter a number (for example, 1).

The sequence number indicates the order in which the dependent change request must be completed
relative to the original change request.
6. If necessary, add any additional information about the Change form to finish relating the change request.
7. Save your work, and then close the change request.
You return to the original change request.
8. To view the updated sequence number, refresh the table.
The record now shows a sequence of 1. The sequence number indicates the order in which you must
Page 164 of 452
8.
Using
complete the current request relative to the dependent request. In this example, you must now complete
the change request (sequence 1) to remove the old software before you can start work on installing the
new software (sequence 2).
Related change requests with sequence numbers (Classic view)
5.10.2 Creating related change requests

When you work with a change or release, you might need to define a related change request. For example, you
might need to define related change requests that address similar problems. A set of related change requests can
result from many changes needed by one requester at the same time.
For a release request, a related change is a manifest included within the release. For information on creating a
change request related to a release request, see Creating a manifest (see page 200).
To define a change request related to another change request, with no dependency

1. Open the change request, and then click the Relationships tab.
2. Select the entry from the Relationships table.
3. From the Quick Actions list, select Create Related Request > Infrastructure Change.
In the Change form, fill in the details on the Change form as described in Initiate stage - Creating change
requests (see page 81).
4.
Page 165 of 452
Using
4. Click Save.
5. Return to the original change request using the breadcrumb bar.
6. Save the original change request.
5.10.3 Relating change requests

When you work with a change request, you might also need to relate a change request to it. Relating change
requests enables the support staff to work with multiple change requests for the same requester at once. With
related change requests, you can optionally designate if the current change request exists in a dependent
relationship to a change request.
To relate a change request to another change request

3. In the Request Type field, select Infrastructure Change, and then click Search.
4. In the Change Relationship Search form, use the various tabs to choose the appropriate search criteria.
5. To use more specific search criteria, click the Advanced Search tab, enter the appropriate search criteria,
and then click Search.
6. In the Change Results table, select the item to relate.
7. In the Relationship Type field, select how to relate the current request to the selected change request.
Related To indicates the two changes are related to each other.
Dependent indicates the current change request depends on the original change. Dependent
changes can be assigned sequence numbers to specify the sequence in which the dependent
change requests should be completed. For more information about dependencies, see the next
procedure, Assigning sequence numbers to dependent change requests (see page 164).
8. Click Relate, and then click OK.
If you create a Dependent relationship, the sequence appears in the Relationships table.
5.10.4 Removing a related change request

This procedure removes the change request from the relationship with another change request. It does not
delete any change requests.
To remove a related change request

1. Open the change request in the Change form, and then click the Relationships tab.
2. Select the request to unrelate, and then click the Remove icon.
5.10.5 Viewing change dependencies

Page 166 of 452
Using
1. Open the change request in the Change form, and then click the Relationships tab.
2. In the Show Related field, select Infrastructure Change.
A list of change requests appears in the table. Changes with a dependent relationship to the current
request are shown as Dependent under the Relationship Type column. The table shows the status of each
request and enables you to monitor the progress of the change request implementation.
3. To view a request, select it, and then click View.
5.11 Working with change request assignments

When BMC Change Management was being configured, the application administrator determined to whom the
change request is to be assigned based on a combination of field values, such as the change location, operational
categorization, and product categorization. Changes can be assigned to an individual or a support group. For
example, all change requests that are categorized as hardware issues might be assigned to the IT Support
Hardware group.
There are different roles within the assignment process-the change manager and change coordinator. The classic
view has an additional change implementer role. The change manager typically oversees the overall change
process, but the change coordinator plans and coordinates the efforts.
Note
This section focuses on change assignment from the perspective of the change coordinator. But there is
potentially a great deal of overlap in responsibility between the change manager and the change
coordinator.
Responsibilities for change coordinators include both assigning and accepting change requests. You must make
sure that the assignment is correct and accept the change request. If you cannot accept or resolve an assigned
change request, you or your manager can reassign the change request to another change coordinator. If the
change request was categorized incorrectly, you can also reassign it. (For information, see Reassigning change
requests (see page 172).)
Change requests can be assigned manually or automatically. If an assignment definition has not been done for
BMC Change Management, you must assign the change manually. (For information, see Automatically assigning
changes (see page 168).)
BMC Change Management can automatically assign change requests when they are defined. The assignment is
based on the change request's categorization. You can view information about who is assigned to the change
request on the Infrastructure Change form. Where you look for this information depends on whether you are
using the Best Practice view or the Classic view.
Page 167 of 452
Using
Best Practice view
Classic view
You can view the Change Coordinator and Change Manager directly
You view the Change Coordinator, Change Manager, and Change
from the Infrastructure Change form.
Implementer assignments from the Assignment tab.
Note
Before you can make any assignments to a Change Manager support group, you must define at least one
individual with the Infrastructure Change Manager functional role.
The application administrator configures to whom the change requests are assigned. Assignment is configured
based on criteria such as the change request's categorization. For example, all change requests that are
categorized as hardware issues might be assigned to the Support-Hardware group. All change requests that are
categorized as software upgrades and originate from California might be assigned to Sonya Software in Santa
Clara. The criteria of the change request together with the application administrator's configuration determines
to whom each change request is assigned.
5.11.1 Automatically assigning changes

You can automatically assign a change by using the Auto Assign option, as follows:
In the Work Detail tab, click the auto assign icon of the
Manager Group field.
In the Assignment tab, select the option from the Set Assignment using or Set
Implementer using menu.
Assigning the change coordinator using Auto Assign uses the requester's information, the Change Location
information, and the Operational and Product Categorization information about the form to determine an
assignment match.
These assignments are based on routing information stored in the CFG:Assignment form. The CFG:Assignment
form assigns the groups and then Auto Assign assigns the individual. For more information, see the Working with
auto-assignment (https://docs.bmc.com/docs/display/itsm80/Working+with+auto-assignment).
5.11.2 Receiving notifications of change request assignments

Change coordinators are notified of new change requests, based on their notification method preferences
defined in their personal record.
Individual Notification An individual change coordinator is notified according to the notification method
specified in their personal record.
For example, if Bob Backline has a notification method of BMC Remedy Alert, he receives a notification
from BMC Remedy Alert for each change request that is assigned to him.
Page 168 of 452
Using
Group Notification A change manager group is notified according to the notification method specified
by each group member's entry in their personal record.
For example, if a change request is assigned to the Support-Software group, each group member is
notified through the notification method specified in their personal record. If Sarah Software has Email
specified as the notification method in her personal record, the notification is sent to her by email. If Bob
Backline has BMC Remedy Alert specified, he is notified accordingly.
For more information, see Change notifications (see page 429).
To receive notification of change assignment by BMC Remedy Alert

1. Log in to BMC Remedy Alert. You must have support staff member permissions.
When you or your group receives a notification that you or your group has been assigned to a change
request, the information appears in the BMC Remedy Alert window.
2. To evaluate a change, select a change request in the BMC Remedy Alert window.
3. Choose Alerts > Details.
The change request appears in the Change form. For more information, see Setting application preferences
(https://docs.bmc.com/docs/display/change81/Setting+application+preferences).
5.11.3 Viewing assigned changes

When the system notifies you that a change request was assigned to you or to one of your groups, you can view
the request from the Changes table on the Change Management console. You can also view all unassigned
change requests.
Select the appropriate option in the Change Management Console based on changes you want to view:
Function
Action
View changes
assigned to you
1. In the Filter By field, choose Defined Searches > By Role > Change Coordinator > All Changes.
2. In the Show field, select Assigned To Me. All changes that are assigned to you are displayed in the Assigned Change
table.
3. Click a change request in the table. The assigned group and other important information is displayed in the Change
Details and Tasks section.
Note: To view the complete assignment information, open the change request. In the Best Practice view, assignment
details are displayed on the Change form. In the classic view, click the Work Detail tab.
View changes
assigned to your
groups
View all changes
assigned to your
group
1. In the Show field, select Assigned to My Selected Groups.

2. Select a group, and then click OK.
In the Show field, select Assigned to All My Groups. All changes that are assigned to you are displayed in the Assigned
Change table.
Page 169 of 452
Using
5.11.4 Assigning change requests

The Assignment tab displays the details of the current assignment. A change must be assigned to a change
coordinator or a Change Management support group. However, the change manager is typically responsible for
the overall change process.
To assign change requests using the Classic view

2. Click the Assignment tab.
Certain fields are automatically filled based on the default configuration and requester information in the
change request. For example, the Change Manager field already has an assignment.
3. To assign a change coordinator, use one of the following options from the Set Assignment Using field, and
then click Set:
My Default Group Assigns the change to you and your default group
My Group List Opens a list of all groups to which you belong. Select the appropriate group from
this list.
Favorite Groups Assigns the change to the typical groups to which your support group assigns
requests
Auto Assign Automatically assigns the request based on predefined mapping. Use this option if no
change coordinator is assigned to the request.
Change Manager When the Change Manager and the Change Coordinator are the same group or
person.
A user must have the Infrastructure Change Coordinator or Infrastructure Change Manager
functional role to be a Change Coordinator. Groups that do not have a user with one of these
functional roles are not available for selection in the Change Coordinator fields.
The change manager and the change coordinator are automatically notified of their assignments.
To assign change requests using the Best Practice view

change request. For example, the Change Manager field already has an assignment.
2. To assign a change coordinator, select the appropriate option:
Coordinator Group Provides a list of coordinator groups. Select the group of the change
coordinator you want to assign the change to.
Groups that have at least one user with the Infrastructure Change Coordinator or Infrastructure
Change Manager functional role are listed for selection.
Change Coordinator Provides a list of users with the functional role of an Infrastructure Change
Coordinator in the selected coordinator group. Select the appropriate change coordinator from this
list.
3.
Page 170 of 452
Using
3. To assign a change manager, select the appropriate option:

Manager Group Provides a list of groups where at least one member has the Infrastructure
Change Manager functional role. Select the Change Manager Group to which you want to assign the
change.
Change Manager Provides a list of users with the functional role of an Infrastructure Change
Manager in the selected Manager Group. Select the appropriate change manager from this list.
Auto Assign Automatically assigns the request based on predefined mapping. Use this option by
clicking the auto-assign icon if no change coordinator is assigned to the request.
The change manager and the change coordinator are automatically notified of their assignments.
5.11.5 Assigning changes to change implementers

You can assign changes to a change implementer. Assignments are similar for a change coordinator, except when
you select Change Coordinator from the Set Implementer using field. Use this option to define the change
coordinator as the change implementer.
Notes
This topic applies only if your are using BMC Change Management in Classic view. The Change
Implementer fields were removed from the Best Practice view, since adding tasks to a change
request is a best practice.
When a change request includes tasks, the Change Implementer fields no longer appear on the
Assignment tab.
If change implementer fields have been set, for example in a change template that was used,
change implementers will be assigned and notified about the change request, but this information
will not be displayed in the Best Practice view.
To assign changes to change implementers using the Classic view

Assigning change implementers (Classic view)
Page 171 of 452
Using
3. To assign a change implementer, use one of the following options in the Set Implementer using field and
then click Set:
My Default Group Assigns the change to you and your default group
this list.
Favorite Groups Assigns the change to the typical groups to which your support group assigns
requests
Auto Assign Automatically assigns the request based on predefined mapping
Change Coordinator Automatically assigns the change to the change coordinator and updates the
change implementer field with the change coordinator
The change implementer is automatically notified of the assignment.
Note
Assignment of a change request to the change implementer is applicable only when the change
request does not have any related tasks. When you add a task to the change request, its
assignment to the change implementer is no longer valid.
5.11.6 Reassigning change requests

You or your manager can reassign the change request to another change coordinator.
For more information on reassigning change requests, see Working with change request assignments (see page
167).
To reassign a change request yourself

2.
Page 172 of 452
Using
2. Use one of the following to select who should be reassigned to the change request.
In the change form select the Coordinator Group and Change Coordinator. On the Work
Detail tab select a Manager Group and Change Manager
On the Assignment tab, select to whom to

assign the change request.
3. Click Save.
The Change Manager or Change Coordinator is notified of the reassigned change request.
5.11.7 Working with reassignment requests

Change managers are responsible for responding to reassignment requests. When a change manager reassigns a
change request to another manager, the person is notified. Upon reviewing the change, the manager can reassign
the change to another qualified change manager.
To respond to reassignment requests

1. Open the Overview console or the Change Management console.
Working with the Overview console (see page 61)
Change Management console functional areas (
https://docs.bmc.com/docs/display/change81/Change+Management+console+functional+areas)
All reassignment requests appear in the table with other change requests. BMC recommends that
you regularly monitor your assigned work to keep track of any change requests reassigned to you.
2. Select the appropriate change request.
3. Click View.
After reviewing the change request, you can manually reassign the change manager or change
coordinator. When using the Classic view, you have an additional option of reassigning it to the change
implementer.
a. To reassign the change request, select the appropriate manager, assignee, or implementer.
b. Select an assignment method (for example, Auto Assign), and then click Set.
5. Click Save.
If you reassign the change request, the new assignee is automatically notified of the changed assignment.
For more information, see Assigning change requests (see page 170).
5.12 Using phases with change requests

BMC Change Management introduced the task management feature that allowed you to complete tasks during
any phase of a change request, not just the Implementation phase as in earlier versions.
Page 173 of 452
Using
For more information, see Task Phase Management (

https://docs.bmc.com/docs/display/change81/Task+Phase+Management).
5.12.1 To use phases with change requests

1. Create or open a change request.
2. Enter the required information.
If Phase Management has been enabled, the Phase field appears on the Change form above the Tasks and
Task Groups table.
4. From the Phase field, choose a phase.
5. Relate an ad hoc task, task template, or task group template to the change request.
6. Assign a task implementer to the task.
After you select a phase and relate your tasks, the Related Templates table shows only tasks included with
that phase.
7. Repeat step 4 through step 6 until you finish all the phases and all the tasks to include in the change
request.
9. Use the Process Flow Status bar to move the change request through the change management lifecycle.
Tasks remain in Staged status until they are ready to be worked on. When you enter a stage in the lifecycle
that includes tasks, the status of those tasks is set to Assigned. The task implementers are then notified (by
email, BMC Remedy Alert, or pager) of tasks assigned to them.
10. Open the tasks defined for the stage and complete them.
Note
If validation of tasks performed in that phase is enabled, you must close any tasks activated for
that phase before you can move the change request to the next stage.
11. Continue to use the Process Flow Status bar to move the change request through its lifecycle until all the
tasks are completed and you reach the Closed stage.
5.12.2 Change task status transitions

1. If the tasks are already assigned to a group or individual, the task status is Assigned when the tasks are
activated. If they are not assigned to a group or individual, the task status is Pending and the task status
reason is Assignment. You must assign the task to a group or individual to move the task status to Assigned.
When a task group is activated, its status changes to Work In Progress while the first task is activated.
2.
Page 174 of 452
Using
2. Tasks in Assigned status can be worked on by the Task Implementer or Assignee. When work on the task
begins, the Task Implementer sets the status of the task to Work In Progress. When the first task's status
changes to Work In Progress from Assigned, the Actual Start Date of the change request is populated with
the current date and time from the workflows.
3. When work on the task is completed, the Task Implementer sets the status of the task to Closed. The
Actual End Date of the change request is populated with the current date and time from the workflows
corresponding to the last task. In the case of task group when all the tasks in the group are closed, the task
group is closed.
If task phase closure is enforced, all tasks of a defined phase must be closed before the change
request can move forward. If any of the tasks are open when the Change Manager or the Change
Coordinator tries to move the request to the next status, the following error is displayed:
This Change Request has at least one open task or task group. Close all
children tasks before setting Change Status to Completed or Closed. (ARERR
45075)
If the task phase closure is not enforced:
All activated tasks can be closed at any stage prior to the Completed status of the change
request as the change request moves forward.
New tasks can be added for any phase at any stage of the change request before the change is
closed.
The first task is activated when the change status is Scheduled.
The change request moves to Completed status if all tasks are completed.
4. When tasks having the same sequence number are closed, the tasks with the next sequence number are
activated.
Note
When a task is created, it is assigned a sequence number that can be updated manually at a later stage.
5.13 Managing CIs

A configuration item (CI) is a physical, logical, or conceptual entity that is part of your IT environment and has
configurable attributes.
Some CI types are virtual, while others are physical and include hardware and software. The Service CI type is an
example of a virtual CI. In this context, a service can be provided from one business or organization within a
business to another. Service CIs can include customer support, employee provisioning, web farms, storage, and
so on.
You can use the information in CIs to diagnose user problems and to determine if a change to a CI or the IT
infrastructure must be made. For example, if a user calls in with a printing problem, you can check the printer's CI
to see whether the printer is down.
Page 175 of 452
Using
To record information against CIs, such as CI unavailability, or to relate an problem investigation to a CI, the CI
must be recorded in the BMC Atrium Configuration Management Database (BMC Atrium CMDB). If you do not
have BMC Asset Management, then BMC Service Desk provides limited ability to manage CIs and inventory.
Note
You can manage configuration items even if your environment does not run BMC Asset Management. To
manage configuration items, including creating and modifying CIs and managing inventory for bulk and
non bulk CI's, you do not need a BMC Asset management license. However, if you are running BMC
Asset Management, then you have access to additional functionality. See the BMC Asset Management
Key concepts (https://docs.bmc.com/docs/display/asset81/Key+concepts) page for more information about
BMC Remedy Asset Management functions.
To make use of this additional functionality, you will need either Asset Admin or User permissions and a
BMC Remedy AR System fixed or floating license.
This section contains the following topics:

Creating CIs (https://docs.bmc.com/docs/display/servicedesk81/Creating+CIs)
Inventory management (https://docs.bmc.com/docs/display/servicedesk81/Inventory+management)
5.13.1 Working with related configuration items

When you work with a change request or a task, you might need to work with related configuration items (CIs).
For example, if you are working on a change request to upgrade memory for a department, you work with the
asset records for the department members, configuration information for desktop systems, and information
about the memory in inventory.
For more information about CIs, see Managing CIs (see page 175).
You can perform the following tasks when working with CIs related to change requests:
View CIs related to a change request (see page 177)
Relate CIs to change requests (see page 176)
Unrelate CIs from change requests (see page 176)
You can also define new CIs to relate to change requests (
https://docs.bmc.com/docs/display/change81/Creating+a+CI).
Relating configuration items to change requests

This topic provide the following instructions:
Page 176 of 452
Using
To relate CIs to change requests (see page 177)

To unrelate CIs from change requests (see page 177)
To relate CIs to change requests

1. Open a change request, and then click the Relationships tab.
2. (Optional) In the Alternate Data Set field, select a dataset to relate with configurations items (CIs).
For more information, see Relating CIs to alternate datasets (see page 273).
Note
The Alternate Data Set field on the Relationships tab defines the dataset that will be used to search
for a CI. For more information about datasets, see Changing datasets (
https://docs.bmc.com/docs/display/asset81/Changing+datasets).
3. From the Request Type field, select Configuration Item, and then click Search.
4. On the CI Relationships Search form, complete the search criteria tabs with the relevant information, and
then click Search.
Matching results appear in the CIs table.
5. In the Relationship Type field, select the type to relate with the change request, for example, Installs.
For more information on relationship types, see CI relationship types (see page 260).
6. Click Relate.
The original change request and the related configuration item appear in the Relationships tab.
Note
When you relate a CI to a change, the CI's Impacted Areas can be automatically copied into the
change's Impacted Areas, based on the Relationship Type. This allows for impact analysis within
the change record and makes sure that Change Approvers can be generated based on any
Impacted Area Approval mappings related to moves, upgrades, impact, or repairs. In the
SYS:Association Types form, administrators can define whether a particular Relationship Type
copies the CI's Impacted Area to the change.
To unrelate CIs from change requests

1. In the Show Related field on the Relationships tab of the Change form, select Configuration Item.
2. Select the configuration item to unrelate, and then click Remove.
Viewing configuration items related to a change request
Page 177 of 452
Using
You can view the configuration information from within BMC Change Management in the Relationships tab of the
Change form.
Select the configuration item from the Show Related list, select the configuration item, and then click View. The
Asset Management Configuration Information form appears, showing details of the configuration.
Note
You cannot define a new configuration item on the Relationships tab. Use the Functions > Manage CIs
on the Change Management console to define new CIs. For more information, see Creating a CI (
https://docs.bmc.com/docs/display/change81/Creating+a+CI).
5.13.2 Searching for CIs from the Change Management console

Use the following procedure to search for configuration items (CI) records from the Change Management
console. Use this procedure any time you need to open a CI record to see details about it, or to modify it.
To search for CIs from the Change Management console

1. From the Navigation pane of the console, choose Functions > Manage CIs.
2. From the CI Type list on the Manage CI Information window, select the type of CI and click Search.
3. On the search form provide information about the CI and click Search. Click Search without entering any
information in the form to search for all available CIs.
4. Select the CI from the search results displayed on the top of the page. Details of the selected CI are
displayed in the CI form.
5.13.3 Creating a CI
To create a configuration item (CI), you must have Asset Admin permission. If you have Asset User permission and
you are modifying a CI, your administrator must open the appropriate CI, and then relate your support group to
the CI.
There are many different types of CIs that you can create. While the general procedure for creating each CI type
is similar, only the specific fields on the CI form change depending on the CI type.
This topic provides several examples of how to create CIs:
To create a business service (see page 179)
To create a computer system CI (see page 180)
To create a bulk inventory CI (see page 182)
To create an inventory location CI (see page 182)
Page 178 of 452
Using
To create a business service

Steps 1 (see page ) through 5 (see page ) describe how to create the service CI. Steps 6 (see page
) through 14 (see page ) describe how to relate the service CI to a company. This is necessary to
ensure the service CI appears in the Service field menu on the Categorization tab (Best Practice view) or
the Classification tab (Classic view), when relating the incident request to a company.
1. From the Navigation pane of the Change Management console, choose Functions > Manage CIs.
2. From the CI Type list, select Logical Entity > Business Service and then click Create.
3. On the Business System form, type the CI name and description.
Recommendation
When creating a CI name, follow a consistent naming convention. According to ITIL guidelines,
identifiers should be short but meaningful. For example, Payroll or Network. The name can be
followed by a numeric code, such as NETWORK100.
4. Complete the optional fields that appear on the form in a way that is appropriate for the service you are
creating.
Optional fields when creating a Service CI
Field name
Description
CI ID
A customer specified identifier. You can use this to augment the CI Name.
Company
The company that owns the service
Impact, Urgency, and Priority
Used to determine service levels when assigning support
Supported
Indicates whether the service currently is supported
System Role
A description of the role the service fulfills in the organization
Additional Information
A place to record any additional information about the service
Users Affected
The number of users who use this service
5. Click Save.
Note
Depending on how your application is configured, after you click Save to create a Service
CI, the Service CI form might be redisplayed in a Modify window.
Page 179 of 452
Using
The People tab referred to in the following procedure does not appear on the Business
Service form until you create and save the CI. The Relationships tab, Outage tab, and
Impact tab also appear after you save the new CI. If the People tab does not appear after
you click Save, then search for and open the CI record as described in To search for CIs
from the console (see page ), and then continue with 6 (see page ).
6. Open the People tab and click Add.

7. From the Type list select People Organization and then click OK.
8. From the Company list in the Organization Search window, select the company to which you are relating
the service and then click Search.
Note
If you are relating the service to the entire company, then skip 9 (see page ).
9. If you need to relate the service either to an organization within the company or to a department within
the organization, select the organization and, if necessary, the department from the Organization and
Department lists.
Organization If you choose Organization, the service is related to the specified organization
within the specified company.
Department If you choose Department, the service is related to the specified department within
the specified organization.
10. From the Choose a Relationship Level list, select how much of the company will be related to this service.
For example, if you are relating the service to the entire company, then select Company. If you specified
department in the preceding step, then select Department, and so on.
11. Click Select.
12. From the Role list in the Asset Person Role window, select Used By and click OK.
13. Click OK to dismiss the confirmation note.
14. Click Save and then click Close.
To create a computer system CI

2. From the CI Type list of the CI Type dialog box, select System > Computer System.
3. Click Create.
4. In the CI Name field of the Computer System form, type a name for the CI.
Recommendation
Page 180 of 452
Using
When creating a CI name, follow a consistent naming convention. According to ITIL guidelines,
identifiers should be short but meaningful, and for hardware they should not based on supplier
device names. For example, the name can include an indicator of the CI's function (such as
Workstation or Monitor) followed by a numeric code, such as MONITOR100.
5. In the CI ID field, type a unique alphanumeric value for the CI.

6. Select the company to which this CI belongs.
7. From the Primary Capability and Capability lists, select the roles this CI performs in your company's
topology.
8. Select a status from the Status list.
The default value is Ordered. You can select one of the following options.
Computer system CI status options
Status
Description
Ordered
The CI was ordered from the supplier.
Received
The CI was received in shipping.
Being
Assembled
The CI is being assembled.
Deployed
The CI was installed.
In Repair
The CI is down for maintenance.
Down
The CI is down, but not yet in maintenance.
End of Life
The CI is no longer being deployed.
Transferred
The CI was transferred to another place.
Delete
The CI is marked for deletion. You must be a member of the APP-Management or APP-Administrator group to mark a CI
for deletion.
In Inventory
The CI is in inventory but not yet deployed. When you select this status, you are prompted to select the inventory place.
On Loan
The CI is on loan to another location.
Disposed
The CI is no longer available and was disposed of.
Reserved
The CI was reserved and taken out of inventory.
Return to
Vendor
The CI must be returned to the vendor as damaged or unwanted.
9. Specify whether the CI is supported by selecting Yes or No from the Supported list.
10. Select what impact or urgency this CI will have if it goes down.
11. In the Users Affected field, specify the number of people who use this CI or are affected if it goes down.
12. Complete the other fields in this area.
Field name
Description
Tag Number
The CI tag number. This is the number usually placed on the product by a member of your IT department to track the CI.
Page 181 of 452
12.
Using
Field name
Description
Serial Number
The CI serial number
Part Number
The CI part number
System Role
The role this CI plays in your company
Status Reason
The reason this CI has the status it does
13. Click the General tab.

14. Categorize your CI using the lists and fields in the Product Categorization area.
15. Specify the place of the CI using the lists and fields in the Location area.
16. Enter the dates of the CI in the lifecycle area.
17. Click the Specifications tab.
18. Add more information about the CI.
19. Click Save.
To create a bulk inventory CI

Note
Bulk inventory items are not tracked by an separate record for each item. Instead, bulk items are tracked
by quantities of an item type. For example, cables used to connect desktop computers to the network do
not require individual records but rather, one record for a bulk quantity of the specific cable type.
2. From the CI Type list of the Manage CI Information dialog box, select Bulk Inventory > Bulk Inventory, and
click Create.
3. In the Bulk Inventory form, complete the following required fields:
Field name
Description
CI Name
Enter the name of the bulk inventory item, for example, Microsoft Windows XP.
Tier 1, Tier 2, and Tier 3
Categorize the item.
Received Quantity
Enter the number of items received.
4. Click Save.
To create an inventory location CI

Note
You can use inventory location CIs to indicate where bulk inventory and other CIs are located.
Page 182 of 452
Using
2. From the Type list of the Manage CI Information dialog box, select System > Inventory Location, and click
Create.
3. In the CI Name field of the Inventory Location form, enter the location name.
4. Complete the optional fields.
5. Click Save.
5.13.4 Managing inventory

You can use the Manage Inventory function to track bulk inventory items and other CIs that are available for
deployment.
Before you can track inventory, you must:
Create bulk inventory CIs, or other CIs to be tracked as inventory. For information about how to do this,
see To create a bulk inventory CI (
https://docs.bmc.com/docs/display/change81/Creating+a+CI#CreatingaCI-procedure134) or To create a computer
system CI (https://docs.bmc.com/docs/display/change81/Creating+a+CI#CreatingaCI-procedure64).
Create inventory location CIs. For information about how to do this, see To create an inventory location CI
(https://docs.bmc.com/docs/display/change81/Creating+a+CI#CreatingaCI-procedure150).
For bulk inventory, specify the received quantity and the inventory locations. For information about how to
do this, see To place bulk CIs in inventory (see page ).
For non-bulk inventory CIs, set the inventory status to In Inventory, and select a location. For information
about how to do this, see To place non-bulk CIs in inventory (see page ).
This section provides the following information about managing inventory:
Managing inventory tasks (see page 183)
Placing non-bulk CIs in inventory (see page 185)
Placing bulk CIs in inventory (see page 186)
Managing inventory locations (see page 186)
Managing inventory tasks

This section describes how to perform inventory management tasks that you most commonly use.
To search for CIs from the console (see page 184)
To view inventory locations (see page 184)
To relocate CIs (see page 184)
To reserve and use inventory (see page 184)
Page 183 of 452
Using
To search for CIs from the console

2. From the CI Type list on the Manage CI Information window, select the type of CI and click Search.
3. On the search form provide information about the CI and click Search. Click Search without entering any
information in the form to search for all available CIs.
4. Select the CI from the search results displayed on the top of the page. Details of the selected CI are
displayed in the CI form.
To view inventory locations

1. From the Navigation pane of console, choose Functions > Manage Inventory.
2. Enter your search criteria in the Manage Inventory dialog box, and click Search.
Results matching your search criteria appear in the table.
3. Select a CI or bulk inventory item from the table, and click View Location.
4. View the CIs in the inventory listed in the Inventory Location form.
5. Click Close.
To relocate CIs
1. From the Navigation pane of the console, choose Functions > Manage Inventory.
2. Search for inventory in the current location using the Manage Inventory dialog box.
3. Select the CI or bulk inventory item you want to relocate, and click Relocate CIs.
4. For the location where you want to relocate the CI, specify search criteria, and click Search in the Search
Inventory Locations dialog box.
5. Select the location where you want to relocate your CI.
6. In the Quantity field, enter the number of CIs you want to relocate.
7. Click Relocate.
To reserve and use inventory

1. From the Navigation pane of console, choose Functions > Manage Inventory.
2. From the CI Type menu in the Manage Inventory dialog box, select the CI or bulk inventory item you want
to reserve and use.
3. Click Search.
4. Click in the Transaction Qty column and enter the number of assets or bulk inventory items you want to
use.
Manage Inventory dialog box with transaction quantity
Page 184 of 452
Using
5. Click Reserve/Use Inventory.

The number of CIs or bulk inventory items in the Qty in Stock column is reduced by the number reserved
and used.
Placing non-bulk CIs in inventory

You can place non-bulk CIs that you want to manage in inventory by changing the status of the CI to In
Inventory, and then designating a location for that CI.
To place non-bulk CIs in inventory

1. Open a bulk CI, as described in To search for CIs from the console (see page ).
2. From the Status list, select In Inventory.
3. Click OK in the confirmation message that appears.
4. In the Search Inventory Locations dialog box, from the Location list, select a location, make sure other
values are correct, and click Search.
5. Select a location and click Return.
Page 185 of 452
Using
Placing bulk CIs in inventory

To place bulk CIs in inventory, you must specify the location or locations for them.
Tip
If you do not see a location, make sure that the CI has a CI type of inventory location, and not physical
location. For information about creating inventory locations, see To create an inventory location CI (
https://docs.bmc.com/docs/display/change81/Creating+a+CI#CreatingaCI-procedure150).
To place bulk CIs in inventory

1. Open a bulk CI, as described in To search for CIs from the console (see page ).
2. On the Inventory Location tab, click Add
3. In the Search Inventory Locations dialog box, specify the search criteria and click Search.
4. Select a location, and click Relate.
5. In the message about the relationship, click OK.
6. If the inventory is stored in multiple locations, for each location, repeat 4 (see page ) and 5 (see page
).
7. Click Close.
On the Bulk Inventory form, the Inventory Location tab lists each of the related locations.
8. Click in the Quantity Per Location field for a location, and type the quantity in that location.
9. Continue to enter the quantity for each location, until all the quantity in stock for the bulk CI is accounted
for.
10. Click Save.
After items are in inventory, you can use the Manage Inventory function to:
View
Relocate
Reserve and use CIs and bulk inventory items
Managing inventory locations

If you have Asset Admin permissions, you can use the Manage Inventory dialog box to view inventory locations,
relocate configuration items (CIs), and reserve and use CIs and bulk inventory items.
Viewing inventory locations (see page 186)
Relocating CIs (see page 187)
Reserving and using inventory (see page 187)
For more information, see Managing asset inventory (
https://docs.bmc.com/docs/display/asset80/Managing+asset+inventory).
Viewing inventory locations

Page 186 of 452
Using
You can view the location of all your CIs from the Manage Inventory dialog box.
To view inventory locations

1. In the Change Management console, choose Functions > Manage Inventory.
2. On the Manage Inventory dialog box, enter your search criteria, and click Search.
3. Select a CI or bulk inventory item from the table, and then click View Location.
Relocating CIs
You can relocate CIs or bulk inventory items from one location to another.
To relocate CIs
2. On the Manage Inventory dialog box, select the CI or bulk inventory item to relocate, and click Relocate
CIs.
3. From the Location list on the Search Inventory Locations dialog box, select the location where to relocate
the CI, and then click Search.
4. Select the location where to relocate your CI.
5. In the Quantity field, enter the number of CIs to relocate, and then click Relocate.
Reserving and using inventory

You can reserve and use the CIs and bulk inventory items that are in inventory.
To reserve and use inventory

2. On the Manage Inventory dialog box, select the CI or bulk inventory item to reserve and use.
3. Click the Transaction Qty column and enter the number of CIs or bulk inventory items to use.
Transaction Qty column
4. Click Reserve/Use Inventory.

The number of CIs or bulk inventory items in the Qty in Stock column is reduced by the number reserved
and used.
Page 187 of 452
Using
6 Using Release Management

This section describes the procedures to create and modify release requests.
Initiate milestone - Creating release requests (see page 188)
Recording the release activities (https://docs.bmc.com/docs/display/change81/Recording+the+release+activities)
Planning milestone - Planning and scheduling the release request (see page 206)
Managing release management approvals (see page 213)
Build milestone - Building a controlled environment for the release (see page 216)
Test milestone - Testing the release (see page 218)
Deployment milestone - Rolling out the release to the business (see page 220)
Close Down milestone - Completing release requests (see page 222)
Working with release manifests (see page 224)
Working with release activities (see page 226)
Working with release request financial information - Rolling up costs (see page 243)
Working with release request assignments (see page 245)
Sending release or activity notifications (see page 250)
Monitoring the progress of a release request (see page 250)
Modifying release requests (see page 253)
6.1 Initiate milestone - Creating release requests

Releases start at the Initiate milestone of the release request lifecycle. The Release Management console enables
any user with Release User permissions to enter release requests into the system. But it is typically release
coordinators who create release requests.
Creating release requests at the Initiate milestone
Page 188 of 452
Using
Note
Release Management uses the following terms extensively:
Milestone A grouping mechanism used to identify key points in the release process.
Phase Used for the deployment types, Phased and Non Phased. These are used to identify the
deployment types for releases.
Page 189 of 452
Using
This section provides the following information about creating release requests:
Creating a release request at the initiate milestone - Best Practice view (see page 190)
Creating a release request at the initiate milestone - Classic view (see page 193)
Specifying the business justification (see page 196)
Selecting release templates (see page 198)
Creating a manifest (see page 200)
6.1.1 Creating a release request at the initiate milestone - Best Practice view
The section describes how to create a release request at the Initiate stage when using the Best Practice view of
Release Management.
To create a release request at the Initiate milestone

1. Review the RFCs to make sure you understand their requirements.
This is a manual step you should perform before you open Release Management. You should understand
the scheduled start and end dates, the CIs involved, the manifests necessary to complete the release, the
CAB approvers, and so on.
Recommendation
Enter information into Release Management as soon as it is available to you. You can revise it at
later milestones.
2. On the Release Management Console, click Create to open the Release form.
The Release ID field is automatically filled with an ID number for the release request.
In the Initiate stage, the release request initially appears in Draft status. The release request has not yet
been submitted to the Release Management process.
3. Use the following fields to specify the release coordinator:
Coordinator Group Specify the group of people with the Release Coordinator functional role. This
list is populated with groups that have at least one user with a Release Coordinator functional role.
Coordinator Specify the user responsible for the release. The list is populated with people with the
Release Coordinator functional role and who are included in the Coordinator Group selected.
4. From the Service field, select the business service configuration item (CI) that relates to the release request
that you are creating.
The Service field relates business service configuration items (CIs) to the release request at the time it is
created. Business service CIs are related either to the customer directly or to the customer's company,
organization, or department.
Note
Page 190 of 452
Using
The business service CI is not a physical CI (such as a printer or a router); it is a logical CI. In this
context, a logical CI is a business service that can be provided from one business, or organization
within a business, to another. Service CIs can include customer support, employee provisioning,
web farms, storage, and so on. When business service CIs are created and made available on the
5. (Optional) Select a template to complete part of the release request.

Release templates are especially useful in any release request that follows well-defined methods for
specific and repeated requirements. Release templates do more than simply fill out fields for you; they can
also include CIs and manifests to the release request. For more information, see Selecting release
templates (see page 198). The template is attached to the release request.
Notes
The release template can be applied in the Draft state, that is, while creating the release
request.
If you start to enter fields in the release request and then select a release template, the
release template overwrites any field values that are already present in the release request.
Any relationships or manifests included with the release request are not overwritten. Any
additional manifests from the template are added as peers, and additional relationships (for
example, CIs) are included with the release request.
6. (Optional) The target date is the date by when the release must be completed, according to the applicable
service level target. Alternatively, the target date can be a date that is agreed to on an ad hoc basis, per
release.
7. Complete the following fields:
Field
Description
Summary
Provide a brief description of the release.
Business
Justification
Specify the business requirement for the request. Select an option based on the policies defined by your company. By default
these values are for informational purpose only. You have the following options:
Corporate Strategic
Business Unit Strategic
Maintenance
Defect
Upgrade
Enhancement
Customer Commitment
Sarbanes-Oxley
Impact
Page 191 of 452
Using
Field
Description
Specify the extent to which the release affects the business. The default value is 4-Minor/Localized. Impact is often directly
related to the extent to which the service has degraded from agreed service levels. Impact can be measured by the number
of people affected, the criticality of the system affected, and the loss of revenue as a result of the service degradation or
disruption.
Urgency
Specify a value that indicates the importance of the release request, and reflects how quickly a release must be implemented,
or the time available to reduce the impact of the release on the business. The default value is Low.
Number of customers affected by associated Releases
(Optional) Specify the importance that you (as support staff) assign to the release request.
Priority
Priority indicates the relative order in which to address the releases. It is influenced by considerations of risk and resource
availability, but is primarily driven by the combination of Urgency and Impact. The default value is Low.
8. Select the Risk Level to indicate the relative risk associated with the release.
The default risk level is Level 1, which is the lowest level. The highest risk level is Level 5. The Risk Level is
used as a criterion to determine required approvals.
9. Select the Release Type for the release request.
You use this field to further categorize the releases that are released into the IT infrastructure.
Option
Description
Full
All components of the release are built, tested and deployed together. You typically use the Full release type if you want to make
sure that the release or version of your application, plus the necessary CI components to run the application, are all linked
throughout the entire process.
Delta
Includes only incremental releases and only those components or CIs that need to be included in this release. You typically use
the Delta release type if your application was moving from version 1.0.00 to 1.1.00.
Package
All individual Full and Delta releases are grouped together and form a packaged release. You typically use the Package release
type if you combine several minor and major updates together.
Backlog
Method to identify and review multiple changes, incidents, and problems that are candidates to target to implement in a release.
The Backlog release type is a grouping mechanism that the CAB uses as their candidates to review for future releases.
Note
Do not manually set the Milestone, Status, and Status Reason fields in the Release form.
When you use the Process Flow Status bar the release request to the next milestone, the value in
the Status field automatically changes, based on the options you select from the Status bar
menus.
10.
Page 192 of 452
Using
10. Click Save to create the release request.

This is the minimum information needed to create the release.
6.1.2 Creating a release request at the initiate milestone - Classic view

The section describes how to create a release request at the Initiate stage when using the Classic view of Release
Management.
To create a release request at the Initiate milestone

1. Review the RFCs to make sure you understand their requirements.
This is a manual step you should perform before you open Release Management. You should understand
the scheduled start and end dates, the CIs involved, the manifests necessary to complete the release, the
CAB approvers, and so on.
Recommendation
Enter information into Release Management as soon as it is available to you. You can revise it at
later milestones.
2. On the Release Management console, click Create.

The Release form appears with the Request ID field automatically filled with an ID number for the release
request. The release request initially appears in Draft status. To enable the release request from Draft status
to be moved to its next status, enter information into the required fields.
3. (Optional) Use a release template to fill out the contents of the release request.
Recommendation
Release templates are especially useful in any release request that follows well-defined methods
for specific and repeated requirements. Release templates do more than simply fill out fields for
you; they can also include CIs and manifests with the release request. For more information, see
Selecting release templates (see page 198).
The Requested By fields are auto-populated with the details of the user who creates the release. If this user
is not associated to a support group, the Support Company is set to the Location Company of the user. If
this user is associated to a support group, the Support Company, Support Organization, and Support Group
is set to the user's default Support Group.
You can modify the Requested By fields if required. The Support Company list is modified based on profile
of the user selected in the Requested By field. For users who are support staff the list includes only Support
Group companies only for that user and for non-support staff the list includes all valid companies listed
under Location Company.
4.
Page 193 of 452
Using
4. In the Summary field, enter a brief description of the release.

5. In the Notes field, enter a more complete description of the release.
6. From the Service field, select a business service CI.
Selecting a business service CI automatically performs the following actions:
Populates the Product Categorization of the release request based on the categorization of the
business service CI. You can modify the Product Categorization values later.
Relates the business service CI to the release request as a Related to association type when the
release is submitted. After it is established, you cannot remove the association created between the
release request and the business service CI from the Relationships tab. However, you can select
another service from the Service field when the release request is in Modify mode.
7. Select the Deployment type for the release request.
You can use this field to further categorize the releases that are released into the IT infrastructure.
Deployment
type
Description
Phased
Stage the deployment of the release to a part of the user base. The operation is repeated for subsequent parts of the user
base through a scheduled rollout plan, for example, the release coordinator identifies a set of changes that must be done at
the same time, for example, all changes for Building 1 at Phase 1, all changes for Building 2 at Phase 2, and so on.
You typically use phased deployments when new services are introduced into a store environment in manageable phases
(such as retail organizations).
Non-Phased
All changes or activities deployed all at the same time in one operation with no restrictions, for example, a company-wide
rollout of new servers.
You typically use non-phased deployments when introducing an application change, and consistency of service across the
organization is important.
Note: ITIL Service Transition Version 3 describes non-phased deployment as the Big Bang method.
Do not manually set the Milestone, Status, and Status Reason fields in the Release form.
When you use the Process Flow Status bar the release request to the next milestone, the value in the Status
field automatically changes, based on the options you select from the Status bar menus.
8. Select the Release Type for the release request.
You use this field to further categorize the releases that are released into the IT infrastructure.
Release
type
Description
Full
All components of the release are built, tested and deployed together. You typically use the Full release type if you want to make
sure that the release or version of your application, plus the necessary CI components to run the application, are all linked
throughout the entire process.
Delta
Includes only incremental changes and only those components or CIs that need to be included in this release. You typically use
the Delta release type if your application was moving from version 1.0.00 to 1.1.00.
Package
All individual Full and Delta releases are grouped together and form a packaged release. You typically use the Package release
type if you combine several minor and major updates together.
Backlog
Method to identify and review multiple changes, incidents, and problems that are candidates to target to implement in a release.
The Backlog release type is a grouping mechanism that the CAB uses as their candidates to review for future releases.
9.
Page 194 of 452
Using
9. Select Impact to reflect the extent to which the release affects the business.
The default value is 4-Minor/Localized. Impact is often directly related to the extent to which the service
has degraded from agreed service levels. Impact can be measured by the number of people affected, the
criticality of the system affected, and the loss of revenue as a result of the service degradation or
disruption.
10. Select the Urgency to indicate the importance the requester assigns to the release request.
Urgency reflects how quickly a release must be implemented, or the time available to reduce the impact of
the release on the business. The default value of the Urgency field is 4-Low.
The following factors can be used to determine Impact and Urgency:
Number of customers affected by associated releases Duration and scope of the service disruption
11. (Optional) To override the priority, select a new Priority to identify the importance you (as support staff)
assign to the release request.
Priority indicates the relative order in which releases should be addressed, for example, Medium. The
priority of the request is automatically calculated for you, based on the Urgency and the Impact values that
you specify. These values are configured in the Release Prioritization form. But you can override the
calculation by selecting a different value, for example, High or Critical.
12. Select the Risk Level to indicate the relative risk associated with the release, from 5 (highest risk) to 1
(lowest risk).
The default value is Risk Level 1. The Risk Level is used as a criterion to determine required approvals.
13. Click Rollup to accumulate the risk level from the related change requests (displayed on the Manifest tab).
The highest Risk Level of all the related change requests is used when rolling up the Risk Level. The risk
rollup is not performed automatically. You can override the risk rollup with a different value.
14. Modify information as needed in the required fields on the General tab, for example, Company, First Name,
and Last Name.
This information is auto-filled, based on your logon. The Company is the organization or group that the
release request is assigned to.
Tip
If you type a letter or name into any of the fields with a (+) sign and press Enter, the field is
autofilled. If multiple choices exist, a selection list or dialog box appears, to help you enter a
name. Otherwise, you are prompted if no such letter or person exists in the system.
15. (Optional) Modify information in the required Release Location Company field.
The Release Location Company field is especially important in a multitenancy environment. In this field,
you can specify the company, department, or other group that controls access to the release request.
16. Click the Assignment tab and ensure that the release is properly assigned. You can manually reassign it to
another release coordinator.
a. Select an assignment method (for example, Auto Assign), and then click Set.
b.
Page 195 of 452
16.
Using
b. Review the Support Company, Support Organization, and Support Group Name (if this information is
not already supplied).
c. Select the release coordinator to whom to reassign the request.
For more information, see Working with release request assignments (see page 245).
17. Click Save to create the release request.
This is the minimum information needed to create the release. You should include additional information
as it is available to you.
18. (Optional) If you need to suspend work temporarily on the release request, use the Process Status Flow
area to move the release request to Pending status. Select Enter Pending and an appropriate status reason
(for example, Manager Intervention) from the Process Flow Status menu.
When you are ready to continue work on the release request, select Resume from the Process Flow Status
menu. The Status field is updated automatically during the Process Flow for other options. For more
information, see Performing additional functions from the Process Flow Status bar (see page 255).
6.1.3 Specifying the business justification

At the Initiate milestone, the release coordinator prepares a business case to justify the release, for example,
compliance with Sarbanes-Oxley requirements or fixing a defect in a mission-critical server.
Release coordinators specify the business justification of the release to initiate the implementation of the release
and to decide on corrective actions (if needed). If there is not enough funding to implement the release, you
should create a contingency plan if an adjusted business case for the release can still get the necessary approvals.
If you cannot get your business case approved, you must inform the requesters of the release that the business
case for the release has been rejected.
Release form Classification information
Page 196 of 452
Using
To specify the business justification

1. Open the release request.
Enter this information in the Business

Justification field on the Release form.
Click the Classification tab.

The Classification tab is used to describe the business justification of the release (for example,
Maintenance) and show which products and services are affected by the release.
3. Select a Business Justification to indicate the business reason for implementing the release request.
Business justification information is important when the request goes through the approval process. You
use this information to make sure funding is available to implement the release.
4. Categorize the release request by filling in the categorization fields.
Click the Categorization tab.
Add this information to the Classification tab.
Page 197 of 452
Using
The application automatically assigns the release request to the submitter if they have the functional role
of a Release Coordinator when the request is saved. Assignments are determined by the rules configured
by the application administrator.
5. To create or relate other items to the release request, click the Relationships tab.
You can create and relate release requests to your current release request before it is saved. You can also
create and relate configuration items, change requests, and so on, to the release request.
Note
If you close the new release request before saving, any new items you created as a relationship or
a manifest, still exist. There is no relationship between these new items and the release request
since the release request was not created.
6. Click Save.
Depending on the settings configured by your application administrator, you might see the Release form in
Modify mode. You might also have to open the Release form in Search mode and query for your request.
6.1.4 Selecting release templates

The Release Template function allows you to select any templates that can be made available for your support
group. You use release templates to quickly and efficiently create standard releases with a minimum of mouse
clicks and keyboard entry. Release templates are useful in any release request that follows well-defined methods
for specific and repeated requirements, for example, Installs, Moves, Add Changes (IMAC). New and occasional
users to Release Management should find release templates very helpful.
To select release templates

1. Create or open a release request.
2. Attach a release template by performing one of the following actions:
a. Click the magnifying glass icon next to the template field on the release
form.
b. Select the support group from the Viewing Templates for Support
Group.
c. Select the correct template from the list displayed.

On the left navigation pane, click Quick Links > Select
Template.
Note
The release template can be applied in the Draft state, that is, while creating the release request.
3.
Page 198 of 452
Using
3. On the Release Template Selection dialog box, click View to examine the contents of a release template.
The template appears in read-only mode. Viewing a template lets you see its relationship, its task and task
group templates, and other important features.
Note
You cannot create, modify, or delete release templates in the Release Management application;
you can only view them. You must use the Application Administration Console to create, modify,
or delete release templates instead.
Any member of your support group with Release Master, Release Config, or Release User with
Support Group Admin permissions can modify release templates for that group. For more
information, see Configuring release templates (
https://docs.bmc.com/docs/display/itsm80/Configuring+release+templates).

The contents of the template are applied to the release request. The release template overwrites any
field values that are already present in the release request, including any relationships or manifest
included with the release request.
The value of the Notes field value from template is appended to existing value.
NULL values in the template will overwrite existing values, except for the following fields:
Summary
Release manager
Support Company
Support Group Name
Support Organization
Location Company
Deployment Type
Risk Level
ServiceCI
Urgency
Change Environment
Lead Time
Change Reason
Impact
Product Cat Tier1
Release Type
Urgency
Page 199 of 452
Using
6.1.5 Creating a manifest

When you are in the Initiate milestone, you should create required release manifests. A manifest functions like a
packing list or an invoice - it describes the schedule and provides an overview of the contents of a particular
release. Here you split the requirements of the release into logical groups of change requests and activities that
can be handled efficiently by change coordinators and activity assignees.
Note
You can create change requests and activities during all milestones, except Close Down.
You can relate a change request to the release; or you can create an ad hoc change request and activity to add to
the release. The manifest items are grouped in the Order column, for example, 0, 1, 2, and so on. However, the
order does not enforce a sequence for execution.
Manifest support and provide visibility to the milestones of the release. You can configure the application to
enforce that the manifest: changes or activities, included in the release must be completed during that milestone
for the release to move to the next stage. For more information on configuring milestones and exit criteria, see
Configuring phase and exit criteria milestones (
https://docs.bmc.com/docs/display/change81/Configuring+phase+and+exit+criteria+milestones).
Note
There is no enforcement for when the activity or change can be started.
In a release, the Manifest tab defines the contents of a release for each milestone. You create the associations
between a release and the various release activities or change requests that are necessary to implement and close
it.
Finally, collision detection is automatically run when you save the release. It runs only on new change requests
that you have added to the release.
For more information, see Detecting CI collisions between change requests (
https://docs.bmc.com/docs/display/change81/Detecting+CI+collisions+between+change+requests) and Working with
release manifests (see page 224).
To create a manifest
1. Click the Manifest tab in the Release form.
The Manifest tab shows the release activities and changes related to the release.
Page 200 of 452
1.
Using
2. From the Request Type list at the bottom of the Manifest tab, select Infrastructure Change or Activity.
Note
The contents of the search form depend on the type of application object you chose in the
Request Type list.
Request type
Action
For more information
Infrastructure
Change
Search Opens the Change Relationship Search form. You use this form to
search for change requests, and then establish a Consists of relationship
change to the release
Create Opens the Change form in New mode
View Opens the change that is related to the release
Remove Removes the change from the relationship with the release; it
does not delete the change
Creating a change request at the

initiate stage - Best Practice view (see
page 83)
Activity
Create Opens the Activity form in New mode

View Opens the activity that is related to the release
Remove Removes the activity from the relationship with the release; it
does not delete the activity
Creating activities - basic steps (see

page 234)
3. Add the activity or change to the release manifest.

The Manifest Attributes dialog box appears. This dialog is displayed whenever you relate a change or
Page 201 of 452
3.
Using
activity to a release manifest. You can specify the milestone and the phase in which the change or activity
should be grouped.
Manifest Attributes dialog box
Note
You can add multiple change requests to the release and assign them to different milestones.
Manifest Attributes dialog box Adding multiple changes to different milestones
Page 202 of 452
Using
4. Specify the milestone and phase for the activity or change, for example, Deployment and Phase 1.
5. Click Apply, and then close the Manifest Attributes dialog box.
6. The original release request is displayed. Click Refresh to view the related request types appear in the
Changes and Activities table.
7. Click the up or down arrows next to Refresh, to change the order of items that have been added to the
release manifest.
The manifest items are grouped in the Order column, for example, 0, 1, 2, and so on. However, the order
does not enforce a sequence for execution.
8. Click Rollup next to the Risk Level field to accumulate the risk level, cost, and time from the related change
requests and activities (displayed on the Manifest tab).
The highest Risk Level of all the related change requests is used when rolling up the Risk Level. The risk
rollup is not performed automatically. The release user can override the risk rollup with a different value.
Note
If you need to add change requests or activities at other milestone, you can click Rollup as needed
on demand.
Rollup also rolls up the following information from the changes in the release manifest.
Budget Cost and Actual Cost-Rolls up financial data from change requests and activities into the
release. You can see costs under Links > Financials when using the Best Practice view and on the
Financials tab of the Release form when using the Classic view.
Time-Rolls up time spent (in minutes) from change requests and activities to the Release form. You
can see time spent on the Date/System tab when using the Best Practice view and the Assignment
tab of the Release form.
9.
Page 203 of 452
Using
9. Save your work.
6.2 Recording the release activities

You might need to modify a release request with work history entries that you add during its life cycle, in order to
document activities performed or information gathered. For example, you can track a release request's progress
in the work history by recording the steps that you took to implement it.
Use the Work Details tab when using the Best Practice view and the Work Info tab when using the Classic view to
add work information about activities performed for the current release request. For example, you can track a
release request's progress by recording the steps that you took to implement it in the work history.
The request should still follow the stages in the recommended life cycle of a release request, as described in
Milestones in the release request lifecycle (
https://docs.bmc.com/docs/display/change81/Milestones+in+the+release+request+lifecycle). The Process Flow Status bar
directs you with messages if there are fields that must be filled in when you move to a new milestone.
You might want to add work information about the following activities:
General Information Notes about the record, for example, you might want to add a note that a particular
CI was deployed, and include the date.
Planning Notes about a plan to implement a global release throughout your organization.
Implementation Installation and backout procedures for the release.
Costing and Charging Additional information about the cost of the current CI, incident, change, or so
on. For example, you might want to add a note that the cost of maintaining a CI was split between two cost
centers, or that the cost to implement a release came under budget.
Any user with release related permissions - User, Master, or Viewer can add or modify work info from the Release
console or the release request in Modify mode. However, only users with Release Master permissions can add
work info to closed Release requests.
If you are using the Best Practice view, you can view multiple work info entries at the same time
by clicking the History icon. When you click this icon, the system displays a pop-up window with
the Notes field entries arranged with the most recent entry at the top (a date and time stamp is
also visible with each entry).
If your user ID has Release Viewer permissions, you can add and modify Work Info entries,
however, you cannot create or modify release requests.
Use the following procedures to add work information about activities performed for the current release request:
To add or modify work information to a release request when using the Best Practice view (see page 205)
Page 204 of 452
Using
To add or modify work information to a release request when using the Classic view (see page 205)
6.2.1 To add or modify work information to a release request when using

the Best Practice view
2. To add new work information, under the Add Work Info details section on the Work Detail tab, enter the
following information:
Notes Enter the details of your work information record in this field.
Attachment Click
to add any attachments related to the work information.
3. Click More Details to select the work information type and add any additional attachments.
5. In the Attachment fields, add any additional attachments required for the work information. You can add
up to three files.
6. When you finish updating the release request, under Add Work Info click Save.
The Save operation adds your entry to the work history.
7. To view or update the entries in the work information, select the work info record and click View. Under
the Edit Work Info section:
a. Update the required fields.
b. To delete an attachment, click the delete
icon for that attachment.
c. Click Save.
8. To view a report of selected activities you performed against this request, select the records from the work
info table and click Report.
9. To view the history of when and by whom each of the work information was added click History .
10. Click Save.
6.2.2 To add or modify work information to a release request when using

the Classic view
1. Open the release request and click the Work Info tab.
Information sources can include, for example, email, system assignment, or the Web.
4. Enter the details of your work information record in the Summary and Details fields.
5. To add an attachment to the record, right-click in the attachment table and select Add from the menu that
appears. With browsers, click the Add button.
Warning
If you select Yes you cannot modify the work log after you save the record.
Page 205 of 452
6.
Using
7. From the View Access list, select Internal or Public.

Internal If you want only users within your organization to see the entry.
Public If you want everyone with access to the system to see the entry, including requesters.
8. When you have finished updating the release request, click Save.
The Save operation adds your entry to the work history. The Show field allows you to filter out specific
work entries based on the type of activity that appear in the table.
9. To see a report of the activities you performed against this release, click Report.
10. To see all entries for work information history, click View.
You can view but not modify the work info records if they are locked.
Note
When you return to the Release Management Console, you might need to refresh the Release
Information table to display all the modified records.
11. Click Save.
6.3 Planning milestone - Planning and scheduling the release

request
After a release request is approved at the Planning Approval phase, the release coordinator must plan the details
associated with the release.
Planning the release request
Page 206 of 452
Using
Plan for the following important details:

Set the release request's status to Planning, and review the planned dates.
Estimate the time the project will take.
Estimate any applicable downtime associated with the release request.
Register an available or unavailable time segment to perform the release.
Assess the risks and impact of the release request.
Specify the business justification for the release (if this was not already done when the release request was
created).
Create your plans.
Calculate the costs associated with the release request.
Submit the release request for approval.
Approvers require this information to be able to decide whether to approve or reject the release request.
6.3.1 To plan and schedule the release request

1. Open the release request at the Planning In Progress status.
2. Open the Change Calendar.
a. Perform one of the following actions:
Choose Quick Action > View Calendar.
Choose Quick Links > View Calendar.
Page 207 of 452
2.
a.
Using
b. Select how many days' worth of requests and business events to show.
c. Select Release Requests to view release requests in the calendar.
d. Select the requests and business events for a specific day.
Change Calendar Viewing release requests
3. Close the Change Calendar when you are finished.

For more information, see Using the Change Calendar in version 8.0.00 (see page 206).
4. Register available or unavailable time segments for your business event, operational categorization, or CI.
5. Click the Date/System tab in the Best Practice view or Dates tab in the Classic view.
Page 208 of 452
Using
When planning a release request, you use this tab to track the scheduled, actual, and deployment start and
end dates of releases.
6. Revise the start and end dates as needed.
Review the Business Justification field on the Release form.
Click the Classification tab, and then review the business justification.
For more information, see Specifying the business justification (see page 196).
8. (Optional) Perform one of the following actions:
Choose Links > Financials.
You can calculate the costs associated with the change request.
For more information, see Close Down milestone - Completing release requests (see page 222).
9. Save your work.
10. Use the Process Status Flow area to move the release request from the Planning In Progress status to the
Build Approval phase.
The release must be approved before it can move forward.
Page 209 of 452
10.
Using
For more information, see Build milestone - Building a controlled environment for the release (see page
216).
6.3.2 Scheduling releases

For the Initiate milestone, in the Release form, use the Dates tab in the Classic view or the Date/System tab in the
Best Practice view to add the scheduled start and end dates for the release. These dates can also be revised for
the Planning milestone. During deployment, you also use this tab to track actual and deployment start and end
dates for the release.
The following information describes each of these date fields on the Release form:
Field
Description
Deployment
Start Date
For the Deployment milestone, provide the date when the release starts to be deployed to the IT infrastructure.
Deployment
For the Deployment milestone, provide the date when the release finishes deploying to the IT infrastructure.
End Date
Requested
For the Planning milestone, provide the date and time when the release should be available.
Availability
Date
Target Date
The target date is the date by when the release must be completed, according to the applicable service level target. Alternatively,
the target date can be a date that is agreed to on an ad hoc basis, per release.
On the Date/System tab, this field is read-only and is automatically set to the target date and time selected on the release form.
Completed
Date
This field is read-only and is automatically set to the current date and time when the status of the release is set to Completed.
Scheduled Start
Date
For the Initiate milestone, use this field to specify the date and time at which the release implementation is scheduled to start (the
moment at which the release is planned to be set to the status Work in Progress).
Scheduled End
Date
For the Initiate milestone, use this field to specify the date and time at which the release implementation is scheduled to be
completed (the moment at which the release is planned to be set to the status Closed).
Note: Scheduled start date and end date values cannot be modified when the release is awaiting approval.
Actual Start
Date
For the Deployment milestone, provide the date for when work started on the release.
Actual End
Date
For the Deployment milestone, provide the date for when work ended for the release.
Release form date information
Page 210 of 452
Using
You can use the Schedule Assist tool to identify possible conflicts associated with releases. You can search for
windows of opportunity that your release request can be scheduled around. The Schedule Assist tool helps you
search for available deployment times for the release request based on global business events and CI availability.
When you create a release request that modifies a CI for example, you must upgrade a server you can
schedule a time segment for the CI that shows it is unavailable to the rest of the support staff. If another member
of the support staff wants that CI to be available, they should schedule their own release in a different time
segment. You can perform the tasks listed in the following table.
Note
The following processes are essentially the same for BMC Change Management and Release
Management, with one exception for the Schedule Assist tool. The Release form shows you the CIs
related to the changes in the release manifest. In BMC Change Management, you see the CIs that are
directly related to the change.
Task
Action
Explanation

1.
Page 211 of 452
Using
Task
Action
Explanation
Register unique
1. In the navigation pane of the Release form, choose Advanced > Time Segments >
Registering time
business events
for releases
Business Event.
2. On the Search Business Event/Location Definition dialog box, click New.
segments (see page 415)

Registering unique
3. On the Business Event/Location Definition dialog box, define a unique time segment for
the business event or categorization.
business events and

operational
4. Click Save.
5. Click Add to create a time segment.
categorizations (see page

420)
6. In the Description field on the Business Time Segment dialog box, enter a description for
the time segment.
Understanding server
time, time zones, and
7. In the Availability field, select Available or Unavailable.

8. In the Level field, select a level of 10 or higher.
time segments (see page

415)
9. In the Duration Type field, select One time (which generates a single occurrence of the
time segment) or Recurring (which cannot span multiple days, but must be scheduled
within a 24-hour period).
10. Enter the starting and ending dates and times for the duration of the time segment.
11. Click Save, and then click Finish.
Registering CI
time segments
for releases

1. In the navigation pane of the Release form, choose Advanced > Time Segments >
Configuration Item (CI).
Registering time
2. In the CI Advanced Search form, enter the information necessary to search for a CI and
then click Search.
segments (see page 415)

Registering time
3. Select a CI from the search results.

4. Click Explore CI to view a CI and its relationship in a tree structure.
segments for CIs Creating a blackout
5. Select the CI.

6. In the Registration for Shared Time Segment dialog box, click Add.
schedule (see page 416)

Understanding server
7. In the Description field on the Business Time Segment dialog box, enter a description for
the time segment.
time, time zones, and

time segments (see page
8. In the Availability field, select Available or Unavailable.

415)
10. In the Duration Type field, select One time (which generates a single occurrence of the
time segment) or Recurring (which cannot span multiple days, but must be scheduled
within a 24-hour period). If you select Recurring, you must specify the recurrence.
12. Click Save to associate the time segment to the CI, and then click Finish.
Use Schedule
Assist to search
for available
times
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
Open the release request.

Click the Dates tab.
Click the Schedule Assist icon.
Define any time segments needed for the CIs.
Click Find Next Available Time.
Click Schedule Time Segment.
On the Associate Time Segment to CIs dialog box, use the following steps to associate
CIs to time segments.
Select the CI to associate the time segment to.
Enter a description of the time segment.
Click Create Time Segment.
Click Next.
Enter the scheduled start date and end date.
Click Next.
Save the change request.
For more information, see Using

Schedule Assist to search for
available times (see page 423)
Page 212 of 452
Using
6.4 Managing release management approvals

Release Management approvals are similar to the BMC Change Management approvals. For detailed information
on the out-of-the-box approval processes provided for Release Management, see Approval processes provided
out-of-the-box for Release Management (see page 213).
The following topics described for BMC Change Management approvals are also applicable for Release
Management:
Multiple approvers and multiple approval levels (see page 142)
Approving or rejecting requests (see page 137)
Resubmitting a rejected request (see page 136)
Approving or rejecting requests via email (see page 143)
This section provides the following information about release management approvals:
Approval processes provided out-of-the-box for Release Management (see page 213)
Understanding the release management approval process (see page 214)
Working with release request approvals (see page 215)
6.4.1 Approval processes provided out-of-the-box for Release Management

Release Management is installed with default approval processes designed out-of-the-box for global use.
Preconfigured approval processes for Release Management
Approval
process
(phase)
Definition
Initiate
The Initiate phase starts when the release request is placed in Initiation Approval status.
If the release request is approved, the request moves to the Registered status.
If the release request is rejected, its Status changes to Rejected.
If there are no approvers defined for the request (that is, if no approvers are mapped to the Initiate approval phase), its Status
changes to Registered and requires the release coordinator to move the request forward.
Planning
The Planning phase starts when the release request is placed in Planning Approval status.
If the release request is approved, it moves to the In Progress status.
If no approvers are mapped to the Planning phase, the release request moves to the In Progress status and requires the
release coordinator to move the request forward.
If the request is rejected, it moves to the Rejected status.
Build
The Build phase starts when the release request is placed in Build Approval status.
If no approvers are mapped to the Build phase, the release request moves to the In Progress status and requires the release
coordinator to move the request forward.
Page 213 of 452
Using
Approval
process
Definition
(phase)
Test
The Test phase starts when the release request is placed in Test Approval status.
If no approvers are mapped to the Test phase, the release request moves to the In Progress status and requires the release
coordinator to move the request forward.
Deployment
The Deployment phase starts when the release request is placed in Deployment Approval status.
If no approvers are mapped to the Deployment phase, the release request moves to the In Progress status and requires the
release coordinator to move the request forward.
Close Down
The Close Down phase starts when the release request is placed in Close Down Approval status.
If the release request is approved, it moves to the Completed status.
If no approvers are mapped to the Close Down phase, the release request moves to the Completed status.
Note
You can view the included approval phases on the Status Flow tab of the Approval Process Configuration
form. For information about configuring approvals as an administrator for BMC Change Management,
see Configuring Approvals (https://docs.bmc.com/docs/display/change81/Configuring+approvals). For
information about working with the BMC Remedy Approval Server as an administrator, see Process
administrator overview (https://docs.bmc.com/docs/display/ars8000/Process+administrator+overview) in the
BMC Remedy Approval Server documentation.
6.4.2 Understanding the release management approval process

After a release is planned and built, the release request is set to a status of Scheduled for Review. The release
coordinator has the opportunity to review plans, schedules, and so on, before moving the release to the
Implementation Approval phase.
Release form Approvers tab
Page 214 of 452
Using
The read-only Current Approval Phase field shows what approval phase the release is in during its life cycle. For
more information, see Approval processes provided out-of-the-box for Release Management (see page 213).
6.4.3 Working with release request approvals

Certain release requests must pass through an approval process before they can be deployed. Approvals can be
defined for each milestone of the release request from Initiate to Close Down.
After a release is planned and built, the release request is set to a status of Build Approval if approval is
configured. The Release Coordinator has the opportunity to review plans, schedules, before approving then and
moving the release to the Test Approval phase.
The read-only Approval Phase field shows what approval phase the release is in during its life cycle.
The application administrators configure the approval processes. The process owner determines the approvals
based on the policies of the business. They determine which release requests require approval, what kind of
approval process the release requests must undergo, and who the approvers are. Support staff and management
can add more approvers to the list.
Related topics
Approving or rejecting requests (see page 137)
Resubmitting a rejected request (see page 136)
Approving or rejecting requests via email (see page 143)
Viewing release requests awaiting approval

Release coordinators submit the requests for approval and monitor the approval process. Approvers are notified
when a release request requires their approval. After reviewing the release request, they can approve it or reject it.
As an approver, you are required to review release requests for approval. You review release requests and provide
approval through the Release Management application or the Approval Central.
Page 215 of 452
Using
To view the release requests awaiting approval from the Approval Central, click Pending Approvals under the
Approval Tasks list of the Approval Central.
To view release requests awaiting approval from the Release Management console
1. In the Release Management console, under Counts in the left navigation pane, click Waiting Approval.
The Releases table shows the release requests waiting approval.
2. Select the release request to review, and then click View.
The approver can approve or reject the release request from the Release Request form, or request further
information.
6.5 Build milestone - Building a controlled environment for the

release
After a release request is approved at the Build Approval phase, you must work the release through the Build
milestone. This milestone assembles the CIs that are needed to create the release package in a controlled IT
environment before it goes into service. You also add change requests and activities to the release.
Release request at the Build milestone
Page 216 of 452
Using
At most companies, the Build milestone is interchangeable with the Test milestone. The Build and Test milestones
are typically iterative processes. Release candidates are built, tested, and frequently kicked back so that they can
be fixed. During the Build milestone, you complete change requests and activities to build and test the release
package. You then find you must add additional change requests and activities to fix bugs, add additional
functionality to the release, and so on.
Page 217 of 452
Using
Note
For release coordinators, the Build milestone is mostly a manual stage to verify that the Build process is
successful. You should use the Release form to update information, revise your plans, add additional
change requests and activities, and so on.
6.5.1 To build the release

1. Open the release request at the Build In Progress status.
2. On the Dates tab in the Classic view or the Dates/System tab in the Best Practice view, revise the start and
end dates as needed.
3. On the Manifest tab, add changes or activities to the release as needed.
4. Click Rollup to accumulate the risk level, costs, and time spent from the related change requests (displayed
on the Manifest tab).
6. Use the Process Status Flow area to move the release request from the Build In Progress status to the Test
Approval phase. The release must be approved before it can move forward. For more information, see Test
milestone - Testing the release (see page 218).
6.6 Test milestone - Testing the release

After a release request is approved at the Test Approval phase, you should test it at the Test milestone, before you
can release it. Testers can be business staff, users, or other IT staff. They verify the release; then you can roll it out.
Release request at the Test milestone
Click the following thumbnail to expand it.
Page 218 of 452
Using
Note
Page 219 of 452
Using
For release coordinators, the Test milestone is mostly a manual stage to verify that the service work is
successful in a controlled environment. You should use the Release form to update information, revise
your plans, add additional change requests and activities, and so on. At most companies, the Test
milestone is interchangeable with the Build milestone.
6.6.1 To test the release

1. Open the release request at the Test In Progress status.
3. Add changes or activities to the release as needed.
6. Use the Process Status Flow area to move the release request from the Test In Progress status to the
Deployment Approval phase. The release must be approved before it can move forward. For more
information, see Deployment milestone - Rolling out the release to the business (see page 220).
6.7 Deployment milestone - Rolling out the release to the

business
After a release request is approved at the Deployment Approval phase, the release is rolled out to the business at
the Deployment milestone. You deploy the release to the IT infrastructure according to the prepared plan at the
scheduled start date (for example, over a long holiday weekend). You must distribute hardware and software to
the installation site. Task implementers must follow a prepared script of tasks and activities to complete the
installation.The Deployment milestone can require approvals to make sure the release does not need to be rolled
back.
Rolling out the release at the Deployment milestone
Page 220 of 452
Using
6.7.1 To deploy the release to the business

1. Open the release request at the Deployment In Progress status.
2. On the Dates tab in the Classic view or the Dates/System tab in the Best Practice view, revise the
deployment start and end dates if needed.
3. You use these date fields to specify when the release is deployed to the IT infrastructure. These dates are
usually different than the Scheduled Start Date and Scheduled End Date, which is typically a longer
process.
4. On the Manifest tab, review the status of the change requests and activities that are included in the release
manifest.
5. (Optional) Use the Schedule Assist tool to search for available deployment times for the release request.
The Schedule Assist tool identifies possible conflicts associated with releases and windows of opportunity
that your release request can be scheduled around. These deployment dates are based on global business
events and CI availability. (For more information, see Specifying the business justification (see page 196).)
7. Save your work.
8.
Page 221 of 452
Using
8. When all the change requests and activities reach Closed status, use the Process Status Flow area to move
the release request from the Deployment In Progress status to the Close Down Approval phase. The release
must be approved before it can move forward. For more information, see Close Down milestone Completing release requests (see page 222).
6.8 Close Down milestone - Completing release requests

After the release request is approved at the Close Down Approval phase, you cannot close the release request
until all tasks are closed, due to success, cancellation, or failure. When all the tasks related to a release request are
closed, the requester and the release coordinator are notified that the release is resolved.
Release request at the Close Down milestone
The Close Down milestone provides the opportunity for reviewers to conduct post-implementation reviews
(sometimes called postmortems) to offer feedback on the effectiveness of the release, and record metrics for
Page 222 of 452
Using
deployment to make sure the release met its service targets. After IT and the business unit (BU) have completed
the review, no further changes or activities are performed on this release. When the requester has verified that
the release request was resolved satisfactorily, the release request can be set to Closed. If the requester does not
close the release request within the allowed response time of it being resolved, the release request is closed
automatically after a specified period of time. The Status Reason for the release request indicates that the release
was automatically closed.The allowed response time depends on how the application administrator configured
the Release Management application. The default is 15 days. If the requester is not satisfied with the release
request, the requester can reopen the release request. The release coordinator is notified that the release request
is reopened, and must respond to the release request. A release request is moved to the Close Down milestone
when it is cancelled.
To close down the release (see page 223)
To cancel a release (see page 223)
6.8.1 To close down the release

1. Open the release request at the Close Down In Progress status.
3. Add changes or activities to the release as needed.
6. Click Next in the Process Flow Status bar to move the release request forward.
After the release is closed, users with Release Master permissions can update information within the change
record. They cannot however update the following fields:
Impact
Urgency
Priority
Risk Level
Release Type
All date
They also cannot add new manifests or ad hoc approvers.
6.8.2 To cancel a release

Once the release moves into the Planning milestone it can be cancelled. Cancelling a release will close the
release record and move it to the Close Down milestone. All changes and activities created or related to the
release must either be Completed, cancelled or Closed to cancel the release request.
2. For the current milestone, select Cancel > Reason. Reason can have the following values:
Page 223 of 452
Using
2.
No Longer Required
Funding Not Available
To Be Re-Scheduled
Resources Not Available
If all related Changes and Activities defined in the Manifest tab are either Completed, Cancelled or Closed, the
status of the release request is changed to Cancelled, with the status reason as the reason selected and the
release request is moved to the Close Down milestone.
6.9 Working with release manifests

A manifest functions like a packing list or an invoice - it describes the schedule and provides an overview of the
contents of a particular release. Here you split the requirements of the release into logical groups of change
requests and activities that can be handled efficiently by change coordinators and activity assignees.
Note
You can create change requests and activities during all milestones, except Close Down.
In a release, the Manifest tab defines the contents of a release at a particular milestone. You create the
associations between a release and the various release activities or change requests that are necessary to
implement and close it.
In the Manifests tab, you can perform the additional functions listed in the following table related release
requests:
Button
Action
View
View the selected item in the Changes and Activities table. Opens the application object form.
Remove
Deletes the relationship with the release.
Search
Opens the Search dialog box for the specified Request Type.
Create
Opens a window allowing you to create the specified Request Type. You can create an Activity or an Infrastructure Change.
Request Type
Displays a list of all the available application objects that can be related to a release.
Show Milestone
Filters the list by selected milestone, for example, Deploy.
Show Related
Filters the list of all the available application objects that are related to a release.
Page 224 of 452
Using
Button
Action
Quick Actions
Performs advanced actions on relationships.
Execute
Executes the selected Quick Action.
6.9.1 Related topics

Creating a manifest (see page 200)
Detecting CI collisions between change requests (
https://docs.bmc.com/docs/display/change81/Detecting+CI+collisions+between+change+requests)
6.9.2 Using Quick Actions on changes and activities

The Quick Actions menu on the Manifests Tab enables you to perform advanced actions on changes and
activities. Not all actions are available with all request types. This table shows the relationship between request
types and the available actions you can perform on them.
Matrix of request types and quick actions
Request type
Relationship quick action
Activity
Update Attributes
Infrastructure Change
Get Related Relationships
Update Attributes
To use quick actions

2. From the Quick Actions menu, select an action.
For example, you can copy relationships from a CI already related to the release request. The following
table lists all the quick actions you can use:
Relationship action
Effect
Update Attributes
Opens Manifest Attributes dialog box for updating milestone attributes for the relationship.
Get Related
Relationships
Copies the relationships of the selected record to the release request's relationships. For more information, see
Copying relationships (see page 270).
3. Click Execute.
6.9.3 Performing other functions with related release requests

In the Manifests tab, you can perform the additional functions with related release requests that are listed in the
following table.
Page 225 of 452
Using
Button
Action
View
View the selected item in the Changes and Activities table. Opens the application object form.
Remove
Deletes the relationship with the release.
Search
Opens the Search dialog box for the specified Request Type.
Create
Opens a window allowing you to create the specified Request Type. You can create an Activity or an Infrastructure Change. For
more information:
Request Type
Displays list of all the available application objects that can be related to a release.
Show
Filters list by selected milestone, for example, Deploy.
Milestone
Show Related
Filters list of all the available application objects that are related to a release.
Quick Actions
Performs advanced actions on relationships.
Execute
Executes selected Quick Action.
6.10 Working with release activities

Release Management module provides the capability of creating and assigning specific units of work called
activities. Activities have their own lifecycle with a series of status transitions, for example, Draft, Assigned, and so
on. You can also establish a sequence of tasks in your activities. Activities are useful when you need to create a
structured sequence of tasks that you must complete to fulfill the release, but these tasks should not be classified
as a change request.
For example, imagine you must release a new version of the Calbro marketing application. One of the work items
that must be completed in the release cycle is training users on the new marketing application. Because training
is not a change request that the Change Management team would complete, you decide instead that training
should be an activity that is assigned, tracked, and completed using the Activity form.
Release Management comes bundled with the Activity form, which provides basic facilities for assignment, status,
work info, and task management. The Release Management integration with the Activity form lets you create any
generic activity that you need to track.
Activity form
Page 226 of 452
Using
You use the Activity form to add a set of activities to a release request. You can track release states and requester
information, relate and assign tasks, and enter work log information.
Note
For more information about the activity assignee role, see Working with activities as an activity assignee
(see page 228).

Working on activities (see page 228)
Working with activities as an activity assignee (see page 228)
Creating activity task groups and tasks (see page 229)
Entering activity work information (
https://docs.bmc.com/docs/display/change81/Entering+activity+work+information)
Closing the activity (see page 232)

Planning financial information for activities (see page 232)
Planning activity dates (see page 233)
Creating activities - basic steps (see page 234)
Working with activity assignments (see page 235)
Selecting activity templates (see page 239)
Page 227 of 452
Using
Activity statuses (see page 239)

Release task status transitions (see page 241)
6.10.1 Working on activities

This section describes the procedure to start working on activities defined for a release.
To work on activities
1. Log in to the Release Management console.
2. Select the activity from the Change Requests and Activities table.
3. Click View. On the activity form, enter information in each of the tabs described in the following steps to
move the activity forward.
4. Click the Assignment tab to review the assignment. If necessary, you can reassign the activity.
For more information, see Accepting activity assignments (see page 238).
5. Click the Work Info tab to enter work information about the activity.
You can track the activity's progress by recording the steps you took to implement it in the work history or
attach a detailed Training Plan. For more information, see Entering activity work information (
https://docs.bmc.com/docs/display/change81/Entering+activity+work+information).
6. Click the Tasks tab to add tasks to the activity.

Tasks allow you to provide more granularity to the Activity if needed. You can assign specific tasks to
specific task implementers. For example, if there are multiple people that need to train users in multiple
locations, you can want to assign work to them using tasks.
You can create activities with related tasks at each release milestone. Tasks have their own independent
lifecycle and continue on their own path. You might decide to complete the training materials tasks during
the Planning milestone, but complete training tasks during Deployment.
For more information, see Creating activity task groups and tasks (see page 229).
7. Click the Financials tab to add budget and actual costs of the activity.
As you work the activities, you can add the costs associated to each activity in each activity record that is
part of the Release Request. The release activity can be in any status except Closed or Completed.
For more information, see Planning financial information for activities (see page 232).
8. Click the Dates tab to add start and end dates. When you start working on an activity, you should enter the
Scheduled Start Date and Scheduled End Date. For more information, see Planning activity dates (see page
233).
9. If there is no need to update information, move the status to In Progress and save your work.
If you need to temporarily stop work on the activity, you can move the activity to the Pending status.
If you must cancel the activity, you can move it to the Cancelled status. This is a terminal status for
the activity. All open tasks are marked as Closed.
6.10.2 Working with activities as an activity assignee

Release Management provides the capability to assign specific units of work known as activities. When work in a
release must be tracked in a lifecycle with specific status transitions, but does not require the complexity of a
Page 228 of 452
Using
change request (for example, approvals), you can use an activity instead. For example, a new payroll application
requires that your user base receives proper documentation and training. Since this requirement is not a change
request that needs to be completed by the Change Management team, the release coordinator creates it as an
Activity using the Activity form, and then assigns it to an activity assignee.
Note
Activities do not typically involve changes to the IT infrastructure.
The activity assignee is typically a member of the support staff and is responsible for planning the activity, for
example, adding scheduled start and end dates; adding work information to the activity, for example, attaching a
training schedule; creating and assigning tasks, for example, the Payroll staff to create training materials, the HR
staff to train the users; and adding financial information, for example, budgeted and actual costs.
For more information, see Activities (https://docs.bmc.com/docs/display/change81/Activities).
The activity assignee requires the following user permissions:
Release User permission grants general access to the Release Management Console. You can open, query,
submit and modify release requests. Release Viewer permission grants access to the Release Management,
but you can only open and query release requests.
Activity User permission grants general access to the Activity form. The activity assignee will be permitted
to query and modify activity requests.
6.10.3 Creating activity task groups and tasks

When you plan an activity, determine whether you can divide it into separate tasks, especially if you need to add
more granularity to the activity. Tasks are the individual components of an activity, and can be assigned to
specific assignees who complete the tasks.
When you add an activity, by default, the Requested By and Location information fields on the Activity form are
populated with information of the user creating the activity.
Tip
When you are creating tasks for an activity, you must complete the Company, First Name and Last Name
fields under Requester Information, Company fields under Location information and the Summary field
on the activity form before you include the tasks.
Page 229 of 452
Using
The Tasks tab displays the tasks that are required to be performed to complete the activity. You can use task
groups to manage an activity with many tasks, each having its own schedule, task assignee, and plan. For less
complex activities, tasks are optional. Tasks are created and modified within the activity and are stored separately
within the Tasks form.
A single activity can have an unlimited number of tasks.After a task is assigned to a support group or an individual,
the assignee receives notifications to perform the various task activities when the activity reaches the Assigned
status.
The task dates are also displayed on the Dates tab.Tasks, like activities, go through many status transitions as they
progress. The status in which a task is created depends upon the status of the parent activity.
Your assigned tasks and task groups are listed in the Tasks and Task Groups table on the Activity form. Tasks are
prefixed with TAS and task groups with TGR. You can also view tasks and task groups related to an activity from
within the Tasks tab of the Activity form.
Activity form Tasks tab
Note
You can click the View Flow button to see a read-only view of the task flow in the task group. For more
information about using the View Flow button, see Using CCM tasks (see page 315).
Adding task groups and tasks to activities follows the same steps as change requests. For more information, see
Implement stage - Working with tasks (see page 150).
Page 230 of 452
Using
6.10.4 Entering activity work information

You sometimes need to modify the activity with work history entries that you can create during its life cycle to
document activities performed or information gathered. You use the Work Info tab to add work information
regarding tasks performed on the current activity. For example, you can track an activity's progress by recording
the steps you took to implement it in the work history, or you can attach a detailed training plan as part of your
overall release strategy.
As you track and supervise an activity, you move it from one status to another, for example, from Assigned to In
Progress. The activity should follow the stages in the recommended life cycle. If you have simple activities or
activities that are already underway, you might see that the status is set to Pending or some other status.
You can categorize work information about the activity (for example, General Information).
To add work information to an activity

1. On the Release Management console, select the activity from the Change Requests and Activities table,
and click View. The activity is displayed in the Activity form.
2. Make the appropriate changes.
3. Click the Work Info tab and take the following steps:
a. From the Work Info Type list, select the type of work information you want to add.
b. From the Source list, select the source of this information.
Information sources can include, for example, email, system assignment, or the Web.
c. Enter the details of your work information record in the Summary and Details fields.
d. To add an attachment to the record, right-click in the attachment table and select Add from the
menu that appears. With browsers, click the Add button.
e. From the Locked list, select Yes or No to lock the log.
Warning
If you select Yes, you cannot modify the work log after you save it.
f. From the View Access list, select one of the following options:
If you want only users within your organization to see the entry, select Internal.
If you want everyone with access to the system to see the entry, including requesters, select
Public.
4. When you have finished updating the activity, click Save.
The Save operation adds your entry to the work history. The Show field allows you to filter out specific
work entries based on the type of activity displayed in the table.
5. To see a report of the activities you performed against this activity, click Report.
6. To display all entries for work information history, click View.
Page 231 of 452
Using6.
Note
When you return to the Release Management console, you might need to refresh the Change
Requests and Activities table to display all the modified records.
6.10.5 Closing the activity

In the final stage of the activity, the activity assignee reviews all the implemented tasks to make sure that each
objective was met. An activity cannot be closed until all tasks are closed.
To close the activity

1. Open the activity.
2. Click the Dates tab, and enter the Actual Start Date and Actual End Date.
3. Click the Financials tab, and enter the actual cost of the activity.
4. Move the activity to the Completed status.
5. After everything is verified using your company's criteria, move the status of the activity to Closed.
6.10.6 Planning financial information for activities

Use the Financials tab to enter the budget and actual costs for the activity. This information is optional.
To plan financial activities for activities

2. Click the Financials tab.
3.
Page 232 of 452
Using
3. In the Budget Cost area, click Add to include an estimated cost for the activity.
This field is read-only. You typically enter this information at the Planning stage of a release.
4. In the Costs dialog box, enter the relevant information in the following required fields:
Cost Center Code Identifies the code name for the business unit or organization within the
company that is charged for servicing the activity. The default cost center is the business unit to
which release coordinator belongs, but you can modify this.
When you select the cost center code, the Company and Cost Center Name fields show the values
attached to the cost center code.
Cost Category This field is automatically filled according to the application you are working in.
Related Cost Enter the rate. You select the Currency from the list. Your administrator sets the
available currencies.
5. Save your changes in the Costs dialog box.
6. On the Financials tab, click View to modify the budget costs.
For information about using other fields on this dialog box, see Adding and viewing costs (see page 294).
7. In the Actual Cost area, click Add to include the final cost for the activity.
8. Save the activity.
6.10.7 Planning activity dates

You should enter the Scheduled Start Date and Scheduled End Date for the activity. The Dates tab in the Activity
form includes various fields where you can enter scheduling information, for example, the actual start date of the
activity.
To plan dates for activities

2. Click the Dates tab.
Scheduled tasks are displayed.
3. In the Activity Dates area, specify the following values to assign the activity:
Page 233 of 452
Using
3.
Scheduled Start Date Optionally, enter an estimated start date.
Scheduled End Date Optionally, enter an estimated end date.
You should set the start date and end date to be different from the dates of the parent release.
6.10.8 Creating activities - basic steps

The following section describes the basic steps for creating an activity.
To create a new activity basic steps

In the Initiate milestone of the Process Flow Status bar, click the arrow and choose Action > Create a
New Activity.
On the Release Management console, click Create (above the Change Requests and Activities table).
On the Manifest tab of the Release form, choose the Activity request type and then click Create.
The Activity form is displayed. The tabs you see vary according to which other applications are
installed, for example, BMC Service Level Management.
The activity initially appears in Draft status. To enable the activity from Draft status to be moved to its
next status, enter information into the following required fields.
2. (Optional) Use an activity template to fill out the contents of the activity.
Activity templates are especially useful in any activity that follows well-defined methods for specific and
repeated requirements. Activity templates do more than simply fill out fields for you; they can also include
tasks with the activity. For more information, see Selecting activity templates (see page 239).
3. In the Summary field, enter a brief description of the activity.
4. In the Detailed Description field, enter a more complete description of the activity.
5. Select the Priority to identify the importance you (as support staff) assign to the activity.
Priority indicates the relative order in which activities should be addressed. It is influenced by
considerations of risk and resource availability. The default value of the Priority field is Low.
6. In the Requester tab, enter the person creating the activity (Requested By).
When creating an activity, the Requested By information is populated automatically with the people and
group information of the person logged in. In Search mode, these fields are blank.
To modify this information, you can click in the Last Name field, enter partial information you might know
about the individual you are looking for, and then press Enter.
From the People Search dialog box that appears, select the appropriate user record, and then click Select.
The other fields in the Requested By section are filled in with information from the user's People form
record.
7. Enter the location information for the activity.
The Location Information is populated automatically with the company information of the person logged
in.
8. Complete Assignment information about the activity.
For information, see Working with activity assignments (see page 235).
9.
Page 234 of 452
Using
9. (Optional) Define work information about the activity.

For information, see Entering activity work information (
https://docs.bmc.com/docs/display/change81/Entering+activity+work+information).
10. (Optional) Create tasks associated with the activity.

For information, see Creating activity task groups and tasks (see page 229).
11. (Optional) Complete financial information associated with the activity.
For information, see Planning financial information for activities (see page 232).
12. (Optional) Plan the activity's dates.
For information, see Planning activity dates (see page 233).
13. Click Save.
6.10.9 Working with activity assignments

Your responsibility as a release coordinator is to properly assign the activity. If an assignment definition has not
been created for the activity, you must assign the activity manually. Otherwise, the best practice is to use the
assignment rules already configured for you by your Release Management administrator.
The activity assignee is then notified of activity assignments by email, pager, or BMC Remedy Alert. Assigned
activities can also be listed in the Assigned Work Orders table in the console.
Activity assignment is based on the activity's categorization. The Assignment tab displays information about
people assigned to an activity as the Request Manager or Request Assignee.
Note
You must define at least one individual with the Request Manager functional role before you can make
any assignments to a Support Group.
During configuration, the administrator determines to whom the activities are assigned. This decision is based on
criteria such as the activity's categorization. For example, all activities that are categorized as hardware issues
might be assigned to the Support-Hardware group. All activities that are categorized as software upgrades and
originate from California might be assigned to Sonya Software in Santa Clara. The criteria of the activity together
with the application administrator's configuration determines to whom each activity is assigned.
The assignee must make sure that the assignment is correct and accept the activity. If the assignment is not
correct, the request manager can reassign the request.
These assignments are based on routing information stored in the Assignment Configuration form. This form
assigns the groups and then Auto Assign assigns the individual. For more information, see Configuring
assignments (https://docs.bmc.com/docs/display/itsm80/Configuring+assignments) in the BMC Remedy ITSM Suite
documentation.
The following topics provide more information about working with activity assignments:
Page 235 of 452
Using
Assigning activities (see page 236)

Receiving notifications of activity assignments (see page 236)
Reviewing activity assignments (see page 237)
Accepting activity assignments (see page 238)
Reassigning activities (see page 238)
Assigning activities
A activity must be assigned to a Support Group. However, a specific request manager is typically responsible for
the overall activity process.
To assign activities
Based on the default configuration and requester information in the activity, certain fields might already be
filled. To assign a request manager or assignee, make selections from the Activity Assignee field.
3. If needed, you can click Clear to remove information from Activity Assignee field.
4. Enter the time spent resolving the activity.
The activity assignee is automatically notified of his assignment.
Receiving notifications of activity assignments

Request assignees are notified of new activities based on their notification method preferences defined in their
personal record. In addition, when an activity moves into a new status, for example, Completed, the activity
executes workflow that triggers notifications. Based on your group or role, you might receive notifications during
Page 236 of 452
Using
various activity states. For more information about notification preferences, see Customizing support staff
notification preferences (https://docs.bmc.com/docs/display/itsm80/Customizing+support+staff+notification+preferences
) in the BMC Remedy ITSM Suite documentation.
The available notifications are as follows:

Individual Notification An individual assignee is notified according to the notification method specified in
their personal record.
from BMC Remedy Alert for each activity that is assigned to him.
Group Notification A support group is notified according to the notification method specified by each
group member's entry in their personal record.
For example, if an activity is assigned to the Support-Software group, each group member is notified
through the notification method specified in their personal record. If Sarah Software has Email specified as
the notification method in her personal record, the notification is sent to her by email. If Bob Backline has
BMC Remedy Alert specified, he is notified accordingly.
To receive notification of activity assignment by BMC Remedy Alert

1. Log in to BMC Remedy Alert. When you or your group receives a notification that you or your group has
been assigned to an activity, the information is displayed in the BMC Remedy Alert window.
2. To evaluate your assignment, select the activity listed in the BMC Remedy Alert window.
The activity is displayed in the Activity form.
Reviewing activity assignments

A activity must be assigned to a Support Group. However, a specific request assignee is typically responsible for
the overall activity process.
To review activity assignments

Page 237 of 452
Using
Based on the default configuration and requester information in the activity, certain fields might already be
filled.
3. To assign an activity assignee, make selections from the menu options.
If needed, you can click Clear to remove information from the Activity Assignee fields.
4. Enter the time spent resolving the activity.
The request assignee are automatically notified of their assignments.
Accepting activity assignments

One responsibility for activity assignees is accepting the activities assigned to them. If an assignment definition
has not been created for the activity, you must assign the activity manually. Otherwise, the best practice is to use
the assignment rules already configured for you by your Release Management administrator.
The activity assignee is then notified of activity assignments by email, pager, or BMC Remedy Alert. Assigned
activities can also be listed in the Assigned Work Orders table in the Release Management console.
Activity assignment is based on the activity's categorization. The Assignment tab displays information about
people assigned to an activity as the Request Manager. The assignee must make sure that the assignment is
correct and accept the activity. If the assignment is not correct, the request manager can reassign the request.
These assignments are based on routing information stored in the Assignment Configuration form. This form
assigns the groups, and then Auto Assign assigns the individual. For more information, see Working with
Reassigning activities
If you cannot accept or resolve an assigned activity, you can reassign the activity to another assignee, or you can
ask your manager to reassign the activity. If the activity was categorized incorrectly, it can also be reassigned.To
reassign an activity yourself
Page 238 of 452
Using
1. Open the activity so that it is displayed in the Activity form.

2. In the Assignment tab, select the manager or assignee to whom you want to assign the activity.
3. Click Save.
The manager or assignee is notified of the reassigned activity.
6.10.10 Selecting activity templates

The Activity Template function allows you to select any templates that can be made available for your support
group. Activity templates are useful in any activity that follows well-defined methods for specific and repeated
requirements
To select activity templates

1. Create or open an activity.
2. From the navigation pane on the left side of the form, choose Quick Links > Select Template.
3. On the Activity Template Selection dialog box, click View to examine the contents of an activity template.
The template appears in read-only mode. Viewing a template lets you see its relationship, its task and task
group templates, and other important features.
Note
You cannot create, modify, or delete activity templates in the Release Management application;
you can only view them. You must use the Application Administration Console to create, modify,
or delete activity templates instead. Any member of your support group with Release Coordinator
permissions can modify activity templates for that group. For more information, see Configuring
activity templates (https://docs.bmc.com/docs/display/itsm80/Configuring+activity+templates).

The contents of the template are applied to the activity. The activity template overwrites any field values
that are already present in the activity. If the activity already includes tasks, these are not overwritten. Any
additional tasks from the template are added as peers.
6.10.11 Activity statuses

You can define multiple activities for a particular milestone. Each activity can go through the multiple statuses.
The status of an activity can be updated either manually or by an action performed on the activity.
An activity can go through the following statuses:
Draft When an activity is created, it is in the Draft status.
Assigned When the activity is assigned, it moves to the Assigned status.
Page 239 of 452
Using
Pending If the activity is not assigned, it moves to the Pending status. It can be moved to the Pending
status for any reason, such as pending for information.
In Progress When work on the activity is started, the activity status to In Progress.
Completed When work on the activity is completed, change the activity status to Completed. The actual
start dates and actual end dates must be entered before the status is changed to Completed.
Note
An activity with a status of Completed can be reopened by changing the status to Pending.
Cancelled If for some reason the activity is cancelled, change the activity status to Cancelled.
Closed When the work on an activity is completed and you want to close the activity, change the activity
status to Closed. Once the activity status is set to Closed, the activity cannot be reopened.
The following table describes the valid status transitions for an activity:
Status to which the activity can be transitioned
Draft
Assigned
Pending
In Progress
Completed
Cancelled
Closed
Draft
NA
Yes
No
No
No
Yes
No
Assigned
No
NA
Yes
Yes
No
Yes
No
Pending
Yes
Yes
NA
Yes
No
Yes
No
In Progress
No
No
No
NA
Yes
Yes
No
Completed
No
No
Yes
No
NA
No
Yes
Cancelled
No
No
No
No
No
NA
Yes
Closed
NA
NA
NA
NA
NA
NA
NA
Before you can complete the request release, all activities must be closed, completed, or cancelled.
Note
You can define multiple tasks for each activity. The out-of-the-box settings define that tasks are
activated in the sequence assigned to them. All tasks with sequence number 1 are activated when the
activity record reaches the Assigned status. The status of the activity can be changed to Completed
when all tasks defined for that activity are closed. You cannot complete an activity if all the tasks
associated with that activity are not completed.
Page 240 of 452
Using
Configuration settings for activating tasks can be modified by modifying the Activity status for Activation field on
the Configure Activity Rule form. For more information on configuring activities, see Configuring activity rules (
https://docs.bmc.com/docs/display/change81/Configuring+activity+rules).
6.10.12 Release task status transitions

This section describes the statuses that a task goes through during its life cycle. After you begin working on a task
you must manually update the status of the task depending on the work done related to that activity. You have
the option to define multiple tasks for an activity.
To define the order in which tasks or task groups should be executed you can use sequence numbers. Multiple
tasks can have the same sequence number. This sequencing mechanism saves time by eliminating the need to
manually define the flow between tasks or task groups.
For more information about defining a sequence for tasks, see Sequence number in task groups and tasks (see
page 307).
Note
If the parent activity is canceled, all related tasks are closed.
Release Task Status Transition
Page 241 of 452
Using
Task status transitions

1. When the parent activity is moved to the In Progress status, tasks are activated in the sequence assigned to
them. For example, all tasks with sequence number 1 are activated first. When all tasks with this sequence
number are Closed, all tasks with the next sequence number are activated simultaneously.
2.
Page 242 of 452
Using
2. After the task is activated:

If assignments are defined for that activity, the task moves to the Assigned state.
If assignments are not defined, the task moves to the Pending state. After assignments are defined, it
moves to the Assigned state.
3. When you start working on the task, you need to change the task status to Work in Progress.
If you require additional information, change the status to Pending. When the required information
in provided, update the status to Work in Progress.
If you choose not to perform a particular task, you can change the status to Bypassed. This can also
be done in an automated fashion depending on your needs.
4. After the task is completed, change the task status to Closed.
5. If multiple tasks are defined for the activity, when you close all tasks with the same sequence number, all
tasks with the next sequence number are activated. After all the tasks within an activity are completed,
status of the activity is changed to Completed. When all the activities defined for a milestone are
completed, the release record can be moved to the next milestone.
6.11 Working with release request financial information Rolling up costs

Risk, time, and costs (actual and budget) from activities and change requests that are related to the release
manifest are rolled up on the Financials tab.
For activities, only the time spent, and the actual and budget costs, are rolled up to the release.
For change requests, in addition to time spent and costs, the highest Risk Level is also rolled up to the
release.
6.11.1 To roll up costs

Click Links > Financials.
Release form Financials tab
Page 243 of 452
Using
Based on the changes and activities displayed in the release manifest, the Release Costs table shows the
costs associated with the release, and rolled-up costs from the related activities or change requests.
For more information, see Working with release manifests (see page 224).
3. Click Add to attach costs to the release.
Note
If you attach a cost entry to the release you are working on, the Release Costs table does not list a
related request ID.
4. Filter the release costs by selecting from the Cost Category field.
The default (the Cost Category field is cleared) displays all entries. Otherwise, select Infrastructure Change,
Release, or Activity to display costs associated with those entries.
5. Filter the release costs by selecting from the Show field.
All Cost Types (the default value) displays all release and rolled-up costs.
6. (Optional) Click View to view the costs associated with the release, or click Delete to remove them.
Note
You can only delete Release costs from the Financials page of the Release form.
Page 244 of 452
Using
6.12 Working with release request assignments

One responsibility for release coordinators is creating the release request assignments. They can be assigned
manually or automatically. If an assignment definition has not been created for the Release Management
application, you must assign the release manually. For information on assigning the release manually, see
Automatically assigning release requests (see page 248).
The release assignee is then notified of release request assignments by email, pager, or BMC Remedy Alert.
Assigned release requests can also be listed in the Release Information table in the console.Release requests are
assigned automatically on creation by the Release Management application. The assignment is based on the
release request's categorization.
The Assignment tab displays information about people assigned to a release as the Release Coordinator The time
spent resolving activities or change requests is automatically rolled up into the release. Separate Time Spent
(Classic view) and Time Information fields display the total time spent (in minutes) for the activities and the
change requests related to the release.
Assigning releases and tracking time spent
Page 245 of 452
Using
Note
You must define at least one individual with the Release Coordinator functional role before you can
make any assignments to a Release Coordinator support group.
During configuration, the application administrator determines to whom the release requests are assigned. This
decision is based on criteria such as the release request's categorization. For example, all release requests that are
categorized as hardware issues might be assigned to the Support-Hardware group. All release requests that are
categorized as software upgrades and originate from California might be assigned to Sonya Software in Santa
Clara. The criteria of the release request together with the application administrator's configuration determines to
whom each release is assigned.The release coordinator must make sure that the assignment is correct and accept
the release request. If the assignment is not correct, the release coordinator can reassign the request.
Page 246 of 452
Using
6.12.1 Reassigning release requests

If you cannot work on an assigned release request, you can reassign it to another release coordinator.You can
also reassign the release request if it was categorized incorrectly.
Release coordinators are responsible for responding to reassignment requests. When a release coordinator
reassigns a release request to another coordinator, the person is notified. Upon reviewing the release, the
coordinator can reassign the release to another qualified release coordinator.
Note
You must set a notification rule and define a milestone for it to enable the notification workflow. For
more information on setting notification rules, see Configuring notification rules (
https://docs.bmc.com/docs/display/change81/Configuring+notification+rules).
To reassign or respond to release reassignment requests

1. Open the Overview Console or the Release Management console.
All reassignment requests appear in the table along with other release requests.
Recommendation
Regularly monitor your assigned work to track any release requests reassigned to you.
2. Select the appropriate release request.

3. Click View. After reviewing the release request, you can manually reassign the release coordinator.
4. To reassign the release request, perform one of the following actions:
Select the Release Coordinator on the Release form.

a. Click the Assignment tab.
b. Select the Release Coordinator to whom to reassign the request.
c. Select an assignment method (for example, Auto Assign), and then click Set.
To deny the reassignment request, you must reassign it to another release coordinator.
5. Click Save.
If you reassign the release request, the new assignee is automatically notified of the changed assignment.
Related topic
Assigning release requests (see page 248)
Page 247 of 452
Using
6.12.2 Automatically assigning release requests

You can automatically assign the release request use the Auto Assign option from the Set Assignment using
menus. Assigning the release coordinator using Auto Assign uses the requester's information, the Release
Location information, and the Operational and Product Categorization information about the form to determine
an assignment match.
These assignments are based on routing information stored in CFG:Assignment form. The CFG:Assignment form
assigns the groups and then Auto Assign assigns the individual. For more information, see Working with
6.12.3 Assigning release requests

The release coordinator is typically responsible for the overall release process.
To assign release requests using the Best Practice view

release request. For example, the Release Coordinator field already has an assignment.
2. To assign a release coordinator, select the appropriate option:
Coordinator Group Provides a list of coordinator groups. Select the group of the release
coordinator you want to assign the release to.
Groups that have at least one user with the Release Coordinator functional role are listed for
selection.
Release Coordinator Provides a list of users with the functional role of a Release Coordinator in
the selected coordinator group. Select the appropriate release coordinator from this list.
3. Save the release request.
The release coordinator is automatically notified of the assignment.
To assign release requests when using the Classic view

Based on the default configuration and requester information in the release request, certain fields are
already filled. For example, the Release Coordinator field already has an assignment.
3. To assign a release coordinator if none is assigned, select Auto Assign from the Set Assignment Using field
and then click Set.
4. To assign a release coordinator, use one of the following options and then click Set:
My Default Group Assigns the release to you and your default group
this list.
Favorite Groups Assigns the release to the typical groups to which your support group assigns
requests
Page 248 of 452
Using
Auto Assign Automatically assigns the request based on predefined mapping

Release Coordinator Assigns the release to you
To be eligible as the release coordinator, a user must have the Release Coordinator functional role.
Groups that do not have a user with one of these roles are not available for selection in the Release
Coordinator field.
5. Save the release request.
The release coordinator is automatically notified of the assignment.
6.12.4 Receiving notifications of release request assignments

Release coordinators are notified of new release requests based on their notification method preferences defined
in their personal record. The available notifications are as follows:
Individual Notification A release coordinator is notified according to the notification method specified in
their personal record.
from BMC Remedy Alert for each release request that is assigned to him.
Group Notification A release coordinator group is notified according to the notification method
specified by each group member's entry in their personal record.
For example, if a release request is assigned to the Support-Software group, each group member is notified
through the notification method specified in their personal record. If Sarah Software has Email specified as
the notification method in her personal record, the notification is sent to her by email. If Bob Backline has
BMC Remedy Alert specified, he is notified accordingly.
To receive release assignment notification by BMC Remedy Alert

1. Log on to BMC Remedy Alert as a Support staff member.
2. When you or your group receives a notification that you or your group has been assigned to a release
request, the information appears in the BMC Remedy Alert window.
3. To evaluate a release, select the release request listed in the BMC Remedy Alert window.
The release request appears in the Release form. For more information, see Setting application preferences
(https://docs.bmc.com/docs/display/change81/Setting+application+preferences).
6.12.5 Updating assignment availability

Your assignment availability status indicates whether you are available to accept work assignments. If your status
is Yes, you are available. If your status is No, you are not available.
You can quickly update your status using the My Profile function.
Note
Page 249 of 452
Using
If you have management level permissions, you can also update the status of the people in the support
group that you manage.
To update assignment availability

1. To open your profile, from the navigation pane in the Release Management console, choose Functions >
My Profile.
2. From the Assignment Availability menu, choose the status you want.
3. Click Save.
6.13 Sending release or activity notifications

When a release request moves into a new Milestone and Status, for example, Deployment In Progress, Release
Management generates notifications. Based on your assignee group or role (release coordinator or requester),
you might receive notifications during various status transitions.
Release notifications are data-driven and easily configured. The following notifications are enabled out of the
box. Your administrator might have created additional notification rules.
Milestones and statuses when notifications are sent
Milestone
Status
Release Coordinator
Assignee Group
Requester
Initiate
Draft
Yes
No
Yes
Deployment
Deployment Approval
Yes
No
Yes
Deployment
In Progress
Yes
Yes
Yes
Deployment
Cancelled
Yes
Yes
Yes
Activities work the same way, except that no out-of-the-box notifications are enabled. Your administrator can
easily configure a rule in which, for example, the activity assignee is notified when the Status of the activity is set
to Draft.
For more information, see Receiving notifications of release request assignments (see page 249). For more
information about notification rules, see Configuring notification rules (
https://docs.bmc.com/docs/display/change81/Configuring+notification+rules).
6.14 Monitoring the progress of a release request

As a release request is being worked on, you can follow its progress by viewing the information by one of the
following methods:
Page 250 of 452
Using
On the Work Detail tab, select the Work Info from the table and then click View.
1. Click the Work Info tab on the Release form.
2. Select the Work Info from the table and then click View.
For example, during its Deployment milestone, you can follow the progress of the tasks as they are being
completed.
To view the progress of a release request when using the Best Practice view (see page 251)
To view the progress of a release request when using the Classic view (see page 252)
6.14.1 To view the progress of a release request when using the Best
Practice view
The release request form displays details about the release assignments, target date, status, next approval
phase, potential risks, and whether the release request has been escalated.
2. View progress details of the release request by clicking the appropriate tab.
Tab
Description
Work Detail
Review the current stage in the approval process for the release request, including the next approval phase.
Note: The Work Detail tab is displayed when you open the Release form.
Manifest
View and create associations to activities and change requests.
Relationships
View and create associations between releases and other application objects (example - incidents, known errors, changes,
problem investigations, software library items, LDAP objects, CI unavailability and configuration items, and other releases).
Date/System
View the planned dates, information related to who and when the release request was submitted and by who and when the
release request was last modified.
SLM
3. View additional details by clicking the appropriate links.

Link
Description
Categorization
View the timing of the release request and its categorizations.
Financials
4. Close the Release form.
Page 251 of 452
Using
6.14.2 To view the progress of a release request when using the Classic
view
The top part of the release request provides information about the status, next approval phase, potential
risks, and whether it is escalated.
2. View progress details of the release request by clicking the appropriate tab.
Tab
Description
General
View who requested the release request and who is assigned to the request. When the release request was created, it was
Classification
View the timing of the release request and its categorizations.
Work Info
View information about each step in the process written in the work information history area.
Manifest
View and create associations to activities and change requests.
Assignments
View who is assigned to the release request as the release coordinator.
Relationships
View or create associations between releases and other application objects (example - incidents, known errors, changes,
problem investigations, software library items, LDAP objects, CI unavailability and configuration items, and other releases).
Approvers
Review the current stage in the approval process for the release request, including the next approval phase.
SLM
Financials
Dates
View the planned dates.
3. Close the Release form.
6.14.3 Managing release effort logs

You can update the effort log to track your effort.
To manage effort log

1. From the release request, choose Functions > Track Effort.
2. Update any of the assessment type information and the time spent.
3. To update assignee effort duration, select an entry and enter the time spent in hours or minutes.
4. To delete the effort log, select an entry and click Delete.
5. Click Save.
Note
Page 252 of 452
Using
You must be the release coordinator to modify the effort time.
6.14.4 Tracking efforts for a release record

The Effort log displays a list of all individuals who have worked on the release during its lifecycle.
Note
Entries in the effort log are not system-generated, so you must enter them manually. The list is not in
chronological order.
To track efforts
2. Choose Functions > Track Effort.
3. Fill in the Select an Assignee fields.
This information is required to select the individual for whom the effort log is being created.
4. Fill in the Select Effort Classification fields.
This information is required to show what kind of effort is being logged, for example, actual
implementation activity.
5. Fill in the Enter Effort Time Spent fields.
This information records where the time was spent.
Note
As needed, you can adjust the time spent in the Update Assignee Effort Duration section. For
information, see Managing release effort logs (see page 252).
6. Click Add, and then click Close.
6.15 Modifying release requests

This section describes how modify the release request status when moving through the release request lifecycle.
Moving the release forward (see page 254)
Performing additional functions from the Process Flow Status bar (see page 255)
Page 253 of 452
Using
6.15.1 Moving the release forward

As you track and supervise a release request, you move it from one milestone to another (for example, from
Initiate to Planning). When you choose different milestones, messages alert you if you need to complete more
fields in the request.
Note
A request should follow the milestones in the recommended lifecycle of a release request, as described
in Milestones in the release request lifecycle (
https://docs.bmc.com/docs/display/change81/Milestones+in+the+release+request+lifecycle). Manually setting
the status values can disrupt the lifecycle in which you enter information about and resolve the release
request.
To modify release requests

2. On the Release form, make the appropriate changes.
3. (Optional) Add manifests to the release request.
For more information, see Creating a manifest (see page 200).
4. (Optional) Modify the release request assignments.
For more information, see Working with release request assignments (see page 245).
5. (Optional) Relate a CI or some other object to the release request.
For more information, see Working with release relationships (see page 265).
6. (Optional) Modify the start and end dates of the release request.
For more information, see Planning milestone - Planning and scheduling the release request (see page 206)
.
7. Save your work.
8. Use the Process Flow Status bar to move the release request forward to the Initiation Approval phase.
For more information, see Performing additional functions from the Process Flow Status bar (see page 255)
.
Note
Out of the box, release requests must be approved before they move to the Planning milestone.
For more information, see Working with BMC Change Management as an approver (see page 133)
and Approval processes provided out-of-the-box for Release Management (see page 213).
9. After the release request is approved, use the Process Flow Status bar to move the release request forward
to the Initiation Registered status.
10.
Page 254 of 452
Using
10. Use the Process Flow Status bar to move the release request forward to the Planning Approval phase. The
release must be approved before it can move forward. For more information, see Planning milestone Planning and scheduling the release request (see page 206).
6.15.2 Performing additional functions from the Process Flow Status bar
You can perform the following functions from the Process Flow Status bar:
Additional functions from the Process Flow Status bar
Function
Action
Move to next status or

milestone
In the Process Flow Status bar, click the arrow on the green status and select Next Stage.
The Change or Release moves to the next status or milestone.
Move the Change or Release

to Pending status
1. In the Process Flow Status bar, click the arrow on the green status and select Enter Pending.
2. Select appropriate status reason (for example, Manager Intervention).
3. Select Resume from the Process Flow Status bar when you are ready to continue work on the request.
Return to earlier status or

milestone
1. In the Process Flow Status bar, click the arrow on the green status and select Back.
2. Select the milestone you want to return to, for example, Initiate.
Note: If you use the Back option to move the request to a previous stage or milestone, all required approvals
defined for any stage that is repeated must be performed again.
Cancel a change or release

request
1. In the Process Flow Status bar, click the arrow on the green status and select Cancel.
2. Select appropriate status reason, for example, Resources Not Available. The Change or Release moves to the
Completed or Close Down milestone.
View process flow help
In the Process Flow Status bar, click the arrow on the green status and select Help.
The process flow help is displayed (if it is installed).
Page 255 of 452
Using
7 Working with relationships

Change requests (and release requests) can affect and can be affected by configuration items (CIs) and other
types of records (changes, releases, incidents, or problems). By defining these relationships, you can define a
more sophisticated overview of the connections and interdependencies between the current request and other
service issues being tracked by your system.
Note
This information about relationships applies equally to release requests. Where exceptions exist, these
are noted.
Change requests can be affected by incidents, problems, and so on. BMC Change Management enables you to
define relationships between change requests and other types of requests if the appropriate application has been
installed.
Note
The options described in the table below will vary based on the BMC Remedy ITSM applications installed
on the server.
Request type
related to
Description
change
request
Other change
requests
When you work with a change request, you can define related requests that address similar issues. For example, a set of related
requests can result from many change requests sent to the service desk by one requester. A set of related requests can also result
from a single request that encompasses several other requests.
You can create a series of dependent change requests, where one must be completed before another request can be started, for
example, a change request to upgrade Microsoft Outlook on the email server that has a Dependent relationship to a change request
to upgrade the operating system. For more information, see Creating related change requests (see page 165) and Relating change
requests (see page 166).
Configuration
items
When you work with a change request, you can view a related configuration item (CI). For example, you might be working with a
desktop system that consists of a laptop, mouse, keyboard, and docking station. The CI has information about the specific type of
these CIs. For more information, see Working with related configuration items (see page 176).
Unavailability
of
configuration
items
When you work on a change request that requires a configuration item that would be unavailable when in use for the change
request, you can view a related CI Unavailability. For more information, see Creating CI unavailability (see page 275).
LDAP objects
Page 256 of 452
Using
Request type
related to
Description
change
request
When you work with a change request, you can view related LDAP objects. For example, you might want to relate a change request
to an LDAP server where all the permission rights are stored to enable seamless authentication with Policy Manager. For more
information, see Performing additional functions with relationships (see page 272).
Release
When you work with a change request, you can view or create release requests. Releases can be related to a change request (in the
Relationships tab, or contain the change request in the Release manifest. For example, you might want to create a release request
and include the change in the Release manifest. For more information, see Working with release manifests (see page 224).
Software
library items
When you work with a change request, you can view related storage locations, for example, different versions of Microsoft Office
along with their license contracts. For more information, see Performing additional functions with relationships (see page 272).
Asset
configuration
When you work with a change request, you might need to work with a related asset configuration. For example, if you are working
on a change request involving a monitor, relate the change to the monitor. You might also want to temporarily assign another
monitor to the requester because work is being done on the original monitor. In this case, you can relate the change request to
both monitor asset records. To perform this procedure, BMC Asset Management must be installed and integrated.
Incidents and
problems
When you work with a change request, you might need to relate incidents and problems. If a change request for a server upgrade
results in connection problems for the people affected by the change, for example, you can relate their incident to the server
upgrade change request as you open the cases. This relationship can provide helpful information to the support staff working on
resolving the incident. To perform this procedure, BMC Incident Management must be installed and integrated. For more
information, see Viewing change dependencies (see page 166). For problem and known error investigation, BMC Problem
Management must be installed.
Projects
A change request can be a part of a larger project. This relationship provides information about the project to which the change is
related. To view this option, BMC IT Business Management Suite must be installed and integrated.
Currently, you cannot relate a change request to a Project from the Change form.
For more information about relationships and request types, see Related request types for BMC Change
Management and Release Management (see page 258).
7.1 Leveraging the power of relationships (video)

Disclaimer
not current.
!common:_graphicsLibrary^video_icon.png! (
View video on YouTube (
http://www.youtube.com/watch?v=HFJ1eL38b30)
http://www.youtube.com/watch?v=HFJ1eL38b30)
Page 257 of 452
Using
7.2 Related request types for BMC Change Management and

Release Management
The Relationships tab shows the relationships between the current change request to CIs and to other modules
inside BMC Change Management.
You use request types to define these relationships. The following table displays a list of request types to which
you can relate changes (or releases) and their available actions, along with their start and end dates. The list varies
depending on the other BMC Remedy ITSM applications you have installed with BMC Change Management.
Note
The Start date and End date values are not displayed in the Best Practice view.
Related request types to Change and Release Management modules

Request type
Actions
Relationship type
Start date
End date
More information
CI Unavailability
(Asset
Management)
Search Opens the CI Unavailability

Relationships Search form to search for
an unavailable CI, and then relate it to the
release.
Related to
Scheduled
Start Date
Scheduled
End Date
See Creating CI
unavailability (see
page 275).
Actual Start
Date
Actual End
Date
Not
applicable
Not
applicable
View Opens the CI that is related to the

release
Remove Removes the CI from the
relationship with the release; it does not
delete the CI
Configuration
Item
Search Opens the CI Relationships

Search form to search for a CI, and then
relate it to the change or release
Related to
View Opens the CI that is related to the

change or release
Installs
Upgrades
Repairs
Remove Removes the CI from the
relationship with the change or release; it
does not delete the CI
See Working with

related
configuration
items (see page
176).
For more
information about
the relationship
types, see CI
relationship types
(see page 260).
Removes
Impacts
Moves
Changes
Project (If BMC

Remedy IT
Not applicable
Not
applicable
Not
applicable
Not applicable
Page 258 of 452
Using
Request type
Actions
Relationship type
Start date
End date
More information
Business
View Opens the Project summary form
Management is
installed)
that displays details of the Project to

which the change is related
Incident (If BMC

Incident
Search Opens the Incident Relationship

Search form to search for an incident,
Related to
Reported
Date
Responded
Date
See Performing
additional
Management is
installed)
and then relate it to the change or release
Caused
functions with
relationships (see
Create Opens the Incident form in New

mode
Corrects
page 272).
View Opens the incident that is related

to the change or release
Remove Removes the incident from
the relationship with the change or
release; it does not delete the incident
Infrastructure
Change
Search Opens the Change Relationship

Search form to search for a change, and
then relate it to the change or release
Dependent
Create Opens the Change form in New

mode
For more information about

these relationship types, see
Relating change requests (see
page 166).
View Opens the change that is related

Scheduled
Start Date
Scheduled
End Date
Actual Start
Date
Actual End
Date
Problem
Reported
On
Workaround
Determined
On
Corrective
Action
Determined
Infrastructure
Chg Initiated
Not
applicable
Not
applicable
Related to
See Creating
related change
requests (see
page 165).
Remove Removes the change from the

relationship with the change or release; it
does not delete the change
Known Error (if
BMC Problem
Management is
installed)
Search Opens the Known Error or

Solution Search form to search for a
known error, and then relate it to the
change or release
Related to
Initiated by
Create Opens the Known Error form in

New mode
See Performing
additional
functions with
relationships (see
page 272).
View Opens the known error that is

related to the change or release
Remove Removes the known error
from the relationship with the change or
release; it does not delete the known
error
LDAP Object
Search Opens the LDAP Search form to

search for an LDAP item, and then relate
it to the change or release
View Opens the LDAP item that is
Not applicable
See Performing
additional
functions with
relationships (see
page 272).
Page 259 of 452
Using
Request type
Actions
Relationship type
Start date
End date
More information
Related to
Problem
Reported
Workaround
Determined
See Performing
additional
On
On
functions with
relationships (see
Known
Error
Solution
Created
page 272).
Create Opens the Problem

Investigation form in New mode
Created
Scheduled
Start Date
Scheduled
End Date
Deployment
Start Date
Deployment
End Date
See Searching for

request types and
establishing the
relationship type
(see page 264).
Not
applicable
Not
applicable
Remove Removes the LDAP item from

release; it does not delete the LDAP item
Problem
Investigation
Search Opens the Problem

Relationship Search form to search for a
(Problem
Management)
problem, and then relate it to the change

or release
View Opens the problem that is related

Remove Removes the problem from
release; it does not delete the problem
Release
Search Opens the Release Relationship

Search form to search for a release
request, and then relate it to the change
or release
Related to
Member of
Create Opens the Release form in New

mode
View Opens the release request that is
Remove Removes the release request
release; it does not delete the change or
release
Software Library
Item
Search Opens the Software Library

Item Search form to search for an Storage
Location, and then relate it to the change
or release
Not applicable
See Performing
additional
functions with
relationships (see
page 272).
View Opens the Storage Location that

is related to the change or release
Remove Removes the Storage Location
release; it does not delete the Storage
Location
7.3 CI relationship types

When you work with a change request, you can view a related configuration item (CI). This section lists the
relationship types available when defining a relationship between a Configuration Item and a Change Request.
Page 260 of 452
Using
When defining a relationship between a Configuration Item and a Change Request, the following options are
available:
Related to Relates the item or request to the Change Request
Upgrades Upgrades the item or items as part of the Change Request process
Repairs Repairs the items or items as part of the Change Request process
Impacts Impacts the item that as part of the Change Request process
Moves Moves an item from one location to another location as part of the Change Request process
Installs Installs the item as part of the Change Request process
Removes Removes an item from the location as part the Change Request process
Changes Changes items as part of the Change Request process
These options are for information purpose which can be used while reporting. You have the option to use them
based on the organizational requirements and processes.
7.4 Defining relationships

You use request types to define relationships. To view a list of request types to which you can relate releases and
their available actions, along with their start and end dates, see Related request types for BMC Change
Management and Release Management (see page 258). The list varies depending on the other BMC Remedy ITSM
applications installed with BMC Change Management.
7.4.1 To define a relationship when using the Best Practice view

1. Open the change or release request.
2. In the Quick Action area, click the arrow beside Create Relationship to.
3. From the menu, select the type of record to which you want to relate the current record.
4. In the Search field of the dialog box that opens, type a search string.
Note
The keyword search is available only when BMC Knowledge Management is installed with BMC
Remedy IT Service Management. If BMC Knowledge Management is not installed, the Advanced
Search is displayed. If the Advanced Search is displayed, in the search window for the request
type, enter information about the search criteria tabs, and then click Search.
For example, if you are creating a relationship to an incident request about a printer that regularly goes
off-line, you might type printer off line.The search scans multiple fields in each record looking for a match,
and returns a list of records that contain any of the words - printer, off, or line in one of the scanned fields.
Page 261 of 452
Using
Note
The type of search dialog box that appears depends on the type of record you chose from the
menu. Try to supply as much information as possible in each type of search to reduce the overall
number of records returned by the search. If, after using a more specific search string, the search
returns too many records, consider using the advanced search. To do this, click Use Advanced
Search, which opens a form in search mode that is relevant to the type of relationship you are
making.
5. From the search results table, select the specific record to which you want to create the relationship.
6. From the Relationship Type list at the bottom of the search dialog box, select the type of relationship you
want to create.
7. Clicking Relate to create the relationship.
Note
The specific list for Select a Relationship Type depends on the type of relationship you are
creating. For example, if you are creating a relationship with another change request record, the
list includes Related to, if you are creating a relationship with an incident request record, the list
includes Related to, Caused, and Corrects. If you are creating a relationship with a known error,
there are two relate buttons: Initiated by and Related to, and so on.
8. Close the search dialog.

The related request types and relationship types appear in the Relationships table. To refresh the table,
click Refresh from the right-click menu.
7.4.2 To define relationships when using the Classic view

1. Open the change or release request from which you want to define the relationship, and then click the
Relationships tab.
2. From the Request Type list, select the type of record you want to relate the current record to.
You can relate a request to any of the options listed in the Request Type field, for example, Infrastructure
Change. For more information on these options, see Related request types for BMC Change Management
and Release Management (see page 258).
Note
For specific instructions on CIs, see Relating configuration items to change requests (see page
176).
3.
Page 262 of 452
Using
3. Click Search to search for a request type or Create to create a new request.
If you create a new change request, the request is automatically related to the change request when you
save it.
4. In the Search field of the dialog box that opens, type a search string. For example, if you are creating a
relationship to an incident request about a printer that regularly goes off-line, you might type printer off
line. Try to supply as much information as possible in each type of search to reduce the overall number of
records returned by the search.
Note
The type of search dialog box that appears depends on the type of record you chose from the
menu.
The search scans multiple fields in each record looking for a match, and returns a list of records that
contain any of the words - printer, off, or line in one of the scanned fields.
Note
If, after using a more specific search string, the search returns too many records, consider using
the advanced search. To do this, click Use Advanced Search, which opens a form in search mode
that is relevant to the type of relationship you are making.
5. From the search results table, select the request with which to define the relationship.
6. From the Select a Relationship Type list at the bottom of the search dialog box, select the type of
relationship to define.
7. Click Relate, and then click OK.
Note
The specific text on the relate button depends on the type of relationship you are creating. For
example, if you are creating a relationship with another change request record, only the Related
to button is displayed. If you are creating a relationship with an incident request record, there are
three buttons: Related to, Caused, and Corrects, if you are creating a relationship with a known
error, there are two relate buttons: Relate With Solution and Relate Without Solution, and so on.
8. Click OK.
9. Close the search window.
The related request types and relationship types appear in the Relationships table. To refresh the table,
click Refresh from the right-click menu.
Page 263 of 452
Using
7.5 Searching for request types and establishing the

relationship type
You can search for a request type (for example, Release or Infrastructure Change) and then establish a
relationship (for example, Related to) to the release.
To search for releases to relate to the current release, use the following criteria:
Release relationship searches
Search type
Criteria
Basic Search
Basic fields on the change or release form.

You can also perform advanced searches.
Categorization Search
Product and Operational Categorization fields, available in Advanced Search options.
Role based search
Support company, location or user login details based on the user role.
Date and Location
Location and date fields.
7.5.1 To search for request types and establish the relationship type
1. Open the change or release request from which to define the relationship, and then click the Relationships
tab.
2. From the Request Type list at the bottom of the Relationships tab, select the type of application object to
which to relate the current request.
3. In the search window for the request type, click the Use Advanced Search link and complete the search
criteria tabs with the relevant query information (for example, the Deployment Type), and then click Search
.
The search form appears.
Note
The contents of the search form depend on the type of application object you chose in the
Request Type list.
Release Relationship Search form (Advanced Search example)
Page 264 of 452
Using
Tip
Supply as much information as possible in the search dialog box to reduce the overall number of
records returned by the search. Matching results appear in a search results table.
4. From the search results table, select the request with which to create the relationship.
5. From the Relationship Type list at the bottom of the search dialog box, select the type of relationship to
create (for example, Related to).
6. Click Relate, and then click OK to close the confirmation dialog box.
The search window closes automatically. The related request is displayed in the Relationships table. To
refresh the table, right-click in the table and select Refresh All in Table.
7.6 Working with release relationships
Page 265 of 452
Using
You can use the Relationships tab to create associations between releases and other application objects, for
example, CI unavailability, configuration items, incidents, infrastructure changes, known errors, LDAP objects,
problem investigations, other releases, and software library items. Relating application objects (such as CIs) to the
release request lets you identify items that the Release Coordinator plans to address in the release.
The relations in a release request are informational only, and are not required to be part of any milestone of the
release request. In addition, the application objects do not have to be Completed or Closed for this release to be
Closed.
For more information on creating a relationship, see Defining relationships (see page 261).
Note
Change requests or activities that are necessary to implement and close the release are added as release
manifests. These are tied to a milestone of the release and must be completed during that milestone for
the release to move to the next stage. For more information, see Creating a manifest (see page 200).
Release form Relationships tab
Page 266 of 452
Using
For more more information, see Working with relationships (

https://docs.bmc.com/docs/display/change81/Working+with+relationships). The information about relationships in the
context of change requests applies equally to release requests. Where exceptions exist, these are noted.
7.7 Viewing the impact of CIs on change requests

You can relate configuration items (CIs) to change requests, based on a simulated impact analysis generated by
the Atrium Impact Simulator tool. Additional workflow in BMC Change Management lets you use Atrium Impact
Simulator functionality to predict how a change to the availability of a CI affects other CIs and services. For
Page 267 of 452
Using
example, you could run a simulation in Atrium Impact Simulator to learn what devices and applications in the
network are affected if you take a specific server offline due to scheduled maintenance or lease returns.
Atrium Impact Simulator is transparently integrated into other BMC applications as an integral part of their
workflow. From BMC Change Management, Atrium Impact Simulator exposes only the features required for the
user, simplifying the user experience.
For more information, see Atrium Impact Simulator analysis for change requests (
https://docs.bmc.com/docs/display/change81/Atrium+Impact+Simulator+analysis+for+change+requests).
Note
The Impact Analysis functionality is not available on the Relationships tab of the Release form.
7.7.1 To view impact of CIs on change requests

2. Relate at least one CI to the request.
You can layer multiple requests for different types of CIs and add to the impacted list. You can use any
Relationship Type except Impacts.
3. In the Relationships tab, click Impact Analysis.
Note
The Impact Analysis button is enabled only for CIs that belong to Production Data Set (PDS).For
more information on PDS, see Relating CIs to alternate datasets (see page 273).
The Atrium Impact Simulator opens.
Page 268 of 452
Using
4. Click Simulate Impact to run the simulation.

In the Simulation Progress dialog box, you can click the Cancel button to stop a long running simulation (if
needed).
5. Click the Results in Table tab.
A list of impacted CIs are listed and also the number of results is displayed in the header bar.
6. To relate the results to the change request, you can perform the following actions:
Note
Running an impact simulation does not relate the results automatically to the change record. You
must click Execute to select the results that should be related.
Action
Result
Set the Relate

column to Yes or
No.
By default, the change results are defaulted to Yes for relate. Using the column relate, you can individual toggle the
action to No or Yes for granular control. These can be set as a group, using Execute options.
Show Only
Services (click to
toggle)
Lists only impacted service CIs in the view. This action has no effect on relating.
Show All Results

(click to toggle)
Lists all impacted CIs in the view. This action has no effect on relating.
Page 269 of 452
Using
Action
Result
Pick list and
These options modify the relate options. They provide a quick way to select groups of CIs to relate or unrelate. You can
Execute button
select from the following options:

Relate All Relates all CIs and services from the change request
Unrelate All Unrelates all CIs and services from the change request
Relate All Services Relates only services to the change request
Unrelate All Services Unrelates only services from the change request
Relate Selected Based on the CIs or services you pick, relates them to the change request
Unrelate Selected Based on the CIs or services you pick, unrelates them from the change request
Click Report
Runs a report that exports all the fields in the simulation. This report can export all fields that are in the new .csv file or
any subset of them.
The report file, which is attached to the change request, provides a history that can be referenced in the future.
Click Cancel
Exits the window without make any changes
Click Save
Creates the CI relationships between the change request and the selected CIs. The CIs are now displayed in the
Relationships tab. Work information is created for the change request, along with a simulation .csv file attached.
7. Click Close to create the CI relationships between the change request and the selected CIs.
The CIs are now displayed in the Relationships tab. Work information is created for the change request,
along with a simulation .csv file attached.
7.8 Copying relationships

When you define a relationship between the current change and another change, the other change request might
also have one or more changes related to it. On the Relationships tab opened from the Copy Related
Relationships form, you can see the related change's other relationships. If you determine that any of these other
relationships need to be related to the current change, you can define the relationship from this form.
By doing this, you can more thoroughly document the change relationships.
7.8.1 To copy relationships

2. Select a change related to the current change.
3. From the Quick Actions list, select Get Related Relationships, and then click Execute.
The Copy Related Relationships form appears, containing a table of all other records related to the record
you selected in Step 2.
4. From the table of related items, select the other items to relate to the current change.
Note
To see a detailed description of an item in the table, select it, and then click View. Use this feature
to help determine whether to relate the other item to the current change.
Page 270 of 452
Using
5. In the Relationship Type field, select the type of relationship to define, and then click Select.
Note
The contents of the Relationship Type list depends on the type of related item you are using to
define the relationship.
The newly created relationship appears in the Relationships table. For more information, see Performing
additional functions with relationships (see page 272).
7.9 Viewing relationships

You can limit which relationships shown with the current change record. You can also limit the list of associated
relationships by selecting Show Related <option>, for example, to see only Known Errors.
7.9.1 To view relationships

3. To view a specific request type, choose it from the Show Related field.
The list varies depending on the other applications you have installed with BMC Change Management.
Relationship
Description
ALL
Shows all related assets, change requests, incidents, CIs, and so on (if you have the corresponding application
installed)
CI Unavailability
Shows the related CI unavailability tied to the change entry. This option is enabled only if BMC Asset Management is
installed.
Configuration Item
Shows the related CIs
Incident
Shows the related incidents. This option is enabled only if BMC Incident Management is installed.
Infrastructure
Shows the related change records
Change
Known Error
Shows the related known errors. This option is enabled only if you have BMC Problem Management is installed.
LDAP Object
Shows the related LDAP objects
Problem
Shows the related problems. This option is enabled only if you BMC Problem Management is installed.
Investigation
Project
Shows related projects
Release
Shows the related release objects
Page 271 of 452
Using
Relationship
Description
Software Library
Shows the related software library items, that is, the location where the master copy of the software program and its
Item
version are stored
The related items appear in the table.

4. Click the
icon.
You can now view the details of the related item.

For example, if you select an incident relationship and click the
icon, the Incident Request form opens,
showing information about the Incident.

Double-click a relationship entry to open the associated form. You then can modify the record, depending
on your configuration.
For relationships external to BMC Change Management (such as an incident or a problem), you must have
the required view permissions for the BMC Remedy ITSM application to view the record details.
7.10 Performing additional functions with relationships

You can perform the following additional functions with relationships.
Function
Modify a
relationship
Action
1. On the Relationships tab of the Change form, select the change with the relationship to modify.
2. From the Quick Actions menu, choose Modify Relationship Type, and then click Execute.
3. Modify the required information and then click Save.
Remove a
relationship
Copy relationships
to a CI that is
related to the
change
Relate a change
request to an LDAP
object
1. On the Relationships tab of the Change form, select the change with the relationship to remove.
2. Click Remove.
1. On the Relationships tab of the Change form, select the corresponding CI relationship entry from the Relationships
table.
2. From the Quick Actions menu, choose Get Related Relationships, and then click Execute.
3. On the Relationships for Configuration Item dialog box, select the item to relate to the current change. Select a
Relationship Type, and then click Select.
When you work with a change request, you might required to define a related LDAP object. For example, to enable seamless
authentication with Policy Manager you might want to relate a change request to an LDAP server where the permission rights
are stored.
1.
2.
3.
4.
Relate a change
request to an
storage location
Click the Relationships tab of the Change form.

Under Create Relationships, select LDAP Objects from the Search list and click the search icon.
On the LDAP Search dialog, select a LDAP Object type and name, and then click Search.
From the search results, select the LDAP object to relate to the change request, and then click Relate.
The change request and the related LDAP item appear on the Relationships tab.
When you work with a change request, you might need to define a related storage location. For example, you might need to
view related storage locations, like different versions of Microsoft Office along with their license contracts. Storage locations
are also used by Policy Manager to determine the location of software to deploy.
Page 272 of 452
Using
Function
Action
1. Click the Relationships tab of the Change form.
2. Under Create Relationships, select Software Library Item from the Search list and click the search icon.
3. On the Software Library Item Search dialog, enter the search criteria, and then click Search.
4. From the search results, select the storage location to relate to the change request, and then click Relate.
The change request and the related storage location appear on the Relationships tab.
7.11 Relating CIs to alternate datasets

When you open the Change form, different datasets are available when relating CIs to a change request:
Personal Preference Change Data Set (CDS) When you open the Change form, the personal preference
change dataset is loaded as a global setting from your application preference settings. If this setting is
blank, the production dataset is loaded from the AST:AppSettings form.
For more information, see Setting application preferences (
https://docs.bmc.com/docs/display/change81/Setting+application+preferences).
Production Data Set (PDS) If there is no CDS, the PDS is loaded as the global setting. The PDS value is
taken from the dataset field on the AST:AppSettings form.
Alternate Data Set (ADS) Field on Change form on the Relationships tab that enables you to select a
different dataset other than the CDS or PDS.
Note
For more information about datasets, see Changing datasets (
https://docs.bmc.com/docs/display/asset80/Changing+datasets) in the BMC Asset Management
documentation.
You must understand the following restrictions if you use an alternate dataset when relating CIs:
Configuration items
Alternate
Data Set
field
Dataset
preference
Result
If there are no CIs

related to the change
Empty
CDS
You can select the ADS as needed. After you start working on the change request, the
setting of the ADS is the dataset that you selected last.
If there are no CIs

related to the change
Empty
PDS
PDS is used.
Note: An empty Alternate Data Set field is equivalent to using the PDS.
If CIs are related to

the change
Selected
Not
applicable
Alternate Data Set field is locked. If you relates a CI with the ADS, you must save the change
to save the ADS.
Note: There is no database rollback on the relationships.
Page 273 of 452
Using
Configuration items
Alternate
Data Set
Dataset
preference
Result
Whatever the
When all related CIs are removed, the Alternate Data Set field becomes editable. If you clear
last value is
the Alternate Data Set field when it is editable, the dataset is PDS.
field
If all related CIs are
Editable
removed
Notes
The CDS is the default value, and is used only if ADS is set to CDS when you relate a CI. If you
choose the PDS, you must clear the Alternate Data Set field.
When the status of the change reaches Closed, the change is locked for everyone except the
Change Master. Only the Change Master can make modifications to a change request in the
Closed status, including adding and removing relationships. For the Change Master, the Alternate
Data Set field behaves the same way as when the relationship is not locked.
7.11.1 To relate CIs from alternate datasets

1. In the Relationships tab, choose a dataset from the Alternate Data Set list, for example, BMC Asset.
Depending on the applications installed, you might see the following options:
BMC Asset
BMC Configuration Import
BMC Sample Dataset
BMC.ASSET.SANDBOX
Alternate Data Set field
2. Relate CIs from the alternate dataset as needed.

The CI Relationships Search dialog box enables you to search for and relate CIs from the alternate dataset.
Page 274 of 452
Using
7.12 Creating CI unavailability

CI Unavailability entries track down time of an outage against a CI. For example, CI unavailability can be an
outage due to scheduled maintenance, usually through a scheduled change. Also, CI unavailability can occur due
to an unexpected circumstance, usually related to an incident.
Note
You can define CI Unavailability entries only if BMC Asset Management is installed.
You can define CI Unavailability entries for a related CI in the following ways:
Directly By clicking the Relate with Unavailability button from the CI Relationships Search form, when
you are creating the relationship with the CI. For more information, see Relating unavailable CIs and
changes (see page 275).
Indirectly By creating the unavailability after the CI has been associated with the change. For more
information, see Defining new CI unavailability for a record - alternative method (see page 277).
When you save the CI Unavailability entry, the CI Unavailability relationship entry is generated. A CI Unavailability
relationship entry then appears on the Relationships tab.
Note
CI Unavailability cannot be tracked directly against CI Components. The Relate with Unavailability
button does not appear on the CI Relationships Search form when you are searching for CIs from a
release request.
7.12.1 Relating unavailable CIs and changes

Typically, change requests occur because a CI needs to be upgraded (such as an operating system) or needs
repair (such as a server). Using BMC Change Management, you can relate unavailable CIs (also known as outage
records) to their related change request. By relating an unavailable CI record to a change request, you can track
its history, and the costs related to changes to the CI.
To relate an unavailable CI to a change request (see page 276)
To relate a change request to a CI with unavailability (see page 276)
To create CI unavailability where other CI unavailability already exists (see page 277)
Page 275 of 452
Using
To relate an unavailable CI to a change request

1. Open a change request, and then click the Relationships tab.
If unavailable CIs are related to the change request, they appear in the Relationships table.
2. From the Request Type list, select CI Unavailability, and then click Search.
3. In the CI Unavailability Search form, enter search parameters to filter the CI relationships shown, and then
click Search.
The quick search buttons enable you to easily filter CI unavailability with different criteria:
All unavailability
All scheduled unavailability
All unscheduled unavailability
4. Select an unavailable record from the list.
5. From the Relationship Type list, select Related to, and then click Relate.
The following actions occur:
Messages alert you that the CI has been automatically related to the change.
The CI Relationships Search form closes.
The unavailable CI and its related CI record appear in the Relationships table.
6. If needed, you can broadcast the CI unavailability.
For more information, see Performing additional functions with CI unavailability (
https://docs.bmc.com/docs/display/change81/Performing+additional+functions+with+CI+unavailability).
To relate a change request to a CI with unavailability

1. Open a change request, and then click Relationships tab.
The Relationships tab shows the requests that you can relate to the change.
2. From the Request Type field, select Configuration Item, and then click Search.
3. On the CI Relationships Search form, complete the search criteria tabs with the relevant information, and
then click Search.
4. In the Relationship Type field, select the type to relate with the change request, for example, Related to.
5. (Optional) Click Explore CI to view a CI and its relationship in the BMC Atrium Explorer.
6. Click Relate with Unavailability.
If the CI has open unavailability entries created against it, the CI Unavailability Exist dialog box appears.
7. Enter the unavailability settings (for example, Scheduled Full and the scheduled start and end dates), and
then click Save.
For information about filling out this dialog box, see To relate an unavailable CI to a change request (see
page 276).
8. Close the CI Relationships Search dialog box.
The CI Unavailability request type appears in the Relationships table.
Page 276 of 452
Using
To create CI unavailability where other CI unavailability already exists

1. Select the associated Configuration Item from the Relationships table.
2. From the Quick Actions menu, select Create New CI Unavailability, and then click Execute.
3. Perform one of the following procedures.
Procedure
Steps
If the CI has open unavailability entries

created against it, the Existing
Configuration Item Unavailability dialog
box appears.
Perform one of the following actions:

Click Create New to define an unavailability entry. You are then prompted to define the
configuration item unavailability, for example, unscheduled full unavailability type, start
and end dates, and so on.
Select an entry from the table, and then click Relate to Current Request to relate the
change directly against the CI unavailability entry. You are then prompted to specify
the relationship type between the current request and the selected CI unavailability.
If the CI does not have any unavailable CI

entries, the Configuration Item
Unavailability dialog box appears.
a. Select the unavailability type that best describes the down time (for example,
Scheduled Full).
b. Enter the appropriate Scheduled Start and Schedule End dates.
c. Enter remaining information, as needed.
d. Click Save.
4. Save the request.
7.12.2 Defining new CI unavailability for a record - alternative method

You can also define CI unavailability entries after the CI has been associated with the change request (or release
request).
Note
You can perform these steps only if BMC Asset Management is installed.
To create CI unavailability from CIs associated with a request

1. Select the associated CI from the Relationships table.
2. From the Quick Actions menu, select Create New CI Unavailability, and then click Execute.
In the Configuration Item Unavailability form, the Unavailability Class defaults to Change. Here you enter
specific details, for example, unscheduled full unavailability type, the actual start date, or the assignment
status.
3. Select the unavailability type that best describes the down time.
The options are as follows:
Scheduled Full Creates high priority
Scheduled Partial Creates medium priority
Page 277 of 452
3.
Using
Unscheduled Full Creates critical priority

Unscheduled Partial Creates high priority
Note
After you select the unavailability class and type, the Priority field is filled based on a
configurable CI Unavailability Prioritization mapping.
4. (Optional) Modify the description identifying the reason why this unavailability is being defined.
5. Enter the appropriate Scheduled Start Date and Schedule End Date.
After you enter the dates into these fields, the system automatically calculates the Estimated Duration.
Note
When a Scheduled Start Date is entered without an Actual Start Date, the Unavailability Status is
automatically set to Scheduled.
6. Enter the Actual Start Date and Actual End Date, as needed.
The system automatically calculates the Actual Duration, based on the actual dates.
Note
When an Actual Start Date is entered without an Actual End Date, the Unavailability Status is
automatically set to Current Unavailability. The Unavailability Status is automatically set to
Restored when the Actual End Date is filled in. After the Actual End Date is set, you can modify it,
but not blank it out.
7. Select where the assignment is set from.

The Assignment is set from field determines where the assignment is based.
Configuration Item Assigns automatically the CI Unavailability entry if an assignment record has
been defined for unavailability from within the Configuration Item Contact relationship
Note
This type of assignment can be configured to be locked or open. Locked means that the
system selects the Assignment Group from the Configuration Item Contact relationship,
and then locks the fields so that they cannot be re-assigned or manually overridden. Open
means that the system selects the Assignment Group from the Configuration Item Contact
Association and then enables you to select another assignment method.
Page 278 of 452
Using
Cross Referenced Request Assigns the CI Unavailability entry when the CI Unavailability is
generated from either an Infrastructure Change or an Incident. This setting keeps the CI
Unavailability assignment synchronized with either the Change or Incident record assignment.
Manually Lets you assign the CI Unavailability entry manually to any group defined within the
application
Automated Routing Assigns the CI Unavailability entry automatically to a support group if you do
not assign a support group from the People tab. Automated Routing is configured using the
CFG:Assignment configuration form.
For more information about configuring BMC Remedy ITSM, see Configuring after installation (
https://docs.bmc.com/docs/display/itsm80/Configuring+after+installation).
8. If you selected Manual assignment, set the assignment company, organization, group, and assignee. The
individual or group assigned to this unavailability record must set the status to Completed after recording
the actual start and end times.
9. Set the Assignment Status to Assigned.
Note
The Assignment Status governs whether the CI Unavailability entry is considered Open or Closed.
Setting the Assignment Status to Completed marks the CI Unavailability entry as closed.
10. (Optional) Click Set From Change Schedule to retrieve the request's scheduled start and end dates and
times.
You can use this button to fill the Schedule Start and End date and times on the CI Unavailability record.
This feature is available only for CI Unavailability records that were generated from a change request (not
release requests).
11. (Optional) Click the CI Status Information tab to change the status of the CI, for example, In Repair.
12. (Optional) Click the Relationships tab to see possible relationships against the unavailability that might
exist, for example, relationships to incidents, changes, or problems. You can also define relationships to
these respective modules.
13. (Optional) Click the Financials tab to define cost entries against the unavailability. This enables you to track
costs associated to the down time.
Note
You must save the CI Unavailability record before you can define Relationships and Financials.
14. (Optional) Click the References tab to see the record identification numbers for any incidents or changes
that might have created the unavailability entry.
15.
Page 279 of 452
Using
15. (Optional) Click the SLM tab to see the service targets and milestones for the restoration of the
unavailability. Service targets and milestones are defined from within BMC Service Level Management.
Escalations can defined to notify the assignment group prior to acknowledgment or resolution breach
times.
16. Click Save to define the new CI unavailability for the record.
7.13 Performing additional functions with CI unavailability

You can perform the additional functions with CI unavailability that are listed in the following table.
Function
Action
Modify CI
unavailability
1. On the Relationships tab of the Change form, select the unavailability entry to modify, and then click View.
2. On the Configuration Item Unavailability form, modify the information as needed, and then click Save.
3. To create a financial cost for the unavailability, click Add on the Financials tab of the Configuration Item. On the Costs dialog
box, enter required information as needed, and then click Save.
Note
The CI unavailability entry represents the entry as seen within the CI Unavailability form. The CI unavailability entry
that appears on the Relationships tab represents the relationship between the Unavailability and the Change.
Modify
outage
information
Delete CI
unavailability
1. From the Change form, choose Functions> Outage List.

2. On the CI Unavailability form, modify the information as needed, and click Save.
For more information, see Outages (see page 280).
1. On the Relationships tab of the Change form, select the unavailability entry to delete.
2. Click Remove.
Note
Deleting a CI Unavailability entry also deletes all related relationships and cost entries against the unavailability. The
CI Unavailability is deleted if the cross-referenced ID is the change ID.
Broadcast CI
unavailability
1. On the Relationships tab of the Change form, select the unavailability entry to broadcast.
2. From the Quick Actions menu, select Broadcast CI Unavailability, and then click Execute.
3. On the New/Modify Broadcasts dialog box, complete the required fields and any other information, and then click Save.
The View Access field is used to make the broadcast available on the web (if your Broadcast form is web-enabled and the
View Access is set to Public).
Note
You must have the Broadcast Submitter functional role to broadcast the current change.
Page 280 of 452
Using
7.14 Working with related incidents

You can perform the following tasks when working with incidents related to change requests:
To define an incident related to a change request (see page 281)
To relate an incident to a change request (see page 281)
To unrelate an incident from a change request (see page 281)
Note
To perform these functions, BMC Incident Management must be installed.
7.14.1 To define an incident related to a change request

1. On the Relationships tab of the Change form, select the entry for which to define an incident.
2. In the Request Type field, select Incident, and then click Create.
3. On the Incident form, define the incident. For instructions, see Registering incident requests (
https://docs.bmc.com/docs/display/servicedesk80/Registering+incident+requests).
4. Save the incident and the change request.

5. To see the incident, refresh the Related Items table.
7.14.2 To relate an incident to a change request

1. On the Relationships tab of the Change form, select the entry to relate to change request
2. In the Request Type field, select Incident, and then Search.
3. From the search results, select the incident to relate to the change request.
4. Select the option for how to relate the incident to the change request, and then click Relate.
7.14.3 To unrelate an incident from a change request

1. On the Relationships tab of the Change form, select the entry to relate to change request.
2. In the Show Related field, select Incident.
3. Select the incident to unrelate, and then click Remove.
7.15 Responding to task reassignments as a change

coordinator
Page 281 of 452
Using
As a change coordinator, you might need to assign new assignees to tasks associated with your change. Task
reassignment is performed manually, directly on the Task form.
7.15.1 To respond to task reassignment requests as change coordinator

1. In the change request, from the Tasks tab, open the task you want to reassign.
3. After reviewing the task, reassign the request as needed.
If you decide to reassign the task:
a. In the Assignee field, select a new staff member.
The task is assigned to this new staff member.
b. In the Notify Assignee field, select Yes.
c. Update the work history.
Note
If you reject the assignment request, set Notify Assignee to Yes and update the work
history.
4. Click Save.
When the task is reassigned, the previous and new assignees are automatically notified of the changed
assignment.
7.16 Using Quick Actions on relationships

The Quick Actions menu on the Relationships tab enables you to perform advanced actions on relationships. Not
all actions are available with all request types. The following table shows the relationship between request types
and the available actions you can perform on them.
Matrix of request types and quick actions
Request type
CI Unavailability
Broadcast CI Unavailability
Modify Relationship Type
Configuration Item
Create New CI Unavailability
Explore CI
Get CI Impact/Urgency
Get CI Product Categorization
Get Impacted Areas
Page 282 of 452
Using
Request type

Show Related Services
Project
None
Incident
Infrastructure Change
Known Error
LDAP Object
None
Problem Investigation
Release
Software Library Item
None
7.16.1 To use quick actions

2. From the Quick Actions menu, select an action.
For example, you can copy relationships from a CI already related to the release request. The following
table lists all the quick actions that you can use.
Effect of using Relationship Actions
Relationship action
Effect
Explore CI
Opens the graphical BMC Atrium Explorer that shows the selected CI's relationship to other CIs.
Create New CI
Unavailability
Creates a new CI Unavailability record for the selected CI.

Note: This option is available only if BMC Asset Management is installed.
For more information, see the following procedures at Relating unavailable CIs and changes (see page 275):
To create CI unavailability where other CI unavailability already exists
To create CI unavailability from CIs associated with a request
Sets the current release request's Impact and Urgency to the corresponding values of the selected CI.
Page 283 of 452
Using
Relationship action
Effect
Get CI
Impact/Urgency
Get CI Product
Sets the current release request's Product Categorization to that defined in the selected CI.
Categorization
Get Related
Copies the relationships of the selected record to the release request's relationships. For more information, see
Relationships
Copying relationships (see page 270).
Modify Relationship
Modifies the relationship type and enter a new description for the related item.
Type
Show Related Services
Displays a list of Services impacted due to the CI.
3. Click Execute.
Page 284 of 452
Using
8 Working with broadcasts

This feature enables you to send messages to your entire organization, selected groups within the organization,
and to external customers. You can use this feature to send messages about work in progress, outages,
knowledge article updates, and so on. You can also use this feature to view messages that were broadcast to you
from other groups in your organization.
Broadcasts are filtered, based on the following criteria:
Global and company-specific broadcasts are displayed to logged-in users.
Only Global broadcasts are displayed to guest users.
This section describes the following tasks:
Creating broadcast messages (see page 285)
Viewing and managing broadcasts (see page 287)
Limiting the number of broadcasts (see page 287)
Controlling the timing of broadcast pop-up messages (see page 288)
8.1 Creating broadcast messages

This section describes how to define a broadcast message. To define a broadcast, you must have the Broadcast
Submitter functional role.
8.1.1 To create a broadcast message

1. On the application console, click the View broadcast link or the New broadcast link.
2. In the View broadcast dialog, click Create, which appears below the Broadcast table.
3. Enter information in the required fields.
Required fields appear in bold on the Broadcast Details tab.
Company Select the company where this broadcast will be sent. Only users with access to this
company see the broadcast. To send the broadcast to everyone, select Global from the Company
list.
The Company field is mandatory. To specify a specific part of the company, fill in the other location
fields. For example, you can specify the site, organization, or department.
Note
Out of the box, you can only define broadcast messages for the Global company.
Page 285 of 452
Using
Subject A short description of what the broadcast is about

Broadcast Message The text of your message
Broadcast Type Select a broadcast type from the list
Broadcast Start Date and Broadcast End Date To start the broadcast now, click in the Broadcast
Start Date field, and then press Enter. To select a date from the calendar, click the Browse button
next to the field. Select a date from the calendar on which to start the broadcast and the date to end
it. You can also specify times of the day using the Time feature at the bottom of the calendar.
Broadcast Originated From This is automatically filled in. The contents depend on where you are
creating the broadcast. If you broadcast from an investigation, the value is set to Problem
Investigation.
Broadcast Originated From ID When you define a broadcast from within a record, this field is
automatically filled in. If you define a broadcast from the main console, the field is unavailable.
View Access To make the broadcast visible only to members of your organization, select Internal.
To make the broadcast visible from the Requester console, select Public.
Send to Twitter? To post the broadcast message using the configured Twitter account, select Yes.
For additional information on receiving broadcast messages using Twitter, see Receiving BMC
Remedy ITSM broadcasts on Twitter (
https://docs.bmc.com/docs/display/itsm81/Receiving+BMC+Remedy+ITSM+broadcasts+on+Twitter).
Note
This option is available only when you select Global in the Company field and set the View
Access value to Public.
Notify Select Yes to broadcast notification automatically sent to an individual or group.

If you select Yes, an Email button and the Notify Support area appears.
Use the Manual Email button to manually send an email about the broadcast. On the Email
System form, enter the recipient's email address in the Internet Email field, and then click
Send Email Now.
Use the Notify Support area to indicate which group to notify of the broadcast. You must
complete all three fields--Support Company, Support Organization, and Support Group. The
notification is sent at the time and on the date specified in the Broadcast Start Date field.
Priority Select a priority level for the broadcast. The choices are Low, Medium, and High.
4. To add an attachment to the Broadcast, right-click inside the table and select Add from the menu.
In the Add Attachment dialog box, click Open to attach the indicated file. Only one attachment is allowed
for each broadcast.
5. If you want members of another group to be able to modify the message, follow these steps:
a. Click the Authoring Groups tab, and then click Manage Authoring Groups.
b. On the Authoring Group dialog box, select the group to have authoring rights, and then click Add.
6. Click Save.
Page 286 of 452
Using
Note
You can broadcast a change from the change record. To broadcast the change choose Functions >
Broadcast Change from the navigation pane of the change record when updating the record. If you
define a broadcast message from a change or release, a relationship is generated between the broadcast
message and the change or release.
8.2 Viewing and managing broadcasts

While viewing broadcast messages, you can modify the broadcast message, define a new broadcast message, and
under some circumstances (when viewing the message from the current record) relate the broadcast message to
the current record.
8.2.1 To manage broadcast messages

1. From the Change Management console or the application console click View Broadcast.
If there are pending broadcast messages that you have not viewed, this link will display as New Broadcast.
2. To view a broadcast message, select the message to view from the Broadcast table and then click View.
The View Broadcast dialog displays details of the selected broadcast message.
To view another message, close the current message, select another message from the Broadcast table
and click View.
3. If the broadcast table contains many messages, limit the number of messages using the Broadcast Search
Criteria tab. For more information, see Limiting the number of broadcasts (see page 287).
4. Click Modify to update the broadcast message.
You must belong to the authorized authoring group for the selected broadcast message and have the functional
role of a Broadcast Submitter to modify the broadcast message. For more details on modifying broadcast
messages, see Creating broadcast messages (see page 285).
Note
Authorized authoring groups are defined on the Authoring Groups tab of the New/Modify Broadcasts
dialog.
8.3 Limiting the number of broadcasts

When viewing broadcasts from the current Asset, Change, Problem or Incident record, you can limit the number
of broadcasts that appear in the Broadcast table.
Page 287 of 452
Using
Note
You can perform this task only when using the Classic view (
https://docs.bmc.com/docs/display/itsm81/Best+Practice+and+Classic+views).
8.3.1 To limit the number of messages

1. From the Quick Links area of the Navigation pane, click View Broadcast.
2. On the View Broadcast dialog box, click the Broadcast Search Criteria tab, and then complete the fields in
the tab.
To return the smallest number of broadcasts, complete as many of the fields as possible.
3. When you finish specifying the search criteria, click Search.
8.4 Controlling the timing of broadcast pop-up messages

From the BMC Asset Management, BMC Change Management, BMC Service Desk:Incident Management, and
BMC Service Desk Problem Management consoles, you can control the timing of broadcast pop-up messages.
Broadcast pop-ups alert you to the presence of broadcast messages.
The options are:
Never Broadcast messages do not automatically pop up on the screen. You will have to click the
Broadcasts link to view them.
On Console Open Broadcasts messages display on the screen when you open the console.
On Console Refresh New broadcast messages display only when you refresh the console.
8.4.1 To set the timing of pop-up messages

1. From the application console, choose Functions > Application Preferences.
2. In the Request Preferences form, click the Broadcast tab.
3. In the Broadcast Auto Popup field, specify one of the following default settings:
Never
On Console Open
On New Broadcast
4. Click Save.
Note
For the changes to take effect, you must close the application and log on again.
Page 288 of 452
Using
9 Working with records

This section discusses some of the common functions related to record handling.
Creating a requester record (see page 289)
Working with requester records (see page 290)
Modifying records (see page 290)
Printing records (see page 291)
Warning
For the purpose of data integrity, BMC does not recommend deleting change requests. Deleting a
change request does not delete the underlying related data, such as approvals, tasks, relationships, and
any other dependencies.
9.1 Creating a requester record

While defining a new change request, release request, or task, you might find that the requester does not have a
record in the database. If this is the case, you must define a record for the requester. You can do this while you
are defining the request or task.
9.1.1 To define a requester record

1. From the IT Home page, click Application Administration Console.
2. Select the appropriate company from the Company field.
3. Click Create next to People.
4. On the People form, complete all the required fields:
Field
Description
First Name
Enter the requester's first name.
Last Name
Enter the requester's last name.
Client Type
Select Operating Company, Customer, or Vendor.
Profile
Status
Set the Status to Enabled (or other option, as needed).
Client
Sensitivity
Select Standard or Sensitive.
Page 289 of 452
Using
Field
Description
VIP
Select Yes or No to indicate the person's appropriate status.
Support
Staff
Select Yes or No to indicate if the requester is a support staff member.
Site
Select a Site loction.
Company
Select access data for one company but not another, based on the companies to which the person is assigned. The Company
field controls access when configuring people.
Business
Enter a business phone number. Also enter an email address.
5. Optionally, complete the remaining fields, including fields on the other tabs.
6. Click Save.
9.2 Working with requester records

When you define change and release requests, or monitor them, you frequently work with requester information.
For example, you might need to search for a requester in the database. If the requester does not exist, you must
define a new requester. Or, you might need to change requester information.
The People form contains all user records. You can access this form in different ways:
Select People on the Application Administration Console.
Select My Profile on the Overview Console, the Change Management console, or the Release Management
console. You then can see your own user record.
Click in the Last Name field, enter partial information about the individual you are looking for, and then
press Enter.
Information stored here is used to automatically fill in requester information fields on many forms. For
more information, see User interface standards for field labels (see page 39).
9.3 Modifying records

After you generate a record, you can modify or update the information it contains.
9.3.1 To modify a record

1. Open the record that you want to modify.
2. Click the field, tab, or link in the navigation pane that contains or takes you to the information you want to
update.
3. Make the appropriate changes.
4. Click Save.
Page 290 of 452
Using
9.4 Printing records

You can print a copy of a record to keep for filing purposes or to share with someone who does not have access
to the application.
9.4.1 To print a record

1. Open the record you want to print.
2. Click Print at the bottom of the form to open the Business Objects Report Preview dialog box, then go to 3
(see page ).
The Business Objects Report Preview dialog box appears, enabling you to view the record before you print
it.
3. Click the Print icon on the menu bar at the top of the dialog box.
When the print confirmation dialog box appears, click the Print icon to send the record to your local
printer.
4. Close the Business Objects dialog box.
Page 291 of 452
Using
10 Working with costs

The Costing module provides functions required by BMC Change Management for management of cost data. It
enables organizations to understand the financial impact of changes or releases on the company's expenses and
where the money is going. For example, BMC Change Management uses it to track the various costs associated
with change and release requests.
This module allows you to track costs for different tasks and then propagate these costs to the parent change or
release record. You can then accumulate the total cost of all the related tasks, services or configuration items
(CIs) related to the parent record.
Costs for a change or release can be added by users with Change User permissions, but only users with Cost
Manager permissions can configure costing information.
Costing process workflow (see page 292)
Costing limitations (see page 293)
Adding and viewing costs (see page 294)
Calculating the costs of a change request (see page 295)
Using autocost estimates (see page 296)
Allocating costs to CIs (see page 297)
For more information on configuring costs, see the following topics:
Working with cost centers (https://docs.bmc.com/docs/display/itsm80/Working+with+cost+centers)
Working with cost rates (https://docs.bmc.com/docs/display/itsm80/Working+with+cost+rates)
Working with finance rules (https://docs.bmc.com/docs/display/itsm80/Working+with+finance+rules)
10.1 Costing process workflow

For a change record, the total cost is calculated as the sum of the cost of the change, the cost of all the tasks
related to it, and the cost of any CIs related to the change.
Select Links > Financials on the Change form to directly add change related costs. On the Financials dialog, click
Add to add the costs incurred for the change.
Note
For change requests that are created by using a change template, costs that are calculated according to
the financial rules are set in the template.
Page 292 of 452
Using
The cost rate template and finance rules are used to calculate task related costs. If not configured, task-related
costs can be added manually. After the task is closed, either the costs that are calculated based on the finance
rule defined or the costs manually entered are added to the cost of the change.
Any CIs related to the change request or its tasks are added into the budget and actual cost if the relationship is
flagged to be included in total cost. You need to manually specify within the relationship record that CI costs
should be included in the total cost of the change.
If there is a CI related to the cost, you can use the Create Allocation option to identify a cost center that will be
charged for the work done on the change. Multiple CIs can be related to the cost. In this case, you can use the
Create Allocation option to define how the cost of the CIs is distributed among the related CIs.
The total costs related to a change request are calculated after the change request is closed. At the time of
closure, a change can involve various costs such as the actual cost of the change itself, the actual cost involved
for a task or CI associated to it, cost of a task related to the change, or other criteria. A change cannot be closed
unless all associated tasks are closed. When individual tasks are closed, their costs are automatically reflected in
the change cost. To include all related costs in the final actual cost of the change request, the total cost of the
change is calculated only after the change is closed.
Select Links > Financials to view the costs related to a change. The total Actual Cost value displays the actual
costs per cost types - that is, Labor, Fixed, Other, and Parts. The cost types provided out of the box are only for
informational purposes and can be used according to requirements. The Change Financials dialog box displays
the total cost based on the cost type for the selected change record.
10.2 Costing limitations

These are the current limitations of the costing module.
The costs calculated for a change are calculated only for a single company and support group. The costs
you want to calculate must be for the same company and support group.
For cost rate templates to be applied, the details defined under Template Categorization must be identical
to the information defined for the change or task to which the template is to be applied.
When calculating the costs of WIP tasks, the effort log for the task must be updated. An effort log can be
added either manually or by using the Start/Stop clock option on the Assignment tab of the change.
Note
Time in WIP will not be calculated without effort logs.
On the Cost Financials dialog in the Best Practice view and in the Financials tab in the Classic view, the
calculation of the total costs is displayed when no cost type is selected. After that you can view details of
Page 293 of 452
Using
only a single Cost Type selected from the Show menu. After that you cannot display the total cost of all
cost types are not displayed.
If you have configured multiple cost types, calculations are done only for the first cost type, which is Labor.
Therefore, BMC recommends that you use only Labor cost type.
10.3 Adding and viewing costs

The costs of the change request or release request including parts, labor, and other associated costs can be
specified and assessed under Financials. The cost can be related to services or a configuration item (CI). The total
of all allocated costs for a change request or a release request is automatically calculated when the request is
closed.
You can calculate the financial affect in implementing a change request. You can calculate the various kinds of
costs, and you can associate costs with CIs.
Note
If you make a mistake when adding a cost entry for example, if you charge too much for a service
you cannot delete the record. However, you can reverse the cost of the record by adding a new cost
record, and then entering a negative value equal to the amount to negate. If you negate a cost, make
sure that you document this in the Description field.
10.3.1 To add or view a cost to a change request

From the left navigation pane, choose Links > Financials.
Note
The Financials option is not available when the change request is in New mode or in the Draft
status.
3. To view costs of a particular type, in the Show field select the type of cost to view.
Note
Page 294 of 452
3.
Using
Initially the calculation of the total costs is displayed when no cost type is selected. After that you
can view details of only a single Cost Type selected from the Show menu. After that the total cost
of all cost types is not displayed.
4. To add a new cost, click Add.

5. In the Costs dialog box, enter the relevant information in the following fields:
Field
Description
Company
This field is automatically filled with the cost center specified in the Cost Center Code field. The Company field identifies the
company charged for servicing the change request.
Cost Center
Identifies the code name for the business unit or organization within the company that is charged for servicing the change
Code
request. The default cost center is the business unit to which the user logging the change request belongs, but you can
modify this.
When you select the cost center code, the Company and Cost Center Name fields show the values attached to the cost
center code.
Cost Center
Name
This field is automatically filled with the name of the cost center specified in the Cost Center Code field.
Cost
Category
This field is automatically filled according to the application you are working in.
Cost Type
Enter the cost type. Options are Fixed, Labor, Other, or Parts. (These values can differ depending on how your application
administrator has configured cost categorizations and the chosen company.)
Cost
Classification
Options are Actual or Budget.
Description
Enter a cost description.
Related Cost
Enter the rate. You select the Currency from the list. Your administrator sets the available currencies.
Related Units
Enter how many units (for example, hours or minutes) were required to implement the change.
Unit Type
Choose how to measure the cost. Choices are Flat Rate, Hours, or Minutes.
Date
Incurred
Date the charge was incurred. If you leave this field blank, it is set to the current date when you save the cost.
6. Click Save.
7. Perform steps 4 (see page 295) through 6 (see page 295) for each cost associated with the change request.
The totals for budgeted and actual costs appear at the bottom of the table.
10.4 Calculating the costs of a change request

When a change request has been resolved, you can calculate the cost involved in implementing it. If a change
manager or task implementer has already added a cost calculation, you can view the calculation.
You can calculate the various kinds of costs, and you can associate costs with CIs. All the costs of a change
request are totaled automatically.
Page 295 of 452
Using
10.4.1 To modify a cost

3. In the Show field, select the type of cost to view.

4. From the table, select the cost to modify. and then click View.
The Costs dialog box contains information about the kind of cost. You cannot make changes in the Cost
Category field.
5. Change the Cost Center Code, Cost Type, Description, or other information as appropriate and click Save.
Note
To delete a cost from a change request, select it, and then click Delete.
10.5 Using autocost estimates

You can include autocost estimates in a change request.
10.5.1 To use autocost estimates

3. In the Calculation Unit Type select Flat Rate, Hours, or Minutes.

4. In the Budget Estimated Total Time enter the time based on unit type.
Use this information to forecast the cost. For example, you budget that the change will take 2 hours to
perform.
5. In the Actual Total Time, enter the time according to the calculation unit type.
Enter this information after the change is completed (for example, you budgeted two hours to do the
change but it took three hours).
If a matching cost rate is found, a cost is generated.
Page 296 of 452
Using
10.6 Allocating costs to CIs

When relating CIs to a change request, you need only one related CI to generate the allocation. If you have two
or more CIs related to a change request, you can distribute the costs of the change request between the different
CIs.
You cannot perform these steps until you relate the CIs to the change request. For more information, see
Working with related configuration items (see page 176).
10.6.1 To allocate costs to configuration items

3. Click Create Allocation.

In the Cost Allocation form, the following sets of information appear:
Cost Information shows information used to calculate the cost of the change request.
Relate To CIs shows all CIs that are related to the change request.
Related CIs With Cost Allocated shows all the CIs after you have allocated the costs to them.
Note
When you are viewing financials on CIs, only actual costs are shown. As a result, a budgeted
cost that is allocated to a CI appears on the change, but does not appear on the CIs
financial table.
4. Enter missing information for cost type, cost rate, and so on.
5. In the Relate To CIs? field, specify whether to relate the cost to a CI:
Divide evenly between CIs divides the cost between all the CIs (including services) that are related to
the change. Doing so divides the Current Total by the number of related CIs.
Let me allocate to CIs distributes the cost among the different CIs. If you choose this option, the
Selected CI Desc and Allocate To Selected CI fields become active. If you do not have CIs or services
related to this change request, you cannot choose this option.
The Related CIs Count field automatically shows the number of CIs that are related to the change
request. You cannot change this information.
6. In the Relate To CIs table, click the CI to which to allocate a cost.
The ID appears in the Selected CI Desc field.
7. In the Allocate to Selected CI field, enter the amount that to allocate to the CI.
8.
Page 297 of 452
Using
8. Click Create Cost Record.

This allocates costs according to your input. The cost record appears in the Related CIs with Costs
Allocated table, and the Unallocated Cost decreases by the amount applied to the CI.
The remaining fields in the form are read-only. They provide the following information:
Unallocated Cost displays the Current Total less the amount already allocated to CIs during this
session.
Average Cost Per CI displays the Current Total divided by Related CIs Count. This field indicates the
amount that each cost record would be if you chose to automatically allocate the costs to the CIs.
9. Continue selecting CIs from the Related CIs table, and apply costs until the Unallocated Cost is equal to 0.
10. Click Close.
The table in the Costs tab shows the cost records you have created. You cannot modify or delete these
records.
Page 298 of 452
Using
11 Working with tasks

This section describes tasks and includes the following topics:
Working with BMC Change Management as a task implementer (see page 299)
Relation of task statuses to change statuses (see page 301)
Creating automatic tasks (see page 304)
Relating ad hoc tasks to change requests (see page 305)
Relating predefined task group or task templates to a change request (
https://docs.bmc.com/docs/display/change81/Relating+predefined+task+group+or+task+templates+to+a+change+request
)
Sequence number in task groups and tasks (see page 307)

The Dates tab (see page 307)
Managing tasks (https://docs.bmc.com/docs/display/change81/Managing+tasks)
Adding work information to a task (see page 310)
Tracking time for tasks (see page 310)
Working with task assignments (see page 311)
Working on assigned tasks (see page 312)
Viewing tasks and task groups (https://docs.bmc.com/docs/display/change81/Viewing+tasks+and+task+groups)
Processing Configuration Management tasks (see page 314)
Using CCM tasks (see page 315)
11.1 Working with BMC Change Management as a task

implementer
When tasks are added to a change request, the change can be implemented using the tasks implementers. In the
Classic view, the Change Implementer fields are hidden. Task implementers are the people or groups responsible
for the tasks related to a change request. Change requests typically start in the Draft status and any related task
groups or tasks are in Staged status. When the change request status is set to Scheduled, the following action
occurs:
If there is a task group, the first task group in the list is activated, and its status is set to Work In Progress.
The status of the first task in the task group is set to Assigned.
If there is no task group, the first task in the list is activated and its status is set to Assigned.
The task implementers are then notified of tasks assigned to them by email, BMC Remedy Alert, or pager.
Implementing tasks in a change request
Page 299 of 452
Using
After tasks are assigned, task implementers can start work on their tasks when the change request reaches the
Implement stage. They log their progress as they complete each task. When all the tasks related to a change
request are either closed or cancelled, the change is set to Complete and the requester and manager are notified
that the change is resolved.
The change approver requires Change User permission to access change request and task records. For a helpful
overview of the entire process, see the following items:
Relation of task statuses to change statuses (see page 301)
Using CCM tasks (see page 315)
Note
Page 300 of 452
Using
For more information about configuring and administering the Task Management System, see
Configuring Task Management System (
https://docs.bmc.com/docs/display/change81/Configuring+Task+Management+System).
11.2 Relation of task statuses to change statuses

Tasks, similar to change requests, go through many status transitions as they progress. The status in which a task
is generated depends on the status of the parent change request.
This section is an example of the flow changes, approval, task groups, and tasks follow with the out of the box
configuration.
Overview of change and task statuses with approval phases
Page 301 of 452
Using
Page 302 of 452
Using
1. A change request starts in the Draft status. Any related task groups or tasks are in Staged status.
If a change request is cancelled, all the task groups and tasks associated with the change are also
cancelled.
If a task group is cancelled, all child tasks of that task group are also cancelled.
2. The change request moves into the Request For Authorization status and the approval group or approvers
are notified that the change request requires approval for the Review phase.
3. After the change is approved it moves into the Request for Change status and the change manager or
change coordinator is notified.
4. The approval group or approvers are notified that the change request requires approval for the Business
Approval phase.
5. After approval the change is moves to the Planning in Progress status and all people assigned to the
change are notified that the change request is ready for planning.
6. The Status Reason field of the tasks gets updated to Staging in Progress and the task implementers are
notified that the task group or tasks are set to Staged.
7. For taskless changes only the change implementer is notified.
8. When the status reason of all the tasks is set to Staging Complete, the change moves into the Scheduled
for Review status and the change manager or change coordinator is notified that the change request is
scheduled for review. If the change rule is configured to bypass the Schedule for Review status, the change
moves to the next valid status.
Note
This is not applicable when Task Phase Management is enabled. For state transitions of the
change with Task Phase Management enabled, see Change status transitions - Draft to complete
with task phase management enabled (
https://docs.bmc.com/docs/display/change81/Change+status+transitions+-+Draft+to+complete+with+task+phase+man
).
9. The approval group or approvers are notified that the change request requires approval for the
Implementation Approval phase.
10. After approval the change moves into the Scheduled status. For change requests scheduled as change with
no impact, all people assigned to the change are notified.
11. The status of tasks with the least sequence number is set to Assigned if assignment has been defined and
the task implementers are notified to start working on tasks when the status is set to Assigned. The status
of tasks with no assignment is set to Pending with Status Reason Assignment (Pending for Assignment). If
the least sequence number is assigned to a task group, the status of the task group is set to Work in
Progress, and the status of the first child task is set to Assigned or Pending depending on whether
assignment has been defined.
12. For taskless changes only the change implementer is notified.
13.
Page 303 of 452
Using
13. Task Implementors set the task to Work in Progress when work begins. Task implementers can now update
the task information, and start implementing the task. When the first task is set to Work In Progress, the
Change moves to Implementation In Progress status. Workflow enters required information into the Actual
Start Date field.
14. After last child task is set to Closed, the task group is set to Closed. When the last task of the change is set
to Closed, the change manager, change coordinator, and change requester are notified that the change
request is completed. Workflow enters required information into the Actual End Date field.
15. The approval group or approvers are notified that the change request requires approval for the Close
Down phase.
16. The change manager or change coordinator is notified when the final review is completed.
17. If change request is cancelled, the requester is notified.
11.3 Creating automatic tasks

Users can create an automatic task that polls a specified field on a specified form (the TMS:SampleApprovalForm
is provided out-of-the-box) to see if approval has been obtained. (If the field on the form is not NULL, approval
has been obtained). The automatic task created is closed after the approval is obtained (Status = Closed and
Status Reason = Success).
After the automatic task is instantiated and becomes active, an initial check is done to see if approval has been
obtained. Approval checking is done through filters that set zTmpExecuteTask to CHECKAPPROVAL on the Task
form. At the same time, the AutomaticIntervalTime is also set based on the Automatic Interval and Unit fields from
the Task Template form.
Approval is obtained, the task is closed and the AutomaticIntervalTime is set to NULL.
If approval is not obtained, an escalation (TMS:TAS:GetDataInterval) is sent every fifteen minutes to check if the
AutomaticIntervalTime is greater than (or equal to) the current time. If it is, the escalation sets zTmpExecuteTask
= CHECKAPPROVAL on the Task form, which starts the approval checking process. This is repeated until approval
is obtained or the task times out (time out values must be set on the Task Template form for the time out to
occur).
The example used in the following procedure is provided out of the box for BMC Change Management 7. x.
11.3.1 To use automatic tasks in a change request

1. Create a change request.
3. Choose the Task Template request type, and then click Relate.
4. Relate the Check Approval automatically task template to the change request.
5. Use the Process Flow Status bar to work the change request to the Implementation In Progress status.
The status of the task is set to Waiting.
6. Open the Sample Task Approval form and search for the sample approval record.
7.
Page 304 of 452
Using
7. Update the record (for example, In the Approved By field, enter your name).
8. Wait at least 15 minutes until the TMS:TAS:GetDataInterval escalation fires.
This escalation checks the Automatic interval.
9. Refresh the change request until the status of the task is set to Closed.
11.4 Relating ad hoc tasks to change requests

You can relate an ad hoc task to the change request. The status of these tasks can be Staged, Assigned, Pending,
Work in Progress, or Closed. You can manually set the assignment for any task. Finally, if you close the task, you
must select whether you are canceling the task or completing it as a success or failure.
11.4.1 To relate an ad hoc task to a change request

1. Open the change request, and then click the Tasks tab.
2. In the Request Type field, select Ad hoc, and then click Relate.
The Task form appears with certain fields in the form filled with data from the change request. You can
click the Open link next to the Request ID field to open the parent change request.
3. Fill in the following required fields:
Name Enter a descriptive name of the task.
Summary Enter a brief description of the task.
The Type field is set by default to Manual when you create an ad hoc task.
4. In the General tab, fill in information about the company.
The Company field defaults to the contents of the Change Location field in the Change form. Your task can
be assigned to a different department or company.
5. On the Requester tab, enter information about the person defining the task (Requester) and the intended
target of the task (Requested For).
Some information is filled by default from the Requested By information of the change request.
6. In the Categorization tab (Best Practice view) or the Classification tab (Classic view), fill in information
about the product and operational categorizations.
7. In the Assignment/Dates tab, fill in the following fields to assign the task:
Assignee Group Optionally, select a task implementer group from the list.
Assignee Optionally, select a task implementer from the list.
The assignment engine automatically assigns the task when the task is generated. You can override
this if needed by manually assigned the task.
Note
If you manually assign a task, the assignee is immediately notified when the task is staged. If
the assignment engine assigns the task, the task is staged but the notification is not sent to
the assignee until the task is activated.
Page 305 of 452
Using
For more information about assignment configuration, see Configuring task assignments (
https://docs.bmc.com/docs/display/change81/Configuring+task+assignments).
Scheduled Start Date Optionally, enter an estimated start date.

Scheduled End Date Optionally, enter an estimated end date.
You might want to set the Start Date and End Date to be different from the dates of the parent
change request.
8. In the Relationships tab, search for and then relate configuration items, LDAP objects, and software library
items that are needed with this task.
Additionally, you can execute any quick actions like Update Attributes, Explore CI or get Related
Relationships for the task.
9. When you finish creating the task, click Save.
10. To specify if you want to notify the assignee or not, reopen the task and in the Assignment tab select the
appropriate option from the Notify Assignee field.
11.5 Relating predefined task group or task templates to a

change request
You can relate a predefined task or task group template to the change request. The Calbro Services sample data
includes a best practice task group and task templates that you can use.
Recommendation
In addition, special templates were created for the integration with BMC Configuration Automation for
Clients (previously known as BMC Configuration Management). Other templates might have been added
by your application administrator.
11.5.1 To add predefined task group and task templates to a change

3. Select Task Group Template or Task Template from the Request Type field, and then click Relate.
All template types for all categories are listed in the Select Template dialog box.
4. (Optional) You can filter the list by selecting the type or category, or both, of the template. To filter the list:
a. Select the type of template:
With task group templates, select Standard or Sequencing.
With task templates, select Manual, Automatic, or ALL.
b. (Optional) From the Category list, select which application the task belongs to, for example, Change
Management System.
The available task groups or tasks for that selection appear in the list. The categorization of the
change request determines which list items appear.
5.
Page 306 of 452
Using
5. (Optional) Click View to see more details about the task group or task template.
6. If a relevant task set appears on the list to include with the change request, select it, and then click Relate.
7. Define a numerical sequence of the tasks, as described in Sequence number in task groups and tasks (see
page 307).
8. When you finish adding templates, save the change request.
11.6 Sequence number in task groups and tasks

The task management subsystem enforces the dependencies between tasks. These relate to any Sequence order
you might have specified in the Change form.
For more information, see Assigning sequence numbers to dependent change requests (see page 164).
When you include task group templates, task templates, or ad hoc tasks in a change request, they are
automatically assigned a sequence number in the order in which you add them to the change request. More than
one task can have the same sequence number; tasks with the same sequence number are considered peers. Peer
tasks can be completed in any order among themselves.
Tasks must be completed sequentially. When the change request's status is set to Scheduled, the task with
sequence number 1 is activated and its status is set to Assigned. When the last task is completed, the change
request is closed.
To renumber a task group or task, you can use the arrow buttons next to the Tasks and Task Groups table on the
Tasks tab of the Change Request. Tasks with lower sequence numbers, for example 1, must be completed before
those with higher numbers, for example, 2, 3, or 4.
11.7 The Dates tab

The Dates tab on the Task form allows you to plan the dates for the task. The Dates tab includes the following
fields:
Field
Description
Scheduled
Start
Date+
The scheduled start date for the task. Depending on the configuration that you set for Action On Scheduled Dates Change while
Configuring change rules (https://docs.bmc.com/docs/display/change81/Configuring+change+rules), you might see the error message or a
warning when the change request is in between Planning In Progress and the Scheduled status.
Scheduled
End
Date+
The scheduled end date for the task
Time
Segment
Action
Lists the time segment options. For more information, see Registering time segments (see page 415).
Automatically populated with the date and time at which the task is saved after the first task moves to the Work in Progress status
Page 307 of 452
Using
Field
Description
Actual
Start
Date+
Actual
End
Automatically populated with the date and time at which the task was saved after the status is moved to the Closed status
Date+
Activate
Automatically populated with the date and time a task moves from the Staged state to an active state.
Time
Duration
Time spent on the task.
in Minutes
This value is calculated using the Closed Time value (on the Assignment tab) and the Activate Time value. The value is calculated as
follows:
(Closed Time - Activate Time) 60
End Time and Activate Time are measured in seconds and then divided by 60 to display the time in minutes.
Assign
Time
Automatically populated with the date and time when the task assignment is saved
Create
Date
Automatically populated with the date and time the task
Modified
Date
Automatically populated with the date and time the task was last modified and saved
Closed
Time
Automatically populated with the date and time when the task status is moved to Closed. This field is displayed only after the Task
status is set to Closed.
User Data
Displays the User ID of the person who submitted the task and who last modified the task
11.8 Managing tasks

In addition to accepting assigned tasks, you can perform the following functions:
Modifying a task (see page )
Closing a task (see page )
Cancelling a task (see page )
Adding financial information to a task (see page )
11.8.1 Modify a task

1. To view a list of tasks, select the change record and click Show Tasks under Details and Tasks.
2. In the Assigned Tasks table on the Change Management console, select the task to modify, and then click
View.
3. On the Task Management form, update the fields.
4.
Page 308 of 452
Using
4. Click the Work Info tab.

5. Define a work info history entry for the task, and then click Save.
11.8.2 Close a task

2. In the Assigned Tasks table on the Change Management console, select the task to close, and then click
View.
3. Click the Assignment tab, and then update the time you spent on the task.
4. Click the Work Info tab, and then define an entry in the Work Info History field.
5. At the top of the Task form, set the Status field to Closed.
6. Select a status reason to describe how the task was closed, and then click Save.
Note
After a task is closed, it cannot be reopened.
11.8.3 Cancel a task

3. Select a task, and then click Cancel.
The status of the task is set to Closed.
Note
If the task has related CIs, you can update any CI costs that are affected by this cancellation. See
Working with related configuration items (see page 176).
11.8.4 Add financial information to a task

2. In the Assigned Tasks table on the Change Management console, select a task, and then click View.
3. Click the Financials tab, and then enter the budgeted estimated total time in hours.
4. When you finish the task, enter the actual total time.
5. Enter your calculation unit type, for example, flat rate.
6. Save the change request. All this information is calculated and rolled up into the change request.
When you are assigned a task, you can contribute financial information for the task. However, you can only
calculate charges for the change inside the change request.
Page 309 of 452
Using
11.9 Adding work information to a task

You can add work information to each task included in the change request. The work information for each task
appears in the Work Info of Selected Task table on the Change form.
11.9.1 To add work information to a task

1. Open the task and then click the Work Info tab.
2. Modify the work information type, if needed.
Information sources can include, for example, email, system assignment, or the web.
4. Enter details of your work information record in the Date, Summary, and Work Info Notes fields.
5. To add attachments, right-click in the attachment table, and then select Add.
7. Select the view access:
If you want only users within your organization to see the entry, select Internal.
If you want everyone with access to the system to see the entry, select External.
8. When you finish updating, click Save.
Your entry is added to the task's work history. The Show field enables you to filter specific work entries
based on the type of activity shown in the table.
9. To see a report of the activities you performed against this task, click Report.
10. To see all work information history entries, click View.
Note
When you return to the Change form, you might need to refresh the Work Info of Assigned Task
table to see all the entries.
11.10 Tracking time for tasks

You can track the time spent on tasks on the Assignments tab on the Task form.
11.10.1 To track task time

1. Open the task.
2. Click the Assignment tab on the Task form.
3. To automatically track the time spent working on tasks, use the Start Clock and Stop Clock options.
a. When you start the task, click Start Time, and then click Save.
b.
Page 310 of 452
3.
Using
b. When you finish working on the task, click Stop Clock, and then click Save.
You can use the start and stop clock buttons as many times as needed. Each successive time, the
new time is added to the value in the Total Time Spent field. The time is automatically calculated,
based on when you click the buttons.
4. To manually track the time spent working on tasks, enter the number of hours or minutes in the Time
Spent fields, and then click Save.
The time you entered is added to the value in the Total Time Hours and Minutes fields.
5. To add the tracking information to the log:
a. After you save the information for tracking the time spent on the tasks, click the Assignment tab on
the Task form.
b. Click Effort Log.
c. Enter information into the effort log, and then click Add to Effort Log.
11.11 Working with task assignments

You can assign a task to a group or an individual, reassign a task to a group or an individual, view tasks assigned to
you, and your group.
To reassign a task (see page 311)
To view tasks assigned to you (see page 311)
To view tasks assigned to your group (see page 312)
To assign a task (see page 312)
To assign all tasks in a change requests (see page 312)
11.11.1 To reassign a task

1. To view a list of tasks, click Show Tasks under Details and Tasks.
2. In the Assigned Tasks table on the Change Management console, select the task to reassign, and then click
View.
3. On the Assignment tab, choose the group or person to assign the task to in the Assignee Group or Assignee
fields.
4. Ensure that the Notify Assignee field is set to Yes, and then click Save.
Until the new implementer accepts the task assignment, you are assigned to the task and have
responsibility for it.
11.11.2 To view tasks assigned to you

1. On the Open the Change Management console, select Assigned To Me from Show.
2. To view a list of tasks, click Show Tasks under Details and Tasks.
3. To view the details of a task, select it, and then click View.
Page 311 of 452
Using
11.11.3 To view tasks assigned to your group

1. On the Open the Change Management console, select Show > Assigned To My Selected Groups.
2. On the My Group Selection dialog box, select the option under View Group, and then click OK.
3. To view a list of tasks, click Show Tasks under Details and Tasks. The open tasks assigned to your group
appear in the Assigned Tasks table.
4. To view the details of a task, select it, and then click View.
11.11.4 To assign a task

1. On the Tasks tab of the Change form, select a parent task or child task that is related to the change
request, and then click View.
2. Select the Assignment tab, select the group or person to work on the task, and then click Save.
The implementer for that task is notified of the task assignment.
11.11.5 To assign all tasks in a change requests

2. Set the Status field to Scheduled.
The change request is set to Scheduled and the status of the first task is set to Assigned.
11.12 Working on assigned tasks

When change request reaches the Implement stage you can start working on the task assigned to you. When a
change request is set to Scheduled and a task is not assigned, the task status is set to Pending. If the task is
assigned, its status is set to Work in Progress.
Note
When the change is in Planning in Progress, all the tasks have a status of Staged and a status reason of
Staging In Progress. When all the tasks' status reasons have become Staging Complete, the change
moves from Planning in Progress to Scheduled For Approval.
11.12.1 To work on tasks assigned to you

1. Open the Change Management Console.
2. From the View By filter, select Personal.
3. Click the Show Tasks Details link in the Change Details and Tasks section to view the Task table.
4.
Page 312 of 452
Using
4. In the Assigned Tasks table, select the task to accept, and then click View.
Tasks are identified by the prefix of TAS. On the Task Management screen, you can click Open next to the
Request ID field to open the parent change request.
5. If you are ready to begin working on the task that is, if the Status field of the change request is set to
Scheduled set the Status field to Work in Progress. This is an important step, because the task then
moves into Work in Progress status. In addition, different escalations occur based on the task's status. If the
task is still in the Scheduled status while you are working on it, an inaccurate escalation can occur.
7. Enter the time spent. When you are ready to start working on the task, you can use the start and stop clock
or the effort log to keep track of how much time you spent.
8. Click the Work Info tab, and then enter the progress you have made on the task. Optionally, you can add
relevant information to the Task Plans field to describe how you intend to complete the task.
9. Click Save.
If this is the first task to be moved to Work in Progress status, the following changes are automatically
made to the change request:
The status of the change request is moved to Implementation in Progress. This includes all tasks
included in the change request. The change manager is notified of the changed status, and the
requester is notified when the status of the change is set to Scheduled.
On the Assignments tab of the Task form (or Task Dates region of the Change form in Classic view)
the Start Date field is filled with the date and time at which the task was saved.
The Actual Start Date of the task and that of the change request is updated with the date and time of
the status change.
For additional responsibilities (for example, closing a task), see Managing tasks (
https://docs.bmc.com/docs/display/change81/Managing+tasks).
11.13 Viewing tasks and task groups

To view your assigned tasks and task groups click the Show Tasks Details link in the Change Details And Tasks
section of the Change Management console. Tasks are prefixed with TAS, and task groups with TGR. You can also
view tasks and task groups related to a change request on the Tasks tab of the Change form.
Note
You can click View Flow to see a read-only view of the task flow in the task group. For more information
about using the View Flow button, see Using CCM tasks (see page 315).
11.13.1 To view task groups and tasks

1. In the Assigned Tasks table on the Change Management console, or from within the Tasks tab of a change
request, select the task group or the task to view.
2.
Page 313 of 452
Using
2. Click View.
3. Modify the task details as needed.
4. Save your work.
11.14 Processing Configuration Management tasks

A change request can include multiple configuration management tasks, each essential to the successful
implementation of the change. The CCM Task Management Subsystem (TMS) manages these tasks in a sequence
you define.
The CCM solution organizes tasks into the following main categories:
Policy-based tasks (https://docs.bmc.com/docs/display/change81/Policy-based+tasks)
Deployment-based tasks (see page 314)
Verification-based tasks (see page 314)
11.14.1 Policy-based tasks

BMC Configuration Automation for Clients enables you to maintain centralized control of packaged data and
applications across the enterprise. You administer the state of each endpoint on your network using Policy
Manager. A policy consists of a list of software packages or patches your targets (users, computers, or groups) are
expected to have. Use Policy Manager to manage the state of software and data on an ongoing basis.
Policy-based tasks include:
Deploying applications and data

Deploying patches
Harvesting licenses when you have exceeded maximum limits
Enforcing the removal of unauthorized applications
11.14.2 Deployment-based tasks

BMC Configuration Automation for Clients also supports the deployment of large volumes of software or data,
and execution of one-time jobs. You administer these tasks using Deployment Manager (DM). Use DM to run
deployment jobs that typically do not require ongoing management. Deployment-based tasks include
distribution of:
Data
Applications
Commands and scripts
11.14.3 Verification-based tasks

Page 314 of 452
Using
The Task Management Subsystem (TMS) launches verification tasks when it receives notification that a
policy-based task has succeeded. You can verify compliance for policy-based tasks based on a target, package, or
both.
You can configure TMS to launch verification tasks manually or automatically. The system verifies tasks based on
the following criteria:
The compliance percentage of specified targets or software packages
A time window that you specify for completing the task
11.15 Using CCM tasks

BMC Change Management comes installed with the predefined task and task group templates that you can use as
shipped for deploying or installing software and verifying task completion. This section describes how you can
launch Configuration Change Management (CCM) tasks at run time from a change request.
For more information, see Best practice CCM task templates and templates (see page 319).
Using tasks inside a parent object (Best Practice view)
Page 315 of 452
Using
Using tasks inside a parent object (Classic view)
11.15.1 To use CCM tasks to install software and verify compliance

1. Open the Change Management console and create a change request.
Although you can add tasks or task groups to a change during any status, they can only be worked on
during the Implementation status.
2. Use the process flow accelerators to advance through the stages of your change request until you reach
the Implementation status.
4. From the Request Type list, select Task Group Template, and then click Relate.
5. In the Select Template dialog box, select a task group, for example, Create and Modify Policy with Closed
Loop Verification and then click Relate.
This example task group comes for use as shipped for deploying software and verifying task completion.
The task group is then added to the change request.
6. (Optional) Click View Flow to see a read-only view of the task flow in the task group.
Page 316 of 452
Using
The Task Flow Viewer uses color codes to illustrate the different stages of the tasks. For example, a blue
stage indicates that its status is Closed, and a yellow stage shows its status is Staged. The Viewer also
shows you the flow between tasks. You can also perform the following functions in the Task Flow Viewer.
Zoom in to focus the view.
Zoom out to expand the view
Click the pan buttons to move the flow around.
7. Select the task to work on, and then click View.
8. On the Tasks form, click the Relationships tab.
9. Search for a Software Library Item. On the Software Library Item Search dialog box, the Storage Location
contains the location of the software. The storage location can either be a physical repository (Fred's top
drawer) or electronic (a folder on your network).
Perform a search for a storage location, select the appropriate record from the search results and then
click Relate.
10. On the Relationship Attributes dialog box, define the relationship attribute, for example, Source.
11. Define the action attribute, for example, Install, and then click Apply. The Storage Location is added to the
change request.
12. Search for a Configuration Item. On the CI Relationships Search dialog box, CIs are the systems where the
software is deployed.
13. Search for a CI, and then click Relate.
14. Define the relationship attribute, for example, Target.
15. Define the action attribute, for example, Install.
16.
Page 317 of 452
Using
16. Click Apply.

The CI is added to the change request.
Note
When the Storage Location and the CI are related to the task, the relationships are carried over to
the change. If a task implementer wants to select storage locations or CIs related to the change,
use the Get Related Relationships quick action on the Relationships tab on the Task form. A similar
quick action on the Task tab of the Change form to enable the change to relate storage locations
or CIs to a task related to the change entry.
17. Click the General tab, and then click Launch.

The Policy Manager is displayed.
Note
If you have deployed the integrated CCM solution with seamless authentication, the task
implementer can launch the task from BMC Change Management or BMC BladeLogic Client
Automation without having to retype your user ID and password.
18.
Page 318 of 452
Using
18. After you have performed the policy changes in the Policy Manager tool, click Save.
19. Close the Policy Manager window to return to the Task form.
20. (Optional) Review the Work Info about the task.
The work information for the task is updated with the changes performed by the task.
a. Click the Work Info tab.
b. In the Work Info History area, select the Policy Manager entry and then click View.
c. After you view the information, close the Work Info dialog box.
d. Click Report to view an ASCII-format report of the task changes.
The report lists the software installed, if the policy was successful, and so on.
21. In the Status field, set the task status to Closed.
The status reason automatically is set to Success. You can select a different status reason, for example,
Failed or Cancelled.
22. After you have made all your modifications, save and close the task.
23. On the Change form, refresh the children of the task group table.
The status of the first task is marked as Closed and the status of the second task is now Waiting.
24. Open the second task:
a. Select the Check Compliance task and then click View.
b. On the Task form, click Details to view the target and package compliance.
c. Verify the compliance in Policy Manager.
d. Close the Viewer to return to the Task form.
25. In the Status field, set the task status to Closed. You can view the work information for the task as needed.
The task record is updated with the changes performed by the task.
26. After you have made all your modifications, save and close the task.
27. In the Change form, refresh the children of the task group and the task and task groups tables. All tasks and
the task group are marked as Closed.
28. Click Save.
11.15.2 Best practice CCM task templates and templates

BMC Change Management ships with the following predefined best practice task group and task templates that
you can use for installing or deploying software and verifying task completion. These templates were specially
created for the integration with BMC BladeLogic Client Automation (previously known as BMC Configuration
Management).
CMM task templates and templates (Best Practice)
Template
Description
Create and Modify

Policy with Closed
Loop Verification
Task group that includes the following tasks:
Create and Modify Policy

Closed Loop Verification (automatically)
You use this task group template when creating or modifying a BMC CM based policy. This template automatically
performs a closed-loop verification to make sure that the task was executed properly.
Page 319 of 452
Using
Template
Description
Closed Loop
Automatic task that calls BMC Configuration Management Policy Manager to set up compliance parameters for Closed
Verification (automatic)
Loop Verification. It verifies the task automatically against compliance status.
Create and Modify
Manual task that defines or modifies a policy using Policy Manager. It uses the Relationships feature to add the CI and
Policy
storage locations to the task.
Deploy Package
Manual task that deploys a package using BMC Configuration Management Deployment Manager. It adds the CI and
storage location using the Relationships feature on task. Verification of a Deployment Manager task is based on the exit
status of the Deployment Manager job.
Execute Remote
Command
Manual task that executes a remote command using BMC Configuration Management Deployment Manager. Verification
of a Deployment Manager task is based on the exit status of the Deployment Manager job.
Execute Remote Script
Manual task that executes a remote script using BMC Configuration Management Deployment Manager. Use the Task
Attachments table to define the remote scripts. Verification of a Deployment Manager task is based on the exit status of
the Deployment Manager job.
Verify Target Status
Manual task for manually verifying the status of a target against BMC Configuration Management. Use this task to verify
that a specified target is in compliance with the policies to which the target has been assigned.
Page 320 of 452
Using
12 Working with reports

BMC Remedy ITSM provides a variety of predefined reports to give you quick and easy access to information
about your system. Use the Report console to generate these reports. If the predefined reports return more
information than you need, you can manage the scope of the report using qualifications. See the following
topics:
Generating a standard report (https://docs.bmc.com/docs/display/change81/Generating+a+standard+report)
Using qualifications to generate a report (see page 323)
Using advanced qualifications to generate a report (see page 324)
BMC Change Management predefined reports (see page 325)
Release Management predefined reports (see page 329)
From the Applications menu, choose Quick Links > AR System Report Console to view customized reports. This
release of BMC Remedy ITSM integrates the Crystal Reports from version 7.6.00 and Web reports from version
7.6.01. On the web interface, a number of reports are available in the Web format. Additional Crystal Reports are
available only if users have a valid Crystal Reports license and have chosen to install them for the web at the time
of installation.
Note
Customer Support can only provide limited assistance if you modify predefined reports and have a
reporting problem. In addition, there is no guarantee that BMC Customer Support can solve problems
that result from these modifications. The standard reports included with the BMC Remedy ITSM
application are designed to be used without modification.
Warning
If your database does not support the Not Equal To argument in this format: "!=", the content of your
reports can be affected. Reports that have additional qualifications that filter out Group By fields (for
example, 'Department' != "Engineering") also filter out the specified conditions and records that have
Group By fields set to Unspecified or Null. Check with your system administrator to determine whether
your database supports this form of the Not Equal To argument.
12.1 Generating a standard report
Page 321 of 452
Using
Use the following procedure to generate a standard report without qualifications. To generate a report with
qualifications, see one of the following topics:
Using qualifications to generate a report (see page 323)
Using advanced qualifications to generate a report (see page 324)
12.1.1 To generate a report without qualifications

1. In the navigation pane on the application console, choose Functions > Reports.
2. On the Reporting console, select one of the options under Show:
All Reports, which displays all available reports
Created by me, which displays reports that you created
3. Under Category, select applicationName > reportCategory > reportName.
A list of available reports is displayed. Reports are organized by category, some of which contain
subcategories. The reports that you see vary according to which applications are installed.
4. Select the report that you want to run.
5. Click Run.
If you select a report that requires additional parameters, you are prompted to enter the required
parameters. For example, if the selected report requires a date range, the date range field appears.
6. Enter the required parameters, and click OK.
7. If the report displayed is a web report, you can specify the following additional options:
Toggle Table of
Display the table of contents for the current report
Contents
Export Report
Export the report to a file of the specified format

To export the report, select the appropriate page options, and click OK. The following formats are available under
the Export Format list:
Excel
PostScript
PDF
Word
PowerPoint
Print Report
Print the report to HTML or PDF format
12.1.2 Using the web based reporting console to create and run adhoc
reports (video)
Disclaimer
Page 322 of 452
Using
not current.
View video on YouTube (http://www.youtube.com/watch?v=n_5tbifs-YA)
(http://www.youtube.com/watch?v=n_5tbifs-YA)

For more information on creating reports, see Creating reports (
https://docs.bmc.com/docs/display/ars8000/Creating+reports) in the BMC Remedy AR System server documentation.
12.2 Using qualifications to generate a report

You can manage the scope of a report by adding qualifications to the criteria that the report engine uses to
generate the report content. You can tell the report to search only certain specified fields for particular values, or
you can build advanced qualifications by using field names, keywords, and operators.
This procedure describes how to generate basic qualifications by using the Show Additional Filter option. To
generate a report by using advanced qualifications, see Using advanced qualifications to generate a report (
https://docs.bmc.com/docs/display/itsm81/Using+advanced+qualifications+to+generate+a+report).
12.2.1 To use qualifications to generate a report

1. From the navigation pane in the application console, choose Functions > Reports.
2. On the Report Console, select one of the options under Show:
4. Select the Show Additional Filter option.
Along with a list of available fields, two sections are displayed-the simple query builder and the advanced
query builder. You use the simple query builder to quickly construct a simple query. Alternatively, advanced
users can use the advanced query builder to build the query by using BMC Remedy AR System query
syntax.
For additional information about the BMC Remedy AR System Report Console, see Reporting on BMC
Remedy AR System data (
https://docs.bmc.com/docs/display/ars81/Reporting+on+BMC+Remedy+AR+System+data).
5. Select a field name from the Available Fields list, and click Add next to the simple query builder.
Page 323 of 452
5.
Using
Note
Click
to remove a qualification.
6. Click the down arrow next to the field name listed in the qualification box, and select the appropriate
operator. Enter or select a value for the field in the right column.
Example
If you want to enter the qualification Cost Center = 001, select the Cost Center field, click the down
arrow next to the field and select =, and then enter 001 in the right column.
7. Repeat steps 5 and 6 for each field that you want to include in the report.
8. When you finish defining your additional qualifications, click Run.
9. If the report displayed is a web report, you can specify the following additional options:
Toggle Table of
Display the table of contents
Contents
Export Report
Export the report to a file of the specified format

To export the report, select the appropriate page options, and click OK. The following formats are available under
the Export Format list:
Excel
PostScript
PDF
Word
PowerPoint
Print Report
Print the file to HTML or PDF format
12.3 Using advanced qualifications to generate a report

You can manage the scope of a report by adding qualifications to the criteria that the report engine uses to
generate the report content. You can tell the report to search only specified fields for particular values, or you can
build advanced qualifications by using field names, keywords, and operators.
12.3.1 To generate a report by using advanced qualifications

1. From the Navigation pane in the application console, choose Functions > Reports.
2.
Page 324 of 452
Using
2. On the Report Console, select one of the options under Show:

4. Select the Show Additional Filter option.
Along with a list of available fields, two sections are displayed-the simple query builder and the advanced
query builder. You use the simple query builder to quickly construct a simple query. Alternatively, advanced
users can use the advanced query builder to build the query by using BMC Remedy AR System query
syntax.
For additional information about the BMC Remedy AR System Report Console, see Reporting on BMC
Remedy AR System data (
https://docs.bmc.com/docs/display/ars81/Reporting+on+BMC+Remedy+AR+System+data).
5. Select a field name from the Available Fields list, and click Add next to the advanced query builder. Use the
BMC Remedy AR System query syntax to build your qualification.
6. Construct your qualification by using the various operators provided by the qualification builder.
7. Repeat steps 5 and 6 for each field that you want to include in the report.
Note
Select the qualification and press Delete to remove a qualification.
8. When you finish defining your advanced qualification, click Run to view the updated report.
12.4 BMC Change Management predefined reports

You first select the type of report that you want to run. The report type pulls information from the appropriate
BMC Remedy ITSM application form. After you select a report type, you select the individual report that you want
to run.
The "Web reports names and descriptions" table describes the predefined Web reports and the "Crystal Reports
names and descriptions" table describes the predefined SAP Crystal Reports included, organized by the type of
report.
Note
Out-of-the-box web reports provided with BMC Remedy IT Service Management cannot be modified
even if the user is an application administrator because the reports are not created using the BMC
Remedy Action Request System Report console. An application administrator, can however, delete these
reports.
Page 325 of 452
Using
Web reports names and descriptions

Report name
Description
Change > Change Requests > Change Manager and Scheduled

Start Date
Changes By Manager and Scheduled Start Date
Shows all change requests grouped by the change manager and scheduled
start date
Change > Configuration Item > Changes Scheduled by

Configuration Item
Changes Scheduled by Configuration Item
Shows all scheduled change requests grouped by CI
Change > Risk > Change Risk Report by Scheduled Start Date
Change Risk Report by Scheduled Start Date
Shows all change requests grouped according to their Risk Level and Planned
Start Dates
Change > Change Requests > Changes with related Problem

records
Changes that have a Problem record associated with them
Shows all the change requests that are related to a Problem record
Change > Change Requests > Changes with related Incident

records
Changes that have an Incident record associated with them
Shows all the change requests that are related to an Incident record
Crystal Reports names and descriptions

Report name
Description
Change > Calendar > Changes By Calendar

Date Range
Changes By Calendar Date Range
Shows all change requests grouped within a specified range of dates
Change > Change Requests > Backed Out

Change Request
Backed Out Change Request
Shows all backed-out change requests
Change > Change Requests > Change

Manager
Changes By Change Manager
Shows all change requests grouped by the change manager
Change > Change Requests > Change Type

Changes By Type
Shows all change requests grouped by change type
Change > Change Requests > Changes By

Assignee and Scheduled Start Date
Shows all change requests grouped by the change coordinator and scheduled start date
Page 326 of 452
Using
Report name
Description
Changes By Assignee and Scheduled Start

Date
Changes By Business Justification
Shows all change requests grouped by the change business justification

Change Coordinator
Changes By Change Coordinator
Shows all change requests grouped by their change coordinator

Status
Changes By Status
Shows all change requests grouped by status
Change > Change Requests > Location And

Scheduled Start Date
Changes By Location and Scheduled Start
Date
Shows all change requests grouped by their change location and sorted by the scheduled start date
Change > Change Requests > Location And

Status
Changes By Location and Status
Shows all change requests grouped by their change location and sorted by the change status.
Change > Change Requests > Operational

Categorization
Changes By Operational Categorization
Shows all change requests grouped by operational categorization
Change > Change Requests > Related

Changes
Changes with Related Changes
Shows all change requests that are related to other change requests, grouped by the parent change
request
Change > Change Requests > Requester

Changes By Requester and Status
Shows all change requests grouped by requester information and support company information
Change > Change Requests > Status Reason

Changes By Status Reason
Shows all change requests grouped by status reason
Change > Change Requests > Class

Changes By Class
Shows all change requests grouped by the change Class, previously termed as change timing
Change > Change Requests > Configuration

Item
Virtual Machines by Decommission Date
Shows all virtual machines with a decommission date proposed for the selected date range
Change> Change Requests> Service Requests
Note: You must have BMC Service Request Management installed to view Service Request related
reports.
Page 327 of 452
Using
Report name
Description
Requests for Virtual Machines
Shows all service requests for virtual machines.
Decommission Requests for Virtual Machines
Shows all decommissioned requests for virtual machines
Extension Requests for Virtual Machines
Shows all requests for virtual machine extensions
Change > Change Requests > Approvals

Change Requests By Approval Status
Shows all change requests grouped by approval status
Change Approvals By Virtual Machines
Shows all change requests related to virtual machines along with the last approval status of the
change
Change > Change Requests > Approval Status

Virtual Machines Requests by Approvals
Shows all service requests for virtual machines grouped by approval status
You must have BMC Service Request Management installed to view this report.
Change > Configuration Item > Open Change

Requests by Configuration Item
Open Changes Requests By Configuration
Item
Shows all change requests related to CIs and grouped by CIs
Change > Configuration Item > Configuration

Item Scheduled Changes
Changes Scheduled by Virtual Machine
Shows all change requests related to virtual machines with status Scheduled and a start date
Change > Configuration Item > Status

Open Change Requests for Virtual Machines
Shows all open change requests related to virtual machines for which the status is not Completed,
Cancelled or Draft
Change > Costs > Cost Categories/Types

Change Cost Categories - Actual Cost
Shows the actual costs incurred for the change requests
Change Cost Categories - Budgeted Costs
Shows the budgeted costs incurred by the change requests
Virtual Machine Costs
Displays costs incurred for the VM. The costs include cost for change for the VM and VM costs.
Change > Costs > Cost

Summary/Year-Quarter
Cost Summary/Year-Quarter by Change
Location - Actual Cost
Cross-tab report that provides the actual costs incurred by the change location
Cost Summary/Year-Quarter by Change

Location - Budgeted Cost
Cross-tab report that provides the budgeted costs by the change location
Cost Summary/Year-Quarter by Operational

Categorization - Actual Cost
Cross-tab report that provides the actual costs incurred by the change operational categorization
Cost Summary/Year-Quarter by Operational

Categorization - Budgeted Cost
Cross-tab report that provides the budgeted costs incurred by the change operational
categorization
Virtual Machine Costs by Quarter
Cross-tab report that provides the quarterly costs incurred for the VM. The costs include cost of the
change for the virtual machine and the actual virtual machine costs.
Page 328 of 452
Using
Report name
Description
Change > Impact > Change Impact Report by

Planned Start Date
Change Impact Report by Planned Start Date
Shows all change requests grouped according to their Impact, Urgency, and Planned Start Dates
Change > Request and Tasks > Changes and

Tasks by Status
Changes and Tasks by Status
Shows all tasks related to change requests sorted by task status
12.5 Release Management predefined reports

The activities of most release coordinators center around release request analysis, for example, determining the
length of time spent on release requests, types of releases requested, and frequently repeated tasks. Release
Management reports to give you quick and easy access to information about your system.
To access the Reporting Console, in the navigation pane on the Release Management console, choose Functions
> Reports. You first select the type of report that you want to run. The report type pulls information from the
appropriate BMC Remedy ITSM application form. After you select a report type, you select the individual report
that you want to run.
The "Web reports names and descriptions" table describes the predefined Web reports and the "Crystal reports
names and descriptions" table describes the predefined SAP Crystal Reports included, organized by the type of
report.
Web reports names and descriptions
Report name
Description
Release > Configuration Item > Configuration Item Scheduled

Releases
Releases Scheduled By Configuration Item
Shows all scheduled release requests grouped by CI
Release > Risk > Release Risk And Impact

Release Risk And Impact By Scheduled Start Date
Shows all releases with details of Risk and Impact, grouped by their scheduled
start date
Release > Release Requests > Problem Records

Releases with Related Problems
Shows all problems related to the release
Release > Costs > Cost Summary/Year-Quarter by Service Actual Cost

Cost Summary/Year-Quarter By Service-Actual Costs
Cross-tab report that provides the actual costs by the Service CI
Release > Configuration Item > Service Scheduled Releases

Releases Scheduled By Service
Shows all releases scheduled by Service CI, grouped by Service CI Name
Page 329 of 452
Using
Crystal reports names and descriptions

Report name
Description
Release > Calendar > Releases By Calendar Date Range

Releases By Calendar Date Range
Shows all release requests grouped within a specified range of dates
Release > Costs > Cost Summary/Year-Quarter by Location Actual Cost

Cost Summary/Year-Quarter By Location- Actual Costs
Cross-tab report that provides the actual costs incurred by the request
location
Release > Release Requests > Activities

Activities By Status and Dates
Shows all releases, grouped by Status and Date
Releases With Activities and Tasks
Shows all activities and tasks associated with releases
Release > Release Requests > Approvals

Release Approvals By Approval Status
Shows all release requests that have been approved, grouped by their approval
status
Release > Release Requests > Change Requests

Releases with Related Changes
Shows all change requests associated with the release
Release > Release Requests > Incident Records

Releases with Related Incidents
Shows all incidents related to the release
Release > Release Requests > Releases with Manifest Information

Releases with Manifest Information
Shows all activities and changes related to releases
Release > Release Requests > Unsuccessful

Unsuccessful Releases
Shows all unsuccessful releases
For detailed information about generating reports, see Generating a standard report (
https://docs.bmc.com/docs/display/itsm80/Generating+a+standard+report).
Page 330 of 452
Using
13 Using reminders
Reminders enable you to define notes for yourself and others. You can send them by email or through BMC
Remedy Alert, and you can specify when they are sent.
You can define generic reminders, or you can define reminders that are associated with a specific change request
or task. For example, you can send yourself a note about a specific change request to remind yourself to follow
up on it.
Whether you access reminders from the console or from within a change request determines which reminders
you are able to view:
When you open the Reminders dialog box from the console, you can view all reminders that you have
created.
When you open reminders from within a change request, you can view reminders associated with that
request. This includes not only your reminders but also those created by other users of the application.
You can modify or delete only the reminders that you have created.
This section provides the following topics:
Creating and viewing reminders (see page 331)
Modifying and deleting reminders (see page 332)
13.1 Creating and viewing reminders

You can set reminders to send notes to yourself and others.
13.1.1 To view and create reminders

1. On the Change Management console select Functions > Reminders.
The Show Reminders tab displays a list of reminders that you can filter using the options in the Show
Reminder drop down.
2. Select the Create Reminder tab to create a new reminder.
3. Enter information in the fields as appropriate.
Field
Description
Notify
The options are as follows:

Individual Select this option to notify a user.
Group Select this option to notify a group.
Note: If you select the Group option, all the people who belong to the support group and have the Infrastructure Change
Page 331 of 452
Using
Field
Description
Approver functional role are set up as approvers. By default, only one approver in the group must sign off on the approval
before it can move to the next status.
Recipient
Enter the name of the user or group and press Enter.
AR login
If you select Individual, this field appears. The logon ID of the user is automatically included when you select the user.
Time
Select the calendar icon to select the date and time for when the reminder needs to be set. By default, the time is set to an hour
ahead of the current time.
Subject
Specify a subject for the reminder.
Message
Enter a brief message related to the reminder.
4. Click Save.
A confirmation message with details of the notifier and time of the reminder is displayed.
13.2 Modifying and deleting reminders

If you open the Reminders dialog box from the Change Management console, all reminders that you created are
shown. If you open the Reminders dialog box from within a change request, only the reminders associated with
that request are shown.
13.2.1 To modify or delete reminders

1. In the Change Management console, or from within a change request, choose Functions > Reminders.
2. In the Show Reminders field on the Reminders dialog box, select the set of reminders to view. The choices
are All, Pending, and Sent.
3. Select a reminder, and then click View.
4. On the Reminder Details dialog box, make your changes to the reminder, and then click Save.
5. To delete a reminder, select it, and then click Delete.
Page 332 of 452
Using
14 Using flashboards
Using the KPI flashboards (see page 333)
Using ROI flashboards (see page 337)
Viewing and displaying data (see page 340)
14.1 Using the KPI flashboards

The KPI flashboards use graphs to show how well various business processes are performing against the
application key performance indicators (KPIs). If you have BMC Service Management Process Model installed, you
can also view the application KPI definitions there.
Tip
The BMC Service Management Process Model defines a key performance indicator as, "a vital and
measurable result to track the efficiency, effectiveness, and predictability of a process."
The KPI flashboard component collects the data according to the selected customer company. Each KPI
flashboard contains two graphs that present the following types of information:
Relevant historical data Use this graph for trending purposes. The most recent historical data displayed
in the graph is collected from the previous month. Historical data goes back to a maximum of one year.
Note
Historical data only appears in a graph when that historical data exists in the database. Typically,
new or recent installations, or upgrades, of the ITSM applications might not have historical data
available.
Current, or real time data Use this graph to see what is happening with the business process now. In
most cases, the displayed real time data is collected from the first day of the current month to today's date.
You can also view the individual request records that are reported by the real time flashboard graph. For
example, you can view all of the incident or change request records that are reported by the Incident
Backlog KPI or the Change Backlog KPI flashboard.
Note
Page 333 of 452
Using
KPI flashboards are available only for version 7.6.00 (and later) of the BMC ITSM applications. If you are
running a mixed environment, that is, if you are running some BMC ITSM applications at version level
7.5.01 (or earlier), you see flashboards with only the version 7.6.00 (or later) applications.
For information about how to do this, see Viewing and displaying data (
https://docs.bmc.com/docs/display/itsm81/Viewing+and+displaying+data).
14.1.1 Related topic

Opening the KPI flashboards (https://docs.bmc.com/docs/display/itsm81/Opening+the+KPI+flashboards)
14.1.2 Opening the KPI flashboards

Use this procedure when you need to open the KPI flashboards to view the information that they contain.
To open the KPI flashboards

1. Choose Functions > KPIs.
2. From the Company list select the customer company for which you want to view KPI flashboards.
3. From the Navigation pane, choose Process KPIs > KPIflashboardLink.
KPIflashboardLink is the link to the specific KPI flashboard that you want to see.
Tip
Click the triangle beside the Process KPI text to open and close this area of the Navigation pane.
14.1.3 BMC Change Management KPIs

The following table describes the BMC Change Management key performance indicators (KPIs):
BMC Change Management KPIs
KPI title
Description of graph content
Frequency of data
collection
Successful
changes
This graph displays:
Monthly
The number of closed change requests with the Status Reason field set to Successful
The total number of closed change requests
Standard
changes
This graph displays:
Monthly
The number of completed change requests with class Standard

The total number of completed change requests
Page 334 of 452
Using
Emergency
changes
This graph displays the number of completed changes with the Timing field set to Emergency.
Monthly
Time to plan
This graph displays the average time taken for the Status field to be set to Scheduled for Review from the
moment a change is registered.
Monthly
Time to
Approve
This graph displays the average time taken for the Status field to be set to Scheduled from Scheduled for
Approval.
Monthly
Backlog of
Changes
This graph displays the number of change requests with Change Type field set to Change for which the
Status field is not yet set to Completed.
Daily
14.1.4 BMC Change Management KPI flashboard variables

KPI flashboards use variables to fetch the data that is used to create the flashboard graphs for the selected
company. In most cases, you can control what data appears in the graph by choosing to hide or display one or
more of the active variables.
For information about how to hide or display variables, see Viewing and displaying data (see page 340).
The following table lists the BMC Change Management KPI graph types, the active variable names, and the
meaning of the information provided. This will help you to understand the effects of choosing to hide or display a
specific variable.
BMC Change Management KPI flashboard variables
Graph type
Variable name
Data displayed by the variable
CHG:CHG:SuccessfulChangesHistory
Changes that were closed successfully for the last year (if the data exists), for the
selected company
CHG:CHG:SuccessfulChangesHistoryC0
Total number of changes that were closed for the last year (if the data exists), for the
selected company
CHG:CHG:SuccessfulChanges
Changes that were closed successfully for the month
CHG:CHG:SuccessfulChanges_C0
Changes that were closed unsuccessfully for the month
CHG:CHG:StandardChangesHistory
Changes that were completed successfully with class "Standard" for the last year (if the
data exists), for the selected company
CHG:CHG:StandardChangesHistoryC0
Total number of changes that were completed for the last year (if the data exists), for
the selected company
CHG:CHG:StandardChanges
Changes that were completed successfully with class "Standard" for the month
Successful
Changes
Historical
Real time
Standard
Changes
Historical
Real time
Page 335 of 452
Using
Graph type
Variable name
CHG:CHG:StandardChanges_C0
Changes that were completed successfully with class not equal to "Standard" for the
month
Emergency
Changes
Historical
CHG:CHG:EmergencyChangesHistory
Completed emergency changes for the past year (if data exists), for the selected
company
Real time
CHG:CHG:EmergencyChanges
Completed emergency changes for the current month for the selected company
Historical
CHG:CHG:TimetoapproveHistory
Time taken to approve the changes during the past year (if data exists), for the selected
company
Real time
CHG:CHG:Timetoapprove
Time taken to approve the changes for the current month for the selected company
Historical
CHG:CHG:TimetoplanHistory
Time taken to plan the changes for the past year (if data exists), for the selected
company
Real time
CHG:CHG:Timetoplan
Time taken to plan the changes for the current month, for the selected company
Historical
CHG:CHG:BacklogofchangesHistory
Completed change requests for the past year (if data exists), for the selected company
Real time
CHG:CHG:Backlogofchanges
Completed change requests for the current month, for the selected company
Time to
approve
Time to plan
Backlog of
Changes
14.1.5 Release Management KPIs

The following table describes the Release Management key performance indicators (KPIs):
Release Management KPIs
KPI title
Description of graph content
Frequency of data
collection
Successful
Releases
This graph displays the number of closed releases with the Status Reason field set to Successful, compared
to the total number of closed releases.
Monthly
Backlog of
Releases
This graph displays the number of releases that do not yet have their Status field set to Completed or higher.
Daily
14.1.6 Release Management KPI flashboard variables
Page 336 of 452
Using
KPI flashboards use variables to fetch the data that is used to create the flashboard graphs for the selected
company. In most cases, you can control what data appears in the graph by choosing to hide or display one or
more of the active variables.
For more information about how to hide or display variables, see Viewing and displaying data (see page 340).
The following table lists the Release Management KPI graph types, the active variable names, and the meaning of
the information provided. This will help you to understand the effects of choosing to hide or display a specific
variable.
Release Management KPI flashboards variables
Graph type
Variable name
RMS:RMS:SuccessfulReleaseHistory
Releases that were closed successfully for the last year (if the data exists), for the
selected company
RMS:RMS:SuccessfulReleaseHistoryC0
Releases that were closed unsuccessfully for the last year (if the data exists), for the
selected company
RMS:RMS:SuccessfulReleases
Releases that were closed successfully for the month (if the data exists), for the
selected company
RMS:RMS:SuccessfulReleases_C0
Releases that were closed unsuccessfully for the month (if the data exists), for the
selected company
Historical
RMS:RMS:BacklogofReleasesHistory
Completed release requests for the last year (if the data exists), for the selected
company
Real time
RMS:RMS:BacklogofReleases
Completed release requests as of date (if the data exists), for the selected company
Successful
Releases
Historical
Real time
Backlog of
Releases
14.2 Using ROI flashboards

The ROI flashboard provides a platform to compare the baseline costs that were incurred prior to implementing
BMC Remedy IT Service Management with the actual costs incurred after installation. The Service Desk ROI
flashboards include the baseline incident request call-handling and the baseline CI outage costs, while the BMC
Change Management ROI flashboard provides the cost of failed changes.
Note
In some cases, if the relative difference between the numbers reported in each graph is large enough,
the smaller graph might not appear on the flashboard. However, a number representing the value of the
smaller graph is always visible.
Page 337 of 452
Using
The information displayed in these graphs helps you to determine the return on investment (ROI) that your
organization achieves from the BMC Remedy ITSM implementation.
Note
To view the ROI console you must have ROI Viewer or ROI Admin permissions.
The ROI data is collected by the ROI flashboard component according to:
The customer company that you select in the ROI console
The date range that you specify in the ROI console
A set of parameters that are configured by someone with ROI Admin permissions
For descriptions of what the configured parameters mean, see BMC Service Desk User documentation and BMC
Change Management user documentation.
Note
ROI flashboards are available only for version 7.6.00 of the BMC Remedy ITSM applications and later. If
you are running a mixed environment, you see only the version 7.6.00 (or later) application flashboards
listed on the ROI console. For example, if you are running version 7.6.00 of BMC Change Management
and version 7.5.01 of BMC Incident Management, you see only the BMC Change Management
flashboards on the ROI console.

Configuring ROI flashboards (https://docs.bmc.com/docs/display/itsm81/Configuring+ROI+flashboards)
Opening the ROI flashboards (https://docs.bmc.com/docs/display/itsm81/Opening+the+ROI+flashboards)
14.2.2 Opening the ROI flashboards

This section describes the procedure to open the ROI flashboards from the BMC Remedy AR System IT Home
page.
To open the ROI flashboards

1. In the Navigation pane of the BMC Remedy AR System IT Home page, select Return on Investment > ROI
Console link.
2. From the lists at the top of the ROI console, select the following parameters:
Company The client company for which you want to create a comparison
Page 338 of 452
2.
Using
Start Date The start date of the period for which the graph is created. The year of the start date
must be 2000 or later.
End Date The end date of the period for which the graph is created
Notes
The companies that you see in the Company list are controlled by your access level.
The remaining fields are completed automatically by the application and are
configurable by the system administrator.
Although you can enter a date range that includes a day of the month, the day of the
month is ignored and only the month and the year are considered. For the purposes
of the system calculations, start date is always assumed to be the first day of the
selected month and year, and the end date is always assumed to be the last day of
the selected month and year. For example, if you enter May 21, 2009, as the Start
Date, and July 10, 2009, as the End Date, the system uses May 1, 2009, as the start
date and July 31, 2009, as the end date.
3. In the ROI Navigation pane, select the ROI that you want to view.
Note
The links to ROI flashboards are based on the BMC Remedy ITSM applications that are installed.
14.2.3 Configuring parameters for the ROI flashboard

The following table describes the ROI parameters that are configured by the ROI admin:
Parameter
Description
Cost (per
hour)
The estimated per hour cost of change used by your organization for creating projections
Effort Input
Can be one of the following values:

Specify Effort Estimate If selected, this parameter represents the estimated number of hours to complete a change request.
This parameter is used to specify a estimate that is different from the one specified in the Baseline Effort field.
Use Baseline Effort If selected, the flashboard uses the same value for Effort Input that is specified for Baseline Cost
Calculations.
Effort
Estimate (in
hours)
The actual value of the Specify Effort Estimate parameter, if that parameter is configured
If you selected the Use Baseline Effort option as Effort Input, the flashboard uses the values specified here. You see the following
values:
Page 339 of 452
Using
Parameter
Description
Baseline
Effort (in hours) The estimated average number of hours required to handle change requests, expressed in hours
Cost
Calculation
Unsuccessful Changes (per month) The number of changes that were expected to be unsuccessful
14.2.4 Active variables

The ROI flashboards use active variables to fetch the data that is used to create the graphs. You can control the
appearance of the graph by choosing to hide or display an active variable.
For information about how to hide or display active variables, see Viewing and displaying data (see page 340).
The following table lists the Cost of Failed Changes active variable names and the meaning of the information
they provide.
Cost of Failed Changes active variables
Active variable name
Meaning
Effort Input selected is Specify Effort

Estimate
ROI:Costoffailedchanges_Baseline
Projected costs. The value is selected from Configuration form.
ROI:Costoffailedchanges_Actual
Actual cost. The value is selected from Change form and the configurations. Actual effort (Effort
estimate) is used for calculations.
Effort Input selected is Use Baseline Effort

ROI:Costoffailedchanges_Baseline
Baseline costs. The value is selected from Configuration form.
ROI:Costoffailedchanges_Usingbaselinecost
Actual cost. The values are selected from Change form and the configurations. Baseline efforts
(efforts (in hour)) are used for calculations.
14.3 Viewing and displaying data

Controls on the open flashboard help you view and display the data. The actions that you can perform and the
procedures that you use to perform them are described in the following table.
Note
Not all of the flashboards support all of these procedures.
Viewing and displaying data
Page 340 of 452
Using
Action
Procedure
View specific records used to create the real time flashboard data
Use this procedure, for example, to view all of the change request records with the Status Reason field set to
Successful. This does not work on the historical data graph.
Zoom a graph
Use the zoom feature to enlarge a section of the graph. You can also use full screen mode to enlarge the entire
graph as described by View a graph in full screen mode which appears later in this table.
The zoom functionality allows you to closely view each category on the X axis. For example, if the X axis has 5
categories, you can use the zoom functionality to view only 2 categories. The maximum zoom is a single
category. For KPI reports with a single category, the zoom function is disabled.
Hide or display the graph legend

The default setting is to show the graph legend. The legend provides information about how to interpret the
graph. Not all graphs have a legend.
Change the graph style

There are a number of different graph styles from which you can choose. For example, you can select to
display the data in a line graph, a bar graph, a stacked bar graph, an area chart, and so on. Not all graphs
support all graph styles.
1. Click anywhere inside the

real time graph.
2. In the search results list,
select the record you want
to view.
1. Click the arrow in the lower

left corner of the graph to
expand the bottom control
panel.
2. Click the magnifying glass
icon, then follow the
onscreen instructions.

panel.
2. Deselect or select the Show
Legend check box to either
hide or display the legend.

panel.
2. Click the double-arrow
button, then select the
graph style you want.
Change the graph titles

You can customize the title text that appears on the graphs to suit your organization's needs. For example, you
can change the titles of the X and Y axis.
Hide or display active variables

The flashboards use active variables to fetch the data that is used to populate the graphs. If you choose to hide
a variable, then the part of the graph that uses the variable is hidden. This gives you the ability to further
customize the flashboards appearance. Not all graphs have active variables that you can turn on or off.
1. In the upper right corner of

the graph, click the Titles
icon.
2. Change the label text
appropriately to your
organization's needs.
3. Click Apply when you finish
updating the text.

the graph, click the Titles
icon.
2. Select or deselect the active
variables that you want to
display or hide.
Page 341 of 452
Using
Action
Procedure
View a graph in full screen mode

You can display the selected graph across the entire screen for better visibility. Not all graphs display in full
screen mode.

the graph, click the Full
Screen icon.
2. When you finish viewing the
graph in full screen mode,
press ESC to restore regular
display mode.
Page 342 of 452
Using
15 Using search
You can search for records from the application consoles. To do this, you can run a series of predefined searches,
search all of the records using the Search form, or create and save your own custom searches using advanced
qualifications.
This section describes the following tasks:
Managing custom searches (see page 344)
Searching all records (see page 345)
Searching all change request records from a Hub server (see page 346)
Methods of searching records
Method
Description
Reference to instructions
Predefined
search
Quickly find records

for which you
frequently search.
You can create
custom searches.
Managing custom searches (https://docs.bmc.com/docs/display/itsm81/Managing+custom+searches)
Searching all
records
Use this type of

search when you
are looking for
record that is not
associated with
your ID or your
group's ID, or any
time you search all
of the records.
Searching all records (https://docs.bmc.com/docs/display/itsm81/Searching+all+records)
Advanced
search (for
BMC Asset
Management
only)
Search for
computer systems
with specific
components. For
example, you can
search for all
computer systems
running a specific
patch or operating
system.
Performing an advanced CI search (
BMC Atrium
CMDB
advanced CI
search (for
BMC Asset
Management
only)
Use the BMC Atrium

CMDB query dialog
box to build
complex searches.
Using the BMC Atrium CMDB query dialog box to search for CIs (
https://docs.bmc.com/docs/display/asset81/Performing+an+advanced+CI+search)
https://docs.bmc.com/docs/display/asset81/Using+the+BMC+Atrium+CMDB+query+dialog+box+to+search+for++CIs
)
Page 343 of 452
Using
15.1 Managing custom searches

You can define and save custom searches in the application consoles. Custom searches using advanced
qualifications allow you to create searches with very specific search criteria, which you can save for reuse. After
you save the custom search, it appears in the My Searches list of the Manage My Searches dialog. It is also listed in
My Searches list under the Filter By field.
Note
The My Searches options is listed only after a custom search is defined.
This topic contains the following information:

To define a custom search (see page 344)
To edit or delete a custom search filter (see page 345)
15.1.1 To define a custom search

1. At the top of the console, click the
icon beside the Filter by field.
2. On the Manage My Searches dialog, in the Search Name field type a name for the search.
3. Click Build Search Qualification to open the Advanced Qualification Search Builder dialog box, and then
define the search qualification.
4. From the Keywords or Fields selection boxes, select the keywords or record fields on which you want to
search.
5. To insert operators (+, =, >,<, and so on), click the appropriate operator button. Place literal values between
double quotation marks:
'Urgency' = $NULL$
'Priority' = "High"
Example
If Allen Allbrook is performing an incident request review and he needs to search for incident requests
that meet the following criteria:
Impact => 2-Significant/Large or 1-Extensive/Widespread
Service = Payroll Service
('Impact' = 2-Significant/Large" OR
'Impact' = "1-Extensive/Widespread")
Page 344 of 452
Using
AND 'Service' = Payroll Service" AND

'Last Resolved Date' >= 07/19/2008"
To search for articles where Business Service = Payroll Service:
'Business Service' ="Payroll Service" AND

'Last Resolved Date' >= "07/19/2010"
6. Click Select to close the Advanced Qualification Builder, and then click Save.
7. Close the Manage My Searches dialog box.
The search appears in the My Searches list of the Filter by field.
15.1.2 To edit or delete a custom search filter

1. At the top of the console, click the
icon beside the Filter by field to open the Manage My Searches
dialog box.
2. Under My Searches, select the search filter that you want to modify or delete.
3. To modify the search filter, edit it as necessary and then click Save.
4. To delete the search filter, click Delete.
5. Click Close.
15.2 Searching all records

The following procedure describes how to search all records. Use this type of search when you are looking for
record that is not associated with your ID or your group's ID, or any time you search all of the records.
15.2.1 To search all records

1. From the application console navigation pane, choose Functions > Search application, where application is
either Work order, Change, Release, Knowledge, Problem or Incident.
A form appears that you can use to perform the search. The form is laid out in a similar way as the actual
request form. It contains the same tabs and the same fields.
2. Use the tabs and fields to build your search conditions.
To reduce the number of records found by the search, enter as much information into the form as you can.
Note
Page 345 of 452
Using
If the Customer field is configured to search on an attribute other than First Name or Last Name,
you can still search using the customer's name by opening the Additional Search tab and using the
First Name or Last Name fields.
3. When you finish entering your search criteria, click Search.

When the search finishes, the search results table lists all the records that match the search criteria.
Note
The search criteria are persistent. This means that if you run a search and then close the
application, the next time that you open the application and perform this procedure, the search
criteria that you entered in this step are still present in the search form. They remain until you
change or delete them.
4. Scroll through the table to find the specific record you want.
5. When you find the record, select it to display in Modify mode.
Note
When you open a record from the search results table, it is added to the history list, but not to the
breadcrumb bar. However, any related records that you open from the record do appear in the
breadcrumb bar and get added to the history list.
15.3 Searching all change request records from a Hub server

Use this procedure to search all records from a hub server.
Use this type of search when you are looking for a record not associated with your ID or your group's ID, or any
time you must search all records.
15.3.1 To search all records

1. From the Navigation pane, choose Functions > Search Change.
The Hub and Spoke Search console appears.
2. When you finish entering your search criteria, click Search.
When the search finishes, the search results list contains all the records that match the search criteria.
3. Scroll through the results list to find the specific records that you want.
Page 346 of 452
3.
Using
Note
When you view the record, it opens directly from the spoke server.
Page 347 of 452
Using
16 Using social collaboration

This release of BMC Remedy ITSM integrates chat functionality, RSS feeds, and Twitter notifications with the BMC
Remedy ITSM applications. Users can now use these tools to collaborate with IT support users, such as Service
Desk agents, or as additional notification options.
Note
For information about configuring social collaboration options, see Configuring social collaboration (
https://docs.bmc.com/docs/display/itsm81/Configuring+social+collaboration).

Chat integration (see page 348)
RSS feeds (see page 348)
Twitter integration (see page 349)
16.1 Chat integration

The chat functionality enables BMC Remedy ITSM users to initiate one-on-one or group live chat sessions in the
context of a specific record (for example a change record) from within the BMC Remedy ITSM applications. Using
this functionality, IT support users can chat with other IT support users and initiate collaborative resolution of an
incident or management of a change, among other actions. Administrators can configure the application to save
these chat sessions as a work info entry within the record.
Note
This integration is not intended for chat sessions between end users and IT.
For more information about using chat, see Using chat (https://docs.bmc.com/docs/display/itsm81/Using+chat).
16.2 RSS feeds

BMC Remedy ITSM enables users to broadcast certain events using the Broadcast Messages functionality.
BMC Remedy ITSM integration with RSS feed enables access to specific BMC Remedy ITSM information using an
RSS reader as an alternative mechanism. Administrators can configure different RSS feeds to which users can
subscribe to. Out of the box, an RSS feeds for Global Public Broadcast messages is provided.
Page 348 of 452
Using
For more information about subscribing to RSS Feeds, see Subscribing to RSS feeds (
https://docs.bmc.com/docs/display/itsm81/Subscribing+to+RSS+feeds).
16.3 Twitter integration

The Twitter integration enables IT support users to propagate public and global BMC Remedy ITSM broadcast
messages to a Twitter account so that users who follow the account receive the messages. The Twitter account
must be configured before users can receive updates. Out of the box, this feature is supported only for broadcast
messages that are Public and provided for the Global company.
For more information about receiving BMC Remedy ITSM broadcasts on Twitter, see Receiving BMC Remedy
ITSM broadcasts on Twitter (
https://docs.bmc.com/docs/display/itsm81/Receiving+BMC+Remedy+ITSM+broadcasts+on+Twitter).
16.4 Where to go from here

For more information about subscribing to RSS Feeds, see Subscribing to RSS feeds (see page 356).
For more information about using chat, see Using chat (https://docs.bmc.com/docs/display/change81/Using+chat).
For more information about receiving BMC Remedy ITSM broadcasts on Twitter, see Receiving BMC Remedy
ITSM broadcasts on Twitter (see page 357).
16.5 Related topics

Enabling chat, Twitter notifications, and RSS feeds (
https://docs.bmc.com/docs/display/change81/Enabling+chat%2C+Twitter+notifications%2C+and+RSS+feeds)
Configuring chat settings (https://docs.bmc.com/docs/display/itsm80/Configuring+chat+settings)

Defining RSS feeds (https://docs.bmc.com/docs/display/itsm80/Defining+RSS+feeds)
Configuring the Twitter integration (https://docs.bmc.com/docs/display/itsm80/Configuring+the+Twitter+integration)
16.6 Using chat

Using the chat feature, users can collaboratively work on BMC Remedy ITSM records. For example, you can
collaboratively resolve issues by initiating a chat conversation related to the incident with other technicians who
might be able to help resolve the issues faster. An IT Support technician can start a chat conversation with other
members of the group to get help resolving an issue. When the chat initiator closes the conversation, it is saved
as a Work Info entry and maintained as a part of the record.
The chat icon is displayed on the landing console when chat is configured for BMC Remedy ITSM, as shown in the
following figure:
Page 349 of 452
Using
Click this icon to open the chat initiation window.

The color of the icon reflects your current chat status. Click the arrow beside the icon to view all chat
conversations and to change your status. The status options are as follows:
Online
Busy
Away
Offline
The application displays a pop-up window when you receive an event like a chat invite or friend invite.
The following topics provide more information about using chat:
Initiating a chat conversation (see page 350)
Adding BMC Remedy AR System users who are not present in the Friends list (
https://docs.bmc.com/docs/display/change81/Adding+BMC+Remedy+AR+System+users+who+are+not+present+in+the+Friend
)
16.6.1 Related topic

Configuring chat settings (https://docs.bmc.com/docs/display/itsm81/Configuring+chat+settings)
16.6.2 Initiating a chat conversation

Follow this procedure to initiate a chat procedure with another user from within the BMC Remedy ITSM
application.
To initiate a chat conversation

1. Within a record (for example a change record), click the chat icon.
The Start Conversation window is displayed with a list of users related to the record.
Page 350 of 452
Using
The following user lists are displayed:

Friends Lists your friends from the configured chat client. For more information about configuring
the friend list, see Mapping the BMC Remedy AR System users to the chat server (
https://docs.bmc.com/docs/display/ars81/Mapping+the+BMC+Remedy+AR+System+users+to+the+chat+server
) in the BMC Remedy Action Request System documentation.
Support group users If the conversation is initiated within a record, the list displays users who
belong to the same support group as the chat initiator.
Assigned users The user to whom the record is assigned. This list is displayed when you initiate the
conversation from a record.
Context Users Lists users from the support groups that the user belongs to.
Form name
User
Support Groups
Activity
Requested By
Activity Assignee
Requested By
Assignee
Asset CI
All users from the People tab
All support groups on the People tab
Contract
Manage by Contract
Manager By
Change
Change Coordinator
Change Manager
Coordinator group
Manager group
Incident
Assignee
Owner
Assigned group
Owner group
Problem
Problem Coordinator
Assignee
Coordinator group
Assigned group
Page 351 of 452
Using
Form name
Known Error
Solution DB
Knowledge Article
User
Support Groups
Problem Coordinator
Coordinator group
Assignee
Assigned group
Assignee
Assigned group
Author
Owner
Owner group
Assigned group
Assignee
Release
Release Coordinator
Coordinator group
Task
Requester
Assignee
Support group
Assignee group
Work order
Request Manager
Request Assignee
Request Manager support group

Request Assignee support group
Note
When you launch a conversation from the landing console, a list of context users is
displayed instead of assigned users.
To add a user from another list to your friends list, click the Send buddy request
icon
displayed next to the user's name when you hover the mouse pointer on the user name.
2. Select the user you want to chat with from the relevant list and click the Start Conversation
icon.
The chat window that is displayed provides the following information:

User name of the person who initiated the conversation.
Subject of the conversation. The subject includes the ID of the record from which the conversation
was initiated, the user who initiated the conversation, and other users included in the conversation.
The subject can be a reference for users being invited to the conversation.
Users can accept or reject the chat invitation. If they accept the invitation, a chat window is opened
in their console. Their chat window displays only a list of users included in the chat and the
conversation.
3.
Page 352 of 452
Using
3. To invite additional users to the conversation, click the Invite Users icon
displayed on the top right
corner of the chat window. All participants can invite other users to the conversation.
Note
To add BMC Remedy AR System users who are not present in the Friends list, see Adding BMC
Remedy AR System users who are not present in the Friends list (
https://docs.bmc.com/docs/display/itsm81/Adding+BMC+Remedy+AR+System+users+who+are+not+present+in+the+Fr
).
When the conversation is complete and the chat initiator closes the chat window, the conversation is either saved
as a Work Info entry in the Work Detail tab of the record from which the conversation was initiated, or not saved
at all. This depends on the option you selected when Configuring chat settings (
https://docs.bmc.com/docs/display/itsm81/Configuring+chat+settings).
Note
If the conversation was not initiated from within a record, the conversation is not saved.
Page 353 of 452
Using
16.6.3 Adding BMC Remedy AR System users who are not present in the
Friends list
On the regular form where you have configured the BMC Remedy AR System server to work with the chat server,
create an active link that executes on the CHAT_SET_CONTEXT_REQ Event type. For more information about
events, see the following tables.
This active link sends an event to the AR System Chat Data Visualization field with Event type as
CHAT_SET_CONTEXT_RESP and Event Data as given below:
ContextUsers=ACommaSeparatedListOfBMCRemedyARSystemUsers;ContextGroups=
ACommaSeparatedListOfGroupIDs;DisplayName=SubjectOfTheChatConversation;
For example:
ContextUsers= John,Max,Amy;ContextGroups=1,2
ContextGroups=1,2;DisplayName=Resolving an IT ticket;
ContextUsers=John,Max,Amy;ContextGroups=1,2;DisplayName=Resolving an IT ticket;
List of events sent from the AR System Chat Data Visualization field to the parent form
Event name
Description
DVF_ON_READY
The Data Visualization Field (DVF) is loaded and is ready to interact. This is not specific to the chat DVM.
No response expected.
CHAT_SET_CONTEXT_REQ
Sent to the parent form for the parent form to supply any contextual information. If the parent form
chooses to provide this information, it later raises a corresponding event, CHAT_SET_CONTEXT_RESP.
CHAT_SESSION_START
Sent to the parent form to provide information on the chat progress. No response expected.
CHAT_INVITATION_SEND
Chat invitation sent. No response expected.
CHAT_USER_JOIN
A person is joining a chat session. This event occurs as many times as anyone joins a chat session. No
response expected.
CHAT_USER_LEFT
A person is leaving a chat session. This event occurs as many times as anyone leaves a chat session. No
response expected.
CHAT_INVITE_RECVD
A person is receiving a chat invitation. This event occurs as many times as anyone receives a chat
session invitation. No response expected.
CHAT_DATA_AVAILABLE
When the chat widget has a chat conversation transcript available, this event is raised prior to chat
session end, so that the parent form has an opportunity to save the transcript.
CHAT_SESSION_END
End of the chat session. No response expected.
CHAT_GET_SESSION_TRANSCRIPT_RESP
Provides a specific chat session transcript to the parent form.
List of events sent from the parent form to the AR System Chat Data Visualization Field
Page 354 of 452
Using
Event name
Description
CHAT_SET_CONTEXT_RESP
Raised by the parent form's workflow during or after processing the CHAT_SET_SESSION_REQ event.
No response expected.
FORM_EVENT_LOGOUT
Indicates to the DVF about things happening on the host form or the application. This is not specific to
the chat DVM.
CHAT_GET_SESSION_TRANSCRIPT_REQ
Gets the chat session text transcript that is accumulated in the chat widget's buffer. This request event
causes the DVF to raise the CHAT_GET_SESSION_TRANSCRIPT_RESP event.
When you create an active link that runs on the Event type CHAT_SET_CONTEXT_RESP, the Start Conversation
window is displayed as follows:
Note
Click here to view a .def file sample that uses the above information through the BMC Remedy AR
System form, "ChatTestForm" and it's related active links. Import this .def file using BMC Remedy
Developer Studio and access the "ChatTestForm" from BMC Remedy Mid Tier to view it.
Start Conversation window

(Click the image to expand it.)
Page 355 of 452
Using
To add users to the Friends list, hover the pointer over the user name that is not present in your Friends list and
click the Add to Friend list icon that appears to the left of the user name.
Add user to Friend list on the Start Conversation window
(Click the image to expand it.)
Note
BMC Remedy AR System does not allow searching and adding friends without context. For example, to
see how BMC Remedy ITSM Suite has defined context users, see Initiating a chat conversation (see page
350).
16.7 Subscribing to RSS feeds

Users can to subscribe to configured RSS feeds from within the BMC Remedy ITSM applications. The RSS feed
option must be enabled in the System Settings configuration. To enable RSS feeds, see Enabling chat, Twitter
notifications, and RSS feeds (
https://docs.bmc.com/docs/display/itsm81/Enabling+chat%2C+Twitter+notifications%2C+and+RSS+feeds).
Page 356 of 452
Using
For additional information about configuring RSS feeds, see Defining RSS feeds (
https://docs.bmc.com/docs/display/itsm81/Defining+RSS+feeds).
16.7.1 To subscribe to RSS feeds

1. On the IT Home Page, click the RSS feeds icon
2. When prompted, enter your BMC Remedy AR System password. Enter the authentication string, if
applicable, in the Authentication text box.
For details about authentication string, see Configuring the AR System server for external
authentication (
https://docs.bmc.com/docs/display/ars81/Configuring+the+AR+System+server+for+external+authentication
).
A list of the RSS feeds that have been configured is displayed.

RSS Feed URLs
3. Copy the URL of the RSS feed that you want to add to your RSS feed client (for example, Microsoft Outlook
RSS feeds).
4. Replace the user name and password in the URL with the appropriate values.
You are now subscribed to receive updates for the selected RSS feeds.
16.8 Receiving BMC Remedy ITSM broadcasts on Twitter

The integration with Twitter enables users to receive BMC Remedy ITSM notifications directly to their Twitter
accounts. Users can follow the functional BMC Remedy ITSM Twitter notification account.
To receive BMC Remedy ITSM broadcasts on Twitter:
The functional BMC Remedy ITSM notification account must be created in Twitter, and configured and
authenticated, before users can follow the account.
Users must have a Twitter account that can receive the BMC Remedy ITSM notifications.
For more information about configuring a functional BMC Remedy ITSM Twitter notification account, see
Configuring the Twitter integration (https://docs.bmc.com/docs/display/itsm81/Configuring+the+Twitter+integration).
Page 357 of 452
Using
16.8.1 To follow ITSM notifications on Twitter

1. On the IT Home Page, click the Twitter icon
Note
If the Twitter icon is not displayed, make sure that you configured the twitter integration (see
Configuring the Twitter integration (
https://docs.bmc.com/docs/display/itsm81/Configuring+the+Twitter+integration) and enabled the
Twitter notification functionality (see Enabling chat, Twitter notifications, and RSS feeds (
https://docs.bmc.com/docs/display/itsm81/Enabling+chat%2C+Twitter+notifications%2C+and+RSS+feeds)
).
2. If you are not logged on to the Twitter account, the logon screen is displayed.
3. Log on to Twitter using your account details.
The Twitter website is opened in a new browser window with the Twitter account that was configured for
the broadcast.
4. On the displayed Twitter page, click Follow to receive broadcast messages posted to this BMC Remedy
ITSM Twitter notification account.
For information about sending BMC Remedy ITSM broadcasts using Twitter, see Creating broadcast messages (
https://docs.bmc.com/docs/display/itsm81/Creating+broadcast+messages).
Page 358 of 452
Using
17 Using BMC Atrium Service Context

Note
To use BMC Atrium Service Context, the BMC applications and BMC Atrium Core must be configured to
support it. For information about the configuration procedures, see Configuring BMC Atrium Service
Context for BMC Remedy ITSM applications (
https://docs.bmc.com/docs/display/itsm81/Configuring+BMC+Atrium+Service+Context+for+BMC+Remedy+ITSM+applications
).

To open the Service Context Summary window from a console (see page 360)
To open the Service Context Summary window from the record (see page 360)
Interpreting the information (see page 361)
Related topic (see page 361)
To use the Service Context Summary window, you must belong to at least one of the following permission
groups (https://docs.bmc.com/docs/display/itsm81/Permission+groups+and+application+access):
Asset User (when working from BMC Asset Management)
Work Order User (when working from BMC Service Request Management)
Incident User or Problem User (when working from BMC Service Desk)
Infrastructure Change User or Release User (when working from BMC Change Management)
BMC Atrium Service Context provides information for business service, application, and computer system CIs. See
Adding support staff (https://docs.bmc.com/docs/display/itsm81/Adding+support+staff) for instructions about how to
add people to permission groups.
You can also see summary information about CIs that are related to the business service, but you must have view
permissions for each related CI to see details about those CIs. If you cannot use the BMC Atrium Service Context
feature, ask your system administrator to ensure that you have the correct permissions.
Notes
BMC Atrium Service Context displays information about the CI related to the record you are currently
viewing. The types of information shown can include new work orders, recently completed changes,
recent open incidents, related outage records, and so on. In addition, you can see CIs that are related to
the business service, which helps you to understand the relationship that the business service has with
Page 359 of 452
Using
its environment.
The time threshold that determines how recently the recent changes, recent incidents, or new work
orders were made or submitted, as well as the criteria used to determine other information types is
configurable. Contact your system administrator for information about how the content of the
information types is determined.
Understanding this relationship helps you to prioritize your incident investigations and align your decisions with
your service level agreements and the overall goals of the business.
BMC Atrium Service Context information is displayed in the Service Context Summary window, which you can
open from a variety of locations. The details that you see from, for example, the incident request form, are the
same details that are shown in the other applications of the BMC IT Service Management Suite and Business
Service Management solution, which ensures that everyone in your organization is working with the same
information.
You can view the Service Context Summary window from one of the following locations:
Application consoles
Forms
17.1 To open the Service Context Summary window from a

console
1. With the application console open, in the summary table, select the record you want to see the BMC
Atrium Service Context information for.
2. On the tool bar at the top of the summary table, click Service Context.
The Service Context Summary window opens for the selected record.
17.2 To open the Service Context Summary window from the

record
BMC Service Desk, BMC Change Management, and BMC Service Request Management (for Work Order
records) With the record open, click the Service Context icon beside the Service field. The Service
Context Summary window opens for the selected record.
Service Context icon
Page 360 of 452
Using
BMC Asset Management With the record open, from the Quick Links area of the navigation pane, click
Service Context. The Service Context Summary window opens for the selected record.
Note
In BMC Asset Management, BMC Atrium Service Context is available from the Business Service,
Computer System, and Application CI forms.
17.3 Interpreting the information

The information panel at the top of the Service Context Summary window identifies the service name. The other
information that appears in the information panel is configurable by your system administrator and comes from
the CI form.
Note
For information about the Owner field, see Setting up the Owner field (
https://docs.bmc.com/docs/display/itsm81/Setting+up+the+Owner+field).
Below the information panel is a list of the key attributes. Next to each attribute is a counter that shows the
number of active records of that type that are related to the selected service. If you click the counter, another
Service Context Summary window opens with a table of detailed information about the records.
For example, if one of the configured attributes is "Recent Incidents" and the counter shows 3, there are 3
incidents currently related to the selected service. If you click the counter, a Service Context Summary window
opens with a table that shows summary information about each of the incidents.
The information that appears in the Service Context Summary window is configurable. Ask your system
administrator for detailed information about how BMC Atrium Service Context is configured in your environment.
17.4 Related topic

For information about configuring BMC Atrium Service Context, see Configuring BMC Atrium Service Context for
BMC Remedy ITSM applications (
https://docs.bmc.com/docs/display/itsm81/Configuring+BMC+Atrium+Service+Context+for+BMC+Remedy+ITSM+applications
).
Page 361 of 452
Using
18 Using the Calendar

The Calendar is a dynamic console for scheduling, managing, and monitoring changes and releases, and
secondary data sources like the related activities and manifest. It is intended to be used by enterprise CIOs and
members of the Change Advisory Board (CAB), usually during a CAB meeting, to view incidents, problems,
changes, releases, CI outages, and business events occurring in the organization for a given duration. The
calendar displays the details of the events similar to the way a project management application shows activities
and tasks, except that the Change Calendar is more dynamic and interactive.
The calendar's primary view displays the following information in a calendar-like schedule:
Related change requests and release requests with their scheduled start and end dates
Related business activities and events
Outages (CI unavailability)
Filters enable you to select the primary data source (change or release records) for the calendar data and
secondary data sources like business events and outages in the Calendar view. Other secondary data sources, like
tasks or the manifest related to a change or release record, can be viewed in the Timeline view of the calendar.
With the help of links to investigative and analysis tools, you can better understand the risk and impact of
changes and releases. Because of better planning, you can make more productive decisions about the forward
schedule of changes (FSC). The Change Calendar helps you consider the interdependencies and potential
conflicts made visible through the Calendar console.
Performance issues occur when you use the Change Calendar in Microsoft Internet Explorer
version 8. Therefore, BMC recommends that you use the latest version of Mozilla Firefox or
Internet Explorer 9 for viewing the Change Calendar.
BMC also recommends that you keep the default view as Calendar and time span as Months.
You can configure the maximum number of records that are displayed in the Change Calendar. For more
information, see Limiting the number of records that appear in the Calendar (
https://docs.bmc.com/docs/display/change81/Limiting+the+number+of+records+that+appear+in+the+Calendar).
If the number of records exceeds the limit that you set, the Change Calendar does not show all the
records. For example, if the limit is set to show 100 records, only the first 100 records are displayed. The
records that are displayed are sorted by start date and the time of the activity.
The following topics provide more information about using the Calendar:
Page 362 of 452
Using
What's new in the 8.1.00 calendar (see page 363)

Locating 8.0 features in the new calendar (see page 365)
Calendar functional areas (see page 368)
Change Calendar views (https://docs.bmc.com/docs/display/change81/Change+Calendar+views)
Using the date picker on the Change Calendar (
https://docs.bmc.com/docs/display/change81/Using+the+date+picker+on+the+Change+Calendar)
Creating user-defined queries in the Change Calendar (

https://docs.bmc.com/docs/display/change81/Creating+user-defined+queries+in+the+Change+Calendar)
Exporting events to the ICS file (see page 382)

Example of using Change Calendar (see page 382)
18.1 What's new in the 8.1.00 calendar

The version 8.1.00 Change Calendar is an enhanced calendar tool that provides a more intuitive and visually
appealing experience for users. The user interface has been significantly enhanced for a better user experience.
This topic provides an introduction to the new features:
Additional Change Calendar views (see page 363)
Additional time duration options (see page 364)
Quick actions for calendar entries (see page 364)
View event details (see page 364)
Visual representation of collisions (see page 365)
Impact analysis (see page 365)
Configurable color schemes for change and release requests (see page 365)
Display of CI outages (see page 365)
18.1.1 Additional Change Calendar views

The Change Calendar now provides three views. The existing Calendar view has been enhanced to display a
consolidated view of the change or release requests, with business events and CI outages.
The following new views have been added:
Eventlist view Displays a list of change or release requests with basic details like the request ID,
summary, scheduled start and end date, status, and service. It provides a quick list of all change or release
requests.
Timeline view Displays the ID of the change or release request in the left pane, and the related tasks and
manifest for the selected duration. It provides a quick list of the change or release requests, and the tasks
or manifests related to them.
For more information, see Change Calendar views (
https://docs.bmc.com/docs/display/change81/Change+Calendar+views).
Page 363 of 452
Using
18.1.2 Additional time duration options

The time duration options include the Month view in addition to the Day and Week views that were available. The
timeline bar enables you to select the duration for which you want to view the data. In addition to changing the
duration, you can also move the time range by a day, week, or month earlier or later than the current date. The
time period depends on the that duration you select. You can click Today on the timeline bar to return to the
current date.
Note
The duration of a Week is equivalent to the 5-day and 7-day periods available in the previous version of
the Change Calendar.
18.1.3 Quick actions for calendar entries

The right-click menu provided for change and release requests, and their related tasks and activities, enables you
to perform the following actions on the request if you have the required permissions:
Open the event
Edit the summary and scheduled date and time for the event
Approve, reject, or reassign requests for which you are a valid approver
View Service Context summary information, if the request has a Service CI associated with it
In the Calendar view, you can reschedule the event by using the drag-and-drop feature. When you move the
event to a new date, the scheduled dates are automatically updated. You can use this feature to reschedule
colliding events.
For additional information about these features, see Calendar functional areas (see page 368).
18.1.4 View event details

When you hover your mouse pointer over an event on the calendar, basic details of the event are displayed in a
small window, known as an InfoTip. The calendar provides options for customizing these InfoTips, and enables
you to display the fields of choice for a request.
For more information about configuring InfoTips, see Managing Calendar administrator preferences (
https://docs.bmc.com/docs/display/change81/Managing+Calendar+administrator+preferences).
If you want to view additional details for a change or release request, related tasks or manifest, or CI outages, you
can select the event and click the Details flyout menu. The Details pane also displays collision and impact
information for change and release requests.
For additional information about these features, see Calendar functional areas (see page 368).
Page 364 of 452
Using
18.1.5 Visual representation of collisions

When you select a change or release request and click the Details flyout menu, the Collision Detection tab
displays a list of colliding requests, if any. Colliding changes are displayed in solid shaded blocks enabling you to
view them in the Calendar view and Timeline view.
For more information, see Calendar functional areas (see page 368).
18.1.6 Impact analysis

Similarly, the Impact Analysis tab of the Details flyout menu lists all the relationships of the selected impact type
from the relationship list created for that record within the application.
For more information, see Calendar functional areas (see page 368).
18.1.7 Configurable color schemes for change and release requests

The previous version of the calendar color-coded the change or release records based on the value of the Risk
Level field. The colors for each Risk Level value were predefined.
Now you can customize the field based on how you want to color-code the change or release records.
For more information about customizing the field and colors, see Managing Calendar administrator preferences (
18.1.8 Display of CI outages

CI outages can now be displayed as a part of the calendar when you use the Calendar view.
For more information, see Calendar view (see page 374).
18.2 Locating 8.0 features in the new calendar

This topic provides information about locating features from the 8.0.00 calendar that have been relocated on the
new Change Calendar UI.
Filters in the left pane (see page 365)
Saved filters and quick filters (see page 366)
Main calendar view (see page 367)
Change Calendar administration options (see page 367)
18.2.1 Filters in the left pane

The following changes have been made in the location of filters and other options in the left pane:
Page 365 of 452
Using
Predefined filters like Quick Filter, Filter By Related CI, and Filter By Location are listed under Queries >
Predefined Queries on the Filters & Queries pane. These queries have been renamed as follows:
8.0.00 query name
8.1.00 query name
Quick Filter
Quick Search
Filter By Related CI
By Related CIs
Note: The CI ID Search field for this query, has been replaced by a CI Name search field.
Filter By Location
By Location
Filter By Service
By Service
The list displayed under Queries > Predefined Queries depends on the value selected in the Filters menu. If
you select Change Request from the Filters menu, all queries related to change requests are displayed.
Business event settings that were included in the left pane are available from the Settings > Preferences
menu of the new calendar.
Quick links for creating change or release requests are now available from the Applications flyout menu.
Business events can be created only within the Change Management or Release Management console.
The Print and Reports links have been replaced by the Print and Reports icons on the top-right menu of the
Change Calendar.
The Set Defaults link from the Quick links menu is now available from Settings > Preferences.
Because the durations defined in the new calendar differ from the durations defined in the previous
calendar, the Timespan in option on the Preferences dialog box is selected as Days for the duration
of a day and Weeks for the duration of 5 days or 7 days.
When you access your preferences for the first time, the Preferred query selection is displayed as My
default filter and has the value that was configured for Set Defaults in the previous calendar.
18.2.2 Saved filters and quick filters

If you saved a Quick Filter, Filter by CI, Filter By Location, or Service CI Search, they are migrated to the new
calendar and are listed under Queries > Predefined Queries on the Filters & Queries pane. However, the following
limitations apply:
The Approval Status value has been deferred in the new version of the calendar. If your customized query
included an Approval Status value, this setting is ignored.
If you created a Quick Filter, Filter by CI, Filter By Location, or Service CI Search that included both changeand release-specific fields, the saved search might be migrated incorrectly.
Note
To ensure that these queries are migrated to the My Queries section of the new calendar, verify
that either only change-specific or only release-specific field values are populated in the existing
filter.
Page 366 of 452
Using
If you created a Quick Filter, Filter by CI, Filter By Location, or Service CI Search but did not select a value
for any of the change- or release-specific fields, the saved search is not migrated.
Note
To ensure that these queries are migrated to the My Queries section of the new calendar, select at
least one change- or release-specific value for the query.
18.2.3 Main calendar view

The following changes have been made in the location of options in the main calendar view:
The Quick Filtering option for a day, 5 days, or 7 days has been replaced by durations of a day, week, or
month accessible from the timeline bar. The duration of 5 days or 7 days is now represented as a week.
Business events and change or release requests were displayed in separate panes. Business events are now
displayed as a part of the change or release request pane of the Calendar view of the Change Calendar.
They are not displayed in the Eventlist or Timeline view.
Details of the change or release request, or the business event, are displayed in an InfoTip when you hover
over the event. Full details of the event are displayed in the Details flyout pane.
The date picker that was displayed in the bottom pane of the calendar can now be accessed by clicking the
arrow next to the Change Calendar header, which displays the data filters applied and duration of the
calendar data.
The Legend that was displayed in the bottom pane of the calendar is now displayed in the left pane of the
calendar.
The scroll feature of the calendar has been replaced by the arrows next to the timeline bar. You can click
Today on the timeline bar to return to the current date.
18.2.4 Change Calendar administration options

The following changes have been made in the location of calendar administration options:
The options that were on the General tab are available in the following locations:
Business event settings can now be accessed from the Settings > Preferences option on the Change
Calendar.
Duration can be selected in the Preferences tab of the Calendar Configuration form.
Depth level for services can now be accessed from the Predefined Queries > By Service filter.
Printer preferences can be selected on the system printer settings dialog box.
The options that you could select on the Change and Release tabs can now be defined within a query in
the My Queries tab of the new Calendar Configuration form.
The options on the System tab are no longer applicable.
Page 367 of 452
Using
18.3 Calendar functional areas

The Calendar displays the data for the selected time span in the selected calendar view. From within the various
views, you can perform multiple operations on an event in the calendar. An event can be a change record, a
release record, a business event, or a CI outage.
You can access the Calendar by using the following options:
From the Applications menu, select Change Management > Calendar.
On the Change Management console or Release Management console, choose Functions > View Calendar.
On the Change form or Release form, choose Quick Action > View Calendar.
This topic describes the options that are available when you are viewing events in the Calendar
Filters & Queries (see page 369)
Time durations (see page 371)
Legend (see page 371)
Event InfoTips (see page 372)
Details flyout pane (see page 372)
Right-click menu commands (see page 372)
Drag-and-drop events (see page 373)
Menu icons (see page 373)
The following figure shows the options described in this topic.
Page 368 of 452
Using
18.3.1 Filters & Queries

The Filters & Queries pane provides options for selecting the primary data source and applying additional filters to
the data.
Filters menu
You can choose to view details of change or release requests for the selected duration by selecting the
appropriate option under Filters.
In the Calendar view, you can additionally choose to view business events and outages. In the Eventlist and
Timeline views, these options are disabled.
Queries menu
You can apply additional queries to filter the displayed data by selecting an option from the Queries > Predefined
Queries menu. If you have any user-defined queries, you can select them from the Queries > My Queries menu.
To clear all the additional queries that have been applied, select Predefined Queries > By Status > All Changes.
Notes
Page 369 of 452
Using
The list of queries that is displayed depends on the value selected in the Filters menu. If you select
Change Request, for example, all queries related to change requests are displayed.
Any saved queries migrated from an earlier version of the calendar are displayed under Queries >
Predefined Queries.
Out of the box, the following predefined queries are available:

Query
name
Description
By
Status
View requests by the status selected from the list. The following options are available:
All Draft Changes All changes that are in the Draft status
All Pending Changes All changes that are in the Pending status
All Pre-Scheduled Changes All changes with a status earlier than Scheduled
All Open Changes with Extensive Impact All changes in the Open status and with the Impact defined as Extensive
All Open Changes All changes in the Open status
By
Service
View requests by service CIs.

You can define, save, and delete your own search criteria, based on service CIs. Service CIs are in a hierarchical structure as defined by
the user company. In searching for change requests by service CI, you can specify the depth level at which to search. For example, depth
level 2 means that you are searching the specified CI, its children, and its grandchildren (in the hierarchy tree) for all the related change
requests.
You can view results based on your search criteria in the Calendar by:
Selecting a saved search from the Saved Searches list and clicking OK
Selecting the search criteria and clicking OK
You can define a new service CI search by selecting search criteria and clicking Save Search.
For more information about service CIs, see Creating a CI (https://docs.bmc.com/docs/display/change81/Creating+a+CI).
By
Location
Include an impact location in your search (for example, by Company, region, site group, or site).
You can define, save, and delete your own search criteria based on categories such as change status, approval status, and so on. But you
can further filter requests by choosing options such as product categorization (for example, Software) and assignment (by manager's
name, group, or assignee).
Selecting search criteria and clicking OK
You can define a new location search by selecting search criteria and clicking Save Search.
By
Related
CI
Define, save, and delete your own search criteria based on categories such as status, impact, and so on. You can further filter requests by
choosing options such as operational categorization (for example, Add) and assignment (by manager's name, group, or assignee).
Finally, you can include CI criteria in your search (for example, a CI class such as software).
Page 370 of 452
Using
Query
name
Description
Selecting the search criteria and clicking OK
You can define a new search by selecting search criteria and clicking Save Search.
Quick
Search
Run and create quick searches for change or release requests based on basic fields.
On the Quick Search dialog box, you can perform the following actions:
Define your search criteria and click OK to run it or click Save Search to save your selections.
Run a saved search by selecting it from the list and clicking OK.
Delete a saved search by selecting it from the list and click Delete Search.
18.3.2 Time durations

The date or date range of the data is displayed in the top pane of the Calendar. Click the arrow next to this date to
view the date picker and select a specific date.
Click the arrows next to the timeline bar to change the duration by a day, week, or month, depending on the
duration that you selected. To move back to the current date, click Today on the timeline bar.
Note
The duration of a week is equivalent to the 5-day and 7-day periods available in the previous version of
the Calendar.
18.3.3 Legend
The Legend in the left pane of the Calendar displays details about the field values and the color codes used for
each value. It includes the color codes for business events, CI outages, and colliding changes. By default, the
Legend is displayed, but you can click the down arrow to hide the details.
On the calendar, change and release requests and their related tasks and manifest are shown in transparent
color-coded blocks. Although related tasks and activities are shown in the predefined default color, the color
code for change and release requests can be configured. For more information about configuring the field and
colors, see Managing Calendar administrator preferences (
Business events and outages that can be displayed in the Calendar view are shown in solid bars. When you are
viewing collisions, colliding changes are displayed in solid shaded blocks. These colors are predefined and cannot
be configured.
Page 371 of 452
Using
18.3.4 Event InfoTips

When you hover your mouse pointer over an event, a summary of the requests is displayed in a small window
called an InfoTip. You can configure the fields displayed in the InfoTip. For more information about adding or
removing fields from the InfoTip, see Managing Calendar administrator preferences (
The InfoTip is a subset of the information displayed on the Details flyout pane. To view additional details about a
request or an outage in the Calendar view, click the Details flyout pane.
18.3.5 Details flyout pane

To view additional details of a change or release request and outages, select the record and click the Details
flyout pane on the right of the calendar. In the Timeline view, you can drill down to the related records like
change tasks or release manifest and view their details in the Details flyout pane.
Note
Details of business events are not displayed in the Details flyout pane.
The Details flyout pane displays the following sections:

Activity Info Displays details of the selected request like summary, ID, status, and coordinators
Collision Detection Displays all the colliding changes for the selected duration. You must have run
collision detection for the selected record from the change or release application to view this information
here. When you select a request and select the Collision Detection option in the Details flyout pane, all
colliding changes are displayed in gray shaded blocks on the calendar. For more information about
collision detection, see Detecting CI collisions between change requests (
Impact Analysis Displays all the relationships of the selected impact type from the relationship list
created for that record within the application. You must have run the impact analysis for the selected
record from the change or release application to view this information here. For more information about
impact analysis, see Viewing the impact of CIs on change requests (see page 267).
18.3.6 Right-click menu commands

When you right-click a change or release request in a view, or their related tasks or manifest in the Eventlist view,
all available commands for the selected record are displayed:
Menu
command
Description
Open
Opens the request in the application console if you have appropriate permissions
Page 372 of 452
Using
Menu
command
Description
Edit Event
Displays a dialog box in which you can update the summary or the start and end date of the request. Ensure that the edited scheduled
dates do not conflict with existing events.
Show
Approval
Displays a light version of Approval Central if you are a valid approver. This version of Approval Central is similar to Approval Central but
does not include the left pane available on Approval Central. As a valid approver, you can approve or reject the request, reassign the
request, and save your changes.
Service
Displays the Service Context Summary window of the service CI associated with the selected request, if any. The summary window
Context
displays the basic details of the service CI. For more information about the Service Context Summary window, see Attributes that are
displayed in BMC Atrium Service Context (
https://docs.bmc.com/docs/display/ac80/Attributes+that+are+displayed+in+BMC+Atrium+Service+Context).
18.3.7 Drag-and-drop events

In the Calendar and Timeline views, you can drag change and release requests to another date and time. In the
Timeline view, the date and time of the event is displayed as a tooltip as you drag the request. In case of a
collision, you can use this feature to move the request to a date and time that does not collide with existing
requests. When you move the request, the details of the event are automatically updated to the new date and
time. A confirmation message is displayed based on the success or failure of the operation. If you do not have
permissions to modify the request, an error message is displayed. In the Timeline view, you can also drag related
tasks and activities. However, you cannot move them across change or release requests.
18.3.8 Menu icons

The following icons are available on the top pane of the calendar:
Icon
Description
In the timeline bar, click the arrows to change the duration by a day, week, or month, depending on the duration that
you had selected. Click Today to see the data for the current date.
Click the Refresh icon to refresh the Calendar data.
If you move multiple events within the Calendar, click the Save icon to save changes made to all the records. This option
is enabled only if Bulk Modification is enabled.
Note: You can move events within the calendar only in the Calendar and Timeline views.
Click the Print icon to print the displayed data. When you click this icon, the Print dialog box appears. Select the
appropriate printer and click OK to print the data. In the Eventlist view and Timeline view, a preview of the printed data is
also displayed. In the Calendar view, the Filters & Queries pane is also printed.
Click the Report Console icon to launch the Reporting console to create or view reports. You must have the required
permissions to view the Reporting console.
For more information about creating reports, see Working with reports (
https://docs.bmc.com/docs/display/change81/Working+with+reports).
Page 373 of 452
Using
Icon
Description
Click the Settings icon to perform the following actions:
Set display preferences at a user level. For more information, see Managing Calendar user preferences (
https://docs.bmc.com/docs/display/change81/Managing+Calendar+user+preferences).
Create or modify user defined queries. For more information, see Creating user defined queries.
18.4 Change Calendar views

The Change Calendar provides multiple options for viewing data. You can choose the format of the data and the
duration.
You can view the data in the following formats:
Format
Description
Calendar
Displays data in a calendar view for the selected duration. This view is similar to the Calendar option in Microsoft Outlook. Use this view
for a quick glance of change or release records, business events, and CI outages. For more information about this view, see Calendar
view (see page 374).
Eventlist
Displays a list of change or release requests for the selected duration with basic details like the request ID, summary, scheduled start
date, scheduled end date, status, and service. Use this view for a quick list of all change or release requests. For more information about
this view, see Eventlist View (see page 376).
Timeline
Displays the ID of the change or release request in the left pane and the related tasks and manifest for the selected duration. Use this
view for a quick list of all the changes and related tasks or releases and related manifest. For more information about this view, see
Timeline view (see page 378).
You can view the data for the following durations:

Duration
Description
Day
Displays data for the date selected . In this view, if the event spans more than a single day, the event is displayed on the top of the day
view.
Week
Displays data for the week based on the date selected. A week spans from Sunday through Saturday. In this view, if the event spans more
than a day, the event is displayed on the top of the day view.
Month
Displays data for the month based on the date selected
The date or date range is displayed in the top pane of the calendar. Click the arrow next to this date to view the
date picker and select a specific date. The data displayed is refreshed based on the date and timeline that you
select.
18.4.1 Calendar view

The Calendar view displays change and release requests for the selected duration on a calendar.It also displays
business events and outages.
Page 374 of 452
Using
Select the appropriate options under Filters in the left pane to view details of change or release requests, business
events, or outages for a selected duration. You can apply additional filters to the displayed data by selecting an
option from the Queries menu. To clear all the additional filters that have been applied, select Predefined Queries
> By Status > All Changes.
Change or release requests are displayed in bars with colored outlines. These colors can be configured based on
certain fields. For more information about configuring the field and colors, see Managing Calendar administrator
preferences (https://docs.bmc.com/docs/display/change81/Managing+Calendar+administrator+preferences). Business
events and outages are displayed in solid bars.
The business events that are displayed can be of two types:
Local Specific to the user's company
Global All business events
By default, level 3 business events are displayed. You can configure the type of business events to view in the
Preferences option of the Settings menu. For more information, see Managing Calendar administrator
preferences (https://docs.bmc.com/docs/display/change81/Managing+Calendar+administrator+preferences) or Managing
Calendar user preferences (https://docs.bmc.com/docs/display/change81/Managing+Calendar+user+preferences).
The outages that are displayed are the defined CI unavailability entries.
The following figure illustrates the Calendar view.
Click the figure to expand it.
Page 375 of 452
Using
In this view, you can perform the following actions:

Select a date from the date picker. The date or date range of the data is displayed in the top pane of the
calendar. Click the arrow next to this date to view the date picker and select a specific date. For more
information, see Using the date picker on the Change Calendar (
https://docs.bmc.com/docs/display/change81/Using+the+date+picker+on+the+Change+Calendar).
View data for the adjoining day, week, or month depending on the duration selected. Click the arrows next
to the timeline bar to change the duration by a day, week or month. To move back to the current date,
click Today on the timeline bar.
Click the +n more... link, which is displayed if a large number of events occur on the same day, to view a list
of all the requests, business events, and outages that are scheduled on that day.
Right-click on a request to open, edit, approve, or view service context information. For more information,
see Viewing the Change Calendar (see page ).
Hover your mouse pointer over an event to view basic information about the event. This information is
displayed as an InfoTip. The fields displayed on the InfoTip can be configured. For more information about
configuring InfoTip data, see Managing Calendar administrator preferences (
Select a change or release request and click the Details flyout pane to view additional details of the event.
For a change or release request, the Details flyout pane also displays collisions and impact analysis. For
more information about the Details flyout pane, see Viewing the Change Calendar (see page ).
Note
Business event information is not displayed in the Details flyout pane.
Drag change or release requests to another date and time. In case of a collision, you can use this feature to
move the request to a date and time that does not collide with existing requests. When you move the
request, the details of the event are automatically updated with the new date and time. A confirmation
message is displayed based on the success or failure of the operation. If you do not have permissions to
modify the request, an error message is displayed.
For a full page view of the calendar, collapse the Filters & Queries pane. Click << next to the title of the
pane to collapse it. When collapsed, click >> in the collapsed pane to expand it.
18.4.2 Eventlist view

The Eventlist view displays a list of the IDs of the requests for the selected duration.
Select the appropriate options under Filters in the left pane to view details of change or release requests for a
selected duration. You can apply additional filters to the data displayed by selecting an option from the Queries
menu. To clear all the additional filters that have been applied, select Predefined Queries > By Status > All
Changes.
The Eventlist view displays the following details:
Page 376 of 452
Using
ID of the change or release request

Summary of the event
Status of the event
Any related services
Scheduled start date and end date of the event
The following figure illustrates the Eventlist view.
Click the figure to expand it.

Click the heading row of any of the fields to sort the list of requests on that field.
to the timeline bar to change the duration by a day, week, or month. To move back to the current date,
Right-click on a request to open, edit, approve, or view service context information. For more information,
see Viewing the Change Calendar (see page ).
Page 377 of 452
Using
Hover your mouse pointer over an event to view basic information about the request. This information is
displayed as an InfoTip. The fields displayed on the InfoTip can be configured. For more information on
Select a request and click the Details flyout pane to view additional details of the event. The Details flyout
pane displays relationships for the selected record.
For a change or release request, the Details flyout pane also displays collisions and impact analysis. For
more information about the Details flyout pane, see Viewing the Change Calendar (see page ).
18.4.3 Timeline view

The Timeline view displays the IDs of the change or release requests on the left and the timeline of the selected
duration on the right. All related tasks and manifests are also listed.
For a change request, all related tasks are displayed.
For a release request, all related activities and change requests are displayed. However, tasks of the related
change requests are not displayed.
Select the appropriate options under Filters in the left pane to view details of change or release requests for a
selected duration. You can apply additional filters to the data displayed by selecting an option from the Queries
menu. To clear all the additional filters that have been applied, select Predefined Queries > By Status > All
Changes.
The following figure illustrates the Timeline view.
Page 378 of 452
Using

to the timeline bar to change the duration by a day, week, or month. To move back to the current date,
Click the down arrow next to the request ID to view the related items like tasks, requests, and manifests. All
related items from the Relationship tab of the request are displayed.
Right-click a request to open, edit, approve, or view service context information. Right-click a task or
activity to open, edit, or view service context. For more information, see Viewing the Change Calendar (see
page ).
Hover your mouse pointer over an event to view basic information about the event. This information is
displayed as an InfoTip. The fields displayed on the InfoTip can be configured. For more information about
Select a request, or a related task or manifest, and click the Details flyout pane to view additional details of
the event. The Details flyout pane displays relationships for the selected record. For a change or a release,
the Details flyout pane also displays collisions and impact analysis. For more information about the Details
flyout pane, see Viewing the Change Calendar (see page ).
Page 379 of 452
Using
Drag changes or releases to another date and time. The date and time of the event is displayed as a tooltip
as you drag the request. In case of a collision, you can use this feature to move the request to a date and
time that does not collide with existing requests. When you move the request, the details of the event are
automatically updated with the new date and time. A confirmation message is displayed based on the
success or failure of the operation. If you do not have permissions to modify the request, an error message
is displayed. You can also drag related tasks and activities. However, you cannot move them across change
or release requests.
Collapse the ID pane and view only the timeline of the events.
18.5 Using the date picker on the Change Calendar

The Change Calendar header provides information about the data filters applied and duration of the calendar
data. For example, if the data filter applied is for all open changes and the duration selected is Month, the header
is All Open Changes for August 2012.
The down arrow next to the header displays the date picker for the calendar, as shown in the following figure:
You can perform the following functions on the date picker:

Click < and > to move the calendar to the previous or next month.
Press Ctrl+Up Arrow or Ctrl+Down Arrow to move the calendar to the same month in the previous or next
year.
18.6 Creating user-defined queries in the Change Calendar

The Change Calendar enables you to create customized queries based on frequently required information.
Queries are created for a data source and associated with a related form. Additional qualifiers can be defined to
query data on the related form.
Page 380 of 452
Using
Data source and form associations are created in the Data Source configuration form.
18.6.1 To create or modify a user-defined query

1. Select Applications > Change > Calendar.
2. In the top-right area of the Change Calendar, click the Settings icon and then select Manage Queries.
3. Click Create to create a new query, or select an existing query from the My Queries list and update the field
values to modify it.
4. Enter or modify the following values:
Field name
Description
Query Name
Define the name of the query by selecting or entering up to three levels of categorization for the query. The Query Tier fields
allow three levels of categorization for your search queries
Data Source
This field is autopopulated depending on the data source selected.
Form
Select the form that you want to use to build your filter query. The Form list displayed depends on the data source selected.
For Change Management, the following forms are available:
Change and Associations Performs a search of change records and associated records
Change and Impacted Areas Performs a search of change records and related impacted areas
Change Management Main Form Performs a basic change record search
Release Manifest to Change Association Performs a search for change records included within a release manifest
For Release Management, the following forms are available:
Release and Associations Performs a search for release records and associated records
Release Management Main Form Performs a basic search of the release records
Build
Qualification
Click the (+) icon to add search criteria to the defined filters based on the fields from the data source form. Use the
Advanced Qualification Builder to define the search criteria by using a combination of valid operators, wildcards, and
keywords and fields found on the selected form.
The Advanced Qualification dialog box includes:
Operators and symbols required to create the search query
The Keywords field from which you can select basic BMC Remedy keywords
The Fields option, which displays the database name of the fields available on the selected data source form.
Use the operators, symbols, and fields to create your query, and then click Select to save the query.
For an example about creating a custom query qualification, see Example - Defining advanced qualifications for the
Change Calendar queries (see page 380).
Enable
Select this option to enable the query.
5. Click Save Query to save the new query or updates made to the existing query.
Any new queries that you create are listed under the query tiers that you defined when creating the query
in the Query selection list of the Manage Queries dialog box. Log off and log on again to view the new
queries in the Queries > My Queries list in the Filters & Queries pane.
6. Click Save to save your changes.
Tip
Page 381 of 452
6.
Using
To delete an existing query from the Query Selection list, select it and click Delete.
18.7 Exporting events to the ICS file

This page has not been approved for publication.
18.8 Example of using Change Calendar

Allen is implementing a new payroll system in the organization. The installation of the new payroll server will
affect the availability of other servers in the organization. The Calendar can help Allen decide the most
convenient time to start this implementation with minimum impact to the people of the organization.
When Allen views the Calendar, he can see the complete details of the events for the duration in the view
configured by the application administrator.
Note
You can configure your viewing preferences from the Settings menu provided. For more information on
configuring display settings, see Managing Calendar user preferences (
https://docs.bmc.com/docs/display/change81/Managing+Calendar+user+preferences).
By looking at the Calendar view for a month, Allen can quickly decide that scheduling a major server installation
on a particular day that has multiple events would overload already strained resources. Any day that has fewer
events would be more promising. The calendar displays not only scheduled change or release requests but also
planned outages or business events, giving Allen better visibility of the load for the selected duration.
If required, Allen can switch to the week to look more closely at the week's schedule or select a Day view to get a
more granular view of the data. He can use the arrows next to the timeline bar to move to an earlier or later time
period of the selected duration.
When Allen finds a time when no time segments are blocked, he can decide to schedule the payroll server
installation. The server installation schedule can overlap other software application installations based on the
organization's configuration policy.
When Allen schedules the installation, if the server installation impacts a CI that might be unavailable or required
by another request during that time, the calendar provides an indication of colliding records. He can also view the
Service Context summary for a Service CI related to the change or release request.
Additionally, Allen can select a request from the calendar and view essential details like the ID, status, and so on,
or open the change request by using the Open option from the right-click menu on the calendar. He can click the
Details flyout pane to view additional details including Collisions and Impact.
Page 382 of 452
Using
19 TMS templates
For greater productivity, the Task Management System (TMS) module allows you to create task templates or
group task templates within task group templates. Users can reuse these templates at runtime during the
fulfillment of a change request or while resolving an incident or problem.
During the definition stage, the task administrator can create various templates for later use during the execution
stage. Following are the types of templates:
Variable templates (see page 410)
Task templates (see page 384)
Task group templates (see page 397)
The following figure shows the relationships among the templates you create during the definition stage and how
those relationships are used at runtime during the execution stage. For example, the administrator designs an
advanced task group template (Task Group Template [itsmps:0]) that associates various task templates (Task
Template [itsmps:A], Task Template [itsmps:B], and so on) in the definition stage. The task group template is
designed according to a specific flow: Task Template [itsmps:A] runs first, and then it branches to Task Template
[itsmps:B] and Task Template [itsmps:C]. When they are completed, Task Template [itsmps: D] starts. The
following figure illustrates advanced template definitions in TMS.
Advanced template definitions in TMS
Page 383 of 452
Using
The administrator adds the Task Group Template [itsmps:0] task group template to any BMC Remedy application
that runs on BMC Remedy AR System, for example, BMC Change Management or some other application you
have created.
At runtime, users of the BMC Remedy Change Management application (for example, the change manager) can
select the Task Group Template 0 task group template from inside a change request. The change manager
assigns all the tasks to task users. When the task user begins working on Task [itsmps:A] and finishes it, it is set to
Closed. The next task user is then notified to start on Task Template [itsmps:B]. When all the tasks are Closed or
Canceled, the task group is set to Closed.
Note
To perform procedures in this section, you must have Task Administrator permission. For information,
see Task Management System permission model (see page 383).
19.1 Task templates

A task template defines a unit of work that carries out a single step in handling a change. At runtime, task
templates are generated as tasks. In the execution stage of a task, the Task form at runtime displays an extra tab
Page 384 of 452
Using
labeled Data. This Data tab makes available a pool of fields (for example, Character01, Character02, and so on)
that you can dynamically use with variable templates. The field label was updated to show the new variable name.
Tasks consist of a combination of the following components:

An automatic action that runs by itself and must be carried out
A specified action that must be accomplished
Data that is entered or mapped in the form of input variables
Data that is written from the task to another task or task group in the form of output variables
These components are configured within the task template.
BMC Change Management, BMC Incident Management, and BMC Problem Management integrate different
amounts of the TMS functionality. The BMC BladeLogic Client Automation integration is launched from within
The task is the main action component of the TMS all the work that is done toward managing and
implementing a change request at runtime is carried out through tasks. In short, a task is a unit of work that is
completed as a step in implementing a change request.
The administrator can create the following distinct types of task templates:
Manual, in which an action (for example, replacing a cable) is performed by a person
Automatic, in which a predefined instruction is automatically executed by the task
At runtime, you can generate tasks in the following ways:
Automatically as part of a task group or a change request. For example, if a change occurs and the change
manager selects a task group, any tasks that are contained within the task group are generated according
to how the flow has been defined.
By selecting from a list of task templates. For example, if a change occurs for which no task group has been
defined, the change manager still has access to all defined task groups and task templates.
Note
If the task template has its Visible value set to No, it cannot be directly selected at runtime.
You can specifically create an ad hoc task to perform some action during a change where no defined task
template is appropriate.
For additional information about creating tasks at runtime, see Viewing tasks at runtime (
https://docs.bmc.com/docs/display/change81/Viewing+tasks+at+runtime).
Note
Page 385 of 452
Using
Six predefined, best practice task templates are automatically installed with BMC Change Management
for integration with BMC BladeLogic Client Automation. As an administrator, you can predefine
additional task templates to use with BMC Change Management.
19.1.1 Creating a task template

You create a basic or advanced predefined task template by completing the following procedures.
Opening the task template form (see page 386)
Entering task template details (https://docs.bmc.com/docs/display/change81/Entering+task+template+details)
Classifying the Task Template form (see page 389)
Defining assignments for the task template (see page 389)
Defining automatic commands (see page 390)
Defining qualifications for task completion (see page 391)
Specifying financial information (see page 391)
Specifying usage information for task templates (see page 392)
Viewing system information for task templates (see page 392)
Opening the task template form

1. On the IT Home page, click the Application Administration Console link.
2. On the Application Administration Console, click the Custom Configuration tab.
3. From the Application Settings list, choose Task Management System > Task Configuration > Task Template,
and then click Open.
Entering task template details

Here you define important task template details, for example, the type of task or the application it applies to.
To enter information in the top pane of the form

1. On the Task Template form, fill in the required fields:
Field
name
Description
Company
The company to which this variable applies
Name
The name of the task template
Summary
A brief description of the purpose of this task template
Type
The type of task template. The options are as follows:

Manual Requires a person to take a certain action. Usually, the person is notified of their assigned task.
Automatic Performs automatic action, for example, rebooting a server
If you select this option, you must specify an automatic command on the Automatic tab before you can save the task
template.
Page 386 of 452
Using
Field
name
Description
For more information, see Creating automatic tasks (see page 304).
Status
The status of the task template. The options are as follows:

Active Enables the template for use during the execution stage
Inactive Deactivates the template. Inactive objects cannot be used at runtime. Usually, you set an object to Inactive
when it is no longer used at runtime, but might be needed again in the future. When it is needed again, you can reset it to
Active.
Potential Puts the template into inactive status. You can design the template without activating it.
2. Fill in the optional fields:

Field name
Description
Category
The application to which group of templates this one belongs. The menu is data-driven by active records in the Integration
Configuration form. For information, see Configuring integrations (
https://docs.bmc.com/docs/display/change81/Configuring+integrations).
SubCategory
An optional sub-category description
Notes
A description of the variable template's function or any other helpful text for future administrators and designers
Priority
The priority of the task template. The priority is applicable during the execution stage.
Visible
Indicates whether this template is visible or hidden to the user for selection during the execution stage
Locale
The locale to which this template is applicable
3. Click Save.
From the General tab, you can specify commands and their parameters, and if the task template is global or used
by a specific company.
To enter information in the General tab

1. On the General tab of the Task Template form, enter the indicated information in the fields that are
grouped as shown in the following table:
Field group
name
Description
Task
Location
area
(Required)
Company information in the Task Location fields. This task template is specific to the company you select.
Command
A Launch Command or Details Command that executes at runtime. Some best practice commands are provided for use
when TMS is being used with the BMC BladeLogic Client Automation applications. Additional commands can be defined for
any other third-party application.
The Region, Site Group, and Site fields are dynamic, which means that the values you can select from these fields are
dependent on the previous selection.
Examples:
A Launch Command is the TMS_OUT_CMS_POLICYMGR used with the BMC BladeLogic Client Automation Policy
Manager task template.
Page 387 of 452
Using
Field group
name
Description
A Details Command is the TMS_OUT_CMS_CHKCOMPLIANCE_STATUS used with the Closed Loop Verification task
template to set up compliance parameters for Closed Loop Verification.
For more information, see Application and task integrations.
Task
Attachments
Attachments that might be necessary for this task template. Attachments might be how-to documents that helps the user
complete the task when the template is used during the execution stage.
Time Out
The timeout value, status, and status reason for the time out. The timeout value is applied to the Activate time field on the
runtime objects. If this timeout value is reached, then the Task or Task Group is set (by an escalation of ten minute intervals)
to the predefined status value.
Note: The clock stops when a Task or Task Group is in Pending status.
The fields in the Time Out section are:
Time Out Value The amount of time after which the task times out at runtime
Unit Seconds, minutes, hours, or days
Time Out Status The status that is set when time out is reached
Time Out Status Reason A corresponding status reason for the status value, if applicable
Both the Launch Command and Details Command on the General tab of the Task Template form are
features that, on the runtime task form, require manual intervention to drive them. In both cases, the user
must click a button.
Only manual task templates should have launch commands. All of the CCM manual task templates
have examples of Launch Command.
Automatic tasks can have a Details Command. Users might get assigned to monitor such a task, and
they might want to do a manual check on an external application, for example, as with the Closed
Loop Verification (automatic) task template for CCM.
For more information, see Predefined task group and task templates (see page 413).
2. (Optional) Click the Define Commands button to view existing commands or create a new command.
Note
Applications for which commands are being defined must be registered in the CAI.
Commands are defined and stored in the Command Automation Interface (CAI) forms. Every command
consists of the following items:
Command Construct a command that is executed at runtime. Commands are static values, for
example, Send.
Parameter Construct a parameter for the command. Parameters are dynamic values that are
defined at runtime from the Tasks form.
For more information, see Command Automation Interface (
Page 388 of 452
Using
https://docs.bmc.com/docs/display/itsm81/Command+Automation+Interface) and Defining command
parameters (https://docs.bmc.com/docs/display/itsm81/Defining+command+parameters) in the BMC

Remedy IT Service Management Configuration documentation.
3. Click Save.
4. Continue setting up the task template, as described in Classifying the Task Template form (see page 389).
Classifying the Task Template form

You use the Classification tab to specify if the task uses product categorization or operational categorization
values.
To classify the task template

1. On the General tab of the Task Template form, click the Classification tab.
2. Enter information in the following fields:
Field name
Description
Operational Categorization
Values from the Operational Categorization lists to classify the task
Values from the Product Categorization lists to classify the task
3. Click Save.
4. Continue setting up the task template, as described in Defining assignments for the task template (see page
389).
Defining assignments for the task template

Use the Assignment tab to specify if the task template should be automatically assigned to a company, group, or
individual. You can also specify if assignees should be automatically notified if a task is assigned to them.
To specify assignment information for the task template

1. On the Assignment tab of the Task Template form, enter information in these fields:
Field name
Description
Assignee Company
The company which is assigned runtime tasks from this task template
Process Name
A process name for the task assignment. This is set up in the Assignment Engine for individual auto-assignment.
Assignee
Organization
The organization from the selected company that is assigned this task
Assignee Group
The group to which this task is assigned at runtime
Assignee
The assignee to whom this task is assigned at runtime
Notify Assignee
Whether the assignee should be notified of the task assignment. The notification method is specified in the
individual's People record.
2.
Page 389 of 452
Using
2. Click Save.
3. Continue setting up the task template form by creating input and output variables, as described in Mapping
input and output variables (see page 410).
Defining automatic commands

The Automatic tab on the Task Template form appears only if the task template that you are defining is for an
Automatic task. You can also create an automatic task that queries fields for approval.
On the Automatic tab, you define the Automatic Command of an automatic task template. All the components
necessary to drive the automatic task template are defined on the Automatic tab. Automatic task templates imply
that the runtime task instantiated from them can automatically run without human intervention. A user could be
assigned to monitor the task but that is not required.
For more information, see Creating automatic tasks (see page 304) and Application and task integrations (
https://docs.bmc.com/docs/display/change81/Application+and+task+integrations).
To set up automatic commands

1. On the Automatic tab of the Task Template form, define automatic commands for this task template:
Field name
Description
Automatic
Command
A command, which is defined as a menu item. The following automatic commands are available:
Add Fields Field1 gets the value of Field2 + Field3; internal to the TMS module
Check Approval Checks to see if approval has been obtained. Frequency of approval check is based on the interval
defined below. Internal to the TMS module. For more information, see Creating automatic tasks.
Copy Field Field1 gets the value of Field2; internal to the TMS module
Set Compliance Best practice automatic task for BMC BladeLogic Client Automation integration. This command
triggers a filter that has a web service (consuming). However, you must install and configure the full CCM integration to
use this functionality.
Set Decimal Field1 gets the contents of Decimal; internal to the TMS module
Set Text Field1 gets the contents of Text; internal to the TMS module
Subtract Fields Field1 gets the value of Field2 - Field3; internal to the TMS module
Automatic
Description
A description of the automatic functions of this task, which guides how the template should be created. This field is populated
when you select an automatic command.
Note: Because the Automatic tab is not displayed in the runtime task, the Name, Summary, and Notes fields should describe
what the automatic task does.
Field 1,
Field 2,
Field 3
(If applicable) The names of these fields that the automatic action requires input from or output to; used with Add Fields,
Copy Field, Set Decimal, Set Text, and Subtract Fields automatic commands
Text
Information about how the automatic action should be implemented and how it should behave; used with the Set Text
automatic command
Decimal
Enter a number to more directly determine the value to be used in an action; used with the Set Decimal automatic command
Interval
Sets the AutomaticIntervalTime based on the interval defined, for example, 1. You use it in connection with the Unit field and
the Check Approval automatic command. For more information, see Creating automatic tasks (see page 304).
Page 390 of 452
Using
Field name
Description
Interval
Sets the AutomaticIntervalTime based on the unit defined, for example, Days, Hours, or Minutes. For more information, see
Unit
Creating automatic tasks (see page 304).
Retries
Number of times this automatic task is retried in the Number of Retries field. This feature allows an automatic task to be
retried if it returns with a Return Code Value of FAILURE.
2. Click Save.
3. Continue setting up the task template by defining completion qualifications, as described in Defining
qualifications for task completion (see page 391).
Defining qualifications for task completion

By default, a task is considered complete when it is run. When a task is complete, its status is Closed and its status
reason is either Success, Canceled, or Failed. If you want other ways of determining whether a task is complete or
successful, you can build qualification statements.
If the qualifications are not met, the task does not close. You set qualifications for task completion only if the task
is automatic.
Note
If a task's status is set manually at runtime, the settings defined here are overridden.
To define qualifications for task completion

1. On the Completion tab of the Task Template form, build a qualification to indicate completion for this task,
template:
Field name
Description
Done Qualification
A qualification statement that is used to evaluate whether the task is complete. A task is done when it is marked as
Closed.
Success
Qualification
A qualification statement that is used to evaluate if the task is successful
2. Click Save.
3. Continue setting up the task template, as described in Specifying financial information (see page 391).
Specifying financial information

Your task template can include auto-cost estimates. You use this information to forecast the cost of the task. For
example, you budget the change should take two hours to perform.
Page 391 of 452
Using
To specify financial information

1. On the Financials tab of the Task Template form, define financial details for this task template:
Field name
Description
Budget Calculation Unit Type
How to measure the cost. Choices are Flat Rate, Hours, or Minutes.
Estimated Total Time
The time based on unit type
2. Click Save.
3. Continue setting up the task template, as described in Specifying usage information for task templates (see
page 392).
Specifying usage information for task templates

The Usage tab tracks whether the task template is being used by Task Group Templates, Parent Templates, or
Request Templates. The metrics indicate how many times the template was used at runtime and some of the
most important status values, for example, Last Used or Closed Success.
Note
The Usage tab does not appear until you save the task template.
To specify usage information

1. From the Show field on the Usage tab on the Task Template form, select Task Group Template, Parent
Template, or Request Template (for example, Change Template).
2. The Used By Templates table shows other templates that are using the task template.
3. Click Save.
4. Continue setting up the task template, as described in Viewing system information for task templates (see
page 392).
Viewing system information for task templates

Review the information about the System tab of the Task Template form. The System tab shows internal
information about the task template.
19.1.2 Example of creating task templates with a workflow

The following procedure is an example of how to create task templates with workflow. The example illustrates
how you can leverage the flow logic in a task group template to bypass tasks.
Page 392 of 452
Using
To build TMS workflow to bypass tasks

1. Create a variable template:
a. From the Application Settings list, choose Task Management System > Task Configuration > Variable
Template, and then click Open.
b. In the Variable Template form, create an entry with the following selections:
Field
Setting
Name
Phone Type
Company
Your company
Type
Local
Status
Active
c. Save and close the Variable Template form.

For more information, see Variable templates (see page 410).
2. Create the phone contact task template:
a. From the Application Settings list, choose Task Management System > Task Configuration > Task
b. In the Task Template form, create an entry with the following selections:
Field
Setting
Name
0 - Phone Contract
Summary
Fill Out Phone Contract
Type
Manual
Status
Active
c. Click the General tab, and then select your company.

d. Click the Assignment tab, and then enter the assignment settings.
e. Click the Output tab, and then map field Character 01 to Phone Type as the local output variable.
f. Click Add to create the output variable mapping.
g. Save the Task Template form.
For more information, see Task templates (see page 384).
3. Create the first phone task template:
a. In the Task Template form, create an entry with the following selections:
Field
Setting
Name
1 - ATT Phone Type Selection
Summary
Select from ATT, Apple, Motorola
Type
Manual
Status
Active
b. Click the General tab, and then select your company.

c.
Page 393 of 452
Using
c. Click the Assignment tab, and then enter the assignment settings.
d. Click the Input tab, and then map Phone Type as the local input variable to the Character 01 field.
e. Click Add to create the output variable mapping.
f. Save the Task Template form.
4. Create the second phone task template:
Field
Setting
Name
1 - Apple Phone Type Selection
Summary
Type
Manual
Status
Active

5. Create the third phone task template:
Field
Setting
Name
1 - Motorola Phone Type Selection
Summary
Type
Manual
Status
Active

6. Create the last task template:
Field
Setting
Name
2 - Register Phone
Summary
Register Phone
Type
Manual
Status
Active

c.
Page 394 of 452
Using
d. Click Add to create the output variable mapping.
e. Save and close the Task Template form.
7. Create the task group template.
For more information, see Advanced task group template - Standard type (see page 401).
a. From the Application Settings list, choose Task Management System > Task Configuration > Task
Group Template, and then click Open.
b. In the Task Group Template form, create an entry with the following selections:
Field
Setting
Name
New Cell Phone Template
Summary
Cell Phone Procurement
Company
Your company
Type
Standard
Note: Select Standard, not Sequencing (the default).
Status
Active
c. Click the Association tab, and then add the task templates you created to the list of current
associations.
d. Click the Flow tab to define the flow relationships between the tasks.
To bypass tasks, you must configure the output of the previous task to be the input on the next task
in the process flow. You then must qualify some tasks so that a particular selection by the person
working the task determines the task flow.
e. Create the following Flow Relationships:
From Task Group or Task (Predecessor Name)
To Task Group or Task (Successor Name)
Start
0 - Phone Contract
0 - Phone Contract
0 - Phone Contract
0 - Phone Contract
2 - Register Phone
2 - Register Phone
2 - Register Phone
To create the flow relationship, you select a task from each of the tables, and then click Flow To. If
you make a mistake, click Remove to delete the relationship.
f. Edit the flow relationship of all the predecessor tasks at level 0 (Phone Contract) that flow to the
successor of the three separate phone type selections at level 1.
For example for the Phone contract to Apple Phone Selection, select the entry under the Flow
Relationships, and then press Edit.
g.
Page 395 of 452
Using
g. Click the Input tab on the Flow Template dialog box, and then map Phone Type as the local input
variable to the Character 01 field.
h. Click Add to create the output variable mapping.
i. Click the Qualification tab, and then enter the following qualification criteria:
'Character 01' = Apple"
j. (Optional) Edit the evaluation and flow criteria, as needed.
k. Create flow qualification criteria for the ATT and Motorola tasks:
'Character 01' = ATT"
'Character 01' = Motorola"
8. Create a sample change request.
9. Add the New Cell Phone task group template to the change request.
10. Use the Process Flow Status bar to work the change request to Implementation In Progress status.
11. Click the Tasks tab, and then click View Flow.
You see how your task flow is branched in the Task Flow Viewer. The following figure illustrates tasks
branched in the Task Flow viewer.
12. View the first assigned task (0 - Phone Contract) in the change request.
13. In the Task form, click the Data tab.
14.
Page 396 of 452
Using
14. In the Phone Type field, enter ATT.

Many field types are available to you for mapping variables. This example only used a character field. But
there are also numeric fields, date/time fields, and so on. When you mapped 'Character 01' to the 'Phone
Type' variable, the field label is updated to show the variable name.
15. Work the task to the Closed status.
When you return to the change request, you now see that the Apple and Motorola tasks have been
bypassed.
This procedure has been a short example of a standard task group template showing how tasks can be bypassed
using built-in workflow in TMS. The bypass state is not selectable by the user, but rather is a result of workflow
processing within the task group flow. If users try to bypass the tasks manually, they will see an error.
19.2 Task group templates

A task group template is a container object that contains tasks and other task groups. When you create a task
group template, you must associate task and task group templates. Task group templates also support the use of
variables.
Note
To perform procedures in this section, you must have Task Administrator permission. For information,
see Task Management System permissions (
https://docs.bmc.com/docs/display/change81/Task+Management+System+permissions).
There are two different types of task group templates:

Basic Uses sequencing to strictly specify the order of the tasks. For more information, see Basic task
group templates - Sequencing type (see page 398).
Advanced Uses a flow mechanism that establishes how the tasks relate to each other. For advanced task
group templates, you can create flow between tasks and task groups to indicate how they behave at
runtime. For more information, see Advanced task group template - Standard type (see page 401).
Before you create a task group template, you should create all the task and task group templates that it contains.
Recommendation
One predefined recommended task group template is automatically installed with BMC Change
Management for integration with BMC BladeLogic Client Automation. As an administrator, you can
predefine additional task group templates to use with BMC Change Management.
Page 397 of 452
Using
19.2.1 Basic task group templates - Sequencing type

Creating a sequencing type of task group template offers the most basic functionality of task group templates.
Sequencing type task templates are also the easiest for administrators to create. The sequence of tasks in a basic
task group template occurs in the strict order that the administrator defines. As a result, administrators and users
do not need to handle complicated qualifications in the task flow.
If needed, users can change the sequence at runtime.
Note
When you are designing your basic task group template, remember that task group templates can
include task templates but also other task group templates. Adding task group templates to your basic
task group template can easily complicate the sequence of tasks offered to users.
Basic template definitions in TMS
Page 398 of 452
Using
Creating a basic task group template

You create basic task group templates from the Application Administration console.
This procedure assumes you already created variable and task templates to include in your basic task group
template. For more information, see the following topics:
Task templates (see page 384)
To create a basic task group template

3.
Page 399 of 452
Using
3. From the Application Settings list, choose Task Management System > Task Configuration > Task Group
4. On the Task Group Template form, select Sequencing as the type of task group template.
This type of task group template contains task templates and task group templates where the sequence
can be changed by users during the execution stage at runtime.
Note
If you select the Sequencing (Basic) type of task group templates, the Flow and Operations tabs do
not appear on the Task Group Template form. Data that is not relevant for the Sequencing (Basic)
type is cleared from the form.
5. In the required task group template fields, enter a Name, Summary, and a Company.
6. In the Category field, select the application to which this task group template belongs, for example, BMC
Change Management.
If you are creating a parent object, you must create a configuration record. For more information, see
Configuring integrations (https://docs.bmc.com/docs/display/change81/Configuring+integrations).
7. On the Association tab, select the task templates and task group templates that your basic task group
template should contain.
These task templates and task group templates are then associated with the basic task group template. At
runtime, when a task group is generated, the associated task groups and tasks are generated to handle the
change.
As shown in Creating associations (see page 403), you can add tasks to the list of current associations. You
can then click the up or down arrows to order the task sequence (for example, 1, 2, 3, and so on). If you do
not order the task sequence (for example, their default sequence is 1, 1, 1, and so on), users can fulfill them
in any order. For more information, see Creating associations (see page 403).
Defining the sequences of tasks in the task group template
8.
Page 400 of 452
Using
8. Click the Input and Output tabs and add variable mappings.
Variable mappings enable data to be passed in to and out of fields when the task group is executed. To
define variable mappings, you map an existing variable to or from a field. For more information, see:
Mapping input and output variables (see page 410)
9. (Optional) Click the Completion tab.
By default, a task group is considered complete when all the task groups or tasks that it contains have run.
When a task group is complete, its status is evaluated. This status can be either Success or Failed. By
default, the task group is considered successful when all the task groups or tasks that it contains have a
status of Success. If any do not have a status of Success, the task group has a status of Failed or Canceled.
For more information, see Defining Done and Success qualifications (see page 409).
10. Click Save.
19.2.2 Advanced task group template - Standard type

The task group template provided with the BMC Remedy ITSM Suite of applications uses advanced - type task
group templates. Advanced task group templates provide a sophisticated flow mechanism that lets you define
how task templates and task group templates relate to each other. You can also use operators to define task
completion.
Note
Unlike basic task group templates that utilize sequencing, users _cannot_change the sequence at
runtime with advanced task group templates. For a step-by-step procedure to create advanced TMS
workflow that bypasses tasks, see Example of creating task templates with a workflow (
https://docs.bmc.com/docs/display/change81/Example+of+creating+task+templates+with+a+workflow).
Creating advanced task group templates

You create advanced task group templates by completing the following tasks:
Opening the Task Group Template form (see page 402)
Entering information in the top pane and the General tab (
https://docs.bmc.com/docs/display/change81/Entering+information+in+the+top+pane+and+the+General++tab)
Creating associations (see page 403)

Creating flow for task group templates (see page 404)
Defining qualifications (https://docs.bmc.com/docs/display/change81/Defining+qualifications)
Mapping input and output variables (see page 410)
Defining operations for completing tasks (see page 407)
Defining Done and Success qualifications (see page 409)
Specifying usage information (see page 409)
Page 401 of 452
Using
Opening the Task Group Template form

3. From the Application Settings list, choose Task Management System > Task Configuration > Task Group
4. From the Type field on the Task Group Template form, select Manual.
Selecting Yes in the Visible field causes data relevant only for the Manual type to appear in the Task Group
Template form, for example, the Flow and Operations tabs.
Entering information in the top pane and the General tab

Here you define important task group template details, for example, the type of task group template (Standard) or
the application it applies to.
Note
If you select the Standard (Advanced) type of task group templates, the Flow and Operations tabs appear
on the Task Group Template form. These tabs so not appear with the Sequencing (Basic) task group
template. Data that is not relevant for the Standard (Advanced) type is cleared from the form.
To enter information in the top pane and the General tab

1. On the Task Group Template form, fill in the required fields:
Field
Name
Description
Name
The name of the parent task group
Summary
A brief description of the purpose of this parent task group template
Company
A company name. This parent task group is available only to the company you select.
Type
The type of task. The options are as follows:

Sequencing This type of basic task group template contains task templates and task group templates where the
sequence can be changed by the user during the execution stage.
Standard This type of advanced task group template contains task templates and task group templates that executes in
the flow defined by the task administrator.
Note: If you are creating an advanced task group template, select Standard.
Status
The status of the group task template. The options are as follows:
Active Enables the template for use at runtime
when it is no longer used at runtime, but might be needed again in the future. When it is needed again, you can set it to
Active.
2.
Page 402 of 452
Using

Field Name
Description
Category
The application to which this group of task group templates belongs
SubCategory
An optional sub-category description
Notes
A description of the task group template's function or any other helpful text for future administrators and designers
Priority
A priority for the task group template. The priority applies during the execution stage.
Visible
Indicates whether this template is visible or hidden to the user for selection during the execution stage
Locale
3. Enter information in the General tab:

Area name
Description
Time Out
A timeout value, a status, and status reason for the time out
The timeout value is applied to the Activate time field on the runtime objects. If this timeout value is reached, the Task or
Task Group is set (by an escalation of ten minute intervals) to the predefined status value.
Note: The clock stops when a Task or Task Group is in Pending status.
The fields in the Time Out section are:
Time Out Value The amount of time after which the task times out at runtime
Unit Seconds, minutes, hours, or days
Time Out Status The status that is set when time out is reached
Time Out Status Reason A corresponding status reason for the status value
Task Group
Attachments
Attachments that might be necessary for this task group template. Attachments might be how-to documents that helps the
user complete the task group when the template is used during the execution stage.
You can add up to three attachments for each task group template.
4. Click Save.
5. Continue setting up the task group template by creating associations between the task templates and the
task group templates that are contained in this task group template, as described in Creating associations
(see page 403).
Creating associations
When defining a task group template, you select the task templates and task group templates that it should
contain to complete a certain action. These task templates and task group templates are then associated with the
task group template and are called associations. At runtime, when a task group is generated, the associated task
groups and tasks are generated to handle the task group.
Note
All associated tasks and task groups that are built into a task group's flow follow the defined flow at
runtime, unless you set up a Sequencing type of Task Group template.
Page 403 of 452
Using
After you have defined the associations, you can establish how they should interrelate at runtime by creating flow
between them. For more information, see Creating flow for task group templates (see page 404).
To define an association
1. On the Task Group Template form, click the Association tab.
The task group templates and task templates that have been defined are listed in the Available Task Groups
and the Available Tasks tables. If any have been selected, they are appear in the Current Associations table.
2. From the Available Task Groups or the Available Tasks table, select a task group or task template to add to
the task group template you are currently defining, and then click Add.
The task group template or task template appears in the Current Associations table.
Notes
Unlike basic task group templates that utilize sequences in the order of tasks, no task
sequence is provided for advanced task group templates.
If you want the same task template or task group template to be used more than once at
runtime, you must add it to the Current Associations table as many times as you want it
used. When you add the same task template or task group template more than once, the
number in the Instance column is incremented to indicate that this is a new instance.
3. To remove a task template or task group template from the Current Associations, select it and then click
Remove.
4. Click Save.
5. Continue creating the task group template by defining the flow between the associations you just created,
as described in Creating flow for task group templates (see page 404).
Creating flow for task group templates

When you define an advanced task group template, you can establish how the associated task group templates
and task templates relate to one another. This is called flow. The flow determines the sequence in which task
group templates and task templates are generated at runtime. If the task group template contains other task
group templates, these likely already have flow established between the task group templates or task templates
that they contain.
A task group template's flow consists of one or more flow relationship records. Each flow relationship record
consists of a task group or task template, called the predecessor, which is linked to another task group or task
template, called the successor.
To indicate the first steps of the flow, you can use the Start record that is provided by the system and link it to a
successor task group or task template. This successor is the first task or task group that is generated when this
task template is invoked.
Page 404 of 452
Using
All active task group and task templates listed in the Current Associations table that are not identified as
successors also are generated as soon as the task group template is invoked at runtime. These tasks are not part
of the advanced flow and can be fulfilled at any time. Multiple instances of the same task or task group template
without predecessors generate multiple instances of tasks or task groups at runtime.
To have two tasks start at the same time, you can mark them both as Start.
To have tasks or task groups occur simultaneously, you can link the same predecessor to more than one
successor. To have more than one task or task group completed before a successor can start, you can link two or
more predecessors to the successor. All predecessors must be completed before the successor task or task group
can start.
When defining flows, ensure that you do not create loops. Be especially careful if you are linking more than one
instance of the same task or task group template within the flow. Check the instance number of the task or task
group in the Instance Number column to make sure that you are not linking to the same one.
All predecessors must be completed before the successor task or task group can start (unless the setting is
changed to Any Complete in the Flow to Successor when field in the Qualification tab of the Flow Template
form).
You can also create a qualification that is used to determine how the flow should be generated. Qualifications use
data supplied by input variables to determine the flow. Before you define a qualification, you must map variables
to fields on the form. Then you can define the qualification against the fields.
For example, you can use the value retrieved from a question in a variable. The flow from the task loads the
variable into a working field using the flow mapping on the flow details page. The qualification references the
field.
Note
The two special system variables, Predecessor Status and Predecessor Failure Code, are available only
for flow. They do not require input variables to be defined.
All associated tasks and task groups that are built into a task group's flow follow the defined sequence at runtime.
To create flows among associations

1. On the Task Group Template form, click the Flow tab.
The task and task group associations that were selected in the Association tab appear in both of the tables
in the upper section of the tab. If any flow relationships have been defined, they appear in the Flow
Relationships table. The first task usually follows the Start point.
Tip
Page 405 of 452
Using
To view any of the task groups or tasks in either of the tables in the upper section of the form,
double-click the task group or task in the list. It is displayed in a dialog box. You cannot make any
changes in this dialog box. You cannot open the Start record. You can double-click entries in the
Flow Relationships table or select an entry and use the Edit button to open a Flow Template form
where you can define properties for the flow.
2. Select Start from the From Task Group or Task table, then select which task template should be the starting
point from the To Task Group or Task table, and then click Flow to.
The flow relationship record appears in the Flow Relationships table.
3. Select a task or task group in the From Task Group or Task table.
4. In the To Task Group or Task table, select the successor task group or task to be generated when the
previous task is completed.
5. Click Flow to.
The flow relationship record is created and is displayed in the Flow Relationships table.
6. If appropriate, define a qualification on the flow to limit when the flow is followed.
For more information, see Defining qualifications (
https://docs.bmc.com/docs/display/change81/Defining+qualifications).
7. Create as many flow relationships as needed to build the entire flow for the task group template, and then
click Save.
All associated tasks and task groups that are built into a task group's flow follow the defined sequence at
runtime.
8. Continue creating the task group template by defining input and output variable mappings, as described in
Mapping input and output variables (see page 410).
Defining qualifications
If needed, you can create a qualification that is used in the advanced task group template to determine how the
flow should be generated. Qualifications use data supplied by input variables to determine the flow. Before you
define a qualification, you must map variables to fields on the form. Then you can define the qualification against
the field.
To define qualifications in advanced task group templates

1. Define the flow of templates, as described in Creating flow for task group templates (see page 404).
2. On the Flow tab on the Task Group Template form, select the flow relationship, and then click Edit.
You define a qualification for the flow that appears in the Flow Template form
3. To define an input variable mapping, in the Variable Name field on the Input tab, select a variable. You can
map Local, System, and Global variables.
For example, you might want to select the system variable holding the predecessor status so that the
predecessor task can be checked.
For information about the different variables, see Creating variable templates (
https://docs.bmc.com/docs/display/change81/Creating+variable+templates).
4. In the To field, select a field to map the variable data to.

5.
Page 406 of 452
Using
5. Click Add.
The mapping appears in the Input Variable Mapping table.
6. (Optional) Click Clear to remove the field and variable you had selected.
7. Add as many input variable mappings as you need for the flow.
8. In the Qualification Criteria text field on the Qualification tab, build a qualification statement to specify
how the flow should be evaluated.
You can include fields in the qualification statement. For example, if you are building a qualification for a
flow where you want to take another action if the task group fails, you would map the variable to the field
and create the following qualification with the Predecessor Status system variable: 'Predecessor
Status'="Failed"
9. In the Evaluate if Predecessor Failure field, select Yes or No to indicate if the qualification should apply if
the task or task group's predecessor has failed.
10. In the Evaluate if Predecessor Canceled field, select Yes or No to indicate if the qualification should apply if
the task or task group's predecessor has been cancelled.
11. In the Flow to Successor when field, select a value:
All Complete causes the successor flow to start only when all predecessors are complete.
Any Complete causes the successor flow to start when any of the predecessors are complete.
12. Click Save.
Defining operations for completing tasks

By default, a task group is considered complete when all the task groups or tasks that it contains have run. When
a task group is complete, its status is evaluated. This status can be either Success or Failed. By default, the task
group is considered successful when all the task groups or tasks that it contains have a status of Success. If any
do not have a status of Success, the task group has a status of Failed or Canceled.
To use other ways of determining whether a task group is complete or successful, you can specify conditions that
are used to evaluate the task group's status.
You can define operations that include statistical expressions and retrieve variable values. These can be used to
gather data from a task group's associated task groups and tasks, and build this data into qualification statements
for evaluating the task group's status. This data can be used to determine if the task group is complete and if it is
successful.
Note
Operations are supported only for one of the Closed Status Reason values Success, Failed, or
Canceled.
When you create a statistical operation for a task group, you can use the following operators to gather data from
the associated task groups or tasks:
Page 407 of 452
Using
Operator
Function
AVG
Calculates the average of a specified field across the associated tasks or task groups
COUNT
Tallies the number of associated tasks or task groups
MIN
Retrieves the minimum value for a specified field across the associated tasks or task groups
MAX
Retrieves the maximum value for a specified field across the associated tasks or task groups
SUM
Adds up the specified field across the associated tasks or task groups
VARIABLE
Passes variable data from the child to the parent
Each operation works on a child type of the available Task or Task Group that you define. If using the MIN, MAX,
SUM, AVG, or COUNT operation, select a field from the task or task group template from to collect the data. If
using the COUNT operation, choose a field like Task ID because this always has a value.
For the operation VARIABLE, a variable is selected, and it should be a variable that is written out (output from) of
the child type of this task group.
Finally, select a Result field to store the operation result. The recommendation is to choose from the field pools
on the Data tab in the runtime Task form.
The results from the operations run on the Task Group can be used in the Done or Success qualifications that
determine if the task is completed or the data can be gathered merely for analysis.
At runtime, whenever an associated task or task group is changed to a completed status (Success, Failed, or
Cancelled), the expression is applied and the task group is evaluated according to its qualification statements.
As you are building the expression, consider that fields in which you do not specify a value are considered as
having a NULL value.
Consider the following information when creating an expression:
To calculate all tasks or task groups, you must select a field that has a value. The COUNT operator will
return inaccurate results if the value in the selected field is NULL.
For example, you might want to select the Request ID field (which always has a value) to COUNT all
successful child tasks. If you choose a field that does not have a value in it, the count could be inaccurate.
To calculate tasks or task groups where a particular field has been filled, you can select that field. If the
field has not been filled when the task or task group is completed and the task group is evaluating, it has a
value of NULL. The task or task group are not included in the calculation.
To define statistical operations for evaluating a task group

1. On the Task Group Template form, click the Operations tab.
2. In the Expression 1 Operation field, select one of the operator values.
Choices are MIN, MAX, SUM, AVG, COUNT, and VARIABLE.
3. In the Task/Task Group field, select the type of associated object to evaluate.
Page 408 of 452
Using
3.
Note
If you are creating an expression for a task group that contains both task groups and tasks and
you want to gather data from both, you must create separate expressions for each. A single
expression can be applied only to either a task or a task group.
4. In the Closed Status Reason field, select a status to include only those items in the specified status in the
calculation. To include all items, regardless of status, leave this field empty.
5. In the From Field field, select the field from which to retrieve or calculate data.
6. In the Result Field field, select the field from the Task Group form that contains the value retrieved or
calculated by the operation, and then click Save.
7. Create a Done or Success Qualification statement that incorporates the Result Field, as described in
Defining Done and Success qualifications (see page 409).
Defining Done and Success qualifications

You can build qualification statements that are used to determine whether a task group is completed or
successful. You can incorporate the data gathered by statistical operations, as explained in Defining operations
for completing tasks (see page 407). The data is used to determine the status of the task group.
To define a Done or Success qualification

1. On the Task Group Template form, click the Completion tab. In the Done Qualification field, build a
qualification statement to evaluate whether the task group is complete. You can use the Result Field entries
from the Operations tab to build the qualification.
2. In the Success Qualification field, build a qualification statement to evaluate if the task group is successful.
You can use the Result Field entries from the Operations tab to build the qualification.
3. Click Save.
Specifying usage information

The Usage tab tracks whether the task group template is being used by Task Group Templates, Parent Templates,
or Request Templates. The metrics indicate how many times the template was used at runtime and some of the
most important status values, for example, Last Used or Closed Success.
Note
The Usage tab does not appear until you save the task group template.
To specify usage information for task group templates

1. On the Task Group Template form, click the Usage tab.
2.
Page 409 of 452
Using
2. On the Show field, select Task Group Template, Parent Template, or Request Template, and then click Save
.
The Used By Templates table shows other templates that are using the task group template.
3. Review the information on the System tab of the Task Group Template form. The System tab shows
internal information about the task template.
Mapping input and output variables

Variable mappings enable data to be passed in to and out of fields when the task group is executed. To define
variable mappings, you map an existing variable to or from a field.
To map an input and output variable mapping to a task group template

1. On the Task Group Template form, click the Input tab.
If any input variable mappings have been defined, they are displayed in the Input Variable Mapping table.
2. In the From Variable list, choose the variable to map.
3. On the To Field field, choose the field to relate the variable to.
In the execution stage, a pool of fields (for example, Character01) is available in the Data tab of the Task
runtime form for variable usage. The To Field list includes all the fields contained in the Task Group runtime
form. You generally should not map to Display Only fields. If you do so, the value assigned is not retained.
4. Click Add.
The variable mapping appear in the Input Variable Mapping table.
5. Click Save, and then click the Output tab.
If any output variable mappings have been defined, they are displayed in the Output Variable Mapping
table.
6. Click the From Field list.
The list includes all the fields contained in the Task Group runtime form.
7. In the To Variable list, choose the variable to map to.
For output variables, you can map only to Local and Global.
8. Click Add, and then click Save.
The variable mapping appears in the Output Variable Mapping table.
9. Continue setting up the task group template, as described in Defining operations for completing tasks (see
page 407).
19.3 Variable templates

Variable templates are the registration records that the task administrator creates and defines for variables in
TMS.
Variables are pieces of data (for example, in a change request or an entry in the parent object) that are passed to
and from task groups and tasks, and into flows in TMS. This information can be recorded and used as the basis for
making decisions in qualifications or as input for other tasks, task groups, and flows. Variable data can be
generated automatically, or it can be supplied manually by resources working on the task.
Page 410 of 452
Using
In the definition stage, the task administrator creates variable templates that are used for mapping in to or out of
fields. Then, during the execution stage, these variables exchange data between the task group, task, or flow at
runtime.
You can register any piece of information as a variable template. You give it a name and assign it a default value, if
needed.
Note
A default value is not required in the variable template. Values in the variables can be dynamically
assigned at runtime.
When data is created at runtime, the instantiation of the variable can have its value modified. However, the
default values of the variable template itself are not modified.
There are three types of variable templates:
Global Used for data that is global to the system and across all requests, for example, in the BMC
Remedy ITSM Suite of applications. Usually this type of variable is not written to, but it can be. These
variables allow general, shared data to be stored across the organization. Examples include the name of
the company.
System Used for characteristics of the entire request that are automatically available. These are usually
pieces of information that are common to all types of requests, but have a unique value.
Local Used for data within a specific context, for example, within the flow of a task, task group, or flow.
Their value exists only within the context in which they are used, not across the request. For example,
although a variable can be used across different task groups in a request, its value is unique for each task
group.
Each variable template has the option to be global or associated with a specific company. If you specify a
company, your variable template can be further classified using a category and subcategory that shows the
integrating system.
The values of variables inside a task group, task, or flow are initialized by the input variables of the task group.
Any task, task group, or flow can access any variable value. If no value exists for a variable, its value is returned as
NULL.
Recommendation
For example, the Create or Modify Policy with Closed Loop Verification task group template
automatically performs a closed loop" verification to make sure that the task was executed properly. The
Page 411 of 452
Using
advanced task group template here is a container for the two associated task templates. Its main
purpose is to provide flow between the two task templates, which also helps in passing data along for
the variables to use.
The two task templates in the task group template use several variable templates when creating or modifying a
BMC BladeLogic Client Automation policy in the following flow:
1. The Create or Modify Policy - BMC BladeLogic Client Automation Policy Manager task template has an
output variable defined that, at runtime, passes the current Task ID of the task into the Prior Task ID
variable.
2. The Closed Loop Verification (automatic) task template has Prior Task ID mapped as an input variable to a
field on the Data tab of the runtime task. When the first manual task completes successfully and the
automatic task is started, the Prior Task ID is passed in and used in this task's processing.
This scenario uses the Prior Task ID as a variable because BMC Policy Manager must retrieve information from the
previous manual task for the automatic task to work successfully.
Note
Four predefined best practice variable templates are automatically installed with BMC Change
Management for integration with BMC BladeLogic Client Automation. As an administrator, you can
predefine additional variable templates to use with BMC Change Management.
19.3.1 Creating variable templates

Use the following steps to create a predefined variable template.
Note
If sample data has been installed, you might want to search for existing variable definitions to modify.
To create a variable template

3. From the Application Settings list, choose Task Management System > Task Configuration > Variable
4. On the Variable Template form, fill in the required fields:
Page 412 of 452
4.
Using
Field
name
Description
Name
The name to assign to the variable
Company
The company to which this task template applies. Select Global if the variable applies to all companies.
Type
The type of variable you are defining. The options are Local, Global, and System.
Note: After you have created and saved a variable template, you cannot change its variable type.
Status
The status of the variable. The options are as follows:

Active Enables the template for use during the execution stage
when it is no longer used at runtime, but might be needed again in the future. When it is needed again, you can reset it to
Active.

Field name
Description
Category
The application to which group of templates this one belongs. The menu is data-driven by active records in the Integration
Configuration form. For information, see Configuring integrations (
https://docs.bmc.com/docs/display/change81/Configuring+integrations).
SubCategory
An optional subcategory description
Notes
A description of the variable template's function or any other helpful text for future administrators and designers
Default
The data value that you want the variable to store by default. You can leave this field empty.
Value
Locale
6. Click Save.
19.4 Predefined task group and task templates

BMC Change Management comes installed with the following predefined, recommended task group and task
templates that you can use as shipped for installing or deploying software and verifying task completion. These
templates were specially created for the integration with BMC BladeLogic Client Automation.
Templates and their descriptions
Template
Description
Create and Modify

Policy with Closed
Loop Verification
Task group template that includes the following tasks:
Create and Modify Policy

Closed Loop Verification (automatically)
Page 413 of 452
Using
Template
Description
You use the task group that contains these two tasks when creating or modifying a BMC Change Management based
policy. This template automatically performs a closed loop verification to make sure that the task was executed
properly.
Closed Loop
Verification
(automatic)
Automatic task that calls BMC BladeLogic Client Automation Policy Manager to set up compliance parameters for Closed
Loop Verification. It verifies the task automatically against compliance status.
Create and Modify

Policy
Manual task that creates or modifies a policy using Policy Manager. It adds the CI and software locations using the
Relationships feature on task.
Deploy Package
Manual task that deploys a package using BMC BladeLogic Client Automation Deployment Manager. It adds the CI and
software locations using the Relationships feature on task. Verification of a Deployment Manager task is based on the exit
status of the Deployment Manager job.
Execute Remote
Command
Manual task that executes a remote command using BMC BladeLogic Client Automation Deployment Manager. Verification
of a Deployment Manager task is based on the exit status of the Deployment Manager job.
Execute Remote
Script
Manual task that executes a remote script using BMC BladeLogic Client Automation Deployment Manager. You use the
Task Attachments table to define the remote scripts to be used. Verification of a Deployment Manager task is based on the
exit status of the Deployment Manager job.
Verify Target Status
Manual task for manually verifying the status of a target against BMC BladeLogic Client Automation. You use this task to
verify that a specified target is in compliance with the policies to which the target has been assigned.
Page 414 of 452
Using
20 Registering time segments

Registering time segments in BMC Change Management works like a calendering system if you schedule a
meeting in a certain conference room, nobody else can reserve the conference room at the same time. Similarly,
you can block out time segments around business events (such as company holidays), categorizations
(Operational Category 1, 2, or 3, and location of the change), or CIs. Time segments enable you to define
windows of time that you can designate as available or unavailable when working on a change request. An
available time segment can specify that a CI is available for use, while an unavailable time segment can be used to
schedule planned maintenance.
When you create a change request that modifies a CI for example, you must replace a mission-critical server
you can schedule a time segment for the CI that shows it is unavailable to the rest of the support staff. If another
member of the support staff wants that CI to be available, they should schedule their own change in a different
time segment.
Time segments enable you to perform the following tasks:
Search available time segments to schedule the change request.
Connect the selected time segments to the change request's operational categorization or to a business
event based on location.
Create time segments or use time segments around the associated CIs.
Select unavailable time segments from the associated CIs to help you plan the Scheduled Start or End Date
and time for the change request.
Select from available time segments from the associated CIs to help schedule work to be done.
For more information about business time and time segments, see Defining business schedules using Business
Time (https://docs.bmc.com/docs/display/ars81/Defining+business+schedules+using+Business+Time) in the BMC Remedy
Action Request System documentation.
The following topics provide more information about registering time segments in BMC Change Management:
Understanding server time, time zones, and time segments (see page 415)
Registering time segments for CIs - Creating a blackout schedule (see page 416)
Registering unique business events and operational categorizations (see page 420)
Using Schedule Assist to search for available times (see page 423)
20.1 Understanding server time, time zones, and time

segments
Page 415 of 452
Using
When adding time segments if the client and the server are in different time zones, all dates and times for the
Business Time Segments appear in the adjusted server time. That is, the Start Date, Start Time, End Date, and End
Time on the Business Time Segment form, and the time segments date and times that are shown in the table
appear in the adjusted server time. Other dates and times on the remainder of the form are in the client's time.
For example, your server is in EST and your client is in PST. Adjusted server time is determined converting the time
at the place the Business Time Segment was created to the time at the physical location of the server. For
example, if the client is located in PST, and the server is located in CST, the time shown on the server is increased
by two hours (to include both MST and PST time zones). Similarly, if the client is located in EST, the time shown
on the server is decreased by one hour.
Also, all time segments must be adjusted into the time zone of the client. For example, if the ticket was created in
PST, the details need to be adjusted into PST. If a Time Segment for a server was defined in CST, adjust it into PST
when creating the time segment for the client.
For more information about adjusting for the time zone differences between the client and the server, see Using
time zones (https://docs.bmc.com/docs/display/ars8000/Using+time+zones) in the BMC Remedy Action Request
System documentation.
20.2 Registering time segments for CIs - Creating a blackout

schedule
Note
If BMC Asset Management is installed, use the Maintenance Schedule or Blackout Schedule to create
time segments for CIs. This section describes using the Registration for Shared Time Segment window in
BMC Change Management, which does not have the same functionality as BMC Asset Management. For
more information, see Creating a blackout schedule (
https://docs.bmc.com/docs/display/asset80/Creating+a+blackout+schedule).
You create times when the current CI will be unavailable or available. This is known as a blackout schedule.
During times when the current CI is unavailable, a CI must not be brought down. The server used by payroll
might have a blackout schedule to indicate that the CI is not available for other tasks (for example,
upgrades or routine maintenance) when paychecks are processed.
During times when the current CI is available, you can schedule the CI for upgrade, maintenance, change
requests, or release requests. This is a scheduled outage. Other users can share this time segment and
conduct multiple requests.
When creating the blackout schedule, you can also specify the levels of availability. For example, you decide that
a specific application service CI must be unavailable to Calbro Services IT during the core hours Monday through
Page 416 of 452
Using
Friday 8:00 A.M. to 5:00 P.M. PST. You can then schedule routine change requests during the specified Saturday
8:00 P.M. to 10:00 P.M. maintenance window. More urgent change requests can be scheduled outside the core
hours.
As a result, you can set up the following blackout schedule for the application service CI:
Core hours Monday to Friday 8:00 A.M. to 5:00 P.M. PST, the CI is listed as unavailable at Level 15.
Everything except Saturday 8 P.M. to 10 P.M. is listed as available at Level 20.
Everything except the core hours is listed as available at Level 25.
For more information about time segments for CIs, see the following topics:
Defining time segments for CIs (see page 417)
Viewing CI relationships (see page 418)
Viewing CI time segments (see page 419)
Relating CI time segments (see page 419)
Removing CI time segments (see page 419)
20.2.1 Defining time segments for CIs

2. On the Change form, choose Functions > Time Segments > Configuration Item (CI).
3. In the CI Advanced Search form, enter the information necessary to search for a CI and then click Search.
The available CIs based on your search criteria appear in the results table.
4. Select a CI from the search results.
5. (Optional) Click Explore CI to view a CI and its relationship in a tree structure.
For information, see Viewing CI relationships (see page 418).
6. Click Select.
You return to the Registration for Shared Time Segment window.
7. Click Add.
8. In the Description field on the Business Time Segment dialog box, enter a useful description for the time
segment.
For example, your naming convention for change request time segments can include the CRQ ID and a
brief description of what the intended change, or the name of the business service affected.
9. In the Availability field, block out periods of time as follows:
Select Available to define a time segment open for normal use (for example, routine scheduled
maintenance).
Select Unavailable to define a time segment that is not available for any other use (for example, a CI
outage when you shut down a server to add more memory).
Change management activities start with a default level of 10, but you can change this level to a number
from 1 through 1000. Level 1 is Workday activities and Level 2 is Holiday activities.
If the schedules for two activities conflict, the event with the highest number takes priority. For more
Page 417 of 452
10.
Using
information, see Understanding levels (https://docs.bmc.com/docs/display/ars8000/Understanding+levels) in the

BMC Remedy Action Request System documentation.
11. In the Duration Type field, select One time (which generates a single occurrence of the time segment) or
Recurring (which cannot span multiple days, but must be scheduled within a 24-hour period). If you select
Recurring, you must specify the recurrence.
Tip
To define an all-day event, select 12:00:00 A.M. of the first day for the start time, and select
12:00:00 A.M. of the following day for the end time.
13. (Optional) For a one-day event, use the same start day and end day and then select End of Day.
This action sets the End Time to 11:59:59 P.M. When the calculation is performed the end of day is
considered the whole day, including the final second.
14. Click Save to associate the time segment to the CI, and then click Finish.
After you build the blackout schedule for one CI, you can reuse it for other CIs if they have the same
schedule.
Note
For important information about time zones, see Understanding server time, time zones, and time
segments (see page 415).
15. Create a schedule for your change request.

20.2.2 Viewing CI relationships

The BMC Atrium Explorer shows configuration items (CIs) and their relationships to other CIs within the BMC
Atrium CMDB. The BMC Atrium Explorer enables you to improve the accuracy of change planning by locating the
CI. For more information, see Exploring CI relationships (
https://docs.bmc.com/docs/display/asset80/Exploring+CI+relationships) in the BMC Asset Management documentation
or Working with CIs and relationships (https://docs.bmc.com/docs/display/ac80/Working+with+CIs+and+relationships)

in the BMC Atrium Core documentation.
To use the BMC Atrium Explorer to view CI relationships

2. In the CI Advanced Search dialog box, search for a CI.
3.
Page 418 of 452
Using
3. From the CI Search Results table, select a CI and then click Explore CI.
4. From the Template list of the BMC Atrium Explorer, select the filter to use to limit the data shown in the
relationship viewer.
A filter template specifies a criteria for the relationship information that appears in the relationship viewer.
5. Click Refresh to apply the selected filter template.
The relationship image is reloaded with the selected data. The legend on the right pane shows the
relationship types.
20.2.3 Viewing CI time segments

2. Search for a CI, and then select it.
3. On the Registration for Shared Time Segment form, select a time segment.
4. Click View.
5. Modify the time segment.
6. Close the form.
7. Click Finish.
20.2.4 Relating CI time segments

4. Click Search.
5. In the Search Time Segment dialog box, select as many time segments as needed.
6. Click Relate.
7. Close the Search Time Segment dialog box.
8. Click Finish.
20.2.5 Removing CI time segments

Removing time segments does not physically delete them or the CI, because there is a many-to-many
relationship between entities and time segments (that is, one time segment can be related to many entities).
Instead, it removes the link between the CI and the time segment.
To remove a CI time segment

4. Click Remove.
5. Click Finish.
Page 419 of 452
Using
20.3 Registering unique business events and operational

categorizations
You must register business events and operational categorizations that are unique, based on their particular
attributes.
Business event uniqueness is based on its title plus its specified attributes. For example, you might define three
different business events that all use the same title, but if each has a different company location, each
combination of title plus company is unique.
In much the same way, you can only define a single categorization based on all its attributes. Use a descriptive
title specifying what particular categorization you are looking at (for example, Calbro Services - Hardware). To
save the categorization, you must also enter the Company and Category 1 fields.
If you define a categorization that has the attributes Company (Calbro Services) and Category 1 (Hardware), you
cannot define another categorization with the same attributes of Company (Calbro Services) and Category 1
(Hardware). You can define another entity where the Company is Calbro Services, Region is North, and Category
1 is Hardware. Optionally you might define a categorization where Company is Calbro Services and Category 1 is
Software. You define any attribute as long as no other categorization exists where all the attributes are an exact
match of another categorization. The purpose is to prevent the creation of duplicate categorizations.
20.3.1 To create and register a time segment for a business event or an

operational category
3. Click one of the following options:
Business Event
Op. Category Location
4. In the resulting dialog box, click New.
Depending on what you selected in the navigation pane, the Search Business Event/Location Definition
dialog box or Search Operational Categorization/Location Definition dialog box appears.
5. Enter the minimum information required to define a unique time segment for the business event or
categorization.
For example, define a time segment with a title of "Holiday Shut Down" and Calbro Services as the
company.
6. Click Save.
The Registration for Shared Time Segment window is displayed.
7. Click Add.
8. In the Description field on the Business Time Segment dialog box, enter a description for the time segment.
9. In the Availability field, block out periods of time as follows:
Page 420 of 452
Using
9.
Select Available to define a time segment open for normal use (for example, routine scheduled
maintenance).
Select Unavailable to define a time segment that is not available for any other use (for example, a CI
outage when you shut down a server to add more memory).
Change management activities start with a default level of 10, but you can change this level to a number
from 11 through 1000. Level 1 is Workday activities and Level 2 is Holiday activities.
If the schedules for two activities conflict, the event with the highest number takes priority. For more
information, see Understanding levels (https://docs.bmc.com/docs/display/ars8000/Understanding+levels) in the
BMC Remedy Action Request System documentation.
11. In the Duration Type field, select One time (which generates a single occurrence of the time segment) or
Recurring (which cannot span multiple days, but must be scheduled within a 24-hour period). If you select
Recurring, you must specify the recurrence.
Tip
To define an all-day event, select 12:00:00 A.M. of the first day for the start time, and select
12:00:00 A.M. of the following day for the end time.
13. (Optional) For a one-day event, use the same start day and end day and then select End of Day.
This action sets the End Time to 11:59:59 P.M. When the calculation is performed the end of day is
considered the whole day, including the final second.
14. Click Save, and then click Finish.
Note
For information about time zones, see Registering time segments (see page 415).
15. Select Quick Action > View Calendar.

16. On the Change console, choose Functions > View Calendar.
The time segment appears in the Business Events displayed in the Calendar.
20.3.2 Searching for business time or operational time segments

You can search for business time or operational time segments that have already been defined. You then can
modify or delete them, as needed.
Page 421 of 452
Using
To search for time segments

2. On the Change console, choose Functions > Time Segments.
Modify Business Event
Modify Op. Category Location
Depending on what you selected in the navigation pane, the Search Business Event/Location
Definition dialog box or Search Operational Categorization/Location Definition dialog box appears.
This forms works like a wizard. Use this form to search for and select a time segment.
4. Enter the search parameters to find a time segment.
5. Select a time segment from the results list and click Select.
6. Click Finish in the Registration for Shared Time Segment dialog displayed.
20.3.3 Viewing and removing time segments

After creating time segments for business events and operational categories, you can modify or remove time
segments.
Note
Removing time segments does not physically delete them or the business event. Instead, it removes the
link between the business event and the time segment.
To view or remove time segments

1. On the Change console, choose Functions > Time Segments > Configuration Item (CI).
Business Event
3. Enter search parameters to find a time segment.
For more information, see Searching for business time or operational time segments (see page 421).
4. Select a time segment from the results list.
5. To modify the time segment, click View.
6. To remove time segments, select a time segment on the Registration for Shared Time Segment form and
click Remove.
7. Close the form.
8. Click Finish.
Page 422 of 452
Using
20.3.4 Relating time segments

You have the option to relate different time segments.
To relate time segments

1. On the Change console, choose Functions > Time Segments.
Business Event
3. Enter search parameters to find a time segment.
4. Select a time segment from the results list.
6. Click Search.
7. In the Search Time Segment dialog box, select as many time segments as needed.
8. Click Relate.
9. Close the Search Time Segment dialog box.
10. Click Finish.
20.4 Using Schedule Assist to search for available times

The Schedule Assist tool helps you create schedules. You can search for available time segments that you can
schedule a change request around. Your search takes into account the selected time segments tied to the change
request's categorization. You can define time segments or use time segments around the associated CIs. Finally,
you can include the associated CIs unavailable time segments to find a Scheduled Start or Scheduled End Date
and Time for the change request.
Note
The Schedule Assist tool is also available on the Release form. For more information, see Specifying the
business justification (see page 196).
Items shown in the Global Time Segments table displayed on the Time Segment Analysis window are based upon
the following criteria:
Start Search Date Range
End Search Date Range
Page 423 of 452
Using
The table shows Business Events and Operational Categorization Location time segments that match the
Operational Categorization, and the Change Location of the current change, and any items that are global. It also
shows items that are an exact match of the Categorization and Location and those above it. For example,
suppose that the Location of the change request uses the following parameters:
Company = Calbro Services
Region = West
Site Group = California
Site = Sunnyvale
After determining the existence of any Location matches, the search would then match any business event
records that match all four parameters or less. If a business event existed for Company = Calbro Services, this
time segment would match also.
The date range also influences which time segments appear. This criterion affects all tables that show time
segments. The table shows any items that intersect the Start Date and End Date search range. If the Start Date
range is 3/1/08 and the End Date Range is 3/15/08, examples of what it might include are the following business
time segments:
Business time segment 1/1/08 to 3/8/08
For example, you create a normal change request to upgrade the application server. The change manager relates
the application service CI to the change request. Then you use the Schedule Assist tool to determine the next
available window to schedule this change request. You indicate the potential start and end dates, that the
Unavailability times at Level 20 should be used, and that the window needs to be scheduled for 1 hour. When you
click the Find Next Avail Time button, the next available time is displayed, given those criteria. After you locate an
available time, you can schedule that time segment to block out that time so it is no longer available for the next
change request.
Note
Schedule Assist does not enforce that a change request has to be scheduled in certain windows or
prevent you from scheduling a change request during any unavailable or available time. You might have
valid reasons for scheduling a change request during an unavailable window. For example, if you know
System A is down for maintenance from 9:00 P.M. to 10:00 P.M. on Saturday night, you might schedule
another change request for related System B during that same window since System A would already be
down.
20.4.1 To search available times for change requests

1. Open a change request.
2.
Page 424 of 452
Using

a. On the Change Form, to search for available times, make sure you
enter the Change Location information.
b. Click the Categorization tab.
Make sure you enter the Operational Category information and click
Save.
c. Click the Date/System tab.
3. Click the

a. Click the Requester tab.
To search for available times, make sure you enter the
Change Location information.
b. Click the Classification tab.
Make sure you enter the Operational Category
information and click Save.
c. Click the Dates tab.
icon.
The Time Segment Analysis window is displayed. You use this window to analyze the time segments and
search for available times. The following fields are available:
Field
Description
Start Search Date

Range
Set by default to the current date.
End Search Date

Range
Set by default to the current date plus 30 days. Use these dates to filter the information in the table fields.
Global Time
Segments
Shows all time segments tied to the change. By default, all Time Segments are selected.
Associated CI's
Shows a list of the CIs tied to the change that have an entity tied to CI.
CI's
Available/Unavailable
Times
Shows available or unavailable times tied to the selected CI. If one CI is selected from the Associated CIs table and
you press =>, only the Time segment tied to that CI appears. For each additional CI selected on the Associated CIs
table, all the associated time segments to each of the selected CIs appear when you click =>.
If you select Available times as a type, the Use Available button is enabled. Clicking Use Available fills the
Available Start Date/Time+ and Available End Date/Time+ fields from the selected record.
If more than one record is selected, only the first selected record is used to fill the fields. If more than one CI
is selected when you click Use Available, only the first selected record is used.
If there are unavailable times, all times that are selected from the unavailable table, plus the selected global
blackouts on the top, plus the Duration and Level fields are used in the calculation when you use the Find
Next Avail Time button or the Create Next Free Time button (except for those times defined using the
Schedule Time Segment button).
Duration
Defines the length and level of the time segment. For example, you can define a level 10 time segment of 2 hours.
Available Start
Date/Time+
Start date and time of available time segment
Find Next Avail Time
Factors in the duration you specified and returns the next available time. The time segment is then entered into the
Available Start Date/Time+ and Available End Date/Time+ fields.
If you press Enter in the Available Start Date/Time+ field, the duration is added to the Available Start Date/Time+
field and the Available End Date/Time fields. You can manually set the TS Start Date/Time+ field to a specific date or
time to give a new start Date to find the next available time segment.
Schedule Time
Segment
Generates the next available time segment based on all the selected time segments in the tables on the Time
Segment Analysis form. You can then can associate it to a particular CI that is tied to the change request.
Page 425 of 452
Using
Field
Description
Time segments that were created using this button are not included in the calculation with the Create Next Free
Time button or the Find Next Avail Time button. Because the next free time was generated for a particular change
request, the time that was set for the current change is not blocked out.
Next
Goes to the next page of the form
Close
Closes the window without returning the information to the change request
4. In the Time Segment Analysis window, enter information to define the time segments needed for the CIs.
This enables you to define new time segments for CIs based on selected time segments and unavailable
times of other CIs. In BMC Change Management, you can only define time segments with a duration type
of One Time.
After you define the time segments, the change coordinator or the change manager can schedule the
change request based on the selected unavailable items or based on an Available schedule.
5. Click Find Next Available Time.
Based on all the selected time segments in the tables on the Time Segment Analysis form, the time
segment is entered into the Available Start Date/Time+ and Available End Date/Time+ fields.
6. Click Schedule Time Segment.
7. On the The Associate Time Segment to CIs dialog box, use the following steps to associate CIs to time
segments:
a. Select the CI to associate the time segment to.
b. Enter a description of the time segment.
If your server is in a different time zone than the client, make sure you include this in your
description. For more information, see Understanding server time, time zones, and time segments
(see page 415).
c. Click Create Time Segment.
d. Close the dialog box.
The time segment is generated and associated to the CI.
The actual date and time might not be exactly what you specified, if the same time segment has
been selected. If so, the first available time is used for the specified CIs. This functionality is similar to
a calendar system. If you try to reserve a conference room, and you do not book it immediately,
someone might take the room before you book it.
8. Click Next.
The Time Segment Analysis window helps the support person pick a scheduled start date and end date of
the change request. From looking at the time segments, you can try to plan your change around the
specified time segment.
The Time Segment Analysis window redisplays, to enable you schedule dates. The scheduled start date and
end date of the change request does not have to match the unavailable time segments. If you have a time
segment from 1/30/06 from 2:00 p.m. to 3:00 P.M., your scheduled change does not have to be 1/30/06
from 2:00 P.M. to 3:00 P.M. The actual change process can be much longer. Your scheduled change might
go from 1/25/06 8:00 A.M. to 2/2/06 8:00 A.M. You might need to perform additional duties to prepare for
Page 426 of 452
Using
the change and then allot additional time afterwards to verify that the change was successful.
Time Segment Analysis window Scheduling dates
The CI's Available/Unavailable Time table shows all time segments associated to all the CIs.
The following fields are available to set the Schedule Start and Scheduled End Date/Time of the change
request:
Field
Description
Start Search Date

Range
Set by default to the current date.
End Search Date

Range
Set by default to current date plus 30 days. Use these dates to filter what appears in the table fields.
Global Time
Segments
Shows all time segments for the change request
Shows available or unavailable times that are tied to the selected CI
Page 427 of 452
Using
Field
Description
CI's
If you select Available in the Type field, you can use one of the Available times to set the scheduled start and
Available/Unavailable
Times
end dates.
If you select Unavailable, you can manually enter a date, or use the date based on the information about the
Available times shown for the global time segments.
Use Available
If you select Available times as a type, the Use Available button is enabled. Clicking Use Available fills the Available
Start Date/Time+ and Available End Date/Time+ fields from the selected record.
If more than one record is selected, only the first selected record is used to fill the fields. If more than one CI is
selected when you click the Use Available, only the first selected record is used.
Scheduled Start
Date/Time
Enables you select a start date and time
Scheduled End
Date/Time
Enables you to select an end date and time
Previous
Goes to the previous page of the form
Next
Returns the Schedule Start Date/Time+ and Scheduled End Date/Time+ values back to the change request
Close
Closes the window without returning the information to the change request
9. Enter the scheduled start date and end date.

10. Click Next.
The change request appears, with the time segment values returned.
Page 428 of 452
Using
21 Change notifications
When a change request moves into a new status, for example, Completed, the application generates
notifications. Based on your group or role, you might receive notifications during various change statuses.
Notifications by groups (see page 429)
Notifications by roles (see page 430)
For more information, see Reassigning change requests (see page 172).
For more information about notification preferences, see Setting notification preferences (
https://docs.bmc.com/docs/display/itsm80/Setting+notification+preferences).
For more detailed information about notifications, see Notification Engine (

https://docs.bmc.com/docs/display/itsm80/Notification+Engine) documentation.
21.1 Notifications by groups

The following table lists the change events that trigger notifications and the change management groups to
which they are sent.
Change statuses when notifications are sent to groups
Current status
Coordinator group
Support group
Request for Change
Yes
Yes
Planning in Progress
Yes
Yes
Scheduled For Review
Yes
Yes
Yes
Yes
Yes
Yes
Change Implementer group
Draft
Request for Authorization
Scheduled For Approval

Scheduled
Yes
Implementation in Progress
Completed
Closed
Pending
Rejected
Yes
Page 429 of 452
Using
Current status
Coordinator group
Support group
Change Implementer group
Cancelled
21.2 Notifications by roles

The following table lists the change statuses that trigger notifications and the change management roles to
which they are sent.
Exception
You will not receive a notification when you change the status of a change request, if you are Change
Coordinator, Change Manager, or Change Implementer for that change request. If you are both, the
Change Coordinator and the Change Manager, an event is triggered only for the Change Manager. Other
users will receive notifications normally.
Change statuses when notifications are sent to roles in version 8.1.00

Current status
Change coordinator
Change manager
Requested by
Requested for
Change implementer
Draft
No
No
No
Yes
No
Request for Authorization
Yes
Yes
No
No
No
Request for Change
Yes
Yes
No
No
No
Planning in Progress
Yes
Yes
No
No
Yes
Scheduled For Review
Yes
Yes
No
No
No
Scheduled For Approval
Yes
Yes
No
No
No
Scheduled
Yes
Yes
Yes 1 (see page 430)
Yes
Yes
Implementation in Progress
No
No
No
No
No
Completed
Yes
Yes
Yes
No
Closed
No
No
No
No
No
Pending
No
No
No
Yes
No
Rejected
Yes
Yes
No
No
No
Cancelled
Yes
Yes
Yes
No
^ 1 No notification is sent to the Requested by user if the Requested by user and the logged-on user are the same
person.^
Page 430 of 452
Using
22 Sending pages and email messages

In BMC Change Management you can send messages by using the following methods:
To individuals by email (see page 431)
To individuals or member of an on-call group as a page (see page 432)
22.1 Sending email

You can send messages about the current record using the BMC Change Management email system.
22.1.1 To send an email message

1. Open the change or release from which to send the email.
2. From the left navigation pane, choose Functions > Email System.
3. On the Email System dialog box, indicate the recipient by selecting either:
Current Contact When you open the Email System form, if there is a current contact assigned to
the record, the contact's name and contact information appears in the table and is the default
recipient.
Current Assignee To select the current assignee, click Select Current Assignee. The current
assignee's name and contact information appears in the table.
4. To select another recipient, complete the following steps:
a. Complete the fields in the People Search Criteria area, and then click Search.
b. Select the recipient's name in the search results table. If you need help deciding which is the correct
name in the list, click View to see more information about an individual.
5. Complete the email information fields as described in the following list:
Internet Email Type the recipient's email address.
To find this information, select the person's name from the search results list, and then click View.
The Internet Email field is on the General tab of the People form.
Email Subject Line The subject line contains the request ID number. You can type over or add to
this information.
Email Message Body Type the message text here. A series of buttons, to the right of the Email
Message Body field, enable you to automatically insert text from the record into the message text.
Note
If one or more of these buttons is unavailable, the corresponding field in the record
contains no information.
Page 431 of 452
Using
Email Attachment To attach a single file to the email message, right-click inside the Email
Attachment table, and then click Add. On the Add Attachment dialog box, select the file to attach,
and then click Open.
6. Click Send Email Now.
22.2 Paging a person or on-call group

You can page individuals or the on-call member of a group about the current record using the BMC Change
Management paging system feature. You can use the procedure below to manually send a page. For information
on sending automated on call pages, see Adding on-call schedules (
https://docs.bmc.com/docs/display/itsm80/Adding+on-call+schedules).
22.2.1 To page a person or an on-call group

1. Open the change from which to send the page.
2. From the navigation pane on the left side of the form, choose Functions > Paging System.
3. On The Paging System dialog box, select either:
Page By Person To page an individual.
Page By On-Call Group To page the on-call member of a specified group.
4. Complete the fields in the Search Criteria area, and then click Search.
5. Select the recipient's name in the search results table, and then click Select.
If you are sending a page to a person instead of an on-call group, and need help finding the correct person,
click View.
6. Complete the fields in the Paging Information area, as follows:
Pager Service Provider Select the recipient's pager service provider.
If you are sending a page to a person, you can find this information by selecting the person's name
from the search results list, and then clicking View. On the People form, click the Notifications tab to
see the Pager Service Provider field.
Note
If you need more information about the service provider, click the button with the globe
icon beside the field. This opens a link that takes you to the service provider's website.
Pager Type This field is automatically filled.

Pager Number This field is automatically filled with the pager's telephone number, when possible.
If the pager number is unavailable to the system, you must enter the pager number manually.
Pager Email If the pager has an email address, type it here. If you are sending the page to a person,
this information is available on the Notifications tab.
Page 432 of 452
Using
Manual Pager Number If the pager's telephone number is not available automatically from the
paging system, type the pager's telephone number here.
Alphanumeric Pager Message or Numeric Pager Message Type your message in this field. Only
one of these fields is enabled, depending on the recipient's type of pager.
7. Click Send Page Now.
Page 433 of 452
Using
23 Managing SLM service targets

If you have BMC Service Level Management installed, the Change and Release form shows both overview and
in-depth information about the change or release request in relation to applicable service targets. You can view
the service targets and milestones for the restoration of the unavailability. Service targets and milestones are
defined from within BMC Service Level Management. Escalations can be set up to notify the assignment group
prior to acknowledgment or resolution breach times.
From the Change and Release form, you can view service targets defined in BMC Service Level Management.
Service targets can be defined in BMC Service Level Management for response time and resolution time. Service
targets can be determined by related CIs, product and operational categorization, and many other criteria. The
Next Target Date field indicates the next deadline out of all the service targets attached to the change.
For information about managing BMC Service Level Management, see BMC Service Level Management overview (
https://docs.bmc.com/docs/display/SLM80/BMC+Service+Level+Management+overview).
Page 434 of 452
Using
24 Enabling the Change Implementer support

group assignment
This topic describes how to enable the Change Implementer support group assignment.
24.1 To enable the Change Implementer support group

assignment
1. From the Application Administration Console, click the Custom Configuration tab.
2. From the Application Settings list, select Foundation > Configure Assignment > Configure Application
Assignment, and then click Open.
The Configure Assignment form is displayed.
3. In the Event field, select -General-.
4. From the Available Systems (Systems supported) select the Change Management check-box.
5. Click Search.
6. Ensure that the status for all records is set to Enabled.
7. Click Save.
Tip
If you want to modify multiple records in one go, select the records that you want to modify, or
click Select All, and then click Modify All. Make the necessary changes, and then click Save on the
top left corner.
Page 435 of 452
Using
Index
8
8 0 00 365
8 1 00 363
A
Accessing 45, 52, 315
Active Variables 335, 336, 340
Activities 226, 228, 229, 232, 232, 233, 234, 235, 236, 237, 238, 238, 239
Activity 239
Activity Assignees 112, 228
Activity Form 54, 70
Add Approver Dialog Box 126
Add Attachment Dialog Box 285, 431
Adding 124, 126, 294, 319, 415
Adding Information 97
Adding Non Approvers 128
Ad Hoc 305
Advanced Ci 210
Advanced Qualifications 324
Advanced Search 45, 52
Advanced Task Group Template 401
Allocating Costs To Cis 297
Alternate Approvers 126, 127
Alternate Dataset 273
Application Administrators 133
Approval 137, 213
Approval Central 131
Approval Levels 142
Approval Process 213
Approval Process Configuration Form 133, 139
Approvals 121, 124, 124, 133, 138, 139, 139, 142, 143, 157, 213, 213, 214, 215, 215
Approvers 124, 126, 127, 130, 133, 142
Approvers Tab 214
Assigned Work Table 64
Page 436 of 452
Using
Assigning 99, 164, 167, 168, 170, 171, 172, 245, 248, 248, 307
Assigning Change Requests 170
Assignment 173, 310
Assignments 168, 169, 235, 236, 236, 237, 238, 249, 249, 311, 312, 389
Assignment Tab 170, 171, 173, 235, 238, 248, 281, 312
Associate 210
Associations 403, 404
Association Tab 403, 404
Atrium Impact Simulator 267
Audit Logs 157
Authoring Group Dialog Box 285
Auto Assignment 319
Auto Cost 296
Autocost Estimates 296
Automatically Tracking Change 160
Automatic Tab 390
Automatic Tasks 304, 384, 390
Available Times 423
Avg Operator 407
B
Benefits 15, 21
Best Practice 15, 21
Best Practice View 14, 25, 27
Blackout 416
Blackout Schedule 416
Bmc Atrium Cmdb 418
Bmc Bladelogic Client Automation 315, 319
Bmc Change Management 25, 27, 29, 30, 40, 44, 45, 48, 52, 54, 56, 58, 59, 60, 61, 62, 64,
65, 80, 81, 83, 91, 91, 93, 94, 94, 97, 99, 101, 105, 107, 109, 110, 110, 112, 112, 113, 115, 121,
124, 124, 126, 126, 127, 128, 130, 131, 133, 136, 137, 138, 139, 142, 146, 148, 149, 149, 150, 151, 155, 157,
157, 158, 159, 160, 161, 162, 164, 165, 166, 166, 166, 167, 168, 168, 169, 170, 171, 173, 173, 174, 175, 176,
177, 178, 183, 183, 185, 186, 186, 186, 187, 187, 188, 190, 193, 196, 198, 200, 206, 210, 213, 214, 215, 215,
216, 218, 220, 222, 224, 225, 225, 226, 228, 228, 229, 232, 232, 233, 234, 235, 236, 236, 237, 238, 238, 239,
239, 241, 243, 245, 247, 248, 248, 249, 249, 250, 250, 252, 253, 254, 255, 258, 260, 264, 265, 267, 270, 271,
272, 273, 275, 275, 277, 281, 281, 282, 289, 290, 290, 291, 292, 292, 293, 294, 295, 296, 297, 299, 301, 304,
305, 307, 310, 310, 311, 312, 314, 314, 314, 315, 325, 329, 331, 331, 332, 334, 334, 335, 336, 336, 337, 338,
339, 340, 344, 345, 346, 362, 410, 413, 415, 415, 416, 417, 418, 419, 419, 419, 420, 421, 422, 423, 423, 429,
429, 430, 431, 431, 432, 434
Bmc Change Managment 15
Bmc Configuration Management 413
Page 437 of 452
Using
Bmc Configuration Manager 319

Bmc Incident Management 62, 281
Bmc Remedy Alert 168, 236, 249
Bmc Remedy Change Management 58, 133
Bmc Remedy Itsm 31, 139, 142, 415, 415
Bmc Remedy Itsm Suite 25, 27, 29, 30, 44, 45, 48, 52, 54, 58, 58, 59, 60, 61, 62, 64, 65, 80,
81, 91, 91, 93, 94, 94, 97, 99, 101, 105, 107, 109, 110, 110, 112, 112, 113, 115, 121, 124, 124, 126,
126, 127, 128, 130, 131, 133, 136, 137, 138, 139, 146, 148, 149, 149, 150, 151, 155, 157, 157, 158, 159, 160,
161, 162, 164, 165, 166, 166, 166, 167, 168, 168, 169, 170, 171, 172, 173, 173, 174, 175, 176, 178, 183, 183,
186, 186, 186, 187, 187, 188, 190, 193, 196, 198, 200, 206, 210, 213, 214, 215, 215, 216, 218, 220, 222, 224,
225, 225, 226, 228, 228, 229, 232, 232, 233, 234, 235, 236, 236, 237, 238, 238, 239, 239, 241, 243, 245, 247,
248, 248, 249, 249, 250, 250, 252, 253, 254, 255, 258, 260, 261, 264, 265, 267, 270, 271, 272, 273, 275, 275,
277, 281, 285, 287, 289, 290, 290, 291, 292, 292, 293, 294, 295, 296, 297, 301, 305, 307, 310, 312, 314, 314,
314, 315, 319, 325, 329, 331, 331, 332, 334, 335, 336, 337, 338, 339, 340, 344, 345, 346, 416, 418, 419, 419,
419, 420, 421, 422, 423, 429, 429, 430, 431, 431, 432, 434
Bmc Slm 434
Broadcast 287, 288
Broadcast Details Tab 285
Broadcast Messages 285, 287
Broadcasts 287, 431
Broadcasts On Twitter 357
Broadcast Submitter Role 285
Build Milestone For Release Management 216
Business Approval 139, 213
Business Approval Phase 139
Business Event 210, 420
Business Events 420
Business Justification 99, 196, 331
Business Location 420
Business Time Segment 210, 416, 420
C
Calendar 362, 363, 365, 368, 374, 376, 378
Change 362, 368
Change Activities 97
Change And Configuration Management 314, 315
Change Calendar 58, 363, 365, 382
Change Class 86
Change Coordinators 40, 45, 81, 146, 167, 168, 172, 245, 249
Change Dashboard 56
Change Dates 115
Page 438 of 452
Using
Change Dependencies 166, 166

Change Environment Field 99
Change Form 45, 94, 97, 99, 115, 157, 157, 161, 206, 258, 261, 264, 305, 431
Change Implementer 435
Change Implementers 171
Change Implementer Support Group 435
Change Initiation Dialog Box 86
Change Kpi 335
Change Location 157, 193
Change Location Company Field 97
Change Management 60
Change Management Console 40, 58, 178, 187, 187, 331
Change Managers 40, 121, 133, 138, 173, 206, 215
Change Notifications 429
Change Reason Field 99
Change Relationship Search Dialog Box 166
Change Request 292
Change Requests 81, 83, 91, 93, 105, 107, 112, 113, 124, 131, 137, 139, 148, 151, 155, 157, 161, 166, 166,
167, 168, 172, 292, 294, 295, 319, 413, 415
Change Request Status 301
Changes 107, 163
Change Stage 81
Change Tasks 413
Change Tasks 150
Change Template 94
Change Templates 83, 94, 94
Change Type Field 86, 193
Chat 350
Ci 176, 416
Ci Advanced Search 416
Ci Relationships 315
Ci Relationships Search Form 176
Ci Relationship Types 260
Ci Relationship Viewer 418
Cis 417
Cis 416
Ci Status 277
Ci Unavailability 275, 275, 277
Class Field 99
Classic View 14, 29, 30
Classification 97
Classification Tab 107, 389
Classifying Task Templates 389
Page 439 of 452
Using
Close Down Approval 213

Close Down Approval Phase 139
Close Down Milestone In Release Management 222
Closed Stage Of Changes 151
Close Status 407
Close Status Reasons 407
Closing 391, 407
Commands 390
Company Field 44, 97, 193
Company View 44
Completing 409
Completion Tab 391, 409
Concept 14, 31, 35, 40, 44, 59, 60, 61, 81, 96, 107, 109, 112, 112, 113, 121, 124, 124, 133, 137, 139,
146, 149, 150, 151, 175, 176, 183, 186, 188, 210, 213, 214, 215, 216, 224, 225, 225, 226, 228, 229, 235, 238,
241, 245, 248, 250, 253, 261, 265, 275, 290, 292, 292, 299, 307, 314, 314, 314, 331, 333, 334, 336, 337, 384,
397, 398, 401, 410, 415, 415, 416, 429, 431
Concepts 31, 142
Configuration Item 176
Configuration Items 86, 139, 176, 177, 178, 183, 185, 186, 187, 213, 267, 272, 273, 275, 275, 277, 297, 416,
418
Configuration Management Tasks 314, 314, 314, 315
Configure Approval 213
Configuring Dependency 112
Consoles 59, 60, 61
Console View 44
Containers 397
Control 288
Coordinator Group 27
Coordinator Group Field 25, 27
Copy Infrastructure Change Dialog Box 161
Copying 161, 270
Copying Tasks 162
Copy Related Relationships Form 270
Cost Allocation Form 297
Costing 292, 293
Costs 292, 294, 295, 296, 297
Costs Dialog Box 294, 295
Cost User Permissions 294
Create Relationship 261
Create Release Requests 190, 193
Creating 157, 158, 164, 165, 166, 229, 235, 238, 253, 258, 261, 275, 275, 277, 285, 289, 344, 386, 401, 404, 416,
420
Creating Change Requests 81
Page 440 of 452
Using
Creating Templates 86
Customer Field 25
Custom Process Flows 94
Custom Search 344
Custom Searches 344
D
Datasets 273
Date 107
System Tab 107
Dates 115, 206, 220, 233
Define Related Incident 281
Defining 390, 403, 407, 409
Defining Qualifications For 391, 409
Denying Reassignment 173, 281
Dependencies 112, 164
Dependent Changes 163
Deployment Based Tasks 314
Deployment Manager 314
Deployment Milestone In Release Management 220
Dm 314
Duration 368
E
Earliest Start 115
Earliest Start Date 115
Effort Log 159
Effort Logs 158, 160, 252, 253
Email 45, 52, 431, 431
Emails 143
Email System Dialog Box 431
Emergency Change 124
Emergency Change Requests 91, 124
Emergency Request 124
Enable 435
Enforcement 112
Evaluating Task Groups 407
Evenlist 368
Example 382
Page 441 of 452
Using
Example Change Calendar 382

Exchanging Data 410
F
Fields 39
Filters 368
Financial Information 243, 391
Financials Tab 391
Flahsboards 335
Flashboards 333, 340
Flow 404
Flow Tab 404
Flow Template 404
Forms 35, 45, 52, 94, 110, 126, 133, 139, 157, 161, 166, 186, 187, 198, 210, 213, 239, 270, 272, 275, 285,
289, 294, 295, 297, 305, 315, 332, 386, 402, 416, 419, 419, 419, 420, 421, 422, 423, 431, 432
G
Generating 323, 324
Global Search 67, 70, 70, 72, 73, 74, 75, 76, 77, 78
Global Variable Templates 410
Group 401
Groups 128, 168, 236, 249, 413, 429
H
Help Desk Form 70
I
Icons 39, 86
Impact Analysis 107
Impact Criteria 96
Impacted Areas 157
Impact Field 86, 193
Implementation Approval 213
Implementation Approval Phase 139
Implement Stage 149, 150
Individual 430
Page 442 of 452
Using
Individual Notifications 236

Information Technology Infrastructure Library 133
Infotips 368
Infrastructure Change Form 72
Initiate 350
Initiate Chate 350
Initiate Milestone In Release Management 188
Inititate Stage 81
Input Tab 410
Interface 14, 39
Inventory 183, 183, 185, 186, 186, 187
It Home Page 13, 31
Itil 133
K
Known Error 258
Known Error Form 73
Kpi 333, 334, 335
Kpi Flashboards 334
L
Labels 39
Ldap Object 258
Lead Time Field 86, 99
Limiting 287
List View 376
Local Variable Templates 410
Location 210
Login 13
Logs 157, 158, 160, 253
M
Manage Inventory 186
Manifests 200, 224
Manifest Tab 200
Manually Tracking Change 160
Manual Task Templates 384
Manufacturer Field 86
Page 443 of 452
Using
Mapping Variables 410

Messages 287, 431
Mid Tier 13
Model 86
Version Field 86
Modify 422
Modifying 80, 290, 295, 332
Modifying Change 97
Modify Profile 80
Modules 35
Multiple Approvers 142
Multi Tenancy 44, 97, 193
My Searches 344
N
Navigating 14
Navigating Console 35
New Features 365
No Impact 213
No Impact Phase 139
Non Approver 128
Non Approvers 130
Non Bulk Cis 185
Non Phased Deployment 193
Notes Field 99
Notification 168, 236
Notification Audit Tab 157
Notifications 128, 130, 157, 168, 236, 249, 250, 429, 429, 430
Notification Tab 432
Number 287
O
Opening 45, 52, 315, 386, 402
Opening Flashboards 334
Operational Catalog 52
Operational Catalog Listing 45
Operations 407
Operations Tab 407, 409
Operators 407
Page 444 of 452
Using
Operators Statistical Operations 407

Output Tab 410
Overview 12
Overview Console 64
P
Paging 431, 432
Peers 112, 307
People Form 289
Performance Rating Field 99
Permissions 294
Phased Deployment 193
Phases 139, 213
Placing In Inventory 185
Plan Change 113
Planning Milestone In Release Management 206
Plan Schedule 113
Policy Manager 272, 315, 319, 413
Pop Up Messages 288
Predefined 315, 319
Predefined Reports 325, 329
Predefined Tasks 413
Predefined Templates 384, 397, 410, 413
Preferences 273
Printing 291
Priority Criteria 96
Priority Field 86
Problem Investigation Form 74
Process Configuration 213
Process Flow 105, 193, 206, 216, 218, 220
Process Flows 94
Process Flow Status Bar 105, 193, 206, 216, 218, 220
Product Categorization Fields 86
Product Name Field 86
Product Selection 45, 52
Pubme 186, 187, 187
Q
Qualifications 323, 391, 409
Page 445 of 452
Using
Queries 368
Quick Links 54
R
Reassigning 172, 173, 238, 281
Reassigning Release Requests 247
Records 290, 291, 345
Reference 15, 21, 25, 27, 29, 30, 39, 39, 45, 52, 54, 64, 70, 70, 72, 73, 74, 75, 76, 77,
78, 239, 258, 260, 293, 307, 319, 325, 329, 335, 336, 339, 340, 401, 413, 429, 430
Refreshing Data 62
Register Categorization 420
Registering 415, 420, 422, 423
Registering Shared Time 419, 419
Registration For Shared Time Segment Form 419
Reject 137
Reject Change 137
Rejected Requests 136
Rejecting 143
Rejections 137
Relate 423
Relate Ci 176, 273
Relate Configuration Items 176
Related 163
Related Change Requests 165, 275
Related Ci 177
Related Cis With Costs Allocated Table 297
Related Incidents 281
Related Predefined Tasks 319
Relate Incident 281
Relating 165, 166, 273, 275, 305, 319, 413
Relationship Attributes 315
Relationships 166, 166, 225, 258, 261, 270, 271, 272, 273, 282
Relationships Tab 176, 258, 261, 264
Release 239
Release Coordinator 30
Release Coordinators 52, 214, 247
Release Effort 252
Release Form 52, 75, 198, 200, 214, 220, 239
Release Management 21, 188, 188, 206, 213, 216, 218, 220, 222, 239, 250, 253, 255, 265, 329
Release Management Console 58
Release Management Kpi Flashboards 336
Page 446 of 452
Using
Release Manager 30
Release Managers 215, 434
Release Manifest Cost 243
Release Requests 138, 188, 190, 193, 196, 198, 200, 206, 210, 214, 215, 215, 216, 218, 220, 222, 224, 239, 243,
245, 247, 248, 248, 249, 250, 253, 254, 258, 264, 265, 292, 331
Release Template 198, 239
Release Templates 190
Release Type 190, 193
Release Type Field 190
Relocating Cis 183, 187
Reminder Details Dialog Box 332
Reminders 45, 52, 331, 331, 332
Reminders Dialog Box 332
Remove 422
Reports 110, 323, 324, 325, 329
Requested Start 115
Requester 97
Requester Console 62
Requester Contacted Icon 97
Requester Records 289, 290
Requesters 60, 133, 290
Requester Tab 97, 157, 234
Request Types 258
Restart 137
Resubmit Rejected Request 136
Review Authorize Stage 107
Rfc 96
Rfc Date 115
Risk Info Icon 86
Risk Level 110
Risks 86, 107, 109, 110, 110, 190, 193
Roi Flashboards 337, 340
Roles 30, 60, 133, 228, 285, 299, 430
Rollback Change Request 148
Rollback Change Requests 93
Rollup 193
Roll Up Cost 243
Rss Feeds 356
S
Schedule Assist 417, 423
Page 447 of 452
Using
Search 210
Search Business Event 421
Location Definition Form 421
Search Categorization 420
Search Form 275
Searching 178, 185, 210, 315, 345, 346, 423
Search Inventory Locations Dialog Box 187
Search Location 420
Search Operational Categorization 421
Location Definition Form 421
Search Time 419, 419
Search Time Segment Dialog Box 419, 419, 423
Segment 210
Selecting Status Values 65
Select Template 94
Select Template Dialog Box 315
Sending Notifications 250, 429
Sequence 163
Sequence Field 99, 112
Sequence Numbers 99, 112, 164, 307
Sequencing Type 398
Sequencing Type Task Group Template 398
Service Ci Type 86
Service Context 359
Service Field 25, 27, 86
Service Targets 434
Shared Time 419, 419
Shared Time Segment 422
Shared Time Segments 423
Smpm 45, 52
Social Collaboration 356, 357
Software Library 315
Software Library Item 258
Software Library Items 258, 272
Solution Database 76
Standard Task Group Template 401
Statistical Operations 407
Status 250, 301, 407, 429
Status Field 86, 190, 193
Status Flow 213
Status Flow Tab 139
Status Transition 239
Storage Location 272
Page 448 of 452
Using
Subscribe Rss Feeds 356

Summary Field 86, 193
Support Group 435
System Information 392
System Tab 392, 409
System Variable Templates 410
T
Tabs 107, 115, 139, 150, 157, 157, 171, 173, 200, 206, 213, 214, 220, 229, 234, 235, 238, 250, 258, 261, 264,
277, 281, 285, 287, 305, 310, 312, 389, 390, 391, 391, 392, 392, 404, 407, 409, 409, 410, 432, 434
Task 12, 13, 58, 65, 67, 80, 83, 86, 91, 91, 93, 94, 94, 97, 99, 101, 105, 110, 110, 115, 126,
126, 127, 128, 130, 131, 136, 138, 139, 148, 149, 155, 157, 157, 158, 159, 160, 161, 162, 164, 165, 166, 166,
166, 167, 168, 168, 169, 170, 171, 172, 173, 173, 174, 176, 177, 178, 183, 185, 186, 186, 187, 187, 190, 193,
196, 198, 200, 206, 210, 215, 218, 220, 222, 228, 229, 232, 232, 233, 234, 236, 236, 237, 238, 239, 243, 247,
249, 249, 250, 252, 253, 254, 255, 261, 264, 267, 270, 271, 272, 275, 277, 281, 281, 282, 285, 287, 289, 290,
291, 294, 295, 296, 297, 304, 305, 310, 310, 311, 312, 315, 323, 324, 331, 332, 334, 338, 340, 344, 345, 346,
356, 357, 386, 389, 389, 390, 391, 391, 392, 401, 402, 403, 404, 407, 409, 409, 410, 417, 418, 419, 419, 419,
420, 421, 422, 423, 423, 432, 434
Task Clock 310
Task Form 77, 305
Task Groups 229, 307, 315, 319, 407, 413
Task Group Template 409
Task Group Template Form 402, 403, 404, 407, 409, 410
Task Group Templates 397, 398, 401, 407, 409, 409, 410
Task Implementers 149, 150, 299, 315
Task Management System 314
Task Phase Management 174
Tasks 137, 143, 149, 150, 162, 229, 281, 299, 301, 305, 307, 310, 310, 311, 312, 314, 314, 314, 319, 384, 389,
390, 391, 407, 410, 413
Tasks And Flow 410
Tasks Tab 150, 229, 305
Task Status Transitions 174
Task Template Form 386, 389, 390, 391, 391, 392, 392, 410
Task Templates 384, 386, 389, 389, 390, 391, 391, 392, 392, 410
Task Time 310, 419
Tempalate Field 25
Template 401
Template Field 27
Templates 94, 198, 239, 319, 384, 397, 410, 413
Test Milestone In Release Management 218
Time 210
Page 449 of 452
Using
Timeline 368, 378

Time Segment 420
Time Segments 210, 415, 415, 416, 417, 419, 419, 419, 420, 421, 422, 423
Timing Reason 99
Tms 314
Tracking 159, 160, 166, 166, 419, 419, 419
Tracking Automatically 160
Tracking Change Time 160
Tracking Manually 160, 224, 225
Tracking Task Time Manually 419, 419
Twitter 357
U
Unavailability 275
Unrelate Ci 176
Unrelate Configuration Items 176
Unrelate Incident 281
Urgency Criteria 96
Urgency Field 86, 193
Usage 392, 409
Usage Tab 392, 409
Using 67, 81, 333, 362
V
Variables 410, 410
Variable Templates 410
Vendor 97
Vendor Contact 101
Vendor Information 101
Vendor Ticket Information 101
Verification Based Tasks 314
Via Email 143
View 378, 422
View Broadcasts Dialog Box 54
Viewing 44, 80, 130, 139, 155, 157, 157, 166, 166, 176, 186, 213, 215, 250, 271, 332, 340, 368, 418
View Profile 80
View Risk Report 110
Views 374
Virtualization Lifecyclce Management 14
Page 450 of 452
Using
W
Whats New 363
With 319
Work Info Dialog Box 315
Work Info Tab 250, 310
Working 319
Work Order Assignments 236
Work Order Form 78
Work Orders 229, 236
Page 451 of 452
Using
Copyright 2013 BMC Software, Inc.

Copyright 2013 BladeLogic, Inc.
BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are registered with the U.S. Patent and Trademark
Office, and may be registered or pending registration in other countries. All other BMC trademarks, service marks, and logos may be registered or
pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the property of their respective owners.
BladeLogic and the BladeLogic logo are the exclusive properties of BladeLogic, Inc. The BladeLogic trademark is registered with the U.S. Patent and
Trademark Office, and may be registered or pending registration in other countries. All other BladeLogic trademarks, service marks, and logos may be
registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the property of their respective
owners.
All Cisco trademarks that are referred to or displayed in the space are registered trademarks or trademarks of Cisco Systems, Inc. and/or its affiliates in
the United States and certain other countries.
All IBM trademarks that are referred to or displayed in the space are trademarks of International Business Machines Corporation in the United States,
other countries, or both.
IT Infrastructure Library is a registered trade mark of the Cabinet Office.
ITIL is a registered trade mark of the Cabinet Office.
Linux is the registered trademark of Linus Torvalds.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
PinkVERIFY and PinkVERIFY logo Trademark Pink Elephant. Used under license from Pink Elephant.
All SAP trademarks that are referred to or displayed in the document are trademarks or registered trademarks of SAP AG in Germany and in several other
countries.
UNIX is the registered trademark of The Open Group in the US and other countries.
The information included in this documentation is the proprietary and confidential information of BMC Software, Inc., its affiliates, or licensors. Your use
of this information is subject to the terms and conditions of the applicable End User License agreement for the product and to the proprietary and
restricted rights notices included in the product documentation.
Restricted rights legend
U.S. Government Restricted Rights to Computer Software. UNPUBLISHEDRIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF THE UNITED STATES.
Use, duplication, or disclosure of any data and computer software by the U.S. Government is subject to restrictions, as applicable, set forth in FAR
Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and DFARS 252.227-7025, as amended from time to time.
Contractor/Manufacturer is BMC SOFTWARE INC, 2101 CITYWEST BLVD, HOUSTON TX 77042-2827, USA. Any contract notices should be sent to this
address.
BMC Software Inc.
2101 CityWest Blvd, Houston TX 77042-2827, USA
713 918 8800
Customer Support: 800 537 1813 or contact your local support center
Page 452 of 452

BMC Change Management 8 1 - User Guide

Uploaded by

Copyright:

Available Formats

BMC Change Management 8 1 - User Guide

Uploaded by

Copyright:

Available Formats

BMC Software Confidential