View source for LP4: Operate the services

<itpmch><title>LP4: Operate the services | YaSM Wiki</title>
<meta name="keywords" content="service operation, yasm operate services, yasm service operation, service management operation process" />
<meta name="description" content="The service operation process in YaSM ensures that the services are delivered effectively and efficiently, in line with the contractual commitments. This includes fulfilling service requests, resolving incidents and problems, as well as carrying out routine operational tasks." />
<meta property="og:url" content="https://yasm.com/wiki/en/index.php/LP4:_Operate_the_services" />
<meta property="og:title" content="LP4: Operate the services | YaSM Service Management Wiki" />
<meta property="og:description" content="The service operation process in YaSM ensures that the services are delivered effectively and efficiently, in line with the contractual commitments. This includes fulfilling service requests, resolving incidents and problems, as well as carrying out routine operational tasks." />
<meta property="og:site_name" content="YaSM Service Management">
<meta property="og:type" content="article" />
<meta property="og:image" content="https://yasm.com/wiki/en/img/yasm-process/16x9/Operate-the-services-yasm-lp4.jpg" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="675" />
<link href="https://plus.google.com/104150539756444616711/posts" rel="publisher" />
</itpmch>
<html><div class="noresize"><a href="https://yasm.com/wiki/de/index.php/LP4:_Betreiben_der_Services"><img src="https://yasm.com/wiki/en/img/yasm-wiki/YaSM-Wiki-Deutsch.png" width="140" height="36" style="float:right;" alt="auf Deutsch" title="This page in German" /></a></div><br style="clear:both;"/>
<p>&nbsp;</p>

<p><b>Process name:</b> <a href="#Process_description">Operate the services</a> - <b>Part of:</b> <a href="/wiki/en/index.php/Service_Management_Processes#Service_lifecycle_processes" title="The service lifecycle processes in YaSM service management">Service lifecycle processes</a>
</p><p><b>Previous process:</b> <a href="/wiki/en/index.php/LP3:_Build_new_or_changed_services" title="LP3: Build new or changed services">Build new or changed services</a>
</p><p><b>Next process:</b> <a href="/wiki/en/index.php/LP5:_Improve_the_services" title="LP5: Improve the services">Improve the services</a></html>
<p>&nbsp;</p>

==Process description==

<html><span id="md-itempage-description" itemprop="description">The <b><span style="color:#465674;">service operation process</span></b> in YaSM (<a href="https://yasm.com/wiki/en/img/yasm-process/Operate-the-services-yasm-lp4.jpg" title="YaSM service operation (LP4)">fig. 1</a>) ensures that the services are delivered effectively and efficiently, in line with the contractual commitments. This includes fulfilling service requests, resolving incidents and problems, as well as carrying out routine operational tasks.</span></p>
<p>&nbsp;</p>

<div itemid="https://yasm.com/wiki/en/img/yasm-process/Operate-the-services-yasm-lp4.jpg" itemscope itemtype="https://schema.org/ImageObject">
<meta itemprop="width" content="1200" />
<meta itemprop="height" content="900" />
<meta itemprop="keywords" content="yasm service operation" />
<meta itemprop="keywords" content="service operation" />
<meta itemprop="keywords" content="service operation process" />
<meta itemprop="keywords" content="ITIL 4 service operation" />
<meta itemprop="representativeOfPage" content="true"/>
<meta itemprop="dateCreated" content="2014-05-02" />
<meta itemprop="datePublished" content="2014-05-08" />
<meta itemprop="dateModified" content="2024-05-19" />
<span itemprop="thumbnail" itemscope itemtype="https://schema.org/ImageObject">
  <meta itemprop="url" content="https://yasm.com/wiki/en/img/yasm-process/16x9/Operate-the-services-yasm-lp4.jpg" />
  <meta itemprop="width" content="1200" />
  <meta itemprop="height" content="675" />
  <meta itemprop="dateCreated" content="2020-06-13" />
  <meta itemprop="datePublished" content="2020-06-14" />
  <meta itemprop="dateModified" content="2024-05-20" />
</span>
<span itemprop="thumbnail" itemscope itemtype="https://schema.org/ImageObject">
  <meta itemprop="url" content="https://yasm.com/wiki/en/img/yasm-process/800px/Operate-the-services-yasm-lp4.jpg" />
  <meta itemprop="width" content="800" />
  <meta itemprop="height" content="600" />
  <meta itemprop="dateCreated" content="2024-05-23" />
  <meta itemprop="datePublished" content="2024-05-29" />
</span>
<span itemprop="thumbnail" itemscope itemtype="https://schema.org/ImageObject">
  <meta itemprop="url" content="https://yasm.com/wiki/en/img/yasm-process/480px/Operate-the-services-yasm-lp4.jpg" />
  <meta itemprop="width" content="480" />
  <meta itemprop="height" content="360" />
  <meta itemprop="dateCreated" content="2024-05-23" />
  <meta itemprop="datePublished" content="2024-05-29" />
