Difference between revisions of "Service Portfolio"

From Hornbill
Jump to navigation Jump to search
 
(93 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 details of a service provides some key values and settings to make a service operational. These options include setting the name, description, status, visibility, and more.  Some of this information is mandatory on the creation of a Service so it is important to plan your service before starting.
 
 
 
=== [[Services Request Configuration|Request Configuration]] ===
 
 
 
:Each Service allow you to configure the different the types of requests which will be available. These included Incidents, Service Requests, Problems, Known Errors, and Changes. Each request type can be configured to meet the particular needs for the service, including BPM workflow, available actions, custom fields, and Request Catalog Itesm.
 
 
 
===Assets===
 
: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  visualizing impact when considering implementing changes to a service, or assets which support a service.
 
 
 
===[[Service FAQs|FAQs]]===
 
:Define Frequently Asked Questions (FAQs) which will be helpful to subscribers of the service on both the Customer and Service Portals.
 
 
 
==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>
 +
{|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.
:* 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.
+
|style="width:5%"|
 +
|
 +
|style="width:22%; border-style: solid; border-width: 1px; border-color:#e6e6e6; background-color:#f2f2f2;"|
  
:: Subscription option types:
+
== Related Articles ==
 +
:* [[Service Details]]
 +
:* [[Service Level Agreements]]
 +
|}
  
::* Company - Use this option to subscribe all internal customers to the Service
+
== Services ==
::* Department - Use this option to subscribe defined Departments to the Service
+
The Services List provides a list of the services that are being managed within Service Manager.
::* Team - Use this option to subscribe defined Teams to the Service
+
:* '''Filter Services'''
::* General - Use this option to subscribe a defined organisational group to the Service  
+
:: 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.
::* User - Use this option to subscribe individual internal users to the Service
+
:* '''Type Filter'''
::* Contact Organization - Use this option to subscribe specific external organizations to the Service
+
:: The ''Type Filter'' option lets you filer the list of displayed services by Business or Techincal type
::* Individual Contacts - Use this option to subscribe individual contacts to the service
+
:* '''Category Filter'''
::* All Contacts - Use this option to subscribe all defined contacts to all supported external organizations to the Service
+
:: The ''Category Filter'' option lets you filter the list of displayed Services by Service Category
  
:: 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.
+
{{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
  
</div>
+
:* '''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.
  
==Service Status==
+
:* '''Service Portfolio Status Filter'''
 +
:: 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 mw-collapsed" data-collapsetext="Show Less" data-expandtext="Read More" style="width:800px">
+
:::* '''''Pipeline'''''
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.
+
:::: Pipeline Services are those that are under planning and development. While in a status of Pipeline the Service will not be available to users.
<div class="mw-collapsible-content">
+
:::* '''''Catalog'''''
* 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.
+
:::: Once a Service has the status of ''Catalog'' it is then accessible to users and requests can now be raised against this service.
* The Three Status options are
+
:::* '''''Retired'''''
: * Available - Indicated by a green icon
+
:::: 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.
: * 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.
+
:* '''[[Service Details]]'''
 
+
:: 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.
:* To Change the Status of the Service, simple select a different option from the drop down list and save.
+
<br>
:* To remove any Status, simply select the 'No Status' option from the drop down list and save.  
+
<br>
</div>
 
</div>
 
  
 +
== [[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.
  
 +
:[[Corporate Service Level Agreements|Read more...]]
 +
<br>
  
[[Category:Service Manager]]
+
-->
 +
[[Category:HDOC]]

Latest revision as of 21:55, 8 February 2024

This document can now be found at its new location in the Hornbill Document Library.

Service Portfolio Overview