Professional Documents
Culture Documents
Fusionhcmpresentation 200125153244
Fusionhcmpresentation 200125153244
You can implement few Modules of Fusion along with other existing
application like Talent Management, Compensation Management & Talent
Review.
So in this case, customer may not give away with an existing core HR
application rather, customer can leverage the new features of Fusion.
A complete set of enterprise cloud services ensures customer success before, during, and
after enablement.
Workforce
Workforce Development
Deployment
Payroll
Oracle Fusion
HCM
Benefits
Global organizational support including global Composite, role based, interactive views of
local currencies, time zone support, localized Role based dashboards with embedded
12
Oracle Cloud Environment Maintenance
•Mandatory Monthly Application Patching cycle
• Patch bundles are applied on 1 st Friday on Stage and 3 rd Friday on Production
•Technology stack fixes are applied on 2 nd and 4th Friday of the month
• Optional weekly as needed one-off patching
• Optional weekly accumulated one-off patching
• 4-6 month application upgrade cycle
• 1 year technology stack or infrastructure upgrade cycle
• Most maintenance is applied Friday Evening through Saturday Morning
13
Fusion Application Deployment Options
The deployment option how the customer wants to implement the Fusion application. Is
it going to be on premise, or on demand, or a SaaS?
•In an on premise model, the Fusion application will be installed and implemented, managed by
the customer themselves. So the hardware, software, everything will be procured by the
customer. They'll be managing it in house. And then all of the maintenance will be handled by
the customer themselves. This will be the most expensive option.
14
•In on demand model, then the hardware and software will be hosted in an Oracle environment,
whereas customer will be able to access the application and also the environment from remote.
In Oracle on demand, the hardware and software will be managed and also hosted by the Oracle
team.
• The third approach is Oracle on demand hosted and managed, Oracle will be responsible
for even maintaining the hardware and software. And any maintenance, like applying the
patches, bundles, everything will be handled by Oracle. With this option, the customer
purchases the product licenses, but Oracle (or an Oracle Partner) is responsible for the software
and infrastructure installation, configuration, and management at a remote datacenter.
•The fourth way of deployment option is SaaS, Software As a Service, wherein customer would
be accessing the Fusion application in a subscription model based upon the models they have
subscribed, and also based upon the timelines. Oracle retains the product licenses and is
responsible for software and infrastructure delivery and management. Customers subscribe to
the services and support plans they want.
•So in a pure SaaS model, the Fusion applications are available in a subscription basis, based
upon the modules that are opted for, based upon the timeline of subscription, and also based
upon the employee data managed.
15
•In a SaaS deployment, all the modules are multi-tenant enabled, in the sense more than one
customer data will be available in the same application, but it will be separated, and security
will be enforced on that in such a way that one customer will not be able to view the data of
other customers.
• The Fusion applications can be deployed in a variety of ways. And these are all the
options available for a customer.
Option 1 - A customer can continue on the current path. Like for example, if a customer
is using EBS 12.1.3, they can continue to go with the same application with the next
version, 12.2 1 or 12.2.2.
Option 2 - The next way of looking at it is Fusion can coexist with the other core HR
application. Like the customer can take a few models of Fusion, and they can use it. And
then they can also integrate Fusion with an existing core HR system. So that's what we
call it as a coexistence opportunity. So in this way, customer will still be using the core
HR system for the day to day transactions and operations, whereas the new features of
Fusion will also be leveraged for other functionalities like talent management,
compensation management, which has embedded analytics feature.
Option 3 - The other way of looking at the deployment option is, customer is planning
to move away from an existing core HR system to the Fusion application suite that
16
covers various pillars, like Human Capital Management, Customer Relationship
Management, and Supply Chain Management. And also other features like
procurement, financials.
17
Fusion HCM – Co-Existence Opportunity
Solution Why?
• A full-featured application suite, leveraging the latest • Enables organizations to gain immediate business value
technologies and industry thought leadership while minimizing upgrade costs
Who?
• PS/EBS HR Customer looking to replace niche
vendor/homegrown
talent system, with an Oracle offering
18
Required employee data is synchronized
with Fusion
Fusion is utilized for the Talent
Management, compensation analysis,
planning, and allocation purposes
Work and compensation changes (Bonus,
Promotions etc.) at the end of the
compensation review cycle are
synchronized back to the source
application
19
©i Copyright 2012. Apps Associates LLC. 20
Integration and Configuration
Objects Key Difference Between
Cloud Deployment and On premise
•No access to database to run SQL
•No access to JDev or Skin Editor
•Cannot Perform ADF customizations
•No ability to develop and custom Java or
PL/SQL code
•No access to Oracle Business Intelligence
applications and data ware housing;
however, user can use BIP and OTBI for
reporting
•Cloud customers are provisioned two
Environments
•For Public cloud , services are available to
the general public and offered on a
subscription basis, with no requirements to
additional licenses or support
•For Private cloud ,services are offered for oracle software and hardware and are available internally , behind fire walls
Transact
Manage
Configure Offerings Configuration
Packages
•Tasks can be assigned to various Fusion project users; status of task completion is
reported at parent task and implementation project level.
•This functionality also allows users to migrate configurations from one instance to
another (Test/Production).
© Copyright 2012. Apps Associates LLC. 23
Getting Started With Fusion Applications
© Copyright 2012. Apps Associates LLC. 24
Configure Offerings
•An implementation project consists of all the tasks required for the implementation. You
refine the list of tasks for the implementation project by reviewing features and selecting
feature options. Because only tasks required for the selected functionality are included,
project initiation productivity is improved.
•Selecting offerings, options, and the related features associated with each offering
dynamically creates an implementation task list based on just the functionality to be
implemented. This can greatly enhance productivity by presenting a targeted list of tasks in
the appropriate implementation order.