In today’s blog post, Service Management workshop leaders Simon Dorst and Michelle Major-Goldsmith provide a sneak peek into some of their thoughts on SIAM in the lead-up to their half-day workshop on SIAM: revolution or evolution, at this year’s Service Management Conference. Service Management Conference Workshops will take place on Tuesday 16 August 2016 in Brisbane.
Service Integration and Management (SIAM), like ITIL® before it, appears to have originated from HM Government (UK). References to SIAM began to emerge in the UK in the late 2000s, when it was purported to provide a framework to obtain better value for money from multi supplier service engagements. Lately its adoption has increased globally due to the increasingly complex, modular managed IT service environment evident in most enterprises.
There is much confusion about whether SIAM is actually something new (i.e. different from ITIL), whether it will last, or even whether it is something relevant.
Our half-day pre-conference workshop for Service Management 2016’s Shake I.T. Up Conference will allow delegates to consider the various perspectives and stakeholders in a SIAM environment. Based on current thinking, global developments and using practical scenarios, it provides the participants with an analysis of the core principles, processes, functions, governance and cultural re-engineering required for SIAM success.
In multi-sourced service delivery models, the key to success is the ability to manage the challenge of cross-functional, cross-process, cross-provider integration. SIAM enables an organisation to derive the benefits of innovation and flexibility that multi-sourcing brings whilst still presenting an integrated service wrap for the customer. SIAM is both framework and a function. Typically built upon the full ITIL lifecycle model, SIAM includes additional focus on ‘end to end’ service governance and controls across all suppliers.
The rationale for SIAM is insurance that the IT and business strategies align with the challenges in multi-provider environments. Integral to this is the three layers of Customer-Retained governance, SIAM Control & Management, and Service Delivery (or variants like Strategic-Tactical-Operational, Defining-Designing-Delivering, Governance-Control-Monitoring etc).
Organisations trying to implement SIAM need to understand the distinction between integrated service management and SIAM. For example, implementing a set of processes within a centralised management will not create a SIAM function. Failing to add the extra elements of SIAM such as governance, autonomy and the impartiality to manage the providers creates SIAM functions that rarely move beyond operational delivery.
For more information, you may want to read: