Change Requests


A change request is a request made to perform a change, usually for an element managed in the CMDB that may have an important impact on user activity.

Each request:

  • Is associated with a catalog entry.
  • Is usually approved by a manager before it is integrated.
  • Is managed in a workflow that generates actions (manual actions performed by Support persons or automatic actions):
    • The workflow starts after the possible questionnaire (standard / multi-sections) defined on the initial step is answered.
    • Each time an action is performed, the status of the request is updated and shows the progress of the process.
    • A history enables you to store a trace of each action performed.
  • Must be scheduled to avoid collision with other previously scheduled changes, release projects or blackout periods, to have a minimum disruption to IT services.

Examples

  • Different change requests:
    • Standard change: Install a fix for Product name - ev itsm.png
    • Normal change: Upgrade the version of the DBMS ==> Prior analysis of possible regressions, impact on specific developments
    • Emergency change: Replace the hard disk of an application server
  • To ensure that the payroll application works correctly at the end of each month, a blackout period is defined during the last three days of each month on the Payroll Server CI hosting the application.

Notes

  • You can use different methods to create a new request:
    • Via a quick call.  Open url.png  See the procedure.
    • Select Transition > Change Requests > New Request or select Home > New Change Request in the menu.
    • Click the quick creation button Creation buttons - New request for change.png Change.
    • Via the Self Service portal (by default, access not available).
  • You can define blackout periods using the New Blackout Period wizard or in a release project. You can also select Transition > Collision Detection > Blackout Periods.
  • You can cancel a request, for example, if it is a duplicate. To do so, use the Cancel / Close wizard. This is possible only if no action has been performed.

Best Practice big icon.pngBest practice

  • To schedule a change and detect collisions with previously scheduled changes, you can use the different resources available:
    • The Collision Detection wizard, by specifying in advance the requested start date or scheduled start date in the request.
    • The Change Schedule, by selecting Transition > Collision Detection > Forward Schedule of Change. This lists all changes, release projects and blackout periods (periods during which CIs must not be changed) scheduled for a given period.

Screen description

Change request.png

Menu access: Transition > Change Requests > Requests

RequestNumber

Request Number: Automatically generated number of the current request when it was created.

  • To format the number, select Administration > Parameters > Auto-Inc Fields.
Status

Status: Current status of the current object, automatically updated via the steps of the workflow.

  • To display the workflow associated with the object, click ? next to the Status field. Next, click World icon.png Display Related Information. The current step will be highlighted in red.
Priority

Priority: Automatically calculated level based on the urgency and impact of the current object, used to prioritize the processing of objects with the same target resolution date.

Target Implementation Date: Latest date on which the change should be implemented.

  • The date and time are displayed in the time zone of the recipient.
  • This date is for information purposes only and does not take the SLA of the request into account.
HyperlinkDocument

Attachments link (followed by the number of documents): Used to attach a list of documents to the current object and access the files, e.g. error file, screenshots. 

  • Access: Also via the Attachments tab.
IsTemplate

Is a Template: Used to indicate if the current object can be used as a template (box is checked) or not (box is not checked). If it is used as a template, certain information in the template will automatically be preloaded when a new object is created.

  • You can use a template in a quick call by selecting the Use an Incident Template wizard or click the [ COPY FROM TEMPLATe ] button. Open url.png  See the procedure.
  • The preloaded information is specific to the template. New objects will also inherit the other information from the catalog.
  • To define the list of fields that should not be duplicated,  select Administration > Other Parameters > {SM} List of Table Columns "SDREQUEST" to exclude from the Duplicate Wizard Incident.
Recipient

Recipient: Name of the person concerned by the current object. It can be different from the requestor

  • A VIP user is indicated by one or more Red star.png depending on the user's VIP level. This means that the object must be given top priority in processing.
RequestingPerson

Requesting Person: User who reported the current object to the IT Support team.

  • A VIP user is indicated by one or more Red star.png depending on the user's VIP level. This means that the object must be given top priority in processing.

Change Description: Catalog entry of the request, used to run the relevant workflow.

Note

Note: Comments on the request. You can also add images or tables using HTML tags.

Justification

Justification: Reasons given by the user to justify the request, taken into account in the approval workflow.

CI

CI Name: Configuration item (CI) concerned by the current object.

Equipment

