Skip to main content

Service Provider Interfaces


With the rise of service specialization, sourcing services from multiple service providers has become the normal way of doing business. This approach has allowed service providers to deliver higher quality services and enhanced support capabilities while more affectively utilizing a greater constrained set of resources.  In order for this cost savings and ability to spread risk to be realized an organization must be able to maintain a strong relationship with each service provider.

In order to support the development of strong relationships in a multi-vendor environment, guidelines and reference points (technological, procedural and organizational) between the organization and the multitude of vendors being engaged must be established.  These validated reference points are known as service provider interfaces (SPI).

A service provider interface is a formally defined reference point which identifies some interaction between a service provider and user, customer, process or one or more suppliers.  SPIs are commonly used to ensure that multiple parties in a relationship have the same points of reference for defining, delivering and reporting on services.

SPIs help to coordinate the end to end management of services that are being used to underpin the delivery of business outcomes.  The service portfolio is used to define service specifications.  Since service levels and responsibilities are negotiated at the same time that these relationships are being established, they should include: 
  • Identification of integration points between various management processes of the organization and the various service providers
  •  Identification of specific roles and responsibilities for managing the ongoing systems management relationship with all parties
  •  Identification of relevant systems management information that needs to be communicated to all parties on an ongoing basis
SPIs may also consider overall management, strategy and transition in addition to live services.  This is extremely significant when the service providers involved are part of a strategic initiative to transform an organizations business.

SPIs are defined, maintained and owned by process owners.  However others such as business representatives and service provider process coordinators may be included in creating these definitions.

Comments

Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables.  An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and th

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service". I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize: SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle. ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with the

ITIL 4 – Decoupling Deployment from Release Management Practice

ITIL 4 is an evolution of ITIL V3. Before we start talking about specific processes or practices, it is important to stress that the focus has shifted. ITIL 4 gives us a fresh perspective to service management and emphasizes the customer user experience, the approach to the overall service value system, the service value chain and value streams , and much more.  Download the What is ITIL 4 document from the ITSM Academy Resource Center and be sure to read past the first few pages for more information on the new perspective that drives modern service management. The emphasis is on value from the customer user experience and integrated holistic approach. That does not mean that the processes are going away. Today we refer to a process as a "practice". Practices are broader in scope than processes and include all 4 dimensions/resources including the process. Two processes or “practices” that have been decoupled in ITIL 4 are the Deployment Management practice an