This document describes Totalamber's ERP rollout methodology, which consists of 7 stages: 1) Developing a global blueprint, 2) Defining business processes, 3) Identifying reports, 4) Establishing a data strategy, 5) Configuring the ERP system, 6) Managing change and training, and 7) Migrating data. The methodology aims to standardize processes, reduce costs and timelines for ERP rollouts across multiple countries by establishing common solutions, tools and factories to support each stage of the implementation process.

1. High Performance. Guaranteed.Totalamber ERP Rollout Methodology& Country Readiness Toolkit

2. Totalamber ERP Rollout Methodology1Global Blueprint (Common Solution)Business ProcessReportsDataConfigurationChange & TrainingData MigrationIntegrationRollout PlanningDATA FACTORYTRAINING FACTORYSUPPORT FACTORYCountry BuildCountry BuildCountry BuildCountry BuildRollout Toolkits & FactoriesSupport >Deploy >Test >Build >Design >Mobilise >Country Rollout Preparation2Country A: Countdown 3Implement A4Country B: Countdown 5Implement B1113141517181920121621106Country C: Countdown Implement C78Country D: Countdown Implement D9

3. Totalamber ERP Rollout Methodology – 1: Global Blueprint (Common Solution)1Global Blueprint (Common Solution)Support >Deploy >Test >Build >Design >Mobilise >Country Rollout Preparation21819Business ProcessCountry BuildCountry A: Countdown DefinitionCommon solution developed by the global team for rollout purposes203Implement AReports21134DataDATA FACTORYCountry BuildCountry B: Countdown Key OutputsCommon solution consisting of: 1) Processes; 2) Reports; 3) Interfaces ; 4) Enhancements; 5) Data Conversion; 6) External Documents (e.g. Invoice); 7) Screens & Forms145Implement B11121621ConfigurationTRAINING FACTORY615Country BuildCountry C: Countdown Change & TrainingSUPPORT FACTORYMain BenefitsEnforces common approach and ways of workings

4. Speed up rollout – reducing time to market and costs

5. Enable smooth integration of new acquisitionsImplement C7Data Migration8Country BuildCountry D: Countdown IntegrationImplement D9Rollout PlanningWorking AssumptionsTruly representative team from countries and processes

6. Global view of processes – standardisation

7. Country sign off to blueprint 10Rollout Toolkits & FactoriesExamples of Tools UtilisedProcess Mapping Tool

8. Functional & Technical Specifications

9. Data Mapping

10. LiSA & SNA – (ERP support strategy)

11. Rollout strategyUsual Skills RequiredBusiness Analysis

12. ERP Functionality Mapping

13. Development Specifications

14. Business facilitation and engagementKey RisksKey business resources not engaged effectively in the blueprint build and testing

15. Totalamber ERP Rollout Methodology – 2. Business Process1Global Blueprint (Common Solution)Support >Deploy >Test >Build >Design >Mobilise >Country Rollout Preparation21819Business ProcessCountry BuildCountry A: Countdown DefinitionGlobal common processes supported by the ERP tool203Implement AReports21134DataDATA FACTORYCountry BuildCountry B: Countdown OutputsProcess Strategy Document (PSD)Process Definition Document (PDD)145Implement B11121621ConfigurationTRAINING FACTORY615Country BuildCountry C: Countdown Change & TrainingSUPPORT FACTORYBenefitsClarity on who does what within a process (RACI)

16. Highlights touch points with other processes and stakeholdersImplement C7Data Migration8Country BuildCountry D: Countdown IntegrationImplement D9Rollout PlanningWorking AssumptionsERP processes would be used as straw man to minimise the risk of customisation

17. One PDD will be developed per process / sub-process10Rollout Toolkits & FactoriesTools UtilisedProcess Definition Template

18. Process Maps (VISIO)

19. RACI MatrixSkills RequiredBusiness Process Mapping

20. ERP Module (e.g. Supply Chain Process)

21. Business Workshop FacilitationRisk MitigationProcess describes the “As-Is” instead of thinking about the “To-Be”

