Difference between revisions of "Service Portfolio"
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
− | In | + | In ''Service Manager'']], a Service is the outcome that fulfills a business need for a customer (internal or external to an organisation). In order to create that outcome a Business Process workflow) is used. |
Some of the ways that a service is used in Hornbill are:- | Some of the ways that a service is used in Hornbill are:- | ||
− | :# The service can be requested using a | + | :# The service can be requested using a service request |
− | :# An incident request can be created using | + | :# An incident request can be created using progressive capture that needs a service to be defined that will resolve it |
:# A change request using progressive capture that needs a service to be defined to carry out the change | :# A change request using progressive capture that needs a service to be defined to carry out the change | ||
:# A problem request can be created using progressive capture that needs a service to be defined that will resolve it | :# A problem request can be created using progressive capture that needs a service to be defined that will resolve it |
Revision as of 12:24, 3 February 2015
In Service Manager]], a Service is the outcome that fulfills a business need for a customer (internal or external to an organisation). In order to create that outcome a Business Process workflow) is used.
Some of the ways that a service is used in Hornbill are:-
- The service can be requested using a service request
- An incident request can be created using progressive capture that needs a service to be defined that will resolve it
- A change request using progressive capture that needs a service to be defined to carry out the change
- A problem request can be created using progressive capture that needs a service to be defined that will resolve it
- A request list can display which service the request is using