</span>
<figure class="mw-halign-left" typeof="mw:File/Thumb"><a itemprop="contentUrl" href="https://yasm.com/wiki/en/img/yasm-process/Operate-the-services-yasm-lp4.jpg" title="Operate the services. - YaSM service operation process LP4"><img srcset="https://yasm.com/wiki/en/img/yasm-process/480px/Operate-the-services-yasm-lp4.jpg 480w, https://yasm.com/wiki/en/img/yasm-process/800px/Operate-the-services-yasm-lp4.jpg 800w, https://yasm.com/wiki/en/img/yasm-process/Operate-the-services-yasm-lp4.jpg 1200w" sizes="100vw" src="https://yasm.com/wiki/en/img/yasm-process/Operate-the-services-yasm-lp4.jpg" fetchpriority="high" decoding="async" width="800" height="600" class="mw-file-element" alt="Fig. 1: Operate the services. - YaSM service operation process LP4. This process corresponds to various ITIL 4 practices, such as 'monitoring and event management', 'ITIL 4 incident management' and 'ITIL 4 problem management'." /></a><figcaption><span style="font-variant:small-caps;"><b>Fig. 1: 'Operate the services'</b><br /><a href="https://yasm.com/wiki/en/img/yasm-process/Operate-the-services-yasm-lp4.jpg" title="YaSM service operation LP4">YaSM service operation process ('LP4')</a>.</span></figcaption></figure></div></html>
<br style="clear:both;"/>

The achieved service quality is measured on a regular basis. The resulting service quality reports are an important input for the service improvement process.

<html><a href="https://yasm.com/wiki/en/img/yasm-process/Operate-the-services-yasm-lp4.jpg" title="Operate the services. - YaSM service operation process LP4">Figure 1</a> above also highlights how three particular sub-processes from service operation (<a href="#LP4.3" title="LP4.3: Monitor the service">Monitor the services</a>, <a href="#LP4.6" title="LP4.6: Resolve incidents and service requests">Resolve incidents and service requests</a>, <a href="#LP4.7" title="LP4.7: Resolve problems">Resolve problems</a>) cooperate in order to detect and resolve actual or potential incidents and their underlying causes (problems).</p>
<p>&nbsp;</p>

<p><i><u>Compatibility</u>: The YaSM service operation process is <a href="/wiki/en/index.php/YaSM_and_ISO_20000#ISO_20000_requirements_and_related_service_management_processes" title="YaSM und ISO 20000">aligned with ISO 20000</a>, the international standard for service management (see ISO/IEC 20000-1:2018, sections <a href="/wiki/en/index.php/YaSM_and_ISO_20000#Relationship-and-agreement" title="ISO 20000 section 8.3: Relationship and agreement">8.3</a>, <a href="/wiki/en/index.php/YaSM_and_ISO_20000#Supply-and-demand" title="ISO 20000 section 8.4: Supply and demand">8.4</a>, <a href="/wiki/en/index.php/YaSM_and_ISO_20000#Service-assurance" title="ISO 20000 section 8.7: Service assurance">8.7</a> and <a href="/wiki/en/index.php/YaSM_and_ISO_20000#Performance_Evaluation" title="ISO 20000 section 9: Performance Evaluation">9</a>) and it corresponds to various ITIL 4 practices, such as '<a href="/wiki/en/index.php/YaSM_and_ITIL#ITIL-4-Monitoring-and-event-management" title="ITIL 4 practices and YaSM processes: ITIL 4 monitoring and event management">monitoring and event management</a>', '<a href="/wiki/en/index.php/YaSM_and_ITIL#ITIL-4-Incident-management" title="ITIL 4 practices and YaSM processes: ITIL 4 incident management">ITIL 4 incident management</a>' and '<a href="/wiki/en/index.php/YaSM_and_ITIL#ITIL-4-Problem-management" title="ITIL 4 practices and YaSM processes: ITIL 4 problem management">ITIL 4 problem management</a>'.</i></html>

==Sub-processes==

<html>YaSM's service operation process has the following sub-processes:</p>

<!-- define schema.org/CreativeWork -->
 <link id="md-type-subProcess" itemprop="additionalType" href="http://www.productontology.org/id/Procedure_(business)" />
