Difference between revisions of "EGI IT Service Management"

From EGIWiki
Jump to: navigation, search
(Service Management Processes)
(Replaced content with " Overview of EGI Service Management has been moved under [http://ims.egi.eu/ EGI Confluence instance] (access restricted to EGI.eu staff) For questions contact [mailto:qua...")
 
(29 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{ITSM_menubar}} {{TOC_right}}
 
  
'''<span style="color:#FF0000">-----(in progress)-----</span>'''
 
  
= Overview of EGI IT Service Management =
+
Overview of EGI Service Management has been moved under [http://ims.egi.eu/ EGI Confluence instance] (access restricted to EGI.eu staff)
  
== What is IT Service Management  ==
 
  
IT service management is the implementation and management of quality IT services performed by IT service providers through people, process and information technology. Service management that can cope with federated environments, such as EGI, often lack the hierarchy and formal agreements seen in other situations.
+
For questions contact [mailto:quality@egi.eu EGI.eu Quality Team]
 
 
EGI.eu is a client partner within the FedSM project, where the focus is on tailoring ITIL best practices within a federated environment such as EGI. The ITIL framework has already been mentioned in a variety of EGI documents and referenced as a strategic area for improving service management across EGI. ITIL is the most widely accepted approach to IT service management and the de facto standard for operating computer centres in the industrial sector providing a cohesive set of best practices, drawn from the public and private sectors internationally.
 
 
 
== What is FitSM  ==
 
 
 
FitSM is a lightweight standards family aimed at facilitating service management in IT service provision, including federated scenarios.&nbsp;The main goals of the FitSM family are:
 
 
 
*Create a clear, pragmatic, lightweight and achievable standard that allows for effective IT service management (ITSM).<br>
 
*Provide a baseline level of ITSM than can act to support ‘management interoperability’ in federated environments where disparate or competing organisations must cooperate to manage services.
 
*Give concrete support for ITSM implementation through assessment tools, guides, templates and samples.
 
*Offer a version of ITSM that can cope with federated environments, which often lack the hierarchy and level of control seen in other situations, as well as other sectors where ITSM is less well accepted.
 
 
 
The FitSM family helps service providers to manage their services in a more consistent, controlled and repeatable way. This supports improvement of your services and sustainable operation.
 
 
 
FitSM provides a simple access point to ITSM implementation, which provides benefits in itself and is also compatible with major international approaches such as the ITIL best practice framework and the ISO/IEC 20000 international standard for ITSM. As such FitSM support later migration to these more heavyweight approaches.
 
 
 
The components of the FitSM standard are freely available from [http://www.fitsm.eu www.fitsm.eu]. Training and personal certification (based on certification from TÜV SÜD) is also available. Free training and certification is offered through the European Commission funded FedSM project ([http://www.fedsm.eu www.fedsm.eu]).<br>
 
 
 
== Objective of ITSM  ==
 
 
 
The objective of ITSM for EGI is to:
 
 
 
*Implement structured processes for the improvement of service delivery to its customers based on the [http://www.fedsm.eu/fitsm FitSM-1:2013 standard].
 
 
 
== Scope Statement  ==
 
 
 
In the first phase of ITSM implementation, EGI focused on 7 of the 14 total [[EGI ITSM#Service_Management_Processes|processes]] outlined by the [http://www.fedsm.eu/fitsm FitSM-1:2013 standard], which is then be expanded to the others. The rationale for those selected is based on the processes that others depend and to balance the effort required to implement ITSM processes overall. The processes are planned to be applied to all services defined in the [http://www.egi.eu/services/catalogue EGI.eu Service Catalogue]&nbsp;starting first with Federated Operations.
 
 
 
More specifically, the first processes for detailing individual activities, processes and procedures will be with Service Portfolio Management, Service Level Management, and Customer Relationship Management.
 
 
 
It was understood that has processes mature, ITSM implementation will focus on the service that will have the most impact, such as looking at CRM for the Federated Cloud.
 
 
 
The self-assessment was conducted for the first 7 processes in 2013. During the annual review of the self-assessment, the first 7 processes were updated, and an initial asssement was done for the final 7, providing a clear picture and focus areas for improvement of all 14 processs.<br>
 
 
 
== General Requirements ==
 
 
 
General requirements for EGI's service management system can be found [[EGI SMS General Requirements|here]]. <br>
 
 
 
= EGI.eu Service Management Policy  =
 
 
 
1.) '''Process Approach.''' To effectively manage all IT services and underlying components, a process-based approach to service management shall be adopted.
 
 
 
*All required processes are defined, communicated and improved based on business needs and feedback from people and parties involved.
 
*Roles and responsibilities are clearly defined.
 
 
 
2.) '''Customer and User Alignment.''' The provision of IT services shall be aligned to customer and user needs.
 
 
 
*IT Services are delivered in a defined quality sufficient to satisfy requirements identified from business processes.
 
*For all IT services, a corporate level SLA and/or specific SLAs, which have been agreed with stakeholders, is in place.
 
 
 
3.) '''Continual Improvement. ''' IT Services and service management processes shall be continually improved.
 
 
 
*Feedback from stakeholders is used to continually improve IT services and service quality. All proposals for improvements are recorded and evaluated.
 
*IT Service management is improved based on continual monitoring of process performance and effectiveness.
 
 
 
4.) '''Training &amp; Awareness. '''Through trainings and awareness measures, it shall be ensured that staff involved in service management activities can effectively perform according to their roles.
 
 
 
5.) '''Leadership. '''Senior management is committed to this policy and its implementation. It provides the resources required to implement and improve service management and enhance customer and user satisfaction with IT services.
 
 
 
<br>
 
 
 