Equipment: Asset tag of the equipment concerned by the current object.

  • Sensitive equipment is indicated by one or more Red star.png depending on the critical level. This means that the object must be given top priority in processing.

Release Project Code: Project associated with the request, describing the change release.

Estimated Costs: Estimated amount for the change release.

Requested Start/Requested End: Requested period for implementing the change.

Scheduled Start/Scheduled End: Scheduled period for implementing the change.

Real Start/Real End: Actual change implementation period.

ActionsHistory

History of Actions table: Information on successive actions performed to process the current object. They can be actions linked to a step in the workflow (e.g. incident processing), to a task (e.g. reminder for user), to a problem that enabled the solution of the object, actions modifying the target resolution date, e.g. modification of the SLA.
         Action History table.png

  • (1) To display the complete form of an action, click Edit form icon.png to open the form or click Display popup icon.png to open a popup window.
  • (2) To display the details of an action, e.g. Send Email, Assignment, Analysis & Resolution, click [+] in the Action cell.
  • (3) To display the exact date on which the action was performed, roll your mouse over the Work Order cell.
  • The target intervention date is displayed in the time zone of the logged-in user.
  • To view the total intervention time and the delay for a completed object, open the form and select the Solution tab which shows a summary of all successive actions.

    Color key for action rows:

Color Action type Description

Action History table - Finish color.png

Completed

  • Action whose actual start and end dates are specified.

Action History table - In progress color.png

In Progress

  • Action whose actual start date is specified but whose actual end date is not specified.

Action History table - To do  color.png

To Do

  • Action whose actual start and end dates are not specified.
  • Accessible via QuickDashboard - My actions counter.png in the Quick Dashboard.

    Contents of the table: It can be customized using the options below.
         Action History table - Options.png

  • (1) Filter: Used to select the action types to be displayed. Note: The display mode is specific to each user, regardless of the workstation used, and it is retained after logout.
    • Detailed View: No filter is applied to action types and all actions are displayed.
    • Compact View: Only actions associated with an action type authorizing its display are visible. Generally, these are action types like Send Email.
  • (2) Details: Note: The display is not retained after logout. The default choice is Hide All.
    • [+] Display All: Used to display all details for all actions, e.g. Send Email, Assignment, Analysis & Resolution.
    • [-] Hide All: Used to display only the row describing the actions, e.g. date, Support person, action type, duration.

List of tabs

     Change request tabs.png

EquipmentSoftwareContracts

Equipment/Software/Contracts: List of equipment, software and contracts in the current request.

ChargedBackServices

Charged Back Services: List of options that can be charged back for the current request.

  • Update: When the request is created.
  • Charge back elements are based on the service request catalog when the request was created. Subsequent modifications will not affect the request.
Financial

Financial: Set of financial information used for the charge back of the current action based on hourly or fixed costs.

Consumables

Consumables: List of consumables in the current object.

  • Update:
    • Automatically via destocking actions in the logistics step of the workflow for the current object.
    • Use Add icon.png in this tab to perform destocking actions outside the logistics step of the workflow.
  • To delete a row: Delete icon.png. The quantity is automatically reintegrated into the storage location stock.

Example documentation icon EN.png  Request to replace HP LaserJet 4L printers  ==>  planned destocking action: delivery of a toner cartridge

Orders

Orders: List of orders associated with the current request.

  • Update: Each time an order linked to the current request is placed.
  • The list displays both closed orders and open orders.
Discussions

Discussions: List of discussions which users can access based on their domain and discussion visibility.

  • Enter the keywords you want in the Search field and press Enter
  • To cancel the search criteria and return to the complete list of discussions, provided you have the relevant rights, click within the box and then click Discussion - Delete icon.png.
Attachments

Attachments: List of documents associated with the current object.

  • Update: Depending on the object, use Add icon.png in this tab or in the Details tab > Attachments link  - Open url.png See the Description.
  • To cancel an existing link: Delete icon.png

Related Incidents: List of incidents linked to the current request.

  • Update: Use the Link to a Change Request wizard in an incident.
  • The current request and linked incidents will each be managed by their own workflow. The status of the current object will not have any impact on linked objects.
     

Related Problems: List of problems linked to the current request.

Related Services: List of service requests linked to the current request.

