Differenze tra le versioni di "Incident Management"
Da itm wiki.
(Etichetta: visualeditor) |
(→Operational model) (Etichetta: visualeditor) |
||
| Riga 5: | Riga 5: | ||
== Operational model == | == 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 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. | ||
| + | |||
| + | [[File:Incident Management Operational Model v1.0.JPG|centre|thumb|500x500px|Incident Management operational model]] | ||
| + | |||
| + | The requester requires to open an ''[[Glossary|incident]]'' by contacting the ''[[Glossary|Service Desk]]''. One of the members of the ''[[Glossary|Service Desk]]'' takes the request in charge | ||
| + | |||
| + | ecoming | ||
== Roles == | == Roles == | ||
== Process == | == Process == | ||
Versione delle 14:53, 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
ecoming