''-Approved by the EGI.eu Director and Operations Management Board on September 27, 2013-'' <br><br>
 
 
 
= Service Management Processes<br>  =
 
 
 
{| class="wikitable"
 
|-
 
! Process
 
! Abbr.
 
! Key goal / objective
 
! Implementation Phase&nbsp;
 
! Process Owner
 
|-
 
| '''[[EGI Service Portfolio Management|Service Portfolio Management]]'''
 
| SPM
 
| Define and maintain a service portfolio
 
| Phase 1
 
| [mailto:sy.holsinger@egi.eu Sy Holsinger], EGI.eu
 
|-
 
| '''[[EGI Service Level Management|Service Level Management]]'''
 
| SLM
 
| Define, agree and monitor service levels with customers by establishing meaningful service level agreements (SLAs) and supportive operational level agreements (OLAs)
 
| Phase 1
 
| [mailto:malgorzata.krakowian@egi.eu Malgorzata Krakowian], EGI.eu
 
|-
 
| '''[[EGI Service Reporting Management|Service Reporting Management]]'''
 
| SRM
 
| Specify all service reports and ensure they are produced according to specifications in a timely manner to support decision-making
 
| Phase 1
 
| [mailto:malgorzata.krakowian@egi.eu Malgorzata Krakowian], EGI.eu
 
|-
 
| '''[[EGI Service Continuity Availability Management|Service Continuity Availability Management]]'''
 
| SCAM
 
| Ensure sufficient service availability to meet agreed requirements and adequate service continuity in case of exceptional situations
 
| Phase 2
 
| [mailto:peter.solagna@egi.eu Peter Solagna], EGI.eu
 
|-
 
| '''[[EGI Capacity Management|Capacity Management]]'''
 
| CAPM
 
| Ensure sufficient capacities are provided to meet agreed service capacity and performance requirements
 
| Phase 2
 
| [mailto:peter.solagna@egi.eu Peter Solagna], EGI.eu
 
|-
 
| '''[[EGI Information Security Management|Information Security Management]]'''
 
| ISM
 
| Manage information security effectively through all activities performed to deliver and manage services, so that the confidentiality, integrity and accessibility of relevant assets are preserved
 
| Phase 2
 
| [mailto:peter.solagna@egi.eu Peter Solagna], EGI.eu
 
|-
 
| '''[[EGI Customer Relationship Management|Customer Relationship Management]]'''
 
| CRM
 
| Establish and maintain a good relationship with customers receiving services
 
| Phase 1
 
| [mailto:gergely.sipos@egi.eu Gergely Sipos], EGI.eu
 
|-
 
| '''[[EGI Supplier Relationship Management|Supplier Relationship Management]]'''
 
| SUPPM
 
| Establish and maintain a healthy relationship with suppliers supporting the service provider in delivering services to customers, and to maintain contracts with suppliers
 
| Phase 1
 
| [mailto:michel.drescher@egi.eu Michel Drescher], EGI.eu
 
|-
 
| '''[[EGI Incident & Service Request Management|Incident &amp; Service Request Management]]'''
 
| ISRM
 
| Restore normal / agreed service operation within the agreed time after the occurrence of an incident, and to respond to user service requests
 
| Phase 1
 
| [mailto:malgorzata.krakowian@egi.eu Malgorzata Krakowian], EGI.eu
 
|-
 
| '''[[EGI Problem Management|Problem Management]]'''
 
| PM
 
| Investigate the root causes of (recurring) incidents in order to avoid future recurrence of incidents by resolving the underlying problem, or to ensure workarounds / temporary fixes are available to support quick restoration of the service, if incidents re-occur
 
| Phase 2
 
| [mailto:malgorzata.krakowian@egi.eu Malgorzata Krakowian], EGI.eu
 
|-
 
| '''[[EGI Configuration Management|Configuration Management]]'''
 
| CONFM
 
| Provide and maintain a logical model of all configuration items and their relationships and dependencies
 
| Phase 2
 
| [mailto:michel.drescher@egi.eu Michel Drescher], EGI.eu
 
|-
 
| '''[[EGI Change Management|Change Management]]'''
 
| CHM
 
| Ensure changes to configuration items are planned, approved, implemented and reviewed in a controlled manner to avoid adverse impact of changes to services or the customers receiving services
 
| Phase 2
 
| [mailto:michel.drescher@egi.eu Michel Drescher], EGI.eu
 
|-
 
| '''[[EGI Release & Deployment Management|Release &amp; Deployment Management]]'''
 
| RDM
 
| Bundle changes to one or more configuration items into releases, so that these changes can be tested and deployed to the live environment together
 
| Phase 2
 
| [mailto:peter.solagna@egi.eu Peter Solagna], EGI.eu
 
|-
 
| '''[[EGI Continual Service Improvement Management|Continual Service Improvement Management]]'''
 
| CSI
 
| Identify, prioritise, plan, implement and review improvements to services and service management
 
| Phase 1
 
| [mailto:sergio.andreozzi@egi.eu Sergio Andreozzi], EGI.eu
 
|}
 
 
 
<br>
 
 
 
= Contact  =
 
 
 
For individual processes please contact the process owner in the table above.
 
 
 
For general questions contact [mailto:policy@egi.eu EGI.eu Strategy and Policy Team]
 
 
 
Senior level management contact: [mailto:operations@egi.eu Peter Solagna], EGI.eu Senior Operations Manager
 
 
 
<br> <br>
 
 
 
[[Category:EGI_ITSM]]
 

Latest revision as of 11:57, 5 August 2016


Overview of EGI Service Management has been moved under EGI Confluence instance (access restricted to EGI.eu staff)


For questions contact EGI.eu Quality Team