The document discusses how patching has changed from an on-premise to cloud model. In the past, patching was difficult and caused issues, but in cloud applications patching now provides new functionality and standardization without the same testing and customization challenges. It recommends focusing on core testing of integrations and reports rather than the entire application when cloud patching is implemented. Examples are given of how clients in HR, finance, and manufacturing have benefited from new capabilities provided through cloud patching.

1. Session ID:
Prepared by:
Remember to complete your evaluation for this session within the app!
11197
Patching is your Friend
In the new world order of EPM and
ERP Cloud
02.28.2019
Doug Hahn
Global Head of EPM
Datavail
@doug_hahn

2. Presenter
• 25+ years in IT, 15 consulting, 10 IT executive
• Teams of 70+
• Experience across multiple disciplines
• Active in ODTUG, IOUG, OAUG and QUEST
– Chair OAUG Marketing and Communication Committee and Content
Generation Sub Committee
– Ex-Chair of the OAUG Customer Support Council
– Former board member BIWA (IOUG)
• Multiple public speaking engagements, OOW, Collaborate and regional users
groups
• Publications:
– OAUG Insight Magazine Summer 2009 edition -- R12 and OBIEE:
Intelligence Investments for Turbulent Times and
– OAUG Insight Magazine Fall 2015 – Oracle Support Identifier Groups.
• OAUG Speaker of the Year 2017
Doug Hahn
Global Head of EPM

3. Win Shoes
Fill out the session survey
for a chance to win an
exclusive pair of Datavail’s
running shoes!

4. About Datavail

5. Our Range of Data Services
Health Checks &
Assessments
Project Services
Upgrades Data Migration
OBIEE & Hyperion
Consulting
24x7 In-Office
Coverage
Operational Managed Services
Monitoring & Incident
Response w/ SLAs
Service Requests
(Patch, Modify, etc.)
Multi-factor Monitoring
Proactive Services
(Health, Tune)
Structured Service
Review
Data Development Services
Development, Tuning,
Automation
Data Warehouse
Build & Optimize
DevOps (Deploy &
Automate)

6. Hyperion
Hero Award
Contest submission deadline:
April 10th
Nominate a Hero at: http://www.datavail.com/hyperion-hero
*Prize value can also be donated to a charity of choice.
*

7. What this session IS
• Understanding of the differences between on-prem and SaaS (Cloud)
applications
• Patching is no longer just for security
• How it can improve your business
• Understanding the patching schedule from Oracle
• How to position patching within your organization
• Applies to many products (on-prem and cloud)
– EPM, Fusion, OAC, Non-Oracle Products

8. What this session is NOT
• Not a specific guide for your organization
• Not one-size-fits-all
• Deeper conversations needed
• You can’t be an expert in 60 min.

9. Agenda
• Quick review of types of cloud
• Understanding not all cloud applications are
the same
• Why is patching a good thing?
• How can I “sell” it to my business users, IT
team, myself???
• What to look for from Oracle and manage the
process so it works for you
• Examples of how it has worked out

10. Typical Cloud Getting Started Mentality
Traditional Silos
• Physical
• Dedicated
• Static
• Heterogeneous
Consolidated
• Virtual
• Shared platform &
shared
infrastructure
• Dynamic
• Standardized
platform &
infrastructure
Private Cloud
• Self-service
• Auto-scaling
• Metering &
chargeback
• Capacity planning
Public Cloud
• Specialized
• Shared
• Standardized
Hybrid Cloud
• Federation across
public & private
clouds
• Interoperability
• Cloud bursting

11. What is Cloud?
Multiple definitions out there
• Types of Cloud or XaaS
– FaaS
– SaaS
– PaaS
– DBaaS
– IaaS
– Hosting
– AMS
• Oracle calls these all Cloud,
others have different
definitions
End
Users
Application
Developers
Network
Architects
SaaS
PaaS
IaaS
ValueVisibilitytoEndUsers

