The Wright Move – A Continued Journey to the Oracle EPM Cloud
1 like451 views
The document outlines Wright Medical Technology's transition from on-premises to cloud-based solutions, emphasizing the implementation of Oracle's EPM Cloud platform. It details the company's history, pain points, project goals, and specific design strategies for financials and workforce applications. Additionally, it highlights lessons learned during the implementation process and outlines next steps for further developments in their cloud strategy.
![FIND US AT OPENWORLD 2019!
IT Financial Management with Oracle EPM Cloud [PRO5553]
Monday 9/16 | 9am-9:45am
26
Conference Sessions:
Client Conference Sessions:
Customers Present: Enterprise Data Management with Oracle EPM
Cloud [PAN5560]
Wright Medical
Thursday, Sept 19, 11:15 a.m. - 12:00 p.m.
PCMCS Customer Presents [PAN5562]
Pacific Life
Thursday, Sept 19, 1:15 p.m. - 2:00 p.m.](https://image.slidesharecdn.com/wrightmedical-continuedjourneytothecloud1-190930131814/85/The-Wright-Move-A-Continued-Journey-to-the-Oracle-EPM-Cloud-26-320.jpg)
The Wright Move – A Continued Journey to the Oracle EPM Cloud
- 1. Wright Medical Technology A Continued Journey from On-Premises to the Cloud 18 September 2019
- 2. AGENDA >Introductions and Company Background >Project Background & Goals >EPBCS Financials: Project Overview, Learnings & Results >EPBCS Workforce: Project Overview, Learnings & Results >Wrap-up and Next Steps >Q&A 2
- 3. INTRODUCTIONS: ABOUT THE SPEAKERS > Kim Province – Sr Manager, Financial Systems > 13+ years of FP&A experience > 6 years with Wright Medical Technology primarily in systems administation > Responsible for HFM, FDMEE, ARCS, EPBCS and EDMCS > Tony Scalese – Vice President of Technology (Alithya) 3
- 4. ALITHYA HISTORY 4 2001 Hyperion Planning introduced to the market (1st Essbase embedded app) 2007 Enhanced Consolidation practice with world class capabilities 2009 HPCM introduced to the market – Ranzal design review 2010 Established Strategic Finance practice to complement our Planning expertise 2012 Exalytics & Performance Testing Lab Establish multi product focus & advisory Proven business analytics leader with a history of successful implementations and continuous growth 1996 Ranzal & Associates Founded 2004 Acquired by Edgewater 2016 Deepened geographic footprint and EPM Cloud expertise 2015 Developed Discovery & Modern Data Architecture Approach 2014 Introduced Hosting, Support & Managed Services Offerings 2018 Ranzal & Alithya join forces to form an EPM/ ERP Cloud Powerhouse
- 5. ALITHYA OVERVIEW – EPM & ANALYTICS 5 Comprehensive Business Solutions Our solutions drive improved business performance through better decision making, strong customer engagement, and optimized operations Deep Partnership Drives Customer Value Adaptable Deployment Models Diverse Client Portfolio & Industry Expertise RetailEnergy/ Utilities Team Highlights Multiple Oracle ACEs Seasoned delivery team with avg 8 years serving clients Experienced management team with avg 15 years in the company Certified Cloud Resources Enterprise Performance Management (EPM) Analytics Financial Services Technology CPG and Manufacturing Healthcare Outstanding Achievement in Big Data 100 Most Promising Big Data Solutions Providers 1,000+ Clients 2,000+ Projects20+ Years Advisory Services Implementation Services Technical Services Hosting & Support Training Services Intellectual Property
- 6. ABOUT WRIGHT MEDICAL Wright Medical Group N.V. is a global medical device company focused on extremities and biologics products. The company is committed to delivering innovative, value-added solutions improving the quality of life for patients worldwide. Wright is a recognized leader of surgical solutions for the upper extremities (shoulder, elbow, wrist and hand), lower extremities (foot and ankle) and biologics markets, three of the fastest growing segments in orthopedics. For more information about Wright, visit www.wright.com. Ticker Symbol: NASDAQ : WMGI 6
- 7. WRIGHT’S EPM HISTORY > Implemented Hyperion Financial Management (HFM), FDMEE and Hyperion Planning in 2014- 2015 > Merger in Oct 2015 doubled the size of the company and significantly increased the complexity of our financial systems environment > Pre merger – 1 ERP, 1 consolidation system and 1 planning system > Post-merger – 13 ERPs, 2 consolidation systems and 2 planning systems > Application enhancements post merger integration (Spring 2016) > Combined all consolidation activity into HFM > Split planning activities between SWB in Adaptive Planning and remainder of P&L in Hyperion Planning > Implemented Account Reconciliation Cloud Service (ARCS) as a pilot for US reconciliations in 2018 with an expansion to UK, Canada, Australia in Q1 2019 > Engaged in an EPM assessment to determine on-premises vs cloud strategy (Early 2019) > Current Project: > Upgrade On-Premises HFM, FDMEE and Planning applications due to looming software support deadlines > Retire Adaptive and replace Workforce Planning functionality 7
- 8. PAIN POINTS > Decrease data refresh time from a planning update to management reporting (due to required hops from Adaptive to Planning to HFM) > HFM dimensionality is confusing for management reporting users (7 customs!) > Still many offline manual spreadsheets used in planning process > Data governance and master data maintenance are manual, time consuming and inconsistent > Infrastructure and on-premises software version is dated and running into support deadlines 8
- 9. PROJECT GOALS > Utilize as much out-of-the-box oracle content as possible to hit tight project timeline and minimize customizations throughout applications > Streamline the data integrations to quickly see planning updates in management reporting > Simplify management reporting application > Provide an integrated planning platform > Flexible planning system always open for input with ability to archive/lock- down formal quarter forecasts > Improve sandboxing and what-if capabilities > Enable workflow for data governance and master data requests 9
- 10. EPBCS FINANCIALS: PROJECT DESIGN > Creation of financials application with same user experience as current planning application with improved performance and reporting speeds. > Simplified dimensionality to minimize possibilities of data input error but same level of detailed analysis required for reporting > Replication of allocations logic from current HFM application > Future Management Reporting needs to be facilitated by financials application > All data input and logic to occur in input (BSO) cube > All aggregations and detail data analysis to occur within reporting cube (ASO) 10
- 11. EPBCS FINANCIALS: OUT OF THE BOX USAGE > Currency Conversion > Valid Intersections utilized to eliminate currency selection requirements > Data Maps utilized to facilitate near real time reporting > Leveraged pre-built dimensionality with addition of existing chart of accounts members included in account dimension 11
- 12. EPBCS FINANCIALS: CURRENCY CONVERSION > Requirement: Each entity has one local currency which needs to be converted to a single USD Reporting currency on save of all input data > Implementing the currency conversion feature is as simple as it looks in training guides. > Lesson Learned: > FX rates need to be copied to the cube where the currency conversions will occur, either through a data map on the FX Rate form or a copy rule that is run on save of FX Rate Input. > Data Input Forms: All data input forms have <Calculate Currencies> calculated on save this way all data is converted immediately upon submission. > Ad-hoc Currency Conversion Rules can be created, customized, and run as needed or set up on a recurring schedule
- 13. EPBCS FINANCIALS: VALID INTERSECTIONS > Requirement: Users select entity and the correct input currency is automatically defined within point-of-view on all input forms. The pre- built valid intersections are used to control the scenarios and the years available for input. > A combination of new valid intersections and form design were used to limit currency selection on all forms.
- 14. EPBCS FINANCIALS: DATA MAPS > Requirement: Simplified user input, with detailed reporting capabilities > Data Maps used to map data to dimensions required for reporting purposes but not required within BSO data input cube. > Requirement: Users input forecast data and can instantaneously review the impact from an aggregated point of view and report. > Data Maps created and utilized to push all data from BSO cube to ASO reporting cube on save of all input forms. > Lessons Learned: > Created several standard data maps and associated the map with data input forms and utilized input forms POV to limit the amount of data moving between the BSO and ASO cubes on save to avoid hitting data limits. > May need to split data pushes into several small data maps to avoid data limits.
- 15. EPBCS FINANCIALS: PREBUILT DIMENSIONALITY > Requirement: Ability to replicate all management reporting occurring within HFM from financials application > Utilized Pre-built dimensionality combined with “Bring-Your-Own-Chart-Of- Accounts” (BYOCOA) methodology > Allowed utilization of existing pre-built dashboards > Flexible with custom dimensionality – Wright added 1 custom
- 16. EPBCS WORKFORCE: PROJECT DESIGN > Utilize out-of-the box content to create a simple standardized forecasting process > Separate pod required for workforce to accommodate asymmetric security requirements between financials and workforce. > All salary, wages, benefits and headcount forecasting to be completed in workforce with data integrations to financials application. 16
- 17. EPBCS WORKFORCE: OUT OF THE BOX USAGE Workforce was a new build and not based on an existing on-premises planning application. The goal was to utilize as much of the out of the box content as possible, allowing for a quick implementation timeframe, as well as to help drive the company to a simplified and standardized process to be utilized globally. > New Hire, Transfer of Existing Employees, Planned Departure, Changing Existing Details Logic > Benefit and Tax Wizard > Merit Set Up > Valid Intersections, Action Menu’s, Smartlists 17
- 18. EPBCS WORKFORCE: NEW HIRES, TRANSFERS > Requirement: Ability to add new hires, transfer existing employees, plan departures and change existing employee and new employee details. > Utilizing the existing logic saved enormous amounts of time > Pro Tip: Become familiar with the various options within the logic. The option selected results in differing calculations, so some education may be required so that users understand how each selection effects salary, wages and benefits calculations etc. ▪ Example: The difference between placing an employee on maternity leave vs. on leave of absence.
- 19. EPBCS WORKFORCE: BENEFITS AND TAXES > Requirement: Benefits and Taxes are calculated as a percentage of Salary plus Overtime or Bonus. > Lessons Learned: > Utilize the custom component type if benefits and taxes are based something other than a % of salary, % of overall earnings, or a flat amount. > Member formulas should be utilized to customize the value type.
- 20. ADDITIONAL LESSONS LEARNED > Repurpose Union Code dimension to be driver dimension. > Example: Employee subtype determines the benefits, additional earnings and taxes required for each employee. > Solution: Union Code was repurposed as employee subtype. > Implementing Out of the box currency conversions lead to slower performance within the BSO cube. > Solution: Currency Conversions occurred within workforce ASO reporting cube by repurposing the Skillset dimension and utilizing member formulas. > Set up custom benefit and tax rates within the OEP_WFP cube to increase performance times of calculations so that benefit and tax rates originate in same cube as other data required for calculations. > Valid Intersections, Action Menu’s, Smartlists artifacts are locked, customization requires creation of new artifact
- 21. EPBCS WORKFORCE TAKE-AWAY > Don’t be afraid of the out-of-the-box solution > Familiarize yourself with its functionality and use the pre-built pieces that fit within the requirements > Layer in additional functionality as required
- 22. HOW DID IT GO? 22
- 24. WHAT’S NEXT > Designing a new BSO cube in EPBCS for statistical data > Expanding management reporting in EPBCS through dashboards and standardized reports > Further expansion of ARCS internationally (e.g. - France) > Data Governance in EDMCS > Migrate HFM 2.4 to FCCS 24
- 25. Q&A > Agenda > Introductions: About the speakers > Alithya History > Alithya Overview – EPM & Analytics > About Wright medical > Wright’s EPM History > Pain Points > Project Goals > EPBCS financials: Project Design > EPBCS financials: Out of the Box Usage > EPBCS financials: Currency Conversion > EPBCS financials: Valid Intersections > EPBCS financials: Data Maps > EPBCS financials: Prebuilt dimensionality > EPBCS WORKFORCE: Project Design > EPBCS Workforce: Out of the Box Usage 25 > EPBCS Workforce: New Hires, transfers > EPBCS Workforce: Benefits and Taxes > EPBCS Workforce: Merit > Additional Lessons Learned > EPBCS workforce take- away > How Did it Go? > What’s Next > Contact Information
- 26. FIND US AT OPENWORLD 2019! IT Financial Management with Oracle EPM Cloud [PRO5553] Monday 9/16 | 9am-9:45am 26 Conference Sessions: Client Conference Sessions: Customers Present: Enterprise Data Management with Oracle EPM Cloud [PAN5560] Wright Medical Thursday, Sept 19, 11:15 a.m. - 12:00 p.m. PCMCS Customer Presents [PAN5562] Pacific Life Thursday, Sept 19, 1:15 p.m. - 2:00 p.m.
- 27. Journey to a Standardized Cloud Budgeting Solution with Thermo Fisher Scientific and Alithya Monday 9/16 |12:30pm-1:15pm EDMCS and FDMEE – The Foundation to Wright Medical’s Hybrid EPM Landscape Tuesday 9/17 | 9am-10am Streamline Capital Planning in Healthcare, Higher Ed, and Transportation with Alithya’s Capital Portfolio Process Tuesday 9/17 | 12pm-1:15pm Oracle ACE Panel: Definitive, Accurate Answers from Oracle Recognized EPM Experts Tuesday 9/17 |1:45pm-2:30pm The Wright Move – A Continued Journey to the Oracle EPM Cloud Wednesday 9/18 |9am-10am Secrets of an EPM Cloud Solution – How to Deliver Superior Profit Performance Wednesday 9/18 | 12pm – 1:15pm 27 BREAKFAST/LUNCH & LEARN/AFTERNOON PRESENTATIONS AT THIRSTY BEAR
- 28. NETWORKING & FUN! Cheers & Beers Unwind in the afternoons with us during the conference while enjoying a fine selection of craft beers brewed by Thirsty Bear. Thirsty Bear Brewing Company Mon 9/16 | Tues 9/17 | Wed 9/18 2pm - 4pm 661 Howard St | San Francisco | CA | 94105 28 Wine Down with Us at Happy Hour Join us for complimentary cocktails and appetizers at our annual Oracle OpenWorld Happy Hour. Wine Down SF Tuesday, September 17th 2019 5pm - 8pm 685 Folsom Street | San Francisco | CA | 94107
- 29. CONTACT INFORMATION 29 Alithya 1025 Westchester Avenue, Suite 108 White Plains, NY 10604 Tel (914) 253-6600 infosolutions@alithya.com 20 West Kinzie Street Suite 13046 Chicago, IL 60610 200 Harvard Mill Square Suite 320 Wakefield, MA 01880 Tony Scalese Vice President - Technology Tony.scalese@Alithya.com