<div itemid="https://yasm.com/wiki/en/index.php/LP4:_Operate_the_services#LP4.1" itemscope itemtype="https://schema.org/CreativeWork" itemref="md-type-subProcess">
<meta itemprop="alternateName" content="YaSM service operation process LP4.1" />
<dl id="LP4.1"><dt itemprop="name">LP4.1: Support the service operation</dt>
<dd itemprop="description">Process objective: To provide support for service operation, for example by ensuring that the required resources for operating the services are available, and by configuring and maintaining operational support systems.</dd></dl>
</div>
<div itemid="https://yasm.com/wiki/en/index.php/LP4:_Operate_the_services#LP4.2" itemscope itemtype="https://schema.org/CreativeWork" itemref="md-type-subProcess">
<meta itemprop="alternateName" content="YaSM service operation process LP4.2" />
<dl id="LP4.2"><dt itemprop="name">LP4.2: Provide guidance for service operation</dt>
<dd itemprop="description">Process objective: To provide instructions for the activities to be carried out by operational staff. This includes, for example, the preparation of detailed guidance for regular maintenance tasks.</dd></dl>
</div>
<div itemid="https://yasm.com/wiki/en/index.php/LP4:_Operate_the_services#LP4.3" itemscope itemtype="https://schema.org/CreativeWork" itemref="md-type-subProcess">
<meta itemprop="alternateName" content="YaSM service operation process LP4.3" />
<dl id="LP4.3"><dt itemprop="name">LP4.3: Monitor the services</dt>
<dd itemprop="description">Process objective: To ensure continuous monitoring of both the service components and service usage, promptly responding to any detected irregularities.</dd></dl>
</div>
<div itemid="https://yasm.com/wiki/en/index.php/LP4:_Operate_the_services#LP4.4" itemscope itemtype="https://schema.org/CreativeWork" itemref="md-type-subProcess">
<meta itemprop="alternateName" content="YaSM service operation process LP4.4" />
<dl id="LP4.4"><dt itemprop="name">LP4.4: Produce service quality reports</dt>
<dd itemprop="description">Process objective: To measure the achieved service quality on a regular basis and to identify areas where service quality must be improved.</dd></dl>
</div>
<div itemid="https://yasm.com/wiki/en/index.php/LP4:_Operate_the_services#LP4.5" itemscope itemtype="https://schema.org/CreativeWork" itemref="md-type-subProcess">
<meta itemprop="alternateName" content="YaSM service operation process LP4.5" />
<dl id="LP4.5"><dt itemprop="name">LP4.5: Perform routine operational tasks</dt>
<dd itemprop="description">Process objective: To execute the routine operational tasks required to deliver the agreed service quality on a sustainable basis.</dd></dl>
</div>
<div itemid="https://yasm.com/wiki/en/index.php/LP4.6:_Resolve_incidents_and_service_requests" itemscope itemtype="https://schema.org/CreativeWork" itemref="md-type-subProcess">
<meta itemprop="alternateName" content="YaSM service operation process LP4.6" />
<dl id="LP4.6"><dt itemprop="name"><a href="https://yasm.com/wiki/en/index.php/LP4.6:_Resolve_incidents_and_service_requests" title="4.6: Resolve incidents and service requests">LP4.6: Resolve incidents and service requests</a></dt>
<dd itemprop="description">Process objective: To resolve service incidents (reports of suspected or actual service failures) or requests for service. In the case of service incidents, the primary objective of this process is to return the service to users as quickly as possible. In some cases this involves applying a workaround if the root cause cannot be readily identified and/ or resolved.</dd></dl>
</div>
<div itemid="https://yasm.com/wiki/en/index.php/LP4.7:_Resolve_problems" itemscope itemtype="https://schema.org/CreativeWork" itemref="md-type-subProcess">
<meta itemprop="alternateName" content="YaSM service operation process LP4.7" />
<dl id="LP4.7"><dt itemprop="name"><a href="https://yasm.com/wiki/en/index.php/LP4.7:_Resolve_problems" title="4.7: Resolve problems">LP4.7: Resolve problems</a></dt>
<dd itemprop="description">Process objective: To manage the lifecycle of all problems, where a problem is the underlying cause of one or several (potential) incidents. The primary objective of this process is to prevent service incidents from happening, and to minimize the impact of incidents which cannot be prevented.</dd></dl>
</div><!-- end of schema.org/CreativeWork --><p></html>

==Process outputs==

<html><!-- define schema.org/DefinedTermSet -->
<div itemid="https://yasm.com/wiki/en/index.php/LP4:_Operate_the_services#process-inputs-outputs" itemscope="itemscope" itemtype="https://schema.org/DefinedTermSet">
<link itemprop="additionalType" href="http://www.productontology.org/id/Input/output" />
<meta itemprop="name" content="YaSM process LP4: documents and records" />
<meta itemprop="alternateName" content="Service operation process outputs" />
<meta itemprop="alternateName" content="Service operation data objects" />
<p><span itemprop="description">This section lists the documents and records produced by the operational process.</span> YaSM data objects <a href="#ydo" title="YaSM data object">[*]</a> are marked with an asterisk, while other objects are displayed in gray.</p>