22. Totalamber ERP Rollout Methodology – 3. Reports1Global Blueprint (Common Solution)Support >Deploy >Test >Build >Design >Mobilise >Country Rollout Preparation21819Business ProcessCountry BuildCountry A: Countdown DefinitionGlobally agreed management and end user reports required from the ERP tool203Implement AReports21134DataDATA FACTORYCountry BuildCountry B: Countdown OutputsReporting Strategy Document (RSD)Report Definition Document (RDD)145Implement B11121621ConfigurationTRAINING FACTORY615Country BuildCountry C: Countdown Change & TrainingSUPPORT FACTORYBenefitsLists the key reports needed by the business

23. Determines the scale and effort needed to develop the reportsImplement C7Data Migration8Country BuildCountry D: Countdown IntegrationImplement D9Rollout PlanningWorking AssumptionsReports identified as part of the process definition – i.e. what is needed to measure and manage the process effectively at all levels

24. RDD will be signed off per report and before build10Rollout Toolkits & FactoriesTools UtilisedReport Definition TemplateSkills RequiredBusiness analysis(KPIs)

25. ERP Reports (Standard & Available Reports)

26. Business Facilitation (needs assessment)Risk MitigationDuplicate the 100’s of existing reports without considering the right-size need

27. Totalamber ERP Rollout Methodology – 4. Data1Global Blueprint (Common Solution)Support >Deploy >Test >Build >Design >Mobilise >Country Rollout Preparation21819Business ProcessCountry BuildCountry A: Countdown DefinitionGlobal data strategy and conversion for ERP implementation and rollout – from mapping to conversion and maintenance203Implement AReports21134DataDATA FACTORYCountry BuildCountry B: Countdown OutputsData Strategy Document (DSD)Data Conversion Document (DCD)145Implement B11121621ConfigurationTRAINING FACTORY615Country BuildCountry C: Countdown Change & TrainingSUPPORT FACTORYBenefitsCleansed Data

28. Standardised data maps

29. Improved data governance

30. Improve consolidation and reportsImplement C7Data Migration8Country BuildCountry D: Countdown IntegrationImplement D9Rollout PlanningWorking AssumptionsA data strategy developed as part of the project to give guidance to all streams

31. A number of DCD would be developed and signed off per business process 10Rollout Toolkits & FactoriesTools UtilisedData Strategy

32. DCD TemplateSkills RequiredData Analyst

33. ERP Data MappingRisk MitigationDCD developed to reflect current practices instead of new ones

34. Totalamber ERP Rollout Methodology – 5. Configuration1Global Blueprint (Common Solution)Support >Deploy >Test >Build >Design >Mobilise >Country Rollout Preparation21819Business ProcessCountry BuildCountry A: Countdown DefinitionGlobal ERP settings and core data to drive the common processes defined203Implement AReports21134DataDATA FACTORYCountry BuildCountry B: Countdown OutputsBase data – e.g. flags / business rulesMaster data – e.g. customer filesConfiguration cookbook145Implement B11121617ConfigurationTRAINING FACTORY615Country BuildCountry C: Countdown Change & TrainingSUPPORT FACTORYBenefitsShow business how the processes described in the PDD would look using the ERP systemImplement C7Data Migration8Country BuildCountry D: Countdown IntegrationImplement D9Rollout PlanningWorking AssumptionsBusiness process owners would work with ERP process specialist to agree the base and master data to support a particular process

35. The configuration would be managed through change control and refreshes10Rollout Toolkits & FactoriesTools UtilisedConfiguration CookbookSkills RequiredERP ConfigurationRisk MitigationConfiguration decision not documented which makes it difficult to support

36. Totalamber ERP Rollout Methodology – 6. Change & Training1Global Blueprint (Common Solution)Support >Deploy >Test >Build >Design >Mobilise >Country Rollout Preparation21819Business ProcessCountry BuildCountry A: Countdown DefinitionStrategies to secure business engagement, buy-in as well as providing effective end user training on the ERP tool203Implement AReports21134DataDATA FACTORYCountry BuildCountry B: Countdown OutputsChange Management Strategy Document (CMSD)Communications Strategy Document (CSD)Training Strategy Document (TSD)Training MaterialTraining Environments - server and data145Implement B11121617ConfigurationTRAINING FACTORY615Country BuildCountry C: Countdown Change & TrainingSUPPORT FACTORYBenefitsSecure business buy-in to blueprint