Related Changes: List of change requests linked to the current request.

  • Update: Use the Link to a Service Request wizard.
  • The current request and linked requests will each be managed by their own workflow. The status of the current object will not have any impact on linked objects.
     

Related Events: List of events linked to the current request.
 

Equipment: List of equipment in the current request, other than the main equipment specified in the quick call.

  • Update: Click Add icon.png in this tab.
  • To cancel an existing link: Delete icon.png
  • When new equipment is added, this does not generate a notification or action in the Request form.
  • The Equipment form is not updated.
  • Equipment linked to the new equipment will not be associated with the request.
Licenses

Licenses: List of licenses in the current object.

  • Update: Click Add icon.png in this tab.
  • To cancel an existing link: Delete icon.png
  • When a new license is added, this does not generate a notification or action in the form of the current object.
Contracts

Contracts: List of contracts in the current object.

  • Update: Click Add icon.png in this tab.
  • To cancel an existing link: Delete icon.png

CI: List of configuration items (CI) in the current request, other than the main CI specified in the quick call.

  • Update: Click Add icon.png in this tab.
  • To cancel an existing link: Delete icon.png
  • When a new CI is added, this does not generate a notification or action in the Request form.
  • Impacting and impacted CIs linked to the new CI will not be associated with the request.
  • The Changes tab in the CI form is automatically updated.
HistoryOfChanges

History of Changes: List of all modifications made to the form of the current object. 

QuestionsResponses

Questions/Responses: History of all answers to questions in questionnaires associated with the current object.

  • Update: Use the steps of the workflow associated with the current object.
Projects

Projects: List of projects associated with the current object.

BlackoutPeriods

Blackout Periods: List of blackout periods defined for the CI associated with the current object as well as for all impacting upstream CIs and impacted downstream CIs.

Solution

Solution: Set of information specified at the end of the processing for the current object.

  • Update: When an action related to the current object is completed. You can also use the Close wizard.

   List of fields:

  • Solution: Contents of the Comment fields specified in the final or closing actions for the current object.
  • Elapsed Time: Actual time spent by different Support persons working on the current object, calculated using information entered in the intervention summary of actions. Note: Unlike the time to solve, this information does not take into account the OLA/UC for each action.
  • Immediate Solution: Used to indicate if the current object was solved during the quick call (box is checked) or if it led to one or more actions (box is not checked), involving a transfer or escalation.
  • Solution Date: Date on which the processing of the current object ended and its meta-status became Completed.
  • Late: Number of minutes exceeding the maximum processing date of the current object, calculated using information entered in the intervention summary of actions.
    • Field calculated for each action: Processing time of the action - OLA/UC target
  • Time to Solve: Actual processing duration of the current object, taking into account the working hours of the Technical Support team and public holidays (OLA/UC defined for the workflow).
  • Total Costs: Total processing cost of the current object, calculated using information entered in the intervention summary of actions.
    • Field calculated for each action: Fixed costs  + (Hourly costs * Elapsed Time)
  • SLA: Name of the SLA applicable to the current request, i.e. the one associated with its category.
  • SLA Target: The target implementation date for the current request, calculated using the start time and the SLA.
    • The date and time are displayed in the time zone of the recipient.
    • Roll your mouse over the field to see a description of the SLA.

Procedures and Wizards

How to create a change request

Via a quick call

RequestCreateQuickCall_Procedure

1. To preload data from the requestor/recipient to the quick call, you should first find the requestor/recipient:

  • You can use the Quick Call field.png field found to the right of the menu bar.
             Quick call - menu area.png
    • Enter the first letters to search for the user's name, login, employee number, email address or phone.
    • Press <ENTER>.
    • If several users correspond to the search criteria, the list will appear. Click Display popup icon.png next to the user you want.
    • If there are current incidents/requests for the selected user, the list will appear. Click [ LOG A NEW CALL ].
  • You can also run a simple global search.
    • Enter the first letters for the search criteria.
    • Press <ENTER>. The list of users corresponding to the search criteria will appear.
               Quick call - employees list.png
    • Click Phone icon.png next to the user you want.

2. Enter the information for the quick call

  • Once it is opened, the progress bar and a counter will indicate the elapsed time.
  • If you selected a user, the form will be preloaded with the user's data.
  • To initialize the request using a template, click [ COPY FROM TEMPLATE ].

