Lessons Learned / Best Practices for Supporting Global Cloud Implementations Mike Booke 15 September, 2015

© 2014 Aurora Technology Management Agenda First Implementation Subsequent Domains Global Considerations Summary © 2014 Aurora Technology Management

First Domain and Database Network connection is critical Allow 90 days for installation Internet VPN vs. Private MPLS Have a back-up network connection Schedule QAD and Virtela network teams as part of turn-up Thoroughly understand bandwidth, latency Utilize QAD managed routers Set-up network monitoring prior to Go-live © 2014 Aurora Technology Management

First Domain and Database (cont.) Make your Cloud Engagement Mgr. part of your implementation team Schedule weekly calls Copy on appropriate emails Be engaged Drive support Ensure you have the new implementation team vs. on-going support Skills and experience may not overlap © 2014 Aurora Technology Management

First Domain and Database (cont.) Create at least two SDLC environments to use as TEST and PROD Fully install and configure PROD without master data Install master data and use TEST for training and CRP’s Update PROD with config’s and scripts (master data if confident) after CRP’s Refresh TEST from PROD for next CRP iteration Load master data and opening balances in PROD prior to Go-live After Go-live refresh TEST and DEV with PROD © 2014 Aurora Technology Management

© 2014 Aurora Technology Management Subsequent Domains Dedicate at least two environments for NEWTEST and golden NEWPROD Keep refresh from impacting and being impacted by SDLC environments Update domain in PROD at Go-live Keep single Cloud Engagement Mgr. if possible If global time differences (+/- 12 hours) mandate, get a temporary regional Engagement Mgr. as well Urgent support will be needed (same day) Allow 90 days for network installation, turn-up and testing © 2014 Aurora Technology Management

Global Considerations Multiple Global Domains on a Single Instance Numerous global domains will make scheduling maintenance extremely complex Especially when running some domains 7 x 24 Latency for a single instance may provide marginal performance and more frequent support issues Plan ahead for back-up and disaster recovery High availability vs multiple instances Leverage Cloud global data centers Consult QAD for optimum architecture © 2014 Aurora Technology Management

© 2014 Aurora Technology Management Summary Cloud based ERP can work! Save capital and overhead of on-prem or internal data center Plan ahead for network capacity, installation and testing Include Cloud Engagement Manager as part of your team Don’t neglect back-up, disaster recovery, and maintenance Be engaged and drive support © 2014 Aurora Technology Management