integrated closed loop. This gives life to tailored solutions that deliver enduring value for our customers, partners and communities. Our comprehensive end to end solutions 4 An introduction to Visy | June 23
Visy | June 23 PAPER & CARDBOARD 1.27M TONNES GLASS 512k TONNES PET 29k TONNES HDPE 18k TONNES OTHER PLASTICS 44k TONNES ALUMINIUM 17k TONNES STEEL 24k TONNES We take it* (FY2022) We make it (FY2022) * Includes recyclable materials used by Visy and provided to other recyclers. Source: Visy Blue Book FY2022 ANZ Materials Reporting GLASS 814k TONNES KRAFT PAPER 681k TONNES RECYCLED PAPER 813k TONNES BOARD 928k TONNES PLASTIC CONTAINERS 1B FOOD CANS 547M PLASTIC PREFORMS 1B BEVERAGE CANS 2.4B
global instance • EULA updated 2006 • S/4HANA transfer rights acquired in 2017 • Cloud Migration to AWS in 2017 with SQL & Unicode Conversion • Supported by Rimini Street 2019 & 2020 • SAP contract renegotiated in 2020, return to SAP Support • ~3,100 users with headroom and indirect/digital coverage • Support Model – Internal, Telstra, AWS Context 7 & Visy SAP journey | June 23
CRM, Supply Chain & HR Systems • Quality Master Data • AI, Automation & Machine Learning • Rationalisation of Applications – Single Instance ERP • Real Time Analytics for decision making • Seamless Networking with Customers & Suppliers Business priorities 8 & Visy SAP journey | June 23
& 2017 – before RISE RISE was introduced upon our return to SAP Support in Dec. 2020 Why change? • Modernise and rationalise our applications with a cloud strategy in place • ERP Strategy needs to fit to our Cloud roadmap • ECC6 EhP7 is 8 years old – limited process improvement opportunities • ECC6 mainstream support ends in 2027, 3 years extended support • User experience is dated, no real time embedded analytics • SAP Cloud Products best integrate to S/4HANA Evaluating RISE | June 23
year duration, with implied renewal “forever” • Common questions: − Scope coverage: products not covered by RISE? − Special concessions? − Historical discounts? − Is there a way back to perpetual? − Estimate future costs RISE Primer | Licensing 13 Perpetual License + Maintenance Subscription & Evaluating RISE | June 23
Common questions: − How do SLAs differ from what we have today? − What about existing Reserved Instances? − Can we influence infrastructure sizing? − How does it co-exist with non-SAP and SAP- adjacent infra (e.g. OpenText)? RISE Primer | Hosting 14 & Evaluating RISE | June 23
does this compare to my existing Basis services? • Can I now fire my Basis team? • How does this operate with my IT Service Desk, other outsourcers? • Is this a turn-key end-to-end solution? 15 RISE Primer | Managed Services & Standard Services Cloud Application Services Optional Services Additional Services Excluded Tasks Evaluating RISE | June 23
2 2.5 Year 1 Year 2 Year 3 Year 4 Year 5 Traditional Model Consumption Cost 0 1 2 3 4 5 Year 1 Year 2 Year 3 Year 4 Year 5 Ramp-up Model Consumption Cost 0 1 2 3 4 5 Year 1 Year 2 Year 3 Year 4 Year 5 Commit to Consume Model Consumption Cost 0 0.5 1 1.5 2 2.5 Year 1 Year 2 Mini RISE Consumption Cost Evaluating RISE | June 23 &
• Full TCO model for both • Qualitative comparison against strategic drivers, operating model • Visy-specific recommendations based on existing SAP contracts • Consider implementation approach against Visy’s business objectives, priorities RISE Assessment Objectives 17 & Evaluating RISE | June 23
BOM SAP Support contract SAP Order Forms Licensing Reports AWS Costs SAP EWAs IT Strategy IT Operating Model RISE Assessment Business Priorities Evaluating RISE | June 23
• Cloud Remix Rights • Comparison between Perpetual Licenses with significant headroom v FUE equivalent and digital access volumes • Spend commitments – minimum spend agreement negotiated when returning to support – consideration of future SaaS spend • Multiple parallel contracts – 15 Appendices to base agreement, divestment agreement with split • Assessment of shelfware and potential replacement with cloud products (SAP Policy) Visy Licensing Analysis 19 & Evaluating RISE | June 23
cheaper than the native AWS scenario, but: • Risks of cost increases (additional services, RISE exit costs, cost increases on renewal) • More complex operating model (no direct access to Basis, everything via service requests, etc.) • Does not allow reuse of existing Reserved Instances • Further scope to negotiate S/4HANA Engine conversion cost RISE option would be more beneficial if there was no spend commitment & Evaluating RISE | June 23
AWS option better aligned with business drivers in 2022 • Visy has an experienced in-house SAP team with direct engagements è RISE would separate scope • RISE means more dependency on SAP • RISE would dilute relationship with AWS (SAP is 50% of our AWS) • RISE required commitment to additional cloud spend. Native AWS covers spend commitment via S/4HANA Engine Purchase & Evaluating RISE | June 23
Retain perpetual licenses 2 Start planning and preparations for a future move to SAP S/4HANA 3 Re-evaluate RISE in a few years 4 & Evaluating RISE | June 23
understand changes in S/4HANA • Evaluating process mining tools: Celonis & Signavio • Zero-based Security review – down to object level • Simplification Item checks – relevance checks (15%) • Review custom objects – 50% are inactive • Review custom transactions – 40% are obsolete • Review custom reports; align to strategy (SAC, Power BI, S/4HANA Embedded) • SAP DAES Star Service – review of licencing and digital access options (indirect usage) Process Licensing & Evaluating RISE | June 23
Retain 7 years? 2 years? • SNP Assessment: System scan to find usage of Org, Modules, Data Analysis, Fiori Impact • Master Data Review with the business • AWS Reserved Instance optimisation • Review of sizing – Housekeeping & Archiving • Considering options for pilot conversion and S/4HANA trial Data Tech & Evaluating RISE | June 23
• Backup/transfer/restore – takes a long time. • Engage SAP early & assign responsibility • Understand end to end migration plan in detail è Faster, less risky paths are possible but not the “default” – requires deep engagement with SAP to realise Migration into RISE 25 & Evaluating RISE | June 23
Disasters • Not customer-invokable • RTO of 4 Hours at extra cost 99.9% • Fast, cluster-based fail-over • Not all hyperscalers, regions • Used only for failures, Disasters • Not customer-invokable • Not used to minimise downtime N/A • Not Available & Evaluating RISE | June 23
Technical Architect without CAS. • Everything is a ticket. Lead times apply . • Your Basis team needs to provide context, validate, test, coordinate. • Don’t assume that the person implementing a change in QA will be the same as doing the Prod change! • You need to fill the gaps in the RACI. Evaluating RISE | June 23
• Some room to move on: • Price • Bill of Materials • Phased start of services • Transition mechanics • Financial commit with remix • Exit clauses • Be prepared for an up-sell push the following year Evaluating RISE | June 23
a very important decision. Assess properly 1 Prepare, prepare, prepare 2 Business outcomes should drive cloud and ERP strategy 3 & Evaluating RISE | June 23