<dl>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">Budget request</dt>
<dd itemprop="description" style="margin-bottom: 1em;">A budget request is typically issued to obtain funding for setting up, improving or operating a service or process. An approved budget request means that the required financial resources have been allocated by the financial manager. <a href="#ydo" title="YaSM data object">[*]</a></dd></div>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">Change record</dt>
<dd itemprop="description" style="margin-bottom: 1em;">A change record contains all details of a change, documenting the lifecycle of a single change. In its initial state, a change record describes a request for change (RFC) which is to be assessed and authorized prior to implementing the change. Further information is added as the change progresses through its lifecycle. <a href="#ydo" title="YaSM data object">[*]</a></dd></div>
<div style="color:#636363" itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">Change status information</dt>
<dd itemprop="description" style="margin-bottom: 1em;">Current status information related to the implementation of a change. This information is sent to the change manager from the various processes that implement authorized changes. It is used by the change manager to keep the change records and the change schedule up-to-date.</dd></div>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">CI record</dt>
<dd itemprop="description" style="margin-bottom: 1em;">Configuration information is maintained in CI records for all configuration items (CIs) under the control of the configuration manager. In this context, CIs can be of various types: Applications, systems and other infrastructure components are treated as CIs, but often also services, policies, project documentation, employees, suppliers, etc. Configuration information is stored in the configuration management system (CMS). <a href="#ydo" title="YaSM data object">[*]</a></dd></div>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">Complaint record</dt>
<dd itemprop="description" style="margin-bottom: 1em;">A record containing the details of a customer complaint, including the actions taken to resolve the complaint. <a href="#ydo" title="YaSM data object">[*]</a></dd></div>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">Customer survey questionnaire</dt>
<dd itemprop="description" style="margin-bottom: 1em;">A customer survey is typically based on questionnaires, aimed at getting insight into overall customer satisfaction and customers' views on specific (aspects of) services. In many cases, answers are given using a scale, for example '1: Very dissatisfied', … , '10: Very satisfied'. <a href="#ydo" title="YaSM data object">[*]</a></dd></div>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">Incident model</dt>
<dd itemprop="description" style="margin-bottom: 1em;">An incident model contains the pre-defined steps that should be taken for dealing with a particular type of incident. The aim of providing incident models is to ensure that recurring incidents are handled efficiently and effectively. <a href="#ydo" title="YaSM data object">[*]</a></dd></div>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">Incident record</dt>
<dd itemprop="description" style="margin-bottom: 1em;">A set of data with all details of a service incident, documenting the history of the incident from registration to closure. A service incident is defined as an unplanned interruption or reduction in quality of a service. Events that could potentially impair a service in the future are also treated as incidents (e.g. the failure of one hard-drive of a set of mirrored drives). See also: <a href="https://yasm.com/wiki/en/index.php/Incident_Record_-_Template" title="Incident record document template">Incident record checklist</a>. <a href="#ydo" title="YaSM data object">[*]</a></dd></div>
<div style="color:#636363" itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">Incident/ request status information</dt>
<dd itemprop="description" style="margin-bottom: 1em;">A message containing the present status of an incident or service request sent to a user who earlier reported a service interruption or submitted a service request. Status information is typically provided to users at various points during an incident's or request's lifecycle. If the resolution time exceeds or is expected to exceed the agreed time frames, status notifications are especially important to keep the user informed.</dd></div>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name" id="Planned-service-outages">Planned service outages</dt>
<dd itemprop="description" style="margin-bottom: 1em;">The planned service outages document or database lists any expected or planned deviations from normal service availability, such as outages due to maintenance work or the implementation of changes. <a href="#ydo" title="YaSM data object">[*]</a></dd></div>
<div style="color:#636363" itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">Pro-active user information</dt>
<dd itemprop="description" style="margin-bottom: 1em;">A notification to users or clients of existing or potential service failures, so that users are in a position to prepare themselves for a period of service unavailability.</dd></div>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">Problem record</dt>
<dd itemprop="description" style="margin-bottom: 1em;">A set of data with all details of a problem, documenting the history of the problem from registration to closure. A problem is defined as the underlying cause of one or more (potential) incidents, although the cause may not be known at the time a problem record is created. Often, a workaround is provided for a problem while a full resolution is not yet available. See also: <a href="https://yasm.com/wiki/en/index.php/Problem_Record_-_Template" title="Problem record document template">Problem record checklist</a>. <a href="#ydo" title="YaSM data object">[*]</a></dd></div>
<div style="color:#636363" itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">Purchase request</dt>
<dd itemprop="description" style="margin-bottom: 1em;">A request to procure goods or services from an external supplier. Purchasing requests are typically sent to the supplier manager, for example if applications, systems or other infrastructure components are needed for setting up a new service, or if standard infrastructure components and consumables are required for service operation.</dd></div>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name" id="Recovery-plan">Recovery plan</dt>
<dd itemprop="description" style="margin-bottom: 1em;">Recovery plans contain detailed instructions for returning specific services and/ or systems to a working state, which often includes recovering data to a defined consistent state. <a href="#ydo" title="YaSM data object">[*]</a></dd></div>
<div style="color:#636363" itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">Request to add skills and human resources</dt>
<dd itemprop="description" style="margin-bottom: 1em;">A request to add skills and human resources to the service provider organization, for example issued during service implementation if new or changed skills and/ or additional human resources are needed for a new service.</dd></div>
<div style="color:#636363" itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">Self-help information for users</dt>
<dd itemprop="description" style="margin-bottom: 1em;">Self-help information for users supplied by the service provider, for example as part of the support pages on the intranet.</dd></div>
<div style="color:#636363" itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">Service access log</dt>
<dd itemprop="description" style="margin-bottom: 1em;">The service access log contains data records gathered by access control systems as users request access to particular services. These data are used, for example, by the security manager, as a basis for improving the security mechanisms and controls.</dd></div>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name" id="Service-operation-manual">Service operation manual</dt>
<dd itemprop="description" style="margin-bottom: 1em;">A service operation manual specifies the activities required for the operation of a service and its underlying infrastructure. The information in the service operation manual is meant to describe the day-to-day tasks in a way that is useful for operational staff. Some instructions related to the operation of particular applications, systems or other infrastructure components may be documented in separate technical manuals or 'standard operating procedures (SOPs)'. <a href="#ydo" title="YaSM data object">[*]</a></dd></div>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name" id="Service-quality-report">Service quality report</dt>
<dd itemprop="description" style="margin-bottom: 1em;">A service quality report gives insight into the service provider's ability to deliver the agreed service quality. Most importantly, it reports on the service levels achieved in relation to the agreed targets, as specified in the service definitions. Service quality reports will also highlight any breaches of contractual commitments and exceptional events. See also: <a href="https://yasm.com/wiki/en/index.php/Service_Quality_Report_-_Template" title="Service quality report document template">Service quality report checklist</a>. <a href="#ydo" title="YaSM data object">[*]</a></dd></div>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">Service request model</dt>
<dd itemprop="description" style="margin-bottom: 1em;">Service request models contain the pre-defined steps that should be taken for dealing with a particular type of service request. The aim of providing service request models is to ensure that routinely occurring requests are handled efficiently and effectively. <a href="#ydo" title="YaSM data object">[*]</a></dd></div>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">Service request record</dt>
<dd itemprop="description" style="margin-bottom: 1em;">A record containing all details of a service request. Service requests are formal requests from a client or user for something to be provided within the framework of existing service agreements - for example, a request for information or advice; to reset a password; or to install a workstation for a new user. <a href="#ydo" title="YaSM data object">[*]</a></dd></div>
<div style="color:#636363" itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">Service usage statistics</dt>
<dd itemprop="description" style="margin-bottom: 1em;">Statistical data on service usage by clients/ users, as a basis for producing client invoices.</dd></div>
<div style="color:#636363" itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">Suggested changes to self-help information</dt>
<dd itemprop="description" style="margin-bottom: 1em;">A suggestion to update self-help information for users supplied by the service provider, for example as part of the support pages on the intranet.</dd></div>
<div style="color:#636363" itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">Suggested improvement to continuity arrangements</dt>
<dd itemprop="description" style="margin-bottom: 1em;">A suggestion for improving service security. Suggestions for security improvements may originate from anywhere within the organization.</dd></div>
<div style="color:#636363" itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">Suggested process modification</dt>
<dd itemprop="description" style="margin-bottom: 1em;">A suggestion for modifying one or several service management processes. Suggestions for process modifications or improvements may originate from anywhere within the organization.</dd></div>
<div style="color:#636363" itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">Suggested service modification</dt>
<dd itemprop="description" style="margin-bottom: 1em;">A suggestion for modifying a service, for example to improve service quality or economics. Suggestions may originate from anywhere within or outside of the service provider organization.</dd></div>
<div style="color:#636363" itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">Support request</dt>
<dd itemprop="description" style="margin-bottom: 1em;">A request to support the resolution of an incident or problem, usually issued from the incident or problem manager when further assistance is needed from technical experts or external suppliers.</dd></div>
<div style="color:#636363" itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">System event log</dt>
<dd itemprop="description" style="margin-bottom: 1em;">The system event log contains data records generated by the monitoring systems which continually check the state of the technical infrastructure. Event records are used, for example, to detect current service interruptions that necessitate immediate action. Event records are also the basis for identifying conditions that require preventive action in order to sustain service quality, such as imminent capacity shortages.</dd></div>
<div style="color:#636363" itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">Technical manual</dt>
<dd itemprop="description" style="margin-bottom: 1em;">A document describing the procedures required to run and maintain a system or infrastructure component. Technical manuals are often provided by external product suppliers or internal development teams.</dd></div>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">Test report</dt>
<dd itemprop="description" style="margin-bottom: 1em;">A test report provides a detailed account of testing activities. A test report is created for example during tests of new or changed service components, or during tests of security or service continuity mechanisms. <a href="#ydo" title="YaSM data object">[*]</a></dd></div>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">Test script</dt>
<dd itemprop="description" style="margin-bottom: 1em;">A test script specifies a set of test cases including their expected outcomes. The nature of the test cases will vary depending on what is to be tested.</dd></div>
<div style="color:#636363" itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<dt itemprop="name">User manual</dt>
<dd itemprop="description" style="margin-bottom: 1em;">A document for end-users, describing how to use a type of application or system. <a href="#ydo" title="YaSM data object">[*]</a></dd></div>
</dl>
</div><!-- end of schema.org/DefinedTermSet --><p>

