Levers enabling industrialised deployment and a effective multi-vendor eco-system We wish to assess the current position of these levers and the opportunity to set these to the right increases ability to reduce costs and accelerate global deployments using Industrialised methods Lever Flexible requirements, phased Implementation + <--- Cost ------ - Template driven, Industrialised Roll out Solution Repeatability Allow each country its own solution, low standardisation Template compliance, common processes, TLS* change only Solution Stability Continuous changes and high regression impacts Very limited changes to the template during roll out Deployment model Local release & deployment teams, minimal central capacity Centralised, offshore release and deployment, local task execution Testing & Validation Retest large portions of solution, low risk approach Only test changes, risk based and time boxed Change Management Individual country change approach, high soft skills Centrally driven focus on readiness, “mandated” adoption Deliverable variations Individual per country, multiple variations, many languages Re-use each deliverable, no changes to foundation outputs Integration Approach Variable integration methods, point to point, each unit varies Single EA integration layer, standard messages, high re-use +Speed + Cost * TLS – Tax, Legal, Statutory
The ability to reduce costs is how we deploy the global delivery model with the right roll out strategy Standardisation and the number of countries in a wave reduces the overall cost but traditional “Big Bang” multi-country Go Live increases the risk Low cost per Unit Global Template, Multi-site phased roll out, “big bang” Go Live 2 Multi-site wave, Individual business Roll in every 2 – 3 months (Perpetual Deployment Model) 3 Ability to standardise Incremental design by wave during roll out, single site per wave 1 This leads us un to the fundamental 2 drivers impact overall costs ; Standardisation and ability to industrialise Ability to reduce timescales through multi site implementations These can be address using different methods with varying impacts Option – 1 where there is no clear roll out plan, no real gains across geographies or inability to manage local alignment Option 2 – the traditional methods – longer phases, big bangs, limited by business risk and effort to scale for cut-over Option 3 – unique approach to multi site, with longer lead times to address variations but reduced risk through individual roll in Our approach enables multi site roll outs with balance of lowest over all cost vs risk Higher cost per unit Geo and Business Unit scope Utilising HCL’s option 3 can actually reduce the risks given individual roll ins
Our typical Global Delivery Model Core Team and Release Management Programme management Cross vendor and wave PMO Central Deployment co-ordination Solution Design Authority Solution Governance Core Team Central Offshore CoE Delivery Local build extensions Independent Testing Data Migration factory Development factory Training Materials Security extensions Environment Management Core Process CoE Team Solution Confirmation for Countries (localisation) Extension designs Monitor Global Acceptance End user readiness Global Design Authority Process CoE Implement. team DSI Wave Deploy Team a c b Near shore Basis Data Near Shore CoE Team Data, testing, dev support EE Team GFS Offshore COE b Testing DSI Wave Deploy Team Number of challenges to manage in a global roll out : Cost – ability to increase offshore leverage Geographic diversity BU leadership and pull Template alignment – balancing central vs local Our delivery model looks to manage this through 3 components Central Programme, GDA and deployment co-ord Local BU led deployment activity Offshore service provision with nearshore We are uniquely placed to have best of breed on shore and offshore woth Sfiteck as a partner in Latam to address scale and cultural dimensions Discuss key points c Dev & Build AMS Deployment Wave hub Local business requirements & process owners Co-ordinate local deployment activities Business readiness, data and floor-walking a DSI Wave Deploy Team Early Engagement Mobilisation activities Template Action Plan Set up local team
A number of key tools will support the ability to manage unique requirements into a global template Corporate wide BPML and tool to enable planning and reduce volumes of changes Benefits cards implemented for managing requests with conditions agreed e.g. $$$ written into budgets if approved * - Business Process Master List Full Template review and define contingency pots based on process scope and clarity Localisation process that deals with extensions to Local Configuration baseline and prevents clogging the system * - Chart of Accounts