SIAM structural elements: service integrator, service providers and retained capabilities
Domain 3 tests the three structural elements - service integrator, service providers and retained capabilities - and whether you can justify a structural option rather than defaulting to one.
The layers
- Customer organisation and governance: owns the business relationship, sets direction, holds accountability.
- SIAM layer: the service integrator owning integration processes, end-to-end performance, cross-provider coordination and reporting.
- Service provider layer: internal or external providers delivering services or service components ("towers" such as network, applications, hosting, security).
Structural options
- Internal integrator: the customer builds the SI function. Strong on control, knowledge and conflict-of-interest avoidance; costly at small scale and slow to mature.
- External integrator: a third party integrates. Fast access to capability; requires strong retained oversight and explicit conflict rules.
- Hybrid integrator: split responsibilities, for example an external integrator operating processes and tooling while service accountability, security and strategy stay internal. Distinguish independent multi-source models from lead or prime provider models, where one provider integrates and delivers - a structural conflict of interest that must be governed.
Retained capabilities
What the organisation keeps because it is strategic, regulated or commercially sensitive: service strategy and demand, enterprise and technical architecture, service ownership, sourcing and contract management, security and compliance, business relationship management and - critically - SIAM oversight when the integrator is external. Retained capability must be funded and staffed; it is not the residue left after outsourcing.
Worked example
A mid-sized insurer with weak internal architecture skills and tight regulatory oversight must choose a model. Reasoning: a fully external integrator is fast but leaves the insurer unable to challenge provider designs or satisfy the regulator; a fully internal integrator takes two years to mature. Hybrid wins: external integrator for process operation, reporting and tooling; retained service owners, security and architecture; a governance board with a written conflict-of-interest rule.
Traps that cost marks
- Assuming retained capabilities shrink to nothing once SIAM is in place.
- Assuming an internal integrator carries no cost or skill requirement.
- Confusing the service integrator with the service desk.
- Placing end-to-end accountability with an external integrator - it stays with the customer.
- Ignoring the conflict of interest in lead or prime provider models.