<p>&nbsp;</p>
<hr />
<p><i><u>Notes</u>:</i>
</p><p><span id="ydo"><strong>[*]</strong> <i>"YaSM data objects"</i> are those documents or records for which the YaSM model provides detailed recommendations: Every YaSM object has an associated checklist (see <a href="https://yasm.com/wiki/en/index.php/Service_Quality_Report_-_Template" title="Service quality report document template">'Service quality report' template</a> and <a href="https://yasm.com/wiki/en/index.php/Service_Management_Checklists#yasm-template-example" title="Examples: YaSM checklists and document templates">more examples</a>) describing its typical contents, and an associated lifecycle diagram depicting how the status of the object changes as it is created, updated, read and archived by various YaSM processes (see <a href="https://yasm.com/wiki/en/img/yasm-project/Yasm-object-lifecycle-diagram.jpg" title="Example: YaSM object lifecycle diagram (.JPG)">example</a>).</span>
</p><p><i>"Other objects"</i> are mostly informal data or information where YaSM has less strong views about their contents. There are no associated lifecycle diagrams or checklists.</html>

==Process metrics==

Process metrics are used, for example, to assess if the service management processes are running according to expectations.

For suggestions of [[Service Management Metrics|suitable metrics]], please refer to the [[Service_Management_Metrics#Metrics_for_the_service_operation_process|list of metrics for the service operation process]].

==Roles and responsibilities==

<span id="responsible">Process owner: An ''operations manager'' will be needed to take overall responsibility for operating a service. For instance, this role will ensure that all day-to-day operational activities are carried out in a timely and reliable way.</span>
<p>&nbsp;</p>

{| class="wikitable" style="background: white; font-size: 95%"
|+style="background:#465674; color:#ffffff; font-size: 110%"|Responsibility matrix: 'LP4: Operate the services'
|- style="vertical-align:top"
! colspan="2"| YaSM role / sub-process
! [[YaSM Roles#Operations-manager|Operations manager]]
! [[YaSM Roles#Operator|Oper.]]
! [[YaSM Roles#Service-owner|Serv. owner]]
! [[YaSM Roles#Technical-domain-expert|Techn. domain expert]]
|- style="text-align:center"
| LP4.1
| style="text-align:left"|[[#LP4.1|Support the service operation]]
|AR	
|R	
|R	
|R
|- style="text-align:center"
|LP4.2
| style="text-align:left"|[[#LP4.2|Provide guidance for service operation]]
|AR	
| -	 
|R
|R
|- style="text-align:center"
|LP4.3
| style="text-align:left"|[[#LP4.3|Monitor the services]]
|A
|R
| - 
| -
|- style="text-align:center"
| LP4.4
| style="text-align:left"|[[#LP4.4|Produce service quality reports]]
|A
|R
|R
| -
|- style="text-align:center"
| LP4.5
| style="text-align:left"|[[#LP4.5|Perform routine operational tasks]]
|A
|R
| -
| -
|-
|- style="text-align:center"
| LP4.6
| style="text-align:left"|[[#LP4.6|Resolve incidents and service requests]]
|colspan="4"|see [[LP4.6: Resolve incidents and service requests#raci-matrix-lp4-6|RACI matrix "LP4.6: Resolve incidents and service requests"]]
|-
|- style="text-align:center"
| LP4.7
| style="text-align:left"|[[#LP4.7|Resolve problems]]
|colspan="4"|see [[LP4.7: Resolve problems#raci-matrix-lp4-7|RACI matrix "LP4.7: Resolve problems"]]
|-
|}

<p>&nbsp;</p>

==Notes==

<html><div itemid="https://yasm.com/wiki/en/img/yasm-process/goal-definition/yasm-service-operation-process.jpg" itemscope itemtype="https://schema.org/ImageObject">
<meta itemprop="caption" content="Process objective: YaSM service operation - Operate the services (LP4)." />
<meta itemprop="width" content="1200" />
<meta itemprop="height" content="627" />
<meta itemprop="dateCreated" content="2021-09-21" />
<meta itemprop="datePublished" content="2021-09-22" />
<span itemprop="thumbnail" itemscope itemtype="https://schema.org/ImageObject">
  <meta itemprop="url" content="https://yasm.com/wiki/en/img/yasm-process/goal-definition/400px/yasm-service-operation-process.jpg" />
  <meta itemprop="width" content="400" />
  <meta itemprop="height" content="209" />
  <meta itemprop="dateCreated" content="2023-12-12" />
  <meta itemprop="datePublished" content="2023-12-29" />
</span>
<meta itemprop="keywords" content="Objectives service operation process" />

<figure class="mw-halign-left" typeof="mw:File/Thumb"><a itemprop="contentUrl" href="https://yasm.com/wiki/en/img/yasm-process/goal-definition/yasm-service-operation-process.jpg" title="Service operation: process objectives">
<img srcset="https://yasm.com/wiki/en/img/yasm-process/goal-definition/400px/yasm-service-operation-process.jpg 400w, https://yasm.com/wiki/en/img/yasm-process/goal-definition/yasm-service-operation-process.jpg 1200w" sizes="100vw" src="https://yasm.com/wiki/en/img/yasm-process/goal-definition/yasm-service-operation-process.jpg" decoding="async" width="400" height="209" class="mw-file-element" alt="The service operation process in YaSM ensures the services are delivered effectively and efficiently, in line with the contractual commitments. This includes fulfilling service requests, resolving incidents and problems, as well as carrying out routine operational tasks." /></a><figcaption><span style="font-variant:small-caps;">Service operation process: Objectives</span></figcaption></figure></div>

<p>Is based on: The service operation process from the <a href="https://yasm.com/en/products/yasm-process-map" title="YaSM Process Map">YaSM Process Map</a>.</p>
<p>By:&#160;&#160;Stefan Kempter&#160;<a href="https://www.linkedin.com/in/stefankempter"><img style="margin:0px 0px 0px 0px;" src="/wiki/en/img/yasm-wiki/bookmarking/linkedin.jpg" width="16" height="16" title="By: Stefan Kempter | Profile on LinkedIn" alt="Author: Stefan Kempter, IT Process Maps GbR" /></a>&#160;&#160;and&#160;&#160;Andrea Kempter&#160;<a href="https://www.linkedin.com/in/andreakempter"><img style="margin:0px 0px 0px 0px;" src="/wiki/en/img/yasm-wiki/bookmarking/linkedin.jpg" width="16" height="16" title="By: Andrea Kempter | Profile on LinkedIn" alt="Contributor: Andrea Kempter, IT Process Maps GbR" /></a>, IT Process Maps.<br style="clear:both;"/><p></html>

==Related articles==

<html><figure class="mw-halign-left" typeof="mw:File/Thumb"><a href="https://yasm.com/wiki/en/index.php/Service_Operation" title="Service operation according to YaSM"><img srcset="https://yasm.com/wiki/en/img/yasm-service-management/400px/service-operation.jpg 400w, https://yasm.com/wiki/en/img/yasm-service-management/480px/service-operation.jpg 480w, https://yasm.com/wiki/en/img/yasm-service-management/service-operation.jpg 1200w" sizes="100vw" src="https://yasm.com/wiki/en/img/yasm-service-management/service-operation.jpg" decoding="async" width="400" height="225" class="mw-file-element" alt="Is the purpose of YaSM's operational process different from ITIL&reg; and what's special about service operation in YaSM?" /></a><figcaption><span style="font-variant:small-caps;">How to operate services in YaSM and the ITSM frameworks.</span></figcaption></figure>
<p><a href="https://yasm.com/wiki/en/index.php/Service_Operation" title="Service operation: How to operate services">Service operation according to YaSM</a></p>
<p>Since the existing guidance on service operation is well established and generally accepted, the service operation process in YaSM is based on the guidance provided in ITIL<sup><small>&#174;</small></sup> and other service management frameworks.</p>
<p>What's special about service operation in YaSM? <br /><a href="https://yasm.com/wiki/en/index.php/Service_Operation" title="Service operation: How to operate services in YaSM and the ITSM frameworks">[&nbsp;...&nbsp;Read more&nbsp;]</a></p>
<br style="clear:both;"/>
<p>&nbsp;</p>

<p><small>
<span itemprop="breadcrumb" itemscope itemtype="https://schema.org/BreadcrumbList">
<span itemprop="itemListElement" itemscope itemtype="https://schema.org/ListItem">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/LP4:_Operate_the_services#Process_description">
<span itemprop="name">Process description</span></a>
<meta itemprop="position" content="1" /></span> ›
<span itemprop="itemListElement" itemscope itemtype="https://schema.org/ListItem">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/LP4:_Operate_the_services#Sub-processes">
<span itemprop="name">Sub-processes</span></a>
<meta itemprop="position" content="2" /></span> ›
<span itemprop="itemListElement" itemscope itemtype="https://schema.org/ListItem">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/LP4:_Operate_the_services#Process_outputs">
<span itemprop="name">Process outputs</span></a>
<meta itemprop="position" content="3" /></span> ›
<span itemprop="itemListElement" itemscope itemtype="https://schema.org/ListItem">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/LP4:_Operate_the_services#Process_metrics">
<span itemprop="name">Metrics</span></a>
<meta itemprop="position" content="4" /></span> ›
<span itemprop="itemListElement" itemscope itemtype="https://schema.org/ListItem">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/LP4:_Operate_the_services#Roles_and_responsibilities">
<span itemprop="name">Roles</span></a>
<meta itemprop="position" content="5" /></span>
</span>
</small></p>

<!-- define schema.org/ItemPage -->
<div itemscope itemtype="https://schema.org/ItemPage">
 <meta itemprop="name Headline" content="LP4: Operate the services" />
 <meta itemprop="alternativeHeadline" content="YaSM service operation process" />
 <meta itemprop="alternativeHeadline" content="Service operation process" />
 <link itemprop="primaryImageOfPage" href="https://yasm.com/wiki/en/img/yasm-process/Operate-the-services-yasm-lp4.jpg" />
 <meta itemprop="significantLinks" content="https://yasm.com/wiki/en/index.php/Service_Management_Checklists#yasm-template-example" />
 <meta itemprop="significantLinks" content="https://yasm.com/wiki/en/index.php/Service_Quality_Report_-_Template" />
 <meta itemprop="significantLinks" content="https://yasm.com/wiki/en/index.php/YaSM_Metrics" />
 <meta itemprop="significantLinks" content="https://yasm.com/wiki/en/index.php/YaSM_Metrics/_Service_Lifecycle_Processes#metrics-lp4" />
</div>

<!-- define schema.org/CreativeWork --> 
 <div itemscope itemtype="https://schema.org/CreativeWork">
 <link id="md-type-process" itemprop="additionalType" href="http://www.productontology.org/id/Business_process" />
  <meta itemscope itemprop="mainEntityOfPage" itemType="https://schema.org/ItemPage"
itemid="https://yasm.com/wiki/en/index.php/LP4:_Operate_the_services" itemref="md-itempage-description">
  <meta itemprop="name" content="LP4: Operate the services" />
  <meta itemprop="alternateName" content="YaSM service operation process" />
  <meta itemprop="alternateName" content="Service operation process" />
  <link itemprop="url" href="https://yasm.com/wiki/en/index.php/LP4:_Operate_the_services" />
  <link itemprop="hasPart" href="https://yasm.com/wiki/en/index.php/LP4:_Operate_the_services#LP4.1">
  <link itemprop="hasPart" href="https://yasm.com/wiki/en/index.php/LP4:_Operate_the_services#LP4.2">
  <link itemprop="hasPart" href="https://yasm.com/wiki/en/index.php/LP4:_Operate_the_services#LP4.3">
  <link itemprop="hasPart" href="https://yasm.com/wiki/en/index.php/LP4:_Operate_the_services#LP4.4">
  <link itemprop="hasPart" href="https://yasm.com/wiki/en/index.php/LP4:_Operate_the_services#LP4.5">
  <link itemprop="hasPart" href="https://yasm.com/wiki/en/index.php/LP4.6:_Resolve_incidents_and_service_requests">
  <link itemprop="hasPart" href="https://yasm.com/wiki/en/index.php/LP4.7:_Resolve_problems">
  <link itemprop="hasPart" href="https://yasm.com/wiki/en/index.php/LP4:_Operate_the_services#process-inputs-outputs">
  <link itemprop="image" href="https://yasm.com/wiki/en/img/yasm-process/Operate-the-services-yasm-lp4.jpg" />
  <link itemprop="image" href="https://yasm.com/wiki/en/img/yasm-process/goal-definition/yasm-service-operation-process.jpg" />
  <link itemprop="isPartOf" href="https://yasm.com/wiki/en/index.php/Service_Management_Processes#service-lifecycle-processes" />
  <meta itemprop="mentions" content="ITIL 4 service operation" />
  <meta itemprop="isBasedOnUrl" content="https://yasm.com/en/products/yasm-process-map" />
  <meta itemprop="inLanguage" content="en" />
  <link  itemprop="citation" href="https://yasm.com/wiki/de/index.php/LP4:_Betreiben_der_Services" />
  <link itemprop="publisher" href="https://yasm.com/en/#YaSMBrand" />
  <link itemprop="copyrightHolder creator" href="https://yasm.com/en/contact#ITProcessMapsOrg" />
  <link itemprop="author" href="https://yasm.com/en/misc/team#StefanKempter" />
  <link itemprop="contributor" href="https://yasm.com/en/misc/team#AndreaKempter" />
</div><p></html>

<!-- This page is assigned to the following categories: -->
[[Category:YaSM process]]
<!-- --- -->