12. Oracle Cloud High-Level Use Cases
Customizations
Application
Platform
Consolidation
Cost Savings
Customizations
App Development
Focus
Customizations
New Capability
Speed
IT Professional Developer Business End User
Application
Different
Users
Service
ProviderConsumer
Service
ProviderConsumer
IaaS
Cloud
Key
Driver
PaaS Cloud SaaS Cloud

13. Not All Cloud Applications are the Same
• Some are true SaaS applications
– May be multi-tenant
– May share code base
– May share hardware
– May share capabilities / standardize
you on a single approach
• Some appear to be SaaS
– They have a URL
– You access it via a browser
– May be dedicated code for you
– May not share code

14. Patching is Different Depending on This
• True SaaS applications have
shared patching
– You get what everyone else gets
– On their time, their schedule
– May not take into consideration your
specific needs
• Non-SaaS
– Like on-prem, your code, your
timeline
– May be a PaaS solution – we
warned about marketing
– More flexibility in patching
– However less advantages for you!

15. Why is Patching Now a Good Thing?
In the past, patching meant:
– Cloning environments
• Do you still have the install media?
• Does your backup even work?
• Can you restore to a different server?
• Integrations, reporting would break
– Coding
• What is going to break?
• How can I fix it, or work around the changes?

16. Why is Patching Now a Good Thing?
In the past, patching meant :
– Testing
• Need to test everything
• How do you test across applications?
– Propagating code to upper environments
– No standard in patching, or impacts
• Things just stop working

17. Why is Patching Now a Good Thing?
Today, patching means
– Much of the testing has been done for you
• Testing against a standard code base is easier to test for core functionality
• Still need to test integrations and reports
• Many others have tested before you
– New Functionality!!!
• Patches with true SaaS applications come with new functionality
• Not just security patching
• Standard code means new capabilities can be integrated quickly and easily

18. Extras
• Backups/BR/DR may now be included in your solution
• High Availability – May be an option to be application cluster aware, or be
highly redundant
• Cloning – creating dev/test environments may be just an option now
• Encryption – many providers include encryption in their offerings
• Testing – some applications have built in testing solutions, or easy-to-
plug-in options

19. Compliance Issues with SaaS
• Multi-tenant concerns
– Are you sharing hardware, data bases?
• Data privacy – is the data PII, PCI, HIPAA?
• Data location
– Moving to a data center down the street
– May not be that simple for compliance
– Contracts are often written with language:
• Internal data stores
• Specific addresses
• “Owned” by company

20. How Can I Sell It?
• SaaS applications have one thing in common: they share resources
This can be good
• Reduced testing
• If one customer gets functionality, every one can
• Spread the costs over time, over hardware
• Reduce capital costs
• No hardware refreshes/no depreciation
• Ability to standardize
• You are always in a supported configuration

21. What to Look Out For
• Quarterly patches are coming
– You still need to test functionality
• Integrations
• Reporting
– You still need to test backup/recovery
– Development environments will be patched first, some lag before production
– There are options to delay production patching
• Most providers will only allow 2-3 versions back, then you are forced to patch
• Can work with product development team to ensure patches are friendly
• You can join early adaptor programs to get further insight to patching

22. Examples of How
Cloud Patching Has
Helped Clients

23. HR/HCM
• Many complex integrations, best of breed
• New functionality around self-serve payroll
deposits
• Initially moved module by module
– Time and labor
– Recruitment
– Compensation
– Benefit tracking
• Working to establish a core set of HR processes

24. Finance Fusion ERP/EPM
• New capabilities in sub-ledger accounting
were made available
• New tools for integrations – moved away
from FTP
• New approval processes around invoicing
became standard
• Removed the need for over 100
customizations
• Drill-through from PBCS on upper-level
members

25. Manufacturing
• Just-in-time shipping was made available
with a patch
• Real time tracking of inventory
• Advanced reporting, new tools available

26. In Summary
• Remember: patching is no longer just an
audit or compliance process
• You get standard processes and as patches
come, you can take advantage of new
functions
• Let others test first, same code, their tests
are valid
• Focus on your core business, instead of
application versions and support

27. Session ID:
Remember to complete your evaluation for this session within the app!
11197
Doug.Hahn@Datavail.com