Introduction to Service Integration and Management
This domain tests the definition of SIAM, why organisations adopt it, who participates in the SIAM ecosystem and how the layers fit together. Expect definition-style questions where one changed word makes an option wrong.
Definition and drivers
The SIAM body of knowledge defines SIAM as a management set of practices used to manage multiple service providers and to integrate them to bring a single, seamless service to the business. The driver is multi-sourcing: services are decomposed into components delivered by different internal and external providers, and no single provider can see or control the end-to-end service. SIAM restores end-to-end accountability without forcing the business back to a single supplier.
Ecosystem and layers
- Customer/business - sets requirements, owns governance and the commercial relationship.
- Service integrator - single point of accountability for the end-to-end service; owns cross-provider processes, end-to-end service levels and provider performance. It integrates, and need not deliver services itself.
- Service providers - deliver to agreed specifications and may subcontract to their own suppliers.
- Layers - governance (customer), management/integration (SIAM), delivery (providers).
SIAM is not a tool, a product, a framework or an outsourcing contract. It is an approach that orchestrates existing practices such as ITIL, COBIT, Lean and DevOps. Delivery models vary: an internal integrator, an external integrator, a hybrid, or one provider acting as lead provider. Benefits cited for SIAM include a single point of accountability, consistent end-to-end processes, cost transparency and faster onboarding of providers.
Worked example
A retailer runs payroll across three providers: an application host, a network provider and an internal database team. Each reports 99.9% availability, yet payroll fails monthly. SIAM reasoning: nobody owns the end-to-end service. Appointing a service integrator, defining one payroll service with an end-to-end service level, an underpinning OLA per provider and one cross-provider incident process gives the business a single accountable owner and a single measured outcome.
Traps
- Assuming SIAM means outsourcing, or that the integrator must be external; internal and hybrid integrators are equally valid.
- Confusing the integrator with a prime contractor that also delivers every service.
- Believing SIAM removes provider accountability - it exposes and coordinates it.
- Treating SIAM as synonymous with ITSM tooling.