Country Readiness Tool-kit

874 views

Published on

Published in: Business, Technology

Country Readiness Tool-kit

  1. 1. High Performance. Guaranteed.<br />Totalamber ERP Rollout Methodology<br />& Country Readiness Toolkit<br />
  2. 2. Totalamber ERP Rollout Methodology<br />1<br />Global Blueprint (Common Solution)<br />Business Process<br />Reports<br />Data<br />Configuration<br />Change & Training<br />Data Migration<br />Integration<br />Rollout Planning<br />DATA FACTORY<br />TRAINING FACTORY<br />SUPPORT FACTORY<br />Country Build<br />Country Build<br />Country Build<br />Country Build<br />Rollout Toolkits & Factories<br />Support ><br />Deploy ><br />Test ><br />Build ><br />Design ><br />Mobilise ><br />Country Rollout Preparation<br />2<br />Country A: Countdown <br />3<br />Implement A<br />4<br />Country B: Countdown <br />5<br />Implement B<br />11<br />13<br />14<br />15<br />17<br />18<br />19<br />20<br />12<br />16<br />21<br />10<br />6<br />Country C: Countdown <br />Implement C<br />7<br />8<br />Country D: Countdown <br />Implement D<br />9<br />
  3. 3. Totalamber ERP Rollout Methodology – 1: Global Blueprint (Common Solution)<br />1<br />Global Blueprint (Common Solution)<br />Support ><br />Deploy ><br />Test ><br />Build ><br />Design ><br />Mobilise ><br />Country Rollout Preparation<br />2<br />18<br />19<br />Business Process<br />Country Build<br />Country A: Countdown <br />Definition<br />Common solution developed by the global team for rollout purposes<br />20<br />3<br />Implement A<br />Reports<br />21<br />13<br />4<br />Data<br />DATA FACTORY<br />Country Build<br />Country B: Countdown <br />Key Outputs<br />Common solution consisting of: 1) Processes; 2) Reports; 3) Interfaces ; 4) Enhancements; 5) Data Conversion; 6) External Documents (e.g. Invoice); 7) Screens & Forms<br />14<br />5<br />Implement B<br />11<br />12<br />16<br />21<br />Configuration<br />TRAINING FACTORY<br />6<br />15<br />Country Build<br />Country C: Countdown <br />Change & Training<br />SUPPORT FACTORY<br />Main Benefits<br /><ul><li>Enforces common approach and ways of workings
  4. 4. Speed up rollout – reducing time to market and costs
  5. 5. Enable smooth integration of new acquisitions</li></ul>Implement C<br />7<br />Data Migration<br />8<br />Country Build<br />Country D: Countdown <br />Integration<br />Implement D<br />9<br />Rollout Planning<br />Working Assumptions<br /><ul><li>Truly representative team from countries and processes
  6. 6. Global view of processes – standardisation
  7. 7. Country sign off to blueprint </li></ul>10<br />Rollout Toolkits & Factories<br />Examples of Tools Utilised<br /><ul><li>Process Mapping Tool
  8. 8. Functional & Technical Specifications
  9. 9. Data Mapping
  10. 10. LiSA & SNA – (ERP support strategy)
  11. 11. Rollout strategy</li></ul>Usual Skills Required<br /><ul><li>Business Analysis
  12. 12. ERP Functionality Mapping
  13. 13. Development Specifications
  14. 14. Business facilitation and engagement</li></ul>Key Risks<br />Key business resources not engaged effectively in the blueprint build and testing<br />
  15. 15. Totalamber ERP Rollout Methodology – 2. Business Process<br />1<br />Global Blueprint (Common Solution)<br />Support ><br />Deploy ><br />Test ><br />Build ><br />Design ><br />Mobilise ><br />Country Rollout Preparation<br />2<br />18<br />19<br />Business Process<br />Country Build<br />Country A: Countdown <br />Definition<br />Global common processes supported by the ERP tool<br />20<br />3<br />Implement A<br />Reports<br />21<br />13<br />4<br />Data<br />DATA FACTORY<br />Country Build<br />Country B: Countdown <br />Outputs<br />Process Strategy Document (PSD)<br />Process Definition Document (PDD)<br />14<br />5<br />Implement B<br />11<br />12<br />16<br />21<br />Configuration<br />TRAINING FACTORY<br />6<br />15<br />Country Build<br />Country C: Countdown <br />Change & Training<br />SUPPORT FACTORY<br />Benefits<br /><ul><li>Clarity on who does what within a process (RACI)
  16. 16. Highlights touch points with other processes and stakeholders</li></ul>Implement C<br />7<br />Data Migration<br />8<br />Country Build<br />Country D: Countdown <br />Integration<br />Implement D<br />9<br />Rollout Planning<br />Working Assumptions<br /><ul><li>ERP processes would be used as straw man to minimise the risk of customisation
  17. 17. One PDD will be developed per process / sub-process</li></ul>10<br />Rollout Toolkits & Factories<br />Tools Utilised<br /><ul><li>Process Definition Template
  18. 18. Process Maps (VISIO)
  19. 19. RACI Matrix</li></ul>Skills Required<br /><ul><li>Business Process Mapping
  20. 20. ERP Module (e.g. Supply Chain Process)
  21. 21. Business Workshop Facilitation</li></ul>Risk Mitigation<br />Process describes the “As-Is” instead of thinking about the “To-Be”<br />
  22. 22. Totalamber ERP Rollout Methodology – 3. Reports<br />1<br />Global Blueprint (Common Solution)<br />Support ><br />Deploy ><br />Test ><br />Build ><br />Design ><br />Mobilise ><br />Country Rollout Preparation<br />2<br />18<br />19<br />Business Process<br />Country Build<br />Country A: Countdown <br />Definition<br />Globally agreed management and end user reports required from the ERP tool<br />20<br />3<br />Implement A<br />Reports<br />21<br />13<br />4<br />Data<br />DATA FACTORY<br />Country Build<br />Country B: Countdown <br />Outputs<br />Reporting Strategy Document (RSD)<br />Report Definition Document (RDD)<br />14<br />5<br />Implement B<br />11<br />12<br />16<br />21<br />Configuration<br />TRAINING FACTORY<br />6<br />15<br />Country Build<br />Country C: Countdown <br />Change & Training<br />SUPPORT FACTORY<br />Benefits<br /><ul><li>Lists the key reports needed by the business
  23. 23. Determines the scale and effort needed to develop the reports</li></ul>Implement C<br />7<br />Data Migration<br />8<br />Country Build<br />Country D: Countdown <br />Integration<br />Implement D<br />9<br />Rollout Planning<br />Working Assumptions<br /><ul><li>Reports identified as part of the process definition – i.e. what is needed to measure and manage the process effectively at all levels
  24. 24. RDD will be signed off per report and before build</li></ul>10<br />Rollout Toolkits & Factories<br />Tools Utilised<br /><ul><li>Report Definition Template</li></ul>Skills Required<br /><ul><li>Business analysis(KPIs)
  25. 25. ERP Reports (Standard & Available Reports)
  26. 26. Business Facilitation (needs assessment)</li></ul>Risk Mitigation<br />Duplicate the 100’s of existing reports without considering the right-size need<br />
  27. 27. Totalamber ERP Rollout Methodology – 4. Data<br />1<br />Global Blueprint (Common Solution)<br />Support ><br />Deploy ><br />Test ><br />Build ><br />Design ><br />Mobilise ><br />Country Rollout Preparation<br />2<br />18<br />19<br />Business Process<br />Country Build<br />Country A: Countdown <br />Definition<br />Global data strategy and conversion for ERP implementation and rollout – from mapping to conversion and maintenance<br />20<br />3<br />Implement A<br />Reports<br />21<br />13<br />4<br />Data<br />DATA FACTORY<br />Country Build<br />Country B: Countdown <br />Outputs<br />Data Strategy Document (DSD)<br />Data Conversion Document (DCD)<br />14<br />5<br />Implement B<br />11<br />12<br />16<br />21<br />Configuration<br />TRAINING FACTORY<br />6<br />15<br />Country Build<br />Country C: Countdown <br />Change & Training<br />SUPPORT FACTORY<br />Benefits<br /><ul><li>Cleansed Data
  28. 28. Standardised data maps
  29. 29. Improved data governance
  30. 30. Improve consolidation and reports</li></ul>Implement C<br />7<br />Data Migration<br />8<br />Country Build<br />Country D: Countdown <br />Integration<br />Implement D<br />9<br />Rollout Planning<br />Working Assumptions<br /><ul><li>A data strategy developed as part of the project to give guidance to all streams
  31. 31. A number of DCD would be developed and signed off per business process </li></ul>10<br />Rollout Toolkits & Factories<br />Tools Utilised<br /><ul><li>Data Strategy
  32. 32. DCD Template</li></ul>Skills Required<br /><ul><li>Data Analyst
  33. 33. ERP Data Mapping</li></ul>Risk Mitigation<br />DCD developed to reflect current practices instead of new ones<br />
  34. 34. Totalamber ERP Rollout Methodology – 5. Configuration<br />1<br />Global Blueprint (Common Solution)<br />Support ><br />Deploy ><br />Test ><br />Build ><br />Design ><br />Mobilise ><br />Country Rollout Preparation<br />2<br />18<br />19<br />Business Process<br />Country Build<br />Country A: Countdown <br />Definition<br />Global ERP settings and core data to drive the common processes defined<br />20<br />3<br />Implement A<br />Reports<br />21<br />13<br />4<br />Data<br />DATA FACTORY<br />Country Build<br />Country B: Countdown <br />Outputs<br />Base data – e.g. flags / business rules<br />Master data – e.g. customer files<br />Configuration cookbook<br />14<br />5<br />Implement B<br />11<br />12<br />16<br />17<br />Configuration<br />TRAINING FACTORY<br />6<br />15<br />Country Build<br />Country C: Countdown <br />Change & Training<br />SUPPORT FACTORY<br />Benefits<br /><ul><li>Show business how the processes described in the PDD would look using the ERP system</li></ul>Implement C<br />7<br />Data Migration<br />8<br />Country Build<br />Country D: Countdown <br />Integration<br />Implement D<br />9<br />Rollout Planning<br />Working Assumptions<br /><ul><li>Business process owners would work with ERP process specialist to agree the base and master data to support a particular process
  35. 35. The configuration would be managed through change control and refreshes</li></ul>10<br />Rollout Toolkits & Factories<br />Tools Utilised<br /><ul><li>Configuration Cookbook</li></ul>Skills Required<br /><ul><li>ERP Configuration</li></ul>Risk Mitigation<br />Configuration decision not documented which makes it difficult to support<br />
  36. 36. Totalamber ERP Rollout Methodology – 6. Change & Training<br />1<br />Global Blueprint (Common Solution)<br />Support ><br />Deploy ><br />Test ><br />Build ><br />Design ><br />Mobilise ><br />Country Rollout Preparation<br />2<br />18<br />19<br />Business Process<br />Country Build<br />Country A: Countdown <br />Definition<br />Strategies to secure business engagement, buy-in as well as providing effective end user training on the ERP tool<br />20<br />3<br />Implement A<br />Reports<br />21<br />13<br />4<br />Data<br />DATA FACTORY<br />Country Build<br />Country B: Countdown <br />Outputs<br />Change Management Strategy Document (CMSD)<br />Communications Strategy Document (CSD)<br />Training Strategy Document (TSD)<br />Training Material<br />Training Environments - server and data<br />14<br />5<br />Implement B<br />11<br />12<br />16<br />17<br />Configuration<br />TRAINING FACTORY<br />6<br />15<br />Country Build<br />Country C: Countdown <br />Change & Training<br />SUPPORT FACTORY<br />Benefits<br /><ul><li>Secure business buy-in to blueprint
  37. 37. Enhance communications with stakeholders
  38. 38. Training programme designed to minimise disruptions </li></ul>Implement C<br />7<br />Data Migration<br />8<br />Country Build<br />Country D: Countdown <br />Integration<br />Implement D<br />9<br />Rollout Planning<br />Working Assumptions<br /><ul><li>An integrated approach taken to link up change, communication and training </li></ul>10<br />Rollout Toolkits & Factories<br />Tools Utilised<br /><ul><li>Training Manual Template
  39. 39. On-line Tool</li></ul>Skills Required<br /><ul><li>Change Management
  40. 40. Stakeholder Engagement & Communications
  41. 41. ERP Training</li></ul>Risk Mitigation<br />Key changes in the as-is processes not explained effectively to the users <br />
  42. 42. Totalamber ERP Rollout Methodology – 7. Data Migration<br />1<br />Global Blueprint (Common Solution)<br />Support ><br />Deploy ><br />Test ><br />Build ><br />Design ><br />Mobilise ><br />Country Rollout Preparation<br />2<br />18<br />19<br />Business Process<br />Country Build<br />Country A: Countdown <br />Definition<br />Common data migration from legacy to the new ERP tool<br />20<br />3<br />Implement A<br />Reports<br />21<br />13<br />4<br />Data<br />DATA FACTORY<br />Country Build<br />Country B: Countdown <br />Outputs<br />Data Migration Strategy Document (DMSD)<br />Data Migration Test Scenarios (DMTS)<br />14<br />5<br />Implement B<br />11<br />12<br />16<br />21<br />Configuration<br />TRAINING FACTORY<br />6<br />15<br />Country Build<br />Country C: Countdown <br />Change & Training<br />SUPPORT FACTORY<br />Benefits<br /><ul><li>Clarity on what needs to be transferred from legacy to new ERP
  43. 43. Assist in determining cutover window when going live</li></ul>Implement C<br />7<br />Data Migration<br />8<br />Country Build<br />Country D: Countdown <br />Integration<br />Implement D<br />9<br />Rollout Planning<br />Working Assumptions<br /><ul><li>A number of data migration cycles
  44. 44. Data set will be used to test the migration process, timing and accuracy</li></ul>10<br />Rollout Toolkits & Factories<br />Tools Utilised<br /><ul><li>Data migration tools</li></ul>Skills Required<br /><ul><li>Data migration </li></ul>Risk Mitigation<br />Data set used in the migration testing does not reflect production environment – making timing estimates for go live inaccurate<br />
  45. 45. Totalamber ERP Rollout Methodology – 8. Integration<br />1<br />Global Blueprint (Common Solution)<br />Support ><br />Deploy ><br />Test ><br />Build ><br />Design ><br />Mobilise ><br />Country Rollout Preparation<br />2<br />18<br />19<br />Business Process<br />Country Build<br />Country A: Countdown <br />Definition<br />Common global interfaces and imports/exports between the ERP tool and legacy systems and spread sheets<br />20<br />3<br />Implement A<br />Reports<br />21<br />13<br />4<br />Data<br />DATA FACTORY<br />Country Build<br />Country B: Countdown <br />Outputs<br />Integration Strategy Document (ISD)<br />Interface Definition Document (IDD)<br />14<br />5<br />Implement B<br />11<br />12<br />16<br />17<br />Configuration<br />TRAINING FACTORY<br />6<br />15<br />Country Build<br />Country C: Countdown <br />Change & Training<br />SUPPORT FACTORY<br />Benefits<br /><ul><li>Common global interfaces developed (e.g. Intra company transfer) speeding up rollout and reducing costs </li></ul>Implement C<br />7<br />Data Migration<br />8<br />Country Build<br />Country D: Countdown <br />Integration<br />Implement D<br />9<br />Rollout Planning<br />Working Assumptions<br /><ul><li>Integration based on to-be processes
  46. 46. Non Core Applications (NCA) identified globally </li></ul>10<br />Rollout Toolkits & Factories<br />Tools Utilised<br /><ul><li>Software landscape (AS-IS) Map / List
  47. 47. Software Survey
  48. 48. Middleware (e.g. BizTalk) </li></ul>Skills Required<br /><ul><li>Integration Strategy
  49. 49. Interface Development </li></ul>Risk Mitigation<br />Blueprint duplicate current imports and exports instead of rationalising them<br />Too many point to point integrations<br />
  50. 50. Totalamber ERP Rollout Methodology – 9. Rollout Planning <br />1<br />Global Blueprint (Common Solution)<br />Support ><br />Deploy ><br />Test ><br />Build ><br />Design ><br />Mobilise ><br />Country Rollout Preparation<br />2<br />18<br />19<br />Business Process<br />Country Build<br />Country A: Countdown <br />Definition<br />Global rollout plan, tools and resources to deliver the blueprint <br />20<br />3<br />Implement A<br />Reports<br />21<br />13<br />4<br />Data<br />DATA FACTORY<br />Country Build<br />Country B: Countdown <br />Outputs<br />Rollout Strategy Document (RSD)<br />Rollout Resources Chart<br />Rollout Command & Control<br />14<br />5<br />Implement B<br />11<br />12<br />16<br />21<br />Configuration<br />TRAINING FACTORY<br />6<br />15<br />Country Build<br />Country C: Countdown <br />Change & Training<br />SUPPORT FACTORY<br />Benefits<br /><ul><li>Visibility on country engagement and sequencing
  51. 51. Standard tools and techniques to speedup rollout cost effectively</li></ul>Implement C<br />7<br />Data Migration<br />8<br />Country Build<br />Country D: Countdown <br />Integration<br />Implement D<br />9<br />Rollout Planning<br />Working Assumptions<br /><ul><li>Rollout stream would be established and mobilised from the outset of the blueprint phase</li></ul>10<br />Rollout Toolkits & Factories<br />Tools Utilised<br /><ul><li>Training Deployment Toolkit
  52. 52. Change Management Toolkit
  53. 53. Cutover Toolkit
  54. 54. Support Toolkit</li></ul>Skills Required<br /><ul><li>Rollout Project Management
  55. 55. Toolkits Development</li></ul>Risk Mitigation<br />Rollout strategy, planning and toolkits considered late in the blueprint phase (just before rollout)<br />
  56. 56. Totalamber ERP Rollout Methodology – 10. Rollout Toolkits & Factories<br />1<br />Global Blueprint (Common Solution)<br />Support ><br />Deploy ><br />Test ><br />Build ><br />Design ><br />Mobilise ><br />Country Rollout Preparation<br />2<br />18<br />19<br />Business Process<br />Country Build<br />Country A: Countdown <br />Definition<br />Globally built and tested rollout checklists, templates and material to speed up the country implementation<br />20<br />3<br />Implement A<br />Reports<br />21<br />13<br />4<br />Data<br />DATA FACTORY<br />Country Build<br />Country B: Countdown <br />Outputs<br />Data checklists<br />Training checklists<br />Support checklists<br />Change Management Checklists<br />14<br />5<br />Implement B<br />11<br />12<br />16<br />21<br />Configuration<br />TRAINING FACTORY<br />6<br />15<br />Country Build<br />Country C: Countdown <br />Change & Training<br />SUPPORT FACTORY<br />Benefits<br /><ul><li>Speed up rollout process using common processes
  57. 57. Reduce rollout costs</li></ul>Implement C<br />7<br />Data Migration<br />8<br />Country Build<br />Country D: Countdown <br />Integration<br />Implement D<br />9<br />Rollout Planning<br />Working Assumptions<br /><ul><li>Rollout tools and techniques tested as part of the blueprint
  58. 58. Rollout work stream established to work with the other blueprint streams in developing rollout checklists and material </li></ul>10<br />Rollout Toolkits & Factories<br />Tools Utilised<br /><ul><li>Checklist templates</li></ul>Skills Required<br />Training / Data / Change Management / Support<br />Risk Mitigation<br />Insufficient time allowed to test the rollout toolkits during the blueprint<br />
  59. 59. Totalamber ERP Rollout Methodology – 11. Blueprint Signoff<br />1<br />Global Blueprint (Common Solution)<br />Support ><br />Deploy ><br />Test ><br />Build ><br />Design ><br />Mobilise ><br />Country Rollout Preparation<br />2<br />18<br />19<br />Business Process<br />Country Build<br />Country A: Countdown <br />Definition<br />Business acceptance of the blueprint and its outputs across the streams<br />20<br />3<br />Implement A<br />Reports<br />21<br />13<br />4<br />Data<br />DATA FACTORY<br />Country Build<br />Country B: Countdown <br />Outputs<br />Test Sign off<br />14<br />5<br />Implement B<br />11<br />12<br />16<br />21<br />Configuration<br />TRAINING FACTORY<br />6<br />15<br />Country Build<br />Country C: Countdown <br />Change & Training<br />SUPPORT FACTORY<br />Benefits<br /><ul><li>Business approval for blueprint prior to commencing rollout </li></ul>Implement C<br />7<br />Data Migration<br />8<br />Country Build<br />Country D: Countdown <br />Integration<br />Implement D<br />9<br />Rollout Planning<br />Working Assumptions<br /><ul><li>Rollout criteria agreed as part of the test strategy
  60. 60. Business provides resources to validate checklists and outputs</li></ul>10<br />Rollout Toolkits & Factories<br />Tools Utilised<br /><ul><li>Test Script Template</li></ul>Skills Required<br /><ul><li>Testing</li></ul>Risk Mitigation<br />Rollout commence without clear sign off<br />
  61. 61. Totalamber ERP Rollout Methodology – 12. Blueprint Gateway . . . ‘Go’ / ‘No Go’ Junction<br />1<br />Global Blueprint (Common Solution)<br />Support ><br />Deploy ><br />Test ><br />Build ><br />Design ><br />Mobilise ><br />Country Rollout Preparation<br />2<br />18<br />19<br />Business Process<br />Country Build<br />Country A: Countdown <br />Definition<br />Determine the readiness of the blueprint for rollout. Business managers considering outstanding issues / bugs at this stage of project<br />20<br />3<br />Implement A<br />Reports<br />21<br />13<br />4<br />Data<br />DATA FACTORY<br />Country Build<br />Country B: Countdown <br />Outputs<br />Decision to commence / delay rollout<br />14<br />5<br />Implement B<br />11<br />12<br />16<br />21<br />Configuration<br />TRAINING FACTORY<br />6<br />15<br />Country Build<br />Country C: Countdown <br />Change & Training<br />SUPPORT FACTORY<br />Benefits<br /><ul><li>Getting business engagement and ownership for the rollout decision and implications</li></ul>Implement C<br />7<br />Data Migration<br />8<br />Country Build<br />Country D: Countdown <br />Integration<br />Implement D<br />9<br />Rollout Planning<br />Working Assumptions<br /><ul><li>Steering committee would play a significant and proactive part in assessing blueprint completion and rollout readiness </li></ul>10<br />Rollout Toolkits & Factories<br />Tools Utilised<br /><ul><li>Go / No Go Checklist</li></ul>Skills Required<br /><ul><li>Steering </li></ul>Risk Mitigation<br />Steering committee not engaged from the outset – hence difficulty in getting decision quickly and effectively<br />
  62. 62. Totalamber ERP Rollout Methodology – 13. Data Factory<br />1<br />Global Blueprint (Common Solution)<br />Support ><br />Deploy ><br />Test ><br />Build ><br />Design ><br />Mobilise ><br />Country Rollout Preparation<br />2<br />18<br />19<br />Business Process<br />Country Build<br />Country A: Countdown <br />Definition<br />Global data centre to prepare country data for migration <br />20<br />3<br />Implement A<br />Reports<br />21<br />13<br />4<br />Data<br />DATA FACTORY<br />Country Build<br />Country B: Countdown <br />Outputs<br />Production (mapped & cleansed) Data Sets.<br />Data sets for environments (training, testing & sandpit)<br />14<br />5<br />Implement B<br />11<br />12<br />16<br />21<br />Configuration<br />TRAINING FACTORY<br />6<br />15<br />Country Build<br />Country C: Countdown <br />Change & Training<br />SUPPORT FACTORY<br />Benefits<br /><ul><li>Consistent and controlled way of getting country data mapped and migrated quickly and cost effectively</li></ul>Implement C<br />7<br />Data Migration<br />8<br />Country Build<br />Country D: Countdown <br />Integration<br />Implement D<br />9<br />Rollout Planning<br />Working Assumptions<br /><ul><li>Data centre with sufficient resources and skills put together to support global rollout from a centralised location</li></ul>10<br />Rollout Toolkits & Factories<br />Tools Utilised<br /><ul><li>Data Loading, Manipulation and migration</li></ul>Skills Required<br /><ul><li>Business Data Analysts
  63. 63. ERP Data Migration Tool
  64. 64. DBA</li></ul>Risk Mitigation<br />Insufficient resources to carry out activities.<br />Country data owners not identified or engaged<br />
  65. 65. Totalamber ERP Rollout Methodology – 14. Training Factory<br />1<br />Global Blueprint (Common Solution)<br />Support ><br />Deploy ><br />Test ><br />Build ><br />Design ><br />Mobilise ><br />Country Rollout Preparation<br />2<br />18<br />19<br />Business Process<br />Country Build<br />Country A: Countdown <br />Definition<br />Global centre to develop, translate and deliver training best practice and outputs<br />20<br />3<br />Implement A<br />Reports<br />21<br />13<br />4<br />Data<br />DATA FACTORY<br />Country Build<br />Country B: Countdown <br />Outputs<br />Training Guides<br />Tutor Training Material<br />Training Data<br />14<br />5<br />Implement B<br />11<br />12<br />16<br />21<br />Configuration<br />TRAINING FACTORY<br />6<br />15<br />Country Build<br />Country C: Countdown <br />Change & Training<br />SUPPORT FACTORY<br />Benefits<br /><ul><li>“Develop once, rollout many times” training approach – resulting in saving in time and costs
  66. 66. Enforces the global view of business processes</li></ul>Implement C<br />7<br />Data Migration<br />8<br />Country Build<br />Country D: Countdown <br />Integration<br />Implement D<br />9<br />Rollout Planning<br />Working Assumptions<br /><ul><li>Training centre of excellence developed as an integral part of the blueprint
  67. 67. Training outputs would be flexible to reflect country changes</li></ul>10<br />Rollout Toolkits & Factories<br />Tools Utilised<br /><ul><li>Training Templates</li></ul>Skills Required<br /><ul><li>Training Preparations and Delivery</li></ul>Risk Mitigation<br />Too generic and high level training material and checklists<br />
  68. 68. Totalamber ERP Rollout Methodology – 15. Support Factory<br />1<br />Global Blueprint (Common Solution)<br />Support ><br />Deploy ><br />Test ><br />Build ><br />Design ><br />Mobilise ><br />Country Rollout Preparation<br />2<br />18<br />19<br />Business Process<br />Country Build<br />Country A: Countdown <br />Definition<br />ERP support centre which provides the IT and business organisations with the required processes, skills and checklists during the rollout<br />20<br />3<br />Implement A<br />Reports<br />21<br />13<br />4<br />Data<br />DATA FACTORY<br />Country Build<br />Country B: Countdown <br />Outputs<br />Support Policies & Procedures<br />Support Guidebook<br />14<br />5<br />Implement B<br />11<br />12<br />16<br />21<br />Configuration<br />TRAINING FACTORY<br />6<br />15<br />Country Build<br />Country C: Countdown <br />Change & Training<br />SUPPORT FACTORY<br />Benefits<br /><ul><li>Switch the business as-usual support quickly and consistently
  69. 69. Manage the transition from legacy support to the new ERP support </li></ul>Implement C<br />7<br />Data Migration<br />8<br />Country Build<br />Country D: Countdown <br />Integration<br />Implement D<br />9<br />Rollout Planning<br />Working Assumptions<br /><ul><li>Support stream engaged in every stage of the blueprint
  70. 70. Knowledge transfer conducted proactively and formally between project and support
  71. 71. New ERP support organisation in place by this stage of the project</li></ul>10<br />Rollout Toolkits & Factories<br />Tools Utilised<br /><ul><li>Support Templates</li></ul>Skills Required<br /><ul><li>Support Management
  72. 72. Helpdesk Handling</li></ul>Risk Mitigation<br />Support staff not recruited or trained early to ensure readiness for rollout<br />IT helpdesk capacity limited to match rollout demands<br />
  73. 73. Totalamber ERP Rollout Methodology – 16. Country Rollout Preparation <br />1<br />Global Blueprint (Common Solution)<br />Support ><br />Deploy ><br />Test ><br />Build ><br />Design ><br />Mobilise ><br /> Rollout Programme<br />2<br />18<br />19<br />Business Process<br />Country Build<br />Country A: Countdown <br />Definition<br />Taking the global blueprint to the countries<br />20<br />3<br />Implement A<br />Reports<br />17<br />13<br />4<br />Data<br />DATA FACTORY<br />Country Build<br />Country B: Countdown <br />Outputs<br />Implementation of global blueprint within each country<br />14<br />5<br />Implement B<br />11<br />12<br />16<br />17<br />Configuration<br />TRAINING FACTORY<br />6<br />15<br />Country Build<br />Country C: Countdown <br />Change & Training<br />SUPPORT FACTORY<br />Benefits<br /><ul><li> Support standardisation
  74. 74. Speed up ERP implementation
  75. 75. Reduce costs of project</li></ul>Implement C<br />7<br />Data Migration<br />8<br />Country Build<br />Country D: Countdown <br />Integration<br />Implement D<br />9<br />Rollout Planning<br />Working Assumptions<br /><ul><li>Rollout programme will be reviewed on regular basis to make sure country sequencing and assumptions are valid</li></ul>10<br />Rollout Toolkits & Factories<br />Tools Utilised<br /><ul><li>Rollout Programme Template</li></ul>Skills Required<br /><ul><li>Rollout Management</li></ul>Risk Mitigation<br />Rollout vision, approach and plans have not been considered during the project definition resulting in limited budget and resources<br />
  76. 76. Totalamber ERP Rollout Methodology – 17. Country Engagement<br />1<br />Global Blueprint (Common Solution)<br />Support ><br />Deploy ><br />Test ><br />Build ><br />Design ><br />Mobilise ><br />Country Rollout Preparation<br />2<br />18<br />19<br />Business Process<br />Country Build<br />Country A: Countdown <br />Definition<br />Mobilise the country management using the factory outputs<br />20<br />3<br />Implement A<br />Reports<br />17<br />13<br />4<br />Data<br />DATA FACTORY<br />Country Build<br />Country B: Countdown <br />Outputs<br />Country Mobilisation Charter<br />14<br />5<br />Implement B<br />11<br />12<br />16<br />21<br />Configuration<br />TRAINING FACTORY<br />6<br />15<br />Country Build<br />Country C: Countdown <br />Change & Training<br />SUPPORT FACTORY<br />Benefits<br /><ul><li>Clarity on country engagement
  77. 77. Management Ownership</li></ul>Implement C<br />7<br />Data Migration<br />8<br />Country Build<br />Country D: Countdown <br />Integration<br />Implement D<br />9<br />Rollout Planning<br />Working Assumptions<br /><ul><li>Country management on board with blueprint and the factory outputs</li></ul>10<br />Rollout Toolkits & Factories<br />Tools Utilised<br /><ul><li>Country Implementation Charter</li></ul>Skills Required<br /><ul><li>Project Management</li></ul>Risk Mitigation<br />Country not providing the right level of management resources to engage effectively during the mobilisation and planning<br />
  78. 78. Totalamber ERP Rollout Methodology – 18. Country A: Countdown<br />1<br />Global Blueprint (Common Solution)<br />Support ><br />Deploy ><br />Test ><br />Build ><br />Design ><br />Mobilise ><br />Rollout Programme<br />2<br />18<br />19<br />Business Process<br />Country Build<br />Country A: Countdown <br />Definition<br />Country preparing for rollout <br />20<br />3<br />Implement A<br />Reports<br />17<br />13<br />4<br />Data<br />DATA FACTORY<br />Country Build<br />Country B: Countdown <br />Outputs<br />Mobilised country team<br />14<br />5<br />Implement B<br />11<br />12<br />16<br />17<br />Configuration<br />TRAINING FACTORY<br />6<br />15<br />Country Build<br />Country C: Countdown <br />Change & Training<br />SUPPORT FACTORY<br />Benefits<br /><ul><li>Giving the business sufficient time to prepare for the rollout
  79. 79. Country team mobilised effectively</li></ul>Implement C<br />7<br />Data Migration<br />8<br />Country Build<br />Country D: Countdown <br />Integration<br />Implement D<br />9<br />Rollout Planning<br />Working Assumptions<br /><ul><li>Business given sufficient time to prepare for training, support and data
  80. 80. Week by week checks to make sure business fulfils its project obligations</li></ul>10<br />Rollout Toolkits & Factories<br />Tools Utilised<br /><ul><li>Countdown checklist</li></ul>Skills Required<br /><ul><li>Project Management – Country Implementation</li></ul>Risk Mitigation<br />Part time project management allocated to drive the project<br />Business provide insufficient resources<br />
  81. 81. Totalamber ERP Rollout Methodology – 19. Country Build<br />1<br />Global Blueprint (Common Solution)<br />Support ><br />Deploy ><br />Test ><br />Build ><br />Design ><br />Mobilise ><br />Country Rollout Preparation<br />2<br />18<br />19<br />Business Process<br />Country Build<br />Country A: Countdown <br />Definition<br />Demonstrate the blueprint to the country key users and build localisation <br />20<br />3<br />Implement A<br />Reports<br />17<br />13<br />4<br />Data<br />DATA FACTORY<br />Country Build<br />Country B: Countdown <br />Outputs<br />Country specific ERP software <br />14<br />5<br />Implement B<br />11<br />12<br />16<br />17<br />Configuration<br />TRAINING FACTORY<br />6<br />15<br />Country Build<br />Country C: Countdown <br />Change & Training<br />SUPPORT FACTORY<br />Benefits<br /><ul><li> Country system based on global blueprint</li></ul>Implement C<br />7<br />Data Migration<br />8<br />Country Build<br />Country D: Countdown <br />Integration<br />Implement D<br />9<br />Rollout Planning<br />Working Assumptions<br /><ul><li>Global blueprint utilised in setting up country solution</li></ul>10<br />Rollout Toolkits & Factories<br />Tools Utilised<br /><ul><li>Blueprint
  82. 82. Data model</li></ul>Skills Required<br /><ul><li>Configuration
  83. 83. Process mapping
  84. 84. Localisation</li></ul>Risk Mitigation<br />Too many customisations required by the country<br />Country wishes to deviate from the global blueprint – change key processes<br />
  85. 85. Totalamber ERP Rollout Methodology - 20. Implementation A<br />1<br />Global Blueprint (Common Solution)<br />Support ><br />Deploy ><br />Test ><br />Build ><br />Design ><br />Mobilise ><br />Country Rollout Preparation<br />2<br />18<br />19<br />Business Process<br />Country Build<br />Country A: Countdown <br />Definition<br />Go live after training users<br />20<br />3<br />Implement A<br />Reports<br />17<br />13<br />4<br />Data<br />DATA FACTORY<br />Country Build<br />Country B: Countdown <br />Outputs<br />Training of key users<br />Training of end users<br />Data Cutover<br />Handover to support<br />14<br />5<br />Implement B<br />11<br />12<br />16<br />17<br />Configuration<br />TRAINING FACTORY<br />6<br />15<br />Country Build<br />Country C: Countdown <br />Change & Training<br />SUPPORT FACTORY<br />Benefits<br /><ul><li>Country live on new ERP quickly and cost effectively</li></ul>Implement C<br />7<br />Data Migration<br />8<br />Country Build<br />Country D: Countdown <br />Integration<br />Implement D<br />9<br />Rollout Planning<br />Working Assumptions<br /><ul><li>Factory outputs (data, training & support) will be used as the basis for the country implementation </li></ul>10<br />Rollout Toolkits & Factories<br />Tools Utilised<br /><ul><li>Factory outputs</li></ul>Skills Required<br /><ul><li>Training
  86. 86. Data Migration
  87. 87. Support Handover</li></ul>Risk Mitigation<br />Country staff not released for training courses<br />
  88. 88. Totalamber ERP Rollout Methodology – 21. Rollout Feedback<br />1<br />Global Blueprint (Common Solution)<br />Support ><br />Deploy ><br />Test ><br />Build ><br />Design ><br />Mobilise ><br />Country Rollout Preparation<br />2<br />18<br />19<br />Business Process<br />Country Build<br />Country A: Countdown <br />Definition<br />Update the factories with globally related changes resulting from the country implementation<br />20<br />3<br />Implement A<br />Reports<br />17<br />13<br />4<br />Data<br />DATA FACTORY<br />Country Build<br />Country B: Countdown <br />Outputs<br />Changes to factory – e.g. new sub process<br />14<br />5<br />Implement B<br />11<br />12<br />16<br />21<br />Configuration<br />TRAINING FACTORY<br />6<br />15<br />Country Build<br />Country C: Countdown <br />Change & Training<br />SUPPORT FACTORY<br />Benefits<br /><ul><li>Keep the blueprint updated and standardised</li></ul>Implement C<br />7<br />Data Migration<br />8<br />Country Build<br />Country D: Countdown <br />Integration<br />Implement D<br />9<br />Rollout Planning<br />Working Assumptions<br /><ul><li>Change control enforced for any changes impacting the global solution</li></ul>10<br />Rollout Toolkits & Factories<br />Tools Utilised<br /><ul><li>Change Control Policy & Template</li></ul>Skills Required<br /><ul><li>Project Management</li></ul>Risk Mitigation<br />Changes conducted by the implementation team without steering committee approval<br />
  89. 89. Totalamber ERP Rollout Methodology & Country Readiness<br />How would you describe your state of readiness in this area<br />Do you have in-house Tools & Techniques<br />#<br />Country Readiness : Go Live - 12weeks<br />Week <br />- 5<br />Week <br />- 4<br />Week <br />- 3<br />Week <br />- 2<br />Week <br />- 1<br />Week <br />- 12<br />Week<br /> - 11<br />Week<br />- 10<br />Week <br />- 9<br />Week <br />- 8<br />Week <br />- 7<br />Week <br />- 6<br />Go Live?<br />Week <br />+ 1<br />Week <br />+ 2<br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />12.1<br />Have you created a handover strategy plan for the rollout to the country? <br />12.2<br />Have you created a presentation for the country managers to mobilise them for the rollout?<br />12.3<br />Have you created a staff questionnaire to enable you to understand the skills and capabilities of the resources to be used in the country rollout?<br />12.4<br />Have you created an IT questionnaire to enable you to understand the current IT Landscape and requirements of the rollout? <br />12.5<br />Have you created data maps for the rollout?<br />12.6<br />Have you created a data cleansing plan for the rollout?<br />12.7<br />Have you created a plan to review the core solution or blueprint as part of the rollout to the country?<br />24<br />
  90. 90. Totalamber ERP Rollout Methodology & Country Readiness<br />How would you describe your state of readiness in this area<br />Do you have in-house Tools & Techniques<br />#<br />Country Readiness : Go Live - 11weeks<br />Week <br />- 5<br />Week <br />- 4<br />Week <br />- 3<br />Week <br />- 2<br />Week <br />- 1<br />Week <br />- 12<br />Week<br /> - 11<br />Week<br />- 10<br />Week <br />- 9<br />Week <br />- 8<br />Week <br />- 7<br />Week <br />- 6<br />Go Live?<br />Week <br />+ 1<br />Week <br />+ 2<br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />11.1<br />Do you have a project management plan for the country rollout?<br />11.2<br />Have you identified the PM to manage the country rollout?<br />11.3<br />Have you created a workshop framework to evaluate and assess the core solution <br />11.4<br />Have you created a training strategy which identifies supper users, end users and training methodology?<br />11.5<br />Have you created a training plan and checklist for end user training?<br />25<br />
  91. 91. Totalamber ERP Rollout Methodology & Country Readiness<br />How would you describe your state of readiness in this area<br />Do you have in-house Tools & Techniques<br />#<br />Country Readiness : Go Live – 10weeks<br />Week <br />- 5<br />Week <br />- 4<br />Week <br />- 3<br />Week <br />- 2<br />Week <br />- 1<br />Week <br />- 12<br />Week<br /> - 11<br />Week<br />- 10<br />Week <br />- 9<br />Week <br />- 8<br />Week <br />- 7<br />Week <br />- 6<br />Go Live?<br />Week <br />+ 1<br />Week <br />+ 2<br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />10.1<br />Do you have a corporate process for the purchase of H/W and Components for the rollout?<br />10.2<br />Do you have a checklist to enable you to order the right components from the right supplier?<br />10.3<br />Have you created a training curriculum?<br />10.4<br />Have you created a checklist to review training material?<br />10.5<br />Have you created a checklist to enable training rooms and training environment to be prepared?<br />10.6<br />Do you have a methodology or a plan to review the solution and the build for the country?<br />26<br />
  92. 92. Totalamber ERP Rollout Methodology & Country Readiness<br />How would you describe your state of readiness in this area<br />Do you have in-house Tools & Techniques<br />#<br />Country Readiness : Go Live - 9weeks<br />Week <br />- 5<br />Week <br />- 4<br />Week <br />- 3<br />Week <br />- 2<br />Week <br />- 1<br />Week <br />- 12<br />Week<br /> - 11<br />Week<br />- 10<br />Week <br />- 9<br />Week <br />- 8<br />Week <br />- 7<br />Week <br />- 6<br />Go Live?<br />Week <br />+ 1<br />Week <br />+ 2<br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />9.1<br />Do you have a checklist to validate the training material?<br />9.2<br />Do you have a checklist to identify the right trainer?<br />9.3<br />Do you have a checklist to ensure the trainer is prepared for the rollout?<br />9.4<br />Do you have a checklist to manage the data cleansing activity?<br />9.5<br />Do you have a on-site support strategy?<br />9.6<br />Have you identified on-site support champions? <br />9.7<br />Have you created a test plan to validate the country solution?<br />9.8<br />Have you created test scripts to validate the country solution?<br />27<br />
  93. 93. Totalamber ERP Rollout Methodology & Country Readiness<br />How would you describe your state of readiness in this area<br />Do you have in-house Tools & Techniques<br />#<br />Country Readiness : Go Live - 8weeks<br />Week <br />- 5<br />Week <br />- 4<br />Week <br />- 3<br />Week <br />- 2<br />Week <br />- 1<br />Week <br />- 12<br />Week<br /> - 11<br />Week<br />- 10<br />Week <br />- 9<br />Week <br />- 8<br />Week <br />- 7<br />Week <br />- 6<br />Go Live?<br />Week <br />+ 1<br />Week <br />+ 2<br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />8.1<br />Have you created a training plan and checklist for supper users?<br />8.2<br />Have you created a checklist to sign-off end user training material?<br />8.3<br />Have you created a checklist to asses and evaluate readiness for country rollout support?<br />28<br />
  94. 94. Totalamber ERP Rollout Methodology & Country Readiness<br />How would you describe your state of readiness in this area<br />Do you have in-house Tools & Techniques<br />#<br />Country Readiness : Go Live - 7weeks<br />Week <br />- 5<br />Week <br />- 4<br />Week <br />- 3<br />Week <br />- 2<br />Week <br />- 1<br />Week <br />- 12<br />Week<br /> - 11<br />Week<br />- 10<br />Week <br />- 9<br />Week <br />- 8<br />Week <br />- 7<br />Week <br />- 6<br />Go Live?<br />Week <br />+ 1<br />Week <br />+ 2<br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />7.1<br />Have you created an approach to review the training material?<br />7.2<br />Have you created a methodology to test and validate the training material?<br />7.3<br />Do you have change control procedures to incorporate changes to training material?<br />7.4<br />Do you have a checklist to sign off training material?<br />29<br />
  95. 95. Totalamber ERP Rollout Methodology & Country Readiness<br />How would you describe your state of readiness in this area<br />Do you have in-house Tools & Techniques<br />#<br />Country Readiness : Go Live - 6weeks<br />Week <br />- 5<br />Week <br />- 4<br />Week <br />- 3<br />Week <br />- 2<br />Week <br />- 1<br />Week <br />- 12<br />Week<br /> - 11<br />Week<br />- 10<br />Week <br />- 9<br />Week <br />- 8<br />Week <br />- 7<br />Week <br />- 6<br />Go Live?<br />Week <br />+ 1<br />Week <br />+ 2<br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />6.1<br />Have you created a communication strategy and plan?<br />6.2<br />Have you created a process to incorporate changes into the communication strategy?<br />6.3<br />Have you created a country-specific / local communication strategy?<br />6.4<br />Have you created a checklist to validate the communications strategy and communication style?<br />30<br />
  96. 96. Totalamber ERP Rollout Methodology & Country Readiness<br />How would you describe your state of readiness in this area<br />Do you have in-house Tools & Techniques<br />#<br />Country Readiness : Go Live - 5weeks<br />Week <br />- 5<br />Week <br />- 4<br />Week <br />- 3<br />Week <br />- 2<br />Week <br />- 1<br />Week <br />- 12<br />Week<br /> - 11<br />Week<br />- 10<br />Week <br />- 9<br />Week <br />- 8<br />Week <br />- 7<br />Week <br />- 6<br />Go Live?<br />Week <br />+ 1<br />Week <br />+ 2<br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />5.1<br />Have you created a checklist for the local solution sign-off?<br />5.2<br />Have you created a check list to sign off the training programme?<br />5.3<br />Have you created a checklist to validate hardware installation?<br />5.4<br />Have you created a checklist to validate training room logistics?<br />31<br />
  97. 97. Totalamber ERP Rollout Methodology & Country Readiness<br />How would you describe your state of readiness in this area<br />Do you have in-house Tools & Techniques<br />#<br />Country Readiness : Go Live – 4/3weeks<br />Week <br />- 5<br />Week <br />- 4<br />Week <br />- 3<br />Week <br />- 2<br />Week <br />- 1<br />Week <br />- 12<br />Week<br /> - 11<br />Week<br />- 10<br />Week <br />- 9<br />Week <br />- 8<br />Week <br />- 7<br />Week <br />- 6<br />Go Live?<br />Week <br />+ 1<br />Week <br />+ 2<br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />4.1<br />Have you created a checklist to validate end user training?<br />4.2<br />Have you created a checklist to assess user skills following training?<br />4.3<br />Have you created a checklist to manage data migration process? (ETL)<br />4.4<br />Do you have a plan to communicate updates & changes to on-site support champions?<br />32<br />
  98. 98. Totalamber ERP Rollout Methodology & Country Readiness<br />How would you describe your state of readiness in this area<br />Do you have in-house Tools & Techniques<br />#<br />Country Readiness : Go Live – 2/1weeks<br />Week <br />- 5<br />Week <br />- 4<br />Week <br />- 3<br />Week <br />- 2<br />Week <br />- 1<br />Week <br />- 12<br />Week<br /> - 11<br />Week<br />- 10<br />Week <br />- 9<br />Week <br />- 8<br />Week <br />- 7<br />Week <br />- 6<br />Go Live?<br />Week <br />+ 1<br />Week <br />+ 2<br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />2.1<br />Do you have a plan and a checklist to manage the data cutover?<br />2.2<br />Do you have plan and checklist to manage and mitigate additional data entry requirements?<br />2.3<br />Do you have an approach to continually review the performance of the support function?<br />2.4<br />Do you have a checklist to validate the handover of support?<br />33<br />
  99. 99. Totalamber ERP Rollout Methodology & Country Readiness<br />How would you describe your state of readiness in this area<br />Do you have in-house Tools & Techniques<br />#<br />Country Readiness – Go Live<br />Week <br />- 5<br />Week <br />- 4<br />Week <br />- 3<br />Week <br />- 2<br />Week <br />- 1<br />Week <br />- 12<br />Week<br /> - 11<br />Week<br />- 10<br />Week <br />- 9<br />Week <br />- 8<br />Week <br />- 7<br />Week <br />- 6<br />Go Live?<br />Week <br />+ 1<br />Week <br />+ 2<br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />1.1<br />Do you have a ‘Go Live’ strategy and plan?<br />1.2<br />Have you created a ‘Go Live’ Checklist?<br />34<br />
  100. 100. Totalamber ERP Rollout Methodology & Country Readiness<br />How would you describe your state of readiness in this area<br />Do you have in-house Tools & Techniques<br />#<br />Country Readiness : Go Live + 1weeks<br />Week <br />- 5<br />Week <br />- 4<br />Week <br />- 3<br />Week <br />- 2<br />Week <br />- 1<br />Week <br />- 12<br />Week<br /> - 11<br />Week<br />- 10<br />Week <br />- 9<br />Week <br />- 8<br />Week <br />- 7<br />Week <br />- 6<br />Go Live?<br />Week <br />+ 1<br />Week <br />+ 2<br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />1.1<br />Have you created a support review checklist?<br />1.2<br />Do you have a methodology to review data quality?<br />1.3<br />Have you created a checklist to manage data quality issues?<br />35<br />
  101. 101. Totalamber ERP Rollout Methodology & Country Readiness<br />How would you describe your state of readiness in this area<br />Do you have in-house Tools & Techniques<br />#<br />Country Readiness : Go Live + 2weeks<br />Week <br />- 5<br />Week <br />- 4<br />Week <br />- 3<br />Week <br />- 2<br />Week <br />- 1<br />Week <br />- 12<br />Week<br /> - 11<br />Week<br />- 10<br />Week <br />- 9<br />Week <br />- 8<br />Week <br />- 7<br />Week <br />- 6<br />Go Live?<br />Week <br />+ 1<br />Week <br />+ 2<br />Started<br />Completed<br />Part<br />Yes <br />Started<br />Completed<br />Part<br />Yes <br />Not Started<br />Nearly Completed<br />No <br />Not Started<br />Nearly Completed<br />No <br />+2.1<br />Do you have a strategy to handover to support?<br />+2.2<br />Have you created a checklist for the handover to support?<br />36<br />

×