Differenze tra le versioni di "Incident Management"
(→Roles) (Etichetta: visualeditor) |
(→Roles) (Etichetta: visualeditor) |
||
Riga 2: | Riga 2: | ||
Of course the preconfigured process (the ''[[Glossary|workflow cartridge]]'') is just an accelerator and the tuning / completion of the initial configuration will still be required. To this aim, the [[Workflow engine|Workflow Engine]] guide may be useful. | Of course the preconfigured process (the ''[[Glossary|workflow cartridge]]'') is just an accelerator and the tuning / completion of the initial configuration will still be required. To this aim, the [[Workflow engine|Workflow Engine]] guide may be useful. | ||
+ | |||
+ | '''<u>IMPORTANT NOTE</u>''': the configuration below is only one of the possible configuration to deal with the ''[[Glossary|incident management]]'' process. The need for a different behaviour of the process may be fulfilled by simple changes of the configuration. | ||
== Operational model == | == Operational model == | ||
Riga 31: | Riga 33: | ||
* 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 | + | * One of the members decides to deal with the ''[[glossary|incident]]'' and takes the incident 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]]''. | || 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]]''. | ||
Riga 42: | Riga 44: | ||
|- | |- | ||
| Incident owner || | | Incident owner || | ||
− | * Offers initial support and attempts to resolve | + | * Role taken on by someone who is part of the ''[[glossary|service desk]]'' team |
− | + | * Offers initial support and attempts to resolve the incident | |
+ | |||
* Activates escalation/ routing/ requests | * Activates escalation/ routing/ requests | ||
− | * | + | * Manages all the communications with the requester |
− | + | * Watches over and monitors the ''[[Glossary|incident]] ''along all its lifecycle ensuring target service levels are achieved | |
− | * | + | * Checks the implemented resolution and sets the ''[[Glossary|incident]] ''to complete |
− | + | * If needed, closes the ''[[Glossary|incident]]'' | |
− | || | + | || The role is set to the service desk member who takes in charge the incident. |
|- | |- | ||
Riga 65: | Riga 68: | ||
== Information == | == Information == | ||
+ | |||
+ | == Visibility == | ||
== Notifications == | == Notifications == |
Versione delle 16:32, 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.
IMPORTANT NOTE: the configuration below is only one of the possible configuration to deal with the incident management process. The need for a different behaviour of the process may be fulfilled by simple changes of the configuration.
Indice
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 |
|
The role is assigned to the service desk member, user "SDSpecialist", who is also member of the "Service Desk"solution group and is set as solution group manager for it. |
Incident owner |
|
The role is set to the service desk member who takes in charge the incident. |
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
Visibility
Notifications
Examples of use
Try the following sequence:
(table with steps, etc.)