Differenze tra le versioni di "Incident Management"
(→Roles) (Etichetta: visualeditor) |
(→Roles) (Etichetta: visualeditor) |
||
Riga 24: | Riga 24: | ||
* Monitors the resolution of the ''[[Glossary|incidents]]'' | * Monitors the resolution of the ''[[Glossary|incidents]]'' | ||
* Confirms that the ''[[Glossary|incident]]'' is closed | * Confirms that the ''[[Glossary|incident]]'' is closed | ||
− | || This role is mapped on a system ''[[Glossary|resource]] ''with ''[[Glossary|user]] ''of ''[[Glossary|user type]]'' "Requester". | + | || This role is mapped on a system ''[[Glossary|resource]] ''with ''[[Glossary|user]] ''of ''[[Glossary|user type]]'' "Requester". The login identifier of this ''[[Glossary|user]]'' is "FinalUser". |
− | The login identifier of this ''[[Glossary|user]]'' is "FinalUser". | ||
|- | |- | ||
Riga 32: | Riga 31: | ||
* This group receives the notifications of all the ''[[glossary|incidents]]'' opened | * This group receives the notifications of all the ''[[glossary|incidents]]'' opened | ||
− | * | + | * One of the members decides to deal with the ''[[glossary|incident]]'' and takes the owner role |
− | || ''''' | + | || This role is mapped on a system ''[[Glossary|resource]] ''with ''[[Glossary|user]] ''of ''[[Glossary|user type]] ''"Resource". The login identifier of this ''[[Glossary|user]] ''is "SDSpecialist". The ''[[glossary|resource]]'' is also member of the "Service Desk" ''[[glossary|solution group]]''. |
|- | |- | ||
− | | | + | | Service desk manager || '''Bold''' || '''Delete''' refers to the application command Delete. |
|- | |- | ||
Riga 51: | Riga 50: | ||
|- | |- | ||
− | | | + | | Technical team member || "Brackets" || "Henry" refers to the content Henry of a field, for example <u>Name</u>. |
|- | |- | ||
Riga 68: | Riga 67: | ||
== Examples of use == | == Examples of use == | ||
+ | Try the following sequence: | ||
+ | |||
+ | (table with steps, etc.) |
Versione delle 15:59, 13 apr 2015
Incident Management process is supported by a SM workflow cartridge that enables the execution of the process according to the ITIL and ISO/IEC 20000 guidelines.
Of course the preconfigured process (the workflow cartridge) is just an accelerator and the tuning / completion of the initial configuration will still be required. To this aim, the Workflow Engine guide may be useful.
Operational model
The preconfigured process has the objective to facilitate and support the resolution of incidents or the provision of workarounds. At the core of the process configuration is the following operational model.
The requester requires to open an incident by contacting the service desk. One of the members of the service desk takes the request in charge,
becoming the owner of it, and starts to manage it. The owner may find a workaround and/or solution for the incident and, therefore, may close it. Alternatively, the owner may not be able to find any solution or workaround and may need to involve technical staff to investigate and find it. In such a case, he/she will route to the technical staff the incident, still remaining accountable for it. In other words, the service desk alwasy acts as a single point of contact (SPOC) for the requester.
Roles
For this process, the following organizational roles are defined:
Organizational role | Description | itmSUITE® role mapping |
---|---|---|
Requester |
|
This role is mapped on a system resource with user of user type "Requester". The login identifier of this user is "FinalUser". |
Service desk member |
|
This role is mapped on a system resource with user of user type "Resource". The login identifier of this user is "SDSpecialist". The resource is also member of the "Service Desk" solution group. |
Service desk manager | Bold | Delete refers to the application command Delete. |
Incident owner |
the Incident
User and closes the Incident
of the Incident Ticket |
Name refers to the field Name. |
Technical team member | "Brackets" | "Henry" refers to the content Henry of a field, for example Name. |
Technical team manager | Italic and underlined | Options refers to the section or tab Options of a form. |
Service manager | Bold and underlined | Relevant text. |
Process
Information
Notifications
Examples of use
Try the following sequence:
(table with steps, etc.)