Wright Medical Technology implemented several EPM Cloud applications to improve and standardize financial planning and reporting processes. This included an initial rollout of Oracle's Account Reconciliation Cloud application, converting existing on-premises Planning and Budgeting to the EPM Cloud version, and replacing a non-Oracle workforce planning solution with Oracle's Workforce Planning Cloud application. Wright Medical was then able to template their implementations to rollout Account Reconciliation Cloud internationally without external partners. The presentations discusses benefits like improved processes, reporting, and maintenance across the various EPM Cloud solutions.

1. Taking Off to Flying Solo:
Tracing Wright Medical’s
Flight Plan Into the Cloud
Nick Boronski
Product Manager – Fin. Close & Consolidation,
Alithya
Kim Province
Sr. Manager – Financial Systems,
Wright Medical Technology

2. ABOUT THE SPEAKERS
> Nick Boronski – Product Manager, Fin. Close & Consolidation
>
> @PocketACE_NB
> /in/PocketACEnb
> (Blog Posts)
> Alithya channel
> Kim Province – Senior Manager for Financial Systems
> 6+ years with Wright Medical Technology
> Oversee all ERP, EPM, and EPM Cloud applications
▪ JDE, HFM, EPBCS, ARCS, EDMCS, CDM / FDMEE
2

3. AGENDA
3
EPM Cloud
> Basic EPM Cloud Rollout (ARCS Phase 1)
> Basic EPM On-Premises to EPM Cloud Conversion (EPBCS)
> Complex Non-Oracle to EPM Cloud Conversion (Workforce Planning)
> New EPM Cloud Technology & Process (EDMCS)
> The “Partnerless” EPM Cloud Rollout (ARCS Phase 2)
> Strategic Considerations for YOU

4. 4
>Alithya offers EPM, ERP, & Analytics
solutions
>Proven business analytics leader
with a history of successful
implementations & growth
>20+ years of implementations
Advisory
Services
Implementation
Services
Technical
Services
Hosting &
Support
Training
Services
Intellectual
Property
>1,000+ clients
>4,000+ projects
>100+ Cloud implementations
>7 Oracle ACEs
>Certified Cloud resources
>EPM, ERP, & Analytics solutions

5. 5

6. BASIC EPM CLOUD ROLLOUT
6
> Rollout of Account Reconciliation Cloud (2018)
Pre-Project Problems
No centralized or
comprehensive solution
- Excel-based / physical print
- Less than 10% uploaded to
shared drive
- Siloed data sources
Manual effort with no
automation
- No enforced workflow
- Excel checklist “owned” by
end-users
Not scalable or modular
- Lack of formal system to
introduce new BUs and
users
- Difficult to track down
historical recons or progress

7. BASIC EPM CLOUD ROLLOUT
7
> Rollout of Account Reconciliation Cloud (2018)
Formalized solution &
process
- Est. ~60+ hours saved on
administrative maintenance
(annually)
- Central repository for all
reconciliations Automation, traceability,
and auditability
- Scheduled daily data loads from
JDE 9.0 & 9.1 GLs
- Auto-submit / Auto-recon rules
- Dashboarding and reporting
Scalable and modular
- More on the international
expansion later…
Post-Project Benefits
Technical

8. BASIC EPM CLOUD ROLLOUT
8
> Rollout of Account Reconciliation Cloud (2018)
Sparked Active Review
of Current Process
- “Clean up” of balance sheet
- Other countries requesting
to be on the solution
Comfort in the Cloud
- Management buy-in
- Kim’s buy-in!
Fitting “in the box”
- New product functionality
that could be easily rolled
outEPM Cloud
Post-Project Benefits
Non-Technical

9. 9
EPM Cloud
GROUND-TO-CLOUD ASSESSMENT
> Goal: Make the
process faster
> Convert Planning to
Enterprise Planning &
Budgeting Cloud
> Reimagine process in
Workforce Planning
> Centralize maintenance in
Enterprise Data Management

10. BASIC EPM ON-PREMISES TO EPM CLOUD CONVERSION
> Conversion from Planning to Enterprise Planning & Budgeting Cloud
> “Lift & Shift” > Streamlined dimensionality
▪ Instantaneous aggregated
reporting; performance
improvement
▪ Simplified end-user experience
> Reporting
re-focused from
on-prem to Cloud
10

