EOH Attachment G - Draft Solution Architecture and Design v1.1 UPDATED 1...

Enterprise Applications to build afoundation of Excellence Attachment G – Draft Solution Architecture and DesignResponse to POINT OF SALERFP number RFP IT 5 - RFP_2016_PROF_00016Attention Christo MaswattieClosing date 24th April 2017

RFP IT 5 - RFP_2016_PROF_00016 – POINT OF SALEContact details for this proposalName Simon JustDesignation Executive – Industry SolutionsCell phone +27 (82) 330 0123Email [email protected] Renee LeeDesignation Account ExecutiveCell phone +27 (83) 212 0438Email [email protected] Business ParkGilroy’s ViewOsborne LaneBedfordviewJohannesburg2007Tel: 011 607 [email protected] proposal, its attachments and any rights attaching hereto are, unless the context clearly indicatesotherwise, the property of EOH Group Limited and/or its subsidiaries (\"the Group\"). It is confidential,private and intended for the addressee only, and may only be used by the addressee for the particularpurpose for which the proposal has been requested. The addressee shall furthermore treat all personalinformation that comes to its knowledge or into its possession as confidential and shall not disclose it.Should you not be the addressee and receive this proposal by mistake, kindly notify the sender, anddelete it immediately. Do not disclose or use the proposal in any manner whatsoever.Views and opinions expressed in this proposal are those of the sender unless clearly stated as those ofthe Group.The Group accepts no liability whatsoever for any loss or damages, whatsoever and howsoever incurredor suffered, resulting or arising from the use of the information in the proposal or its attachments. TheGroup does not warrant the accuracy of the contents of this proposal. Page 2 of 21

RFP IT 5 - RFP_2016_PROF_00016 – POINT OF SALETable of Contents1. Introduction .........................................................................................................................41.1 Purpose .............................................................................................................................................................. 41.2 Scope .................................................................................................................................................................. 42. Our Proposed Architecture ..................................................................................................52.1 Oracle Retail Xstore Point Of Service (XStore) ................................................................................................. 52.2 Oracle Retail Xstore Office (Xcenter & Xadmin)............................................................................................... 6 2.2.1 Xcenter....................................................................................................................................................... 6 2.2.2 Xadmin ....................................................................................................................................................... 62.3 Oracle Retail Store Inventory Management (SIM)........................................................................................... 62.4 Oracle Retail EFTLink ......................................................................................................................................... 62.5 Oracle Retail Xstore Mobile .............................................................................................................................. 72.6 Oracle Retail Configuration & Extensibility ...................................................................................................... 72.7 Hardware Architecture...................................................................................................................................... 8 2.7.1 Stand Alone Stores x 150 .......................................................................................................................... 8 2.7.2 Multi-Store Malls x 200............................................................................................................................. 8 2.7.3 Store Hardware Configuration ................................................................................................................. 93. Deployment Approach .......................................................................................................133.1 Introduction ..................................................................................................................................................... 133.2 Problem Statement ......................................................................................................................................... 133.3 Deployment Integration “Phases” .................................................................................................................. 13 3.3.1 Initial Rollout of Xstore Ahead of MOM V 16 ........................................................................................ 14 3.3.2 Xstore Rollout After MOM V16 Go Live ................................................................................................. 17 3.3.3 Completion of Xstore Rollout (End State) .............................................................................................. 203.4 Deployment Approach Assumptions .............................................................................................................. 20 Page 3 of 21

RFP IT 5 - RFP_2016_PROF_00016 – POINT OF SALE1. Introduction1.1 PurposeThe purpose of this document is to present the solution architecture and design for the Point of Sale (POS)solution. This document is intended to be read by solution architects, developers or testers who would beinvolved in the solution in any capacity.1.2 ScopeThe scope of this document is limited to the following components below. Each of these components isexplained in detail further below.  Oracle Retail Xstore Point Of Service (XStore)  Oracle Retail Xstore Office (Xcenter & Xadmin)  Oracle Retail Store Inventory Management (SIM)  Oracle Retail EFTLink  Oracle Retail POS Mobile Page 4 of 21

RFP IT 5 - RFP_2016_PROF_00016 – POINT OF SALE2. Our Proposed ArchitectureOur solution proposal to Edcon comprises of modules from the Oracle Retail Stores domain, that support a high-service store environment. Major functions within this domain include the generation of sales and returnstransactions, inventory management, and returns management. These components will address the width anddepth of the scope as outline by Edcon..Mall EDCON Store EDCON Store Xstore EDCON Data Center Datasource Xoffice Xstore Store Server Replication Data Xcenter Xadmin xStore Xcenter Foundation FOUNDATION Datastore Data Data Application (Merchandising, Server Pricing and Xstore Promotion) Xstore POS Datasource SIM Back Office (Store Inventory Management) Source Systems Xstore POS (RMS, RPM) Lead Register RXM (Extension Module) EFT LINK RWMS OFFLINE Datasource OFFLINE Datasource (Warehouse Management System)Xstore Mobile POS Xstore POS Registers ORCE (Customer Experience) Vision Figure 1 - Solution OverviewThese products were purposefully packaged to deliver the value to Edcon by driving down the total cost,aligning to the Edcon initiatives that are aimed at achieving the defined objectives of the organization, andaddressing the concerns identified.2.1 Oracle Retail Xstore Point Of Service (XStore)Oracle Retail Xstore Point Of Service (XStore POS) is robust point-of-service functionality and platform whichenables retail staff to deliver on brand promise in store with inventory visibility, customer intelligence, andseamless transactions  Serves as the front-end user interface with which the store cashier interacts.  Consumes foundation data to produce a retail transaction.  Supports multiple foundation data sources for operator data, item, price and promotion, in order to ensure operational functionality in the event that a primary data source becomes unavailable. Page 5 of 21

RFP IT 5 - RFP_2016_PROF_00016 – POINT OF SALE  Serves as the back-end to persist transactions into store’s data source and initiate replication process to save transactions to centralized repository.  Provides Point-of-Service (POS) operator management – creation of temporary operators, changing passwords, assigning roles, and editing application roles. 2.2 Oracle Retail Xstore Office (Xcenter & Xadmin)Oracle Retail Xstore Office is a web-based application used to administer corporate- based functions such as OracleRetail Xstore Point-of-Service configuration, setup and maintenance and file management for the Oracle RetailXstore Suite, viewing the electronic journal, store reports, monitoring Oracle Retail Xstore Point-of-Service versionsin use at the store, register levels, and monitoring alerts. 2.2.1 Xcenter  System of record for raw retail transactions for the stores domain.  Provides services for transaction replication from stores to enterprise.  Provides service for cross-store transaction retrieval. 2.2.2 Xadmin  Provides centralized configuration and data management for the enterprise.  Provides employee management for the Xadmin Application.  Provides deployment management to propagate changes to stores.  Provides centralized view for transaction journal across stores.  Provides centralized reporting tool to help monitor and analyze stores’ operations and sales. 2.3 Oracle Retail Store Inventory Management (SIM) SIM is a mobile and PC-based inventory management application that helps track inventory positions in the store. It increases store efficiency by helping store associates to execute and monitor all store inventory transactions.  Serves as the front-end user interface for inventory operations within stores.  System of record for store perpetual inventory. 2.4 Oracle Retail EFTLinkOracle Retail EFTLink is a middleware product that enables Oracle to remove Xstore Point of Service from the costlyand frequently changing Payment Application Data Security Standard. EFTLink uses an industry-standard interfaceto the point of service and then translates the messages to the relevant format provided by the payment provider,enabling the POS to be outside of the payment scope. Page 6 of 21

RFP IT 5 - RFP_2016_PROF_00016 – POINT OF SALE2.5 Oracle Retail Xstore MobileOracle Retail Xstore Mobile is a mobile point‐of‐sale (POS) extension of the Xstore register software. UsingXstore Mobile, many of the actions that employees normally performed on a register can now be performed outon the sales floor.Xstore Mobile is built utilizing the existing Xstore core frameworks and work flows to ensure a consistentexperience for the associate. It is platform independent and runs on iOS and Android. The application is built asa thin client, enabling speed of deployment and without operating system dependencies.2.6 Oracle Retail Configuration & ExtensibilityOracle Retail support several different configuration formats. Configurations are generally more flexible,manageable, extensible, and easily deployed than code-based modifications. These include:  XML,  Java Resource Bundle,  Java Properties, and  Database.EOH will be leveraging a number of these technologies to address Edcon’s requirements. The table belowdescribes how these extensions.Dev Item Headline Approach TimelinesUser Interfaces Xstore Forms Framework The Forms Framework allows users to create and configure forms*.Workflow Xstore Operation Chain An operation chain is a configurable sequence of operations Framework (OpChains) (tasks) that comprise a logical process or workflowIntegrations Xstore Data Transfer DTX is used for data transfer and translation to allow Framework for (DTX) disparate data sources to be seamlessly managed in Xstore Point of Service through a consistent interfaceInterfaces Xstore Point of Service The Services interface is accessed through separate services, Services interface each with its own application programming interface (API).Enhancements Xstore Operation Chain Operation Chains provide business logic for various functions Framework (OpChains) throughout Xstore Point of Service. Page 7 of 21

RFP IT 5 - RFP_2016_PROF_00016 – POINT OF SALE2.7 Hardware Architecture2.7.1 Stand Alone Stores x 150 Figure 2 - Hardware Architecture: Stand Alone Stores x 1502.7.2 Multi-Store Malls x 200 Figure 3 - Hardware Architecture: Multi-Store Malls x 200 Page 8 of 21

RFP IT 5 - RFP_2016_PROF_00016 – POINT OF SALE2.7.3 Store Hardware Configuration Figure 4 - Store Hardware Configuration: EDCON Front Office POS Page 9 of 21

RFP IT 5 - RFP_2016_PROF_00016 – POINT OF SALE Figure 5 - Store Hardware Configuration: EDCON BackOffice and Mobile POS Page 10 of 21

RFP IT 5 - RFP_2016_PROF_00016 – POINT OF SALE Figure 6 - Store Hardware Configuration: EDCON Store Server Figure 7 - Store Hardware Configuration: EDCON Mall Server Page 11 of 21

RFP IT 5 - RFP_2016_PROF_00016 – POINT OF SALE Figure 8 - Store Hardware Configuration: EDCON Peripherals Page 12 of 21

RFP IT 5 - RFP_2016_PROF_00016 – POINT OF SALE3. Deployment Approach3.1 IntroductionTailoring the specific rollout of Xstore require more deep dive analysis of mall and high-profile store locations;this will be in sharp contrast to the Merchandising and Planning (M&P) rollout which will focus on a brand bybrand deployment model.The result of having different deployment approaches for the POS and M&P system will be that for a period alevel of coexistence will be required between the new POS system, the new M&P system and the four legacyRetek Merchandising platforms.From the data transfer perspective, the approaches being suggested for both of the POS and M&P system willrequire a number of temporary integrations to be set up between the new and the Legacy environments. TheIntegration activities will be been broken into three phases. Connections to and from the Legacy POS system(Avenew) to the new merchandising system will be outside of the scope of EOH/OLR and will be theresponsibility of the M&P SI.The key areas of focus will be the management of foundation & transactional data; it will have to be split insome cases and sent to both systems in others3.2 Problem StatementEdcon’s Core Systems Roadmap, places the Point of Sales implementation on the critical path. The target datefor the ‘day 1’ POS solution requires the assumption is that the new POS solution will initially receive foundationdata and pass back transaction data to the current Merchandising solution until the new Merchandising andPlanning solution is fully operational.Managing the initial integration between the new POS solution and the current Merchandising and Planningsolution and migrating the integration to the new Merchandising and Planning solution when it becomesoperational is critical to the successful deployment of the POS solution?In response to Edcon’s request for clarity during the Proof of Concept, EOH developed the DeploymentApproach illustrated below.3.3 Deployment Integration “Phases”The following phase have been proposed (see Diagram Below):  Initial Rollout of Xstore Ahead of MOM V 16  Xstore Rollout After MOM V16 Go Live  Completion of Xstore Rollout (End State) Page 13 of 21

RFP IT 5 - RFP_2016_PROF_00016 – POINT OF SALETimeframes provided by shortlisted suppliers through the RFP response process, details to be confirmed during mobilisationTimeline CY17 Q1 CY17 Q2 CY17 Q3 CY17 Q4 CY18 Q1 CY18 Q2 CY18 Q3 CY18 Q4 CY19 Q1 CY19 Q2 CY19 Q3 CY19 Q4 CY20 Q1 FY17 Q4 FY18 Q1 FY18 Q2 FY18 Q3 FY18 Q4 FY19 Q1 FY19 Q2 FY19 Q3 FY19 Q4 FY20 Q1 FY20 Q2 FY20 Q3 FY20 Q4Integration Commercials, Mobilisation and PlanningIntegration Stand UpContinuous Integration Governance and Support M&P SIM-Support Core Integration Work streamsStore rollout INTcomplete Integration Service POS go live go live Day 1 POS Product Build2 Store Rollout POS Roadmap Merchandise Aligned Roadmap releases go live go live MOM Product Build 1 Brand Migration POS Initial Rollout of Xstore Ahead of MOM V 16 Phase 1Integration Xstore Rollout After MOM V16 Go Live Phase 2a Phases Completion of Xstore Rollout (Remaining M&P rollout) Phase 2b Completion of Rollout (End State) Phase 3 Figure 9 - Phased Integration Deployment Plan: Top Level Plan3.3.1 Initial Rollout of Xstore Ahead of MOM V 16Edcon Legacy Retek Instances Integration Hub Transformation to Edcon Legacy Retek 8 (4) Avenue Avenue POS Retek 8 (3) (a) Foundation Retek 8 (2) Data Transformation to Edcon TO-BE Retek 8 (1) XCenter XCenter (b) Transactional Routing Merch / Edcon TO-BE Data by Store Item SIM Lookup ID Transformation to Table of stores SIM on new Stores Solution Figure 10 - Phase 1: Foundation and Transactional from Retek 8 only Foundation Data needs to be sent from Retek 8 to all systems. This type of data does not need to be disseminated based on any sort of store ID. (a) Transactional data coming from Retek 8 instances, such as Purchase Orders, RTV requests, Transfers and so on will need to be routed based on the store ID. If the Store ID is on the new Stores solution, it will need to be sent to Xcenter and SIM. Otherwise, it will be sent to Avenue (b) The merchandise hierarchy and item ids will require transformation as part of the integration to Xcenter and SIM Page 14 of 21

RFP IT 5 - RFP_2016_PROF_00016 – POINT OF SALEEdcon Legacy Retek Instances Integration Hub Edcon Legacy Retek 8 (4) Avenue POS Retek 8 (3) Item (a) Sales, Retek 8 (2) Lookup Inventory Edcon TO-BE Retek 8 (1) Transactions XCenter Transformation to Routing Retek 8 Routing (b) Sales Edcon TO-BE by Store by Store Transactions SIM ID ID (c) Inventory Transactions Table of stores Table of stores on by Retek 8 RMS 16 (none at Instance this stage) Figure 11 - Phase 1: Transactions from Stores to Retek 8 SIM- INT Sales and Inventory will flow from Avenue (a) Sales transactions will flow from Xcenter (b) SIM- Inventory transactions will flow from SIM (c) INT A placeholder is setup for the next phase where filtering is performed based on whether or not the store is on RMS 16. As all stores are still on Retek 8, the flow would continue to Retek 8 for all transactions. After transformation to the format required by Retek 8 occurs, routing based on the ID of the store to the appropriate Retek 8 instance will occur € The RIB may not yet exist in the picture. Other mechanisms are available for getting the transactional information to SIM.Integration Hub Routing Inventory Edcon Legacy by Store Transactions (a) Avenue POS Table of stores on SIM 16 ID Transformation to Edcon TO-BE Avenue SIM Routing by Store Item Lookup ID Transformation to SIM Inventory Transactions from SIM Figure 12 - Phase 1: Intra Store Transactions (Transfers) If Store to Store Transfers are required between stores live on Avenue, and stores live on SIM, additional integration effort will be required in order to be able to handle those scenarios, unless they are handled by a different process and managed on an exception basis only (e.g. Inventory Adjustments) Page 15 of 21

RFP IT 5 - RFP_2016_PROF_00016 – POINT OF SALE  This will need to include transfer requests from stores to stores, shipments, and possibly even the receipts.  All such transactions would be posted to the Integration HUB, and if the store ID belongs to the other system, then transformation will occur into the format required by the other system and the message will be routed accordingly. Otherwise, it will just be filtered out.  For example: o A Store to Store transfer may occur in a store in Avenue, to be received at a store who is live in SIM. o Avenue would publish this information to the Integration HUB (a) o Based on the store ID, a lookup would occur to see if the store is live on SIM (b) o If the store is live, then transformation to the corresponding format required by SIM would occur (e.g. an ASNIn) Page 16 of 21

RFP IT 5 - RFP_2016_PROF_00016 – POINT OF SALE3.3.2 Xstore Rollout After MOM V16 Go LiveEdcon Legacy Retek Instances Integration Hub Transformation to Edcon Legacy Retek 8 (4) Avenue Avenue POS Retek 8 (3) (a) Foundation Data(Retek instance upgrade in Transformation to Edcon TO-BEprocess) XCenter XCenterEdcon TO-BE RIB (a) (b) Transactional Routing Merch / Edcon TO-BERMS V16 Data by Store Item SIM Foundation Data (a) Foundation ID Lookup SIM-RIB Data Transactional Table of stores on Transformation to SIM-INT Data (a) Transactional SIM/Xcenter V16 SIM Data Routing Transformation to by Store Avenue ID (c) Base (b) Transactional Data# RIB Stands for Oracle Retail Transportation Direction Integration Bus Figure 13 - Phase 2a: Foundation and Transactional from RMS and Retek 8 When RMS 16 is introduced and rolled out, some foundation information and transactional information will begin to be maintained within RMS 16 Base integration will be leveraged wherever it can. As such, for any data that exists within RMS 16, the RIB will be used to get this information to SIM, and the base extracts from RMS will be used to get this information to Xstore (a and b) Anything created in RMS 16 that is foundation or transactional will be routed within the Integration HUB and transformed into the format required by Avenue, but only for the stores that are not yet live on SIM (c) Leveraging base integration wherever possible is more cost effective, because it reduces the amount of custom transformation effort required by the solution. It also means that in the end state, the integration will be mostly base, which makes the upgrade path much easier, cheaper, and supported. Page 17 of 21

RFP IT 5 - RFP_2016_PROF_00016 – POINT OF SALEEdcon Legacy Retek Instances Integration Hub Transformation to Routing (a) Sales, Edcon Legacy Retek 8 (4) Retek 8 by Store Inventory Avenue POS Retek 8 (3) Routing Transactions by Store ID Edcon TO-BE(Retek instance upgrade in (b) Sales XCenterprocess) ID Transactions Edcon TO-BEEdcon TO-BE Table of stores Merch Table of stores on (c) Inventory SIMRMS V16 by Retek 8 / Item RMS 16 Transactions Instance Lookup SIM-RIB Transformation to RMS 16 (a) RIB (b) SIM-INT Transactional Data RTLog Gen RTLog Transportation Direction Figure 14 - Phase 2a: Transactions from systems to Retek 8 and RMS 16 Sales will come from both Avenue and Xcenter For any sales that come from Avenue, where the store is live on RMS 16, routing and transformation will occur to transform those files to the format required ty RMS (ReSA) v16 (a). The same will occur for anything inventory related. The RIB will be used for SIM to get data into RMS 16 (b) Xcenter would also broadcast sales information to the base RTLog Generator. This is base integration between Xcenter and RMS (ReSA) v16. As each phase Stores is rolled from Retek 8 to RMS 16, a cleanup of the data that has been loaded into RMS 16 would occur. The details of this would be identified during the Analysis phase Page 18 of 21

RFP IT 5 - RFP_2016_PROF_00016 – POINT OF SALEEdcon Legacy Retek Instances Integration Hub Transformation to Edcon TO-BE Retek 8 (4) XCenter XCenter Retek 8 (3) (a) Foundation Data Merch / Edcon TO-BE(Retek instance upgrade in Item SIMprocess) (b) Transactional Data Lookup SIM-RIBEdcon TO-BE RIB (a) Transformation to SIM-INTRMS V16 SIM Foundation Data Transactional Data Base (b) Transactional Data# RIB Stands for Oracle Retail Transportation Direction Integration Bus Figure 15 - Phase 2b: Foundation and Transactional from RMS and Retek 8Edcon Legacy Retek Instances Integration Hub Transformation to (b) Sales Edcon TO-BE Retek 8 (4) Retek 8 Transactions XCenter Retek 8 (3) Routing by Store Merch (c) Inventory Edcon TO-BE(Retek instance upgrade in / Item Transactions SIMprocess) ID Lookup SIM-RIBEdcon TO-BE Table of storesRMS V16 by Retek 8 Instance RIB (b) SIM-INT Transactional Data RTLog Gen RTLog Transportation Direction Figure 16 - Phase 2b: Transactions from systems to Retek 8 and RMS 16 Page 19 of 21

RFP IT 5 - RFP_2016_PROF_00016 – POINT OF SALE3.3.3 Completion of Xstore Rollout (End State)Edcon TO-BE Base Edcon TO-BERMS V16 XCenter Transactional Data Edcon TO-BE SIM RIB (a) Foundation Data SIM-IRIB Transactional Data Transportation Direction Figure 17 - Phase 3: Foundation and Transitional from RMS v16 After all phases are moved to RMS 16, and the Stores rollout is complete, the integration architecture is simplified. Base integration is leveraged for foundation and transactional information for getting data to both Xcenter and SIMEdcon TO-BE RTLog Gen Edcon TO-BERMS V16 XCenter RTLog Rib Edcon TO-BE SIM Transactional Data SIM-IRIB Transportation Direction Figure 18 - Phase 3: Transactional from Stores After the rollout is complete, Avenue, and all instances of Retek 8 will be decommissioned. As such, base integration will be used from XCenter to transmit RTLogs to RMS 16. The RIB will also be used to publish all information from SIM to RMS 16.3.4 Deployment Approach Assumptions  During Analysis, mapping rules to a possible future state merchandise hierarchy would need to be defined and implemented within the Integration Hub.  Use of base integration will be leveraged wherever possible in order to reduce the development effort, reduce cost and complexity, and simplify the upgradability of the solution.  ODI will be used as the Integration Hub for Phase 1 & 2 Page 20 of 21

RFP IT 5 - RFP_2016_PROF_00016 – POINT OF SALE  A single instance of XCenter and SIM will be used for all Edcon Brands  During rollout, Edcon would be responsible for updating the data source leveraged by Integration Hub to define the store flows.  Edcon will consider a rollout strategy which would minimize the occurrences of store to store transfers between stores live on SIM, with stores live on Avenue. If this is not feasible, additional throwaway integrations will be necessary. Page 21 of 21