Difference between revisions of "Service Manager Request Types"
Jump to navigation
Jump to search
(Created page with "== Introduction ==") |
|||
| (22 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| + | This document can now be found at its new location in the [https://docs.hornbill.com/servicemanager-user-guide/service-portfolio/requests/request-types Hornbill Document Library]. | ||
| + | |||
| + | [[file:hornbill-document-library.png|Request Types|link=https://docs.hornbill.com/servicemanager-user-guide/service-portfolio/requests/request-types]] | ||
| + | <!-- | ||
| + | |||
| + | <div style="border:1px solid #90C0FF; background:#D0E0FF; width:99%; padding:4px; margin-bottom:10px;"> | ||
| + | __NOTOC__ | ||
| + | {| style="width:100%" | ||
| + | |[[Main Page|Home]] > [[Service Manager]] > Request Types | ||
| + | |style="text-align:right;"|[[:Category:Service_Manager|Index]] | ||
| + | |} | ||
| + | </div> | ||
| + | {|style="width: 100%" | ||
| + | |- valign="top" | ||
| + | |style="width:73%"| | ||
== Introduction == | == Introduction == | ||
| + | The Request Types make up the key aspect of Service Manager, providing the raising and tracking of different requests types to facilitate the management and delivery of your services. Access to the different request types is control through each user's rights and roles within Service Manager. | ||
| + | |style="width:5%"| | ||
| + | | | ||
| + | |style="width:22%; border-style: solid; border-width: 1px; border-color:#e6e6e6; background-color:#f2f2f2;"| | ||
| + | |||
| + | == Related Articles == | ||
| + | * [[Request Settings]] | ||
| + | * [[Custom Buttons]] | ||
| + | * [[Request List]] | ||
| + | |} | ||
| + | |||
| + | == Incidents == | ||
| + | Incidents are used to manage unplanned interruptions or reduction in quality to an IT service. Hornbill Service Manager allows users with the appropriate roles and rights, to log, view, progress, escalate and resolve Incidents. The Hornbill platform provides a [[Business Process Designer|Business Process Engine]] which be can configured to support your Incident processes and can automate events such as tasks, timers, notifications, and escalations. | ||
| + | |||
| + | ::*[[Logging Incidents]] | ||
| + | ::*[[Incident Requests]] | ||
| + | ::*[[Incident Diagnosis & Investigation]] | ||
| + | ::*[[Escalation, Resolution & Closure]] | ||
| + | |||
| + | |||
| + | == Problems == | ||
| + | Problems are used to manage the investigation of an issue where the root cause is unknown. | ||
| + | |||
| + | ::* [[Problem Records]] | ||
| + | ::* [[Investigating Problems]] | ||
| + | ::* [[Workarounds and Known Errors]] | ||
| + | |||
| + | == Changes == | ||
| + | Change management aims to ensure that standardized methods and procedures are used for efficient handling of all changes. | ||
| + | |||
| + | ::* [[Change Requests]] | ||
| + | ::* [[Raising Changes]] | ||
| + | ::* [[Approving, Scheduling, and Implementing Changes]] | ||
| + | |||
| + | == Service Requests == | ||
| + | Request fulfillment (or request management) focuses on fulfilling Service Requests, which are often minor (standard) changes (e.g., requests to change a password) or requests for information. The term "standard change" means pre-approved, repeatable, pre-defined, low risk changes. If the change does not meet these criteria then it is not a standard change and should be defined as a request for change. | ||
| + | ::* [[Service Requests]] | ||
| + | |||
| + | == Releases == | ||
| + | Release Management allows for the planning and release of a number related changes under a single Release record | ||
| + | |||
| + | ::* [[Release Requests]] | ||
| + | |||
| + | [[Category:Service Manager]] | ||
| + | --> | ||
| + | [[Category:HDOC]] | ||
Latest revision as of 18:21, 19 April 2024
This document can now be found at its new location in the Hornbill Document Library.