11. COMPLEX NON-ORACLE TO EPM CLOUD CONVERSION
> Reimagine process in Workforce Planning
> Conversion / Enhancement from Adaptive Planning to Workforce Planning
ComplexitySystem Process
> Many unique situations by
location, by person, etc.
> Difficulty enforcing
standards
> Lack of governors
> No clear “single source”
> Different hierarchies /
structures
11

12. COMPLEX NON-ORACLE TO EPM CLOUD CONVERSION
> Reimagine process in Workforce Planning
> Conversion / Enhancement from Adaptive Planning to Workforce Planning
Challenge: Staying
“in the box”
> Tight project timeline
> Capitalize on future
enhancements by Oracle
12

13. COMPLEX NON-ORACLE TO EPM CLOUD CONVERSION
> Reimagine process in Workforce Planning
> Conversion / Enhancement from Adaptive Planning to Workforce Planning
> New data feeds
13
Workday: Live data from source
for driver-based process

14. COMPLEX NON-ORACLE TO EPM CLOUD CONVERSION
> Reimagine process in Workforce Planning
> Conversion / Enhancement from Adaptive Planning to Workforce Planning
> New data feeds
> Standardization
14
Product and Process

15. COMPLEX NON-ORACLE TO EPM CLOUD CONVERSION
> Reimagine process in Workforce Planning
> Conversion / Enhancement from Adaptive Planning to Workforce Planning
> New data feeds
> Standardization
> Enhanced reporting
15

16. COMPLEX NON-ORACLE TO EPM CLOUD CONVERSION
> Reimagine process in Workforce Planning
> Conversion / Enhancement from Adaptive Planning to Workforce Planning
> New data feeds
> Standardization
> Enhanced reporting
> New functionality
16
Employee transfers,
departures, leave of
absence, etc.

17. NEW EPM CLOUD TECHNOLOGY & PROCESS
> Centralize maintenance in Enterprise Data Management
> Align maintenance processes
and reduce duplication of
effort
▪ EPBCS Financials, Workforce,
HFM, (future)ARCS
> Provide governance,
controls, and visibility
into changes
▪ Who, when and where
17

18. 18
Application
Layer
Cloud Data
Management
FDMEE
Data Integration Layer
FinancialsWorkforce
Reporting
Layer
Source
Systems JDE
ARCS EPBCS HFM
SmartView
/ Ad-hoc
EPM
Automate
REST API
EDMCS
EDMCS
WorkdayGL
Extracts
ARCS
HFM
“Jumpbox”
Financial
Reports
NEW EPM CLOUD TECHNOLOGY & PROCESS

19. YES!
THE “PARTNERLESS” EPM CLOUD ROLLOUT
19EPM Cloud
> ARCS International Rollout by Wright Medical Technology Team
> Templatized previous implementation
▪ Utilized existing artifacts (ex. Formats, Holidays)
▪ Utilized existing methodology (ex. Summary Profiles)
▪ Utilized existing customization (ex. Rules, Attributes)
Question: Does our
out-of-the-box
solution scale?
YES!
YES!
YES!
YES!
YES!
YES!YES!
YES!YES!

20. THE “PARTNERLESS” EPM CLOUD ROLLOUT
20EPM Cloud
> ARCS International Rollout by Wright Medical Technology Team
Owned and implemented
by international team
- Kim the Overseer
- Capitalized on previous
success
Quick implementation /
fast time-to-value
- Strategic selection of
business units / personnel
- Completed in a few weeks
New requests to join in!
- Obvious and tangible benefits
- Unsolicited positive feedback
> Templatized previous implementation

21. 21

22. 22
> A modular approach to EPM Cloud
> Begin with the roadmap
> Hybrid environment: both Cloud
(EPBCS, ARCS, EDMCS, etc.) and on-
premises (HFM, etc.)

23. 23
> When and how to capitalize on
“out-of-the-box” functionality
> Few customizations: ARCS, Workforce
> Many customizations: Planning, HFM
> Mixed: EDMCS

24. 24
> Templatize success
> Understand strategic goals
> Examine the process and products
> Utilize Partner and in-house resources
efficiently

25. 25
> Templatize success
> Understand strategic goals
> Examine the process and products
> Utilize Partner and in-house resources
efficiently
EPM Cloud