|
|
| (110 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| − | __NOTOC__[[Main Page|Home]] > [[Service Manager]] > Services
| + | This document can now be found at its new location in the [https://docs.hornbill.com/servicemanager-user-guide/service-portfolio/overview/ Hornbill Document Library]. |
| | | | |
| − | == Introduction ==
| + | [[file:hornbill-document-library.png|Service Portfolio Overview|link=https://docs.hornbill.com/servicemanager-user-guide/service-portfolio/overview/]] |
| − | In ''Service Manager'', a Service is used to manage and define an area of the Service Desk that fulfills a particular business need for a customer. This is achieved using a combination of service levels, business process workflows, request routing, and subscriptions to each of the services. The number of defined services may range from a single service used to define and manage all IT requests, to a collection of categorized services, with each one providing a particular focus.
| + | <!-- |
| − | | + | <div style="border:1px solid #90C0FF; background:#D0E0FF; width:99%; padding:4px; margin-bottom:10px;"> |
| − | <br>
| + | __NOTOC__ |
| − | | + | {| style="width:100%" |
| − | == Administration ==
| + | |[[Main Page|Home]] > [[Service Manager]] > Services |
| − | To create, view, or edit a Service, you need the '''Services Manager''' role associated to your Hornbill User account. Having this role will make the Services menu item visible under the Service Manager application icon.
| + | |style="text-align:right;"|[[:Category:Service_Manager|Index]] |
| − | | + | |} |
| − | <br>
| |
| − | | |
| − | == Services List ==
| |
| − | The Services List provides a list of the services that are being managed within Service Manager. From here you can
| |
| − | * Create a New Service
| |
| − | * Delete a Service
| |
| − | * View a Service
| |
| − | | |
| − | The Services List is divided into three different sections based on their portfolio status of Pipeline, Catalog, or Retired.
| |
| − | | |
| − | <br>
| |
| − | | |
| − | ==Managing a Service==
| |
| − | This section looks at the different elements that makes up a service and how each area is managed.
| |
| − | | |
| − | === Service Details ===
| |
| − | The detail of a service provides some key values and settings to make a service operational.
| |
| − | :* '''Name''': The name of your Service. | |
| − | :* '''Description''': A brief description of your service
| |
| − | :* '''Category''': Used to group your Services. Select one from the pre-defined list
| |
| − | :* '''Portfolio Status''': ''Catalog'', ''Pipeline'', or ''Retired''
| |
| − | ::*'''Catalog''' will make your new service immediately available for selection when an analyst is logging a request via Progressive Capture, or for consumers of the Service logging requests via the Hornbill Portals.
| |
| − | ::*'''Pipeline''' will hide your Service from Analysts and consumers of the service. Use the Pipeline status when your service is in development.
| |
| − | ::*'''Retired''' will also hide your Service from Analysts and consumers of the service. Set a status of Retired when your Service is no longer in use. | |
| − | :* '''Portal Visibility''': If the Service will be visible on the Customer and Service Portal for subscribed users.
| |
| − | ::* '''Visible''' Subscribed users will see, and have access to their requests raised against the Service, even if they you have restricted their ability to raise tickets from the portals for this Service.
| |
| − | ::* '''Hidden''' Subscribed users will not see the Service on the Customer or Service portal - Useful when defining a technical Service rather than a business Service. | |
| − | :* '''Service Icon''': The Icon which will be used to represent the service on the Service and Customer Portals for the subscribers to this service | |
| − | | |
| − | ==Request Configuration==
| |
| − | | |
| − | Use this tab to configure all the different settings per Request Type for the Service. For example it is possible to configure different forms, action bar options, business processes etc for Incidents raised against the Service, compared when Service Requests, Problem's, Changes.
| |
| − | | |
| − | <div class="mw-collapsible mw-collapsed" data-collapsetext="Show Less" data-expandtext="Read More" style="width:800px">
| |
| − | :* Business Processes
| |
| − | <div class="mw-collapsible-content">
| |
| − | :: It is possible to associate a workflow to each request type. Clicking on the slect box will present you with the available Business Processes that have been configured via Hornbill Administration. Remember, for a Business Process Workflow to be initiated when a request is logged, it must be marked as “Active”. Inactive workflows can be identified and avoided here by looking for the word “inactive” in brackets next to the workflow name. | |
| − | :: Associating a Business Process workflow is optional at this stage, and can be done at a later date.
| |
| − | | |
| − | :: Once you are happy with the details you have entered, click “Create” to complete the configuration of your first Service.
| |
| − | | |
| − | :: You can learn more about designing and building business processes to underpin the Services you provide here: [[Business_Process_Workflow | Building Business Processes]]
| |
| − | | |
| − | </div>
| |
| | </div> | | </div> |
| | + | {|style="width: 100%" |
| | + | |- valign="top" |
| | + | |style="width:73%"| |
| | + | ==Introduction== |
| | + | The Service Portfolio provides features and configuration settings for defining the Services that you offer to your customers. These options include services, request priorities, and Corporate Service Level Agreements. |
| | | | |
| − | <div class="mw-collapsible mw-collapsed" data-collapsetext="Show Less" data-expandtext="Read More" style="width:800px">
| + | Each defined service can include a combination of service levels, business process workflows, request routing, and subscriptions. The number of defined services may range from a single service used to define and manage all IT requests, to a collection of categorized services, with each one providing a particular focus. |
| − | :* Email Template
| |
| − | <div class="mw-collapsible-content">
| |
| − | :: It is possible to define for each request type and for each Service which email template will be used when analysts are manually sending emails from the request forms.
| |
| | | | |
| − | :: This allows Service owners to have control over the signature and other request variables which are defined in email templates, and they would like included in any manual email communication for requests linked to their Service. | + | |style="width:5%"| |
| | + | | |
| | + | |style="width:22%; border-style: solid; border-width: 1px; border-color:#e6e6e6; background-color:#f2f2f2;"| |
| | | | |
| − | ::* By default the email template specified in the '''app.email.template.request.sendMessage''' app setting in the admin console will be used. It is possible to change which template to use for each request type per service by choosing another available email template from the drop down list. | + | == Related Articles == |
| | + | :* [[Service Details]] |
| | + | :* [[Service Level Agreements]] |
| | + | |} |
| | | | |
| − | ::* Email templates are defined in the Admin console, under the Service Manager and email configuration options | + | == Services == |
| | + | The Services List provides a list of the services that are being managed within Service Manager. |
| | + | :* '''Filter Services''' |
| | + | :: The ''Filter Services'' option lets you quickly locate a Service. When typing in the Filter Services field, the name of the Service and the Service Description will be searched. |
| | + | :* '''Type Filter''' |
| | + | :: The ''Type Filter'' option lets you filer the list of displayed services by Business or Techincal type |
| | + | :* '''Category Filter''' |
| | + | :: The ''Category Filter'' option lets you filter the list of displayed Services by Service Category |
| | | | |
| − | ::* If no default email template exists, or another email template is not chosen a blank plain email template will be used. | + | {{bullet1|Status Filter|This options lets you filter the list of services based on their current operational status}} |
| | + | {{bullet1|Owner Filter|Filter the list of services based on the owner of the service}} |
| | + | {{bullet1|Configure Columns|Select the cog icon to select the available columns that you wish to display, along with their order within the list.}} |
| | + | :* '''Design a New Service''' |
| | + | :: Use the ''Design a New Service'' button to start the process of having a new Service added to your Service Desk |
| | | | |
| − | ::* The Email template specified is only used when emails are manually sent from within a request. All automated emails fired by the business process engine, can be configured when designing your [[Business_Process_Workflow | business processes]] for each request type again via the admin console. | + | :* '''Delete a Service''' |
| − | </div>
| + | :: When your mouse passes over a Service a delete option is displayed. This should only be used when a Service has been added in error. In order to maintain historic information such as requests and subscriptions, the service should be ''Retired'' rather than deleted. |
| − | </div>
| |
| | | | |
| − | <div class="mw-collapsible mw-collapsed" data-collapsetext="Show Less" data-expandtext="Read More" style="width:800px">
| + | :* '''Service Portfolio Status Filter''' |
| − | :* Form Designer | + | :: Below the ''Service Filter'' each of the available ''Service Statuses'' can be selected to view services grouped by status. The options include ''All Services'', ''Pipeline'', ''Catalog'', and ''Retired''. |
| − | <div class="mw-collapsible-content">
| |
| − | :: It is possible for you to define custom fields to use against each request type per service. Using the form designer you can edit which default fields will be displayed in the '''Details''' section of each request form, as well as add new fields, set field validation, configure mandatory options and using drag and drop to re-order how the required fields will be displayed. | |
| − | </div>
| |
| − | </div>
| |
| − | <div class="mw-collapsible mw-collapsed" data-collapsetext="Show Less" data-expandtext="Read More" style="width:800px">
| |
| − | :* Portal Head's Up Display (HUD)
| |
| − | <div class="mw-collapsible-content">
| |
| − | [[File:HUD_Portal.png|center|800px]]
| |
| − | :: When a business process is defined and supporting either the Incident or Service Request request types, it is possible to define what level of visibility you wish to give to your customers of the processes progress through a graphical head's up
| |
| − | :: display. It is possible to give no visibility, top level or a granular view per request type and per service via either the Service and Customer Portals.
| |
| | | | |
| − | :: The default option is '''Off'''. | + | :::* '''''Pipeline''''' |
| | + | :::: Pipeline Services are those that are under planning and development. While in a status of Pipeline the Service will not be available to users. |
| | + | :::* '''''Catalog''''' |
| | + | :::: Once a Service has the status of ''Catalog'' it is then accessible to users and requests can now be raised against this service. |
| | + | :::* '''''Retired''''' |
| | + | :::: When a Service is no longer required, it can have the status set to ''Retired''. Once retired, a service will no longer be visible to users and requests can no longer be raised against the service. |
| | | | |
| − | :::* '''Off''' - No graphical representation of the supporting business process will be displayed on the request forms on either the Service or Customer Portal
| + | :* '''[[Service Details]]''' |
| − | :::* '''Stages Only''' - Top level visibility of each of the defined stages will be displayed at the top of the request forms on the Service and Customer Portals. This will allow the subscribed customers to see the stages which have been completed and those which are still outstanding. | + | :: By clicking on any of the Services in the list you can view the [[Service Details]]. From within the Service Details, you can plan, configure, and manage each service. |
| − | :::* '''Stages and Checkpoints''' - This will show both the process stages and the defined checkpoints for each stage. This will give the subscribed customers the same level of visibility of the requests progress as the analysts see, and will allow them to see which stages and checkpoints have been completed and what is still outstanding to complete.
| + | <br> |
| − | </div> | + | <br> |
| − | </div> | |
| − | <div class="mw-collapsible-content"><div class="mw-collapsible-content"><div class="mw-collapsible mw-collapsed" data-collapsetext="Show Less" data-expandtext="Read More" style="width:800px">
| |
| − | :* Request Actions
| |
| − | <div class="mw-collapsible-content">
| |
| − | [[File:Request_Actions.png|center]]
| |
| | | | |
| − | :: Define which actions are available to analysts working on requests raised against the Service. It is possible to configure which Action Icons will appear on the Action Bar on the different request forms for each Service. It is possible to configure different Actions per request type per Service.
| + | == [[Corporate Service Level Agreements]] == |
| | + | The Corporate Service Level Agreements (SLA) tab allows you to define your corporate service level agreements which can be shared between services. Each Corporate SLA lets you define Service Levels, Service Level Targets and the rules for applying these to requests. |
| | | | |
| − | :: An example being you may choose not to enable the 'Escalation' Action against Service Requests if you are not using Priorities for requests of this type for a particular Service. However you have this available for Incidents and Problems where you have chosen to use priorities for those request types. | + | :[[Corporate Service Level Agreements|Read more...]] |
| − | | + | <br> |
| − | ::* The Default position is all Actions Icons are available for all request types
| |
| − | ::* Enable or Disable an Action by clicking on the Action Icon for each Request type
| |
| − | ::* Hover over each Action Icon to see a tooltip with the Actions purpose.
| |
| − | </div>
| |
| − | </div>
| |
| − | <div class="mw-collapsible-content"><div class="mw-collapsible-content"><div class="mw-collapsible mw-collapsed" data-collapsetext="Show Less" data-expandtext="Read More" style="width:800px">
| |
| − | :* Request Categories
| |
| − | <div class="mw-collapsible-content">
| |
| − | [[File:Service_Categories.png|center]] | |
| − | :: Define which logging and resolution categories are available per request type per service. It is possible to configure which level of the category tree will be the starting level (exposed) when choosing a category on requests against each Service.
| |
| − | | |
| − | ::* The default position is to use the root of the category tree for all request types against all Services.
| |
| − | ::* Configure a different starting level per request type for each service by clicking on either the '''Category Level''' or '''Resolution Category Level''' options and choosing a different starting level.
| |
| − | ::* Once configured only child levels of the category tree will be presented when adding a category to a request via Progressive Capture or the Request Details forms.
| |
| − | </div>
| |
| − | </div>
| |
| − | <div class="mw-collapsible mw-collapsed" data-collapsetext="Show Less" data-expandtext="Read More" style="width:800px">
| |
| − | :* Self Service
| |
| − | <div class="mw-collapsible-content">
| |
| − | :: When defining a service it is possible to decide if the subscribed customers will have the option to raise either an Incident or a Service Request against the service. In most cases it will be one or the other but it is possible to provide both options per service.
| |
| − | :::* Making the '''Incident''' type visible will enable a '''Get Help''' button against the service on the Service and Customer portals.
| |
| − | :::* Making the '''Service Request''' type visible will enable a '''Raise Request''' button against the service on the Service and Customer portals.
| |
| − | | |
| − | :: The default setting is to enable both Incidents and Service Requests for each Service, however to improve the customer experience and make it simpler for them to understand what action to perform on the portals, you can turn one or both options on or off.
| |
| − | | |
| − | :: The default text of the above buttons can be customized via the Portal configuration options in the administration portal, under the configure portals options, and translations options.
| |
| − | </div>
| |
| − | </div>
| |
| − | <div class="mw-collapsible mw-collapsed" data-collapsetext="Show Less" data-expandtext="Read More" style="width:800px">
| |
| − | :* The Request Catalog
| |
| − | <div class="mw-collapsible-content">
| |
| − | :: Request Catalog Items are used to create a catalog of defined requests which can be used on the Portals or by Support Staff to raise requests to fulfill a specific requirement for that particular Service. Catalog Items can be added to both Incidents and Service Requests. For each Catalog item you can define the following:
| |
| − | ::* A unique Progressive Capture Script
| |
| − | ::* A unique Business Process Workflow
| |
| − | ::* Publish in multiple languages
| |
| − | ::[[Request Catalog| Read more... ]]
| |
| − | </div>
| |
| − | </div>
| |
| − | | |
| − | ==Assets==
| |
| − | [[File:Service_Assets.png|thumb|right]]
| |
| − | | |
| − | Link which assets support or underpin the provision of the Service.
| |
| − | | |
| − | * Add one or multiple assets to a Service record.
| |
| − | | |
| − | Associating the assets which support a service helps support quicker Incident and or Problem resolutions by making it quick and easy to understand what infrastructure is directly used to provide each service. Change management can benefit from visualising impact when considering implementing changes to a service, or assets which support a service.
| |
| − | | |
| − | ==FAQ's==
| |
| − | | |
| − | Define Frequently Asked Questions which will be helpful to subscribers of the service on both the Customer and Service Portals.
| |
| − | | |
| − | [[Service FAQs | Creating, Viewing and Managing FAQ's]]
| |
| − | | |
| − | ==Bulletins==
| |
| − | | |
| − | Define Service specific announcements or news which will be shared with the subscribers of the Service on both the Customer and Service Portals
| |
| − | | |
| − | [[Service Bulletins | Creating, Viewing and Managing Service Bulletins]]
| |
| − | | |
| − | ==Service Visibility==
| |
| − | | |
| − | <div class="mw-collapsible mw-collapsed" data-collapsetext="Show Less" data-expandtext="Read More" style="width:800px">
| |
| − | :* Teams
| |
| − | <div class="mw-collapsible-content">
| |
| − | :: It is possible to define which of your support teams have the rights to view and manage requests raised against each Service. By default if no teams are defined against a service all support Teams will be able to do the following:
| |
| − | :::* View All requests raised against the Service from the Request list > Filters > All My Services.
| |
| − | :::* Be Assigned a request raised against the Service from Progressive Capture assignment forms, Request forms, and multi select assignment options on the Request List view.
| |
| − | | |
| − | ::If teams are added to the Service:
| |
| − | :::* Only analysts which belong to those teams will be able to view and manage requests made against the Service.
| |
| − | :::* It will only be possible to assign or reassign a request to another team or analyst in a team which supports the Service
| |
| − | :::* Using the global search bar, analysts will only see results for requests which are logged against services their teams support, or requests which are assigned to them, their teams or where they have been added as members to the requests.
| |
| − | | |
| − | </div>
| |
| − | </div>
| |
| − | | |
| − | <div class="mw-collapsible mw-collapsed" data-collapsetext="Show Less" data-expandtext="Read More" style="width:800px">
| |
| − | :* Subscribing to a Service
| |
| − | <div class="mw-collapsible-content">
| |
| − | :: It is possible to subscribe customers to a service based on various organisation groups. The default position for a service is that all customers will be entitled to use the Service.
| |
| − | | |
| − | :: Through the Administration console, you can define your own organisational groups and once defined these groups and a number of default subscription options will be available through the Subscribers drop down menu.
| |
| − | | |
| − | :: Subscription option types:
| |
| − | | |
| − | ::* Company - Use this option to subscribe all internal customers to the Service
| |
| − | ::* Department - Use this option to subscribe defined Departments to the Service
| |
| − | ::* Team - Use this option to subscribe defined Teams to the Service
| |
| − | ::* General - Use this option to subscribe a defined organisational group to the Service
| |
| − | ::* User - Use this option to subscribe individual internal users to the Service
| |
| − | ::* Contact Organization - Use this option to subscribe specific external organizations to the Service
| |
| − | ::* Individual Contacts - Use this option to subscribe individual contacts to the service
| |
| − | ::* All Contacts - Use this option to subscribe all defined contacts to all supported external organizations to the Service
| |
| − | | |
| − | :: Note :- Department, Team and General options will only appear in the drop list once they have been defined in the Administration console. These can be defined under the Users, Roles & Organisations menu and the Organisation option.
| |
| − | | |
| − | </div>
| |
| − | </div>
| |
| − | | |
| − | ==Service Status==
| |
| − | | |
| − | <div class="mw-collapsible mw-collapsed" data-collapsetext="Show Less" data-expandtext="Read More" style="width:800px">
| |
| − | It is possible to set the status of each service, and an accompanying message so that subscribers to the service can see the status and any supporting message when accessing either the Service or the Customer Portals.
| |
| − | <div class="mw-collapsible-content">
| |
| − | * The default position is 'No Status', this will result in no status or message being displayed on the Service or Customer Portals, this is important when Service Status is not relevant to a Service.
| |
| − | * The Three Status options are
| |
| − | : * Available - Indicated by a green icon
| |
| − | : * Impacted - indicated by an amber icon
| |
| − | : * Unavailable - indicated by a red icon
| |
| − | | |
| − | When any of the above status's are chosen a default message will be displayed, and can be edited. Once saved the status and message will be visible to the subscribers of the service on the Service and or Customer Portals.
| |
| − | | |
| − | :* To Change the Status of the Service, simple select a different option from the drop down list and save.
| |
| − | :* To remove any Status, simply select the 'No Status' option from the drop down list and save.
| |
| − | </div>
| |
| − | </div>
| |
| − | | |
| − | ==Managing Services==
| |
| − | | |
| − | <div class="mw-collapsible mw-collapsed" data-collapsetext="Show Less" data-expandtext="Read More" style="width:800px">
| |
| − | * Editing an Existing Service
| |
| − | <div class="mw-collapsible-content">
| |
| − | :* To '''Edit''' an existing service, select it from the list.
| |
| − | :* To edit a section of the form, click the Edit button located on the right hand side of the section header:
| |
| − | :* Once you are happy with your amendments, click Save.
| |
| − | </div>
| |
| − | </div>
| |
| − | | |
| − | <div class="mw-collapsible mw-collapsed" data-collapsetext="Show Less" data-expandtext="Read More" style="width:800px">
| |
| − | * Deleting a Service
| |
| − | <div class="mw-collapsible-content">
| |
| − | :* To delete a Service, hover over a service on the Service list. The trashcan [[File:Trashcan.png|16px|trashcan]] will appear to the right of service name.
| |
| − | :* Click and confirm your action in the pop up that follows.
| |
| − | </div>
| |
| − | </div> | |
| | | | |
| − | [[Category:Service Manager]] | + | --> |
| | + | [[Category:HDOC]] |
