Partners, suppliers and service integration

Very few organizations deliver services entirely on their own. Cloud platforms, software vendors, telecommunications carriers, outsourced support desks, consultants and specialist partners all contribute components and capabilities. Lesson 10 introduced partners and suppliers as one of the four dimensions. This lesson goes deeper: how organizations decide what to source and from whom, how they classify and manage suppliers according to risk and value, the main sourcing models, how service integration and management (SIAM) coordinates many suppliers, and how contracts and exit planning protect the value the system is meant to deliver.

Why partners and suppliers matter to the value system

Every value chain activity can involve partners and suppliers. Obtain/build often relies on them for components. Deliver and support may be partly outsourced. Engage may work through partners who face customers. Design and transition may use specialist consultants. Even plan and improve draw on supplier roadmaps and benchmarking. When a supplier fails, the effect flows through the value streams that depend on it, and the organization's customers experience the failure regardless of whose fault it was.

This creates a simple but important principle: an organization cannot outsource its accountability to customers. It can outsource work, but it remains responsible for the service it promises.

Partners versus suppliers

ITIL distinguishes relationships along a spectrum, as ITIL-110 described. At one end are basic supplier relationships, where a commodity is bought on standard terms. At the other are partnerships, where two organizations share goals, plan jointly and invest in each other's success. The terms partner and supplier are sometimes used loosely; what matters is the nature of the relationship, which should match the importance and risk of what is being sourced.

Factors in a sourcing strategy

Deciding what to source, and how, is a strategic choice. ITIL suggests several factors that influence an organization's supplier strategy, described here in plain language: its strategic focus (whether it prefers to concentrate on core competencies and source the rest), its corporate culture (some organizations prefer to keep work in-house), resource scarcity (skills that are hard to hire may be easier to source), cost (sourcing may be cheaper or more expensive than doing it internally), subject-matter expertise (a specialist may do the work better), external constraints (regulation and policy may restrict sourcing), and demand patterns (variable demand may favour flexible supplier capacity).

Sourcing models

Organizations use several sourcing models, often in combination. Insourcing keeps work inside the organization. Outsourcing transfers work to an external supplier. Single sourcing uses one supplier for a given type of service; multi-sourcing spreads work across several suppliers, often with one coordinating them. Partnership or joint ventures share investment and risk. Cloud services add consumption-based models where the organization pays for what it uses.

Classifying suppliers by risk and value

Not all suppliers deserve the same attention. A widely used tool for classifying them is the purchasing portfolio matrix associated with Peter Kraljic, which places each supplier or category on two axes: the impact on the organization's results (profit or value impact) and the supply risk (how hard it would be to replace the supplier or how vulnerable supply is). The four quadrants suggest different management approaches.

Contracts and agreements

Contracts set out what suppliers commit to: services, service levels, prices, responsibilities, data handling, security, liability, termination and dispute resolution. A frequent failure is a mismatch between what the organization promises its customers and what its suppliers promise it. If a customer agreement commits to 99.9 % availability but the hosting contract commits only to 99.5 %, the organization carries the gap.

Service integration and management (SIAM)

When an organization uses many suppliers, someone must coordinate them so that end-to-end services work. Service integration and management (SIAM) is an approach in which a service integrator takes responsibility for coordinating multiple suppliers, managing the interfaces between them and providing a single point of accountability for end-to-end service performance. The integrator may be an internal team, an external provider or a hybrid. SIAM is described in its own body of knowledge, separate from ITIL, but fits naturally into the partners and suppliers dimension.

Managing supplier performance

Supplier management is an ongoing activity, not a one-time procurement event. It includes regular performance reviews, tracking service levels and satisfaction, managing risks, handling disputes and planning improvements together. The supplier management practice, covered in ITIL-141, supports this work. For strategic suppliers, reviews should cover not only past performance but future plans and how both organizations can improve value.

Exit planning

Every supplier relationship eventually ends, whether by choice, by contract expiry or because the supplier fails. Exit planning prepares for that moment: how data will be returned, how services will be transferred, what knowledge must be captured and how long the transition will take. Exit plans are particularly important for strategic and bottleneck suppliers, where replacement is hard.

In Canada, the federal government centralized much of its IT infrastructure in Shared Services Canada, created in 2011 to provide email, data centre and network services to federal departments. Departments therefore act partly as consumers of an internal shared supplier, while procurement of external suppliers runs through Public Services and Procurement Canada.

Supplier risk and concentration

Relying heavily on a single supplier creates concentration risk: if that supplier suffers an outage, a security breach or financial trouble, many services fail at once. Cloud platforms are a common example, since one provider may host email, collaboration, data storage and business applications. Organizations manage concentration risk by understanding which services depend on which suppliers, designing critical services to tolerate a supplier failure where the cost is justified, and keeping exit plans current.