Best Practice icon.png  Use the help resources -  Open url.png See Default lists filter:

  • Search link to consult the problem knowledge base.
  • Known Errors link to consult the known error base.
  • List of contextual news articles related to the category of the incident.
  • List of the the most relevant articles from the problem knowledge base and known error base once the Description field is completed.

3. Decide what you want to do with the quick call:

  • If the request is solved, click [ RESOLVE ].
    • Enter the intervention summary. The time spent with the user is immediately counted. 
    • The quick call is saved. 
    • The workflow will proceed to the next step and the request will have the associated status.
  • Click [ TRANSFER ] to transfer the form to another group or Support person.
    • Requalify the request if required by selecting the most appropriate category.
    • The target resolution date is automatically calculated by applying the SLA by priority if it is defined for the priority level of the request, or failing that, the SLA associated with the category of the request.
    • Click [ FINISH ]. The new form is created. The Quick Dashboard counters will be updated for the relevant Support persons.

Best Practice icon.png  Select a group instead of a specific Support person. This way, even if the Support person is absent, the action can still be performed by another group member.

  • If you want to interrupt the quick call without processing the incident and save the form so that you can resume it at a later time, click [ SAVE AS DRAFT ].Open url.png See the description of drafts.
    • The workflow will not be started.
    • The meta-status of the request will be Processing in Progress.
    • To retrieve the form subsequently, select Operation > Incidents > Drafts.
  • Click [ CANCEL ] to interrupt the quick call without saving the request.

5. Once you have saved the quick call, the request number will automatically be displayed. 

  • Click the link to open the form.
  • To process actions for the new request: Open url.png  See the procedure.

Via a new request

1. Select the type of change you want to request:

  • You can display the list of different types of changes available in the catalog by selecting Transition > Change Requests > New Request or Home > New Change Request. Next, click Add icon.png next to the entry you want.
        Note:
    • The types of changes displayed depend on the tree structure of the catalog. Click an element to display the sublevels.
    • To display the details of a type of change, click Display popup icon.png next to it.
  • You can also click the quick creation button Creation buttons - New request for change.png Change and select the entry you want by clicking Tree open icon.png in the Category field.

2. Enter the information for the request.

3. Click [ FINISH ] or [ DISPLAY REQUEST ] in the last step of the wizard to display the new form.

4. To process actions for the new request: Open url.png  See the procedure.

IncidentRequestTemplate_Procedure

How to manage templates

1. Select the object you want to use as a template.

  • Open the form you want. Note: Only objects whose meta-status is Processing in Progress can be selected. 
  • Select the Is a Template box. 

2. Use this template in the quick call.

  • Click [ COPY FROM TEMPLATE ] or run the Use an Incident Template wizard. Note: By default, the button is not present in the quick call.  Open url.png  See the procedure to find out how to add it.
  • Select the template you want using the radio button and click [ APPLY ] to load the template fields to the quick call.

Note:

  • You can also run a search on the description of objects using the Search field.
  • Click Open eye icon.png to view the entire text of each description.
             Incident Request templates.png

Wizards

Link to a Project
Link to Several Service Requests
Link to a Continuity Plan
Link To a Problem
Cancel / Close
Change Target Resolution Date
Change SLA
Create a Child Request
Collision Detection  (only if the request concerns a CI)
Create Unavailability  (only if the request concerns a CI)
Send Email to Requestor
Impact Analysis  (only if the request concerns a CI)
End of Unavailability  (only if the request concerns a CI)
Execute Script
Update Request Detail  (only if financial approval has not been given, or failing that, if the reception phase has not been totally completed)
Notification for Action  (only if the request concerns a CI)
Notification for Information  (only if the request concerns a CI)
New Blackout Period
New Task
Notify Support Person
Reminder for Support Person
Reopen  (only if the request is closed)
Availability Simulation  (only if the request concerns a CI)
Capacity Simulation (only if the request concerns a CI with capacities)

Tags:
Last modified by Unknown User on 2017/12/04 10:41
Created by Administrator XWiki on 2016/09/29 15:51

Shortcuts

Recent Updates

Haven't been here in a while? Here's what changed recently:

-   Product name - ev itsm.png
-   Product name - ev sas.png

Interesting Content

How to Automate Integration
Add a Shortcut to an App
History
Quick Dashboard
Full text search - Stop Words

Powered by XWiki ©, EasyVista 2018