UGF9091 - Persky-OOW 2014 PBCS Hyperion Planning in The Cloud PDF

Oracle PBCS
Planning & Budgeting

Cloud Service
September 28, 2014

2014 Performance Architects, Inc. Proprietary & Confidential
Todays Speaker
Senior Director at Performance Architects
16 years of experience in the EPM
(Hyperion) space
Implemented several budgeting/planning &
reporting solutions across a variety of
industries
Chuck
Persky
Proficient in Oracle EPM Hyperion

Planning, Hyperion Essbase, and related
components
2014 Performance Architects, Inc. Proprietary & Confidential Page 2
Who We Are
Source: Performance Architects
Agenda
What is The Cloud
What is PBCS
PBCS versus On-Premise
Case Studies / Use Cases
Questions
Todays Attendees?
Who are todays attendees?
People who have NO prior experience in the
Oracle EPM (Hyperion Planning) space, and want
to learn about PBCS
OR
People who ARE familiar with, or already use,
Oracle EPM on-premise (Hyperion Planning) and
want to know more about PBCS
What is The Cloud

Confusing? Everything is in the cloud or up in the cloud
Several definitions
Simply put, the cloud is not a physical thing or place. It is a network of servers
Private Cloud
Oracle Cloud Services
Oracle Cloud
Build
Managed
Subscribe
Customer owns.
Customer operates.
Customer owns.
Provider operates.
Provider owns.
Provider operates.
PBCS Subscription
Planning and Budgeting Cloud Service

Oracle SaaS (Software as a Service)
offering
Priced $$$/user/month
Provides enterprise-wide planning
capabilities in a cloud-based,
subscription-based, deployment model
SaaS Considerations
Typical items to consider when
evaluating SaaS options
Each organization must weigh the importance of these items
SaaS Upside
Low operational expense
SaaS Downside
Security and compliance concerns
No infrastructure / capital investments Data integration with other systems

Lower short term TCO
Longer term TCO uncertain
Streamlined implementation capable
Scalability (adding apps, etc.)
Frequent automatic upgrades
Frequent automatic upgrades
What is PBCS
Planning & Budgeting framework
Provides (2) environments

Each provides (1) Planning application
Each provides ability to create several plan types for each

application
Capable rapid implementation

No Servers, Installs / lighter procurement process?
Wizards, starter kits, tutorials
Enterprise grade security, availability, scalability

Fully Managed: upgrades, patches, backups
What is PBCS
Full power of Hyperion Planning, available in the cloud
Same foundation as on-premise Hyperion Planning

Proven technology foundation
Built on v11.1.2.3
Familiar Planning Components

Input forms
Task Lists
Approvals (Process Management)
Business Rules
Dimension/Member security
Reporting
Smart view on client / FR Studio provided via cloud!
PBCS vs. On-Premise

PBCS
On-Premise
Instances
Two Environments / Instances
No limit on environments
Applications
Single planning application

No modules / No EPMA
Multiple planning applications

Planning modules, EPMA
Essbase (EAS)
No exposed access to Essbase. Many

functions moved into PBCS
Traditional Essbase administration tool

(EAS)
Dimensions
Six pre-defined dimensions with the ability

to create up to 14 total dimensions
Six pre-defined dimensions with the ability
Limitations on number of members per
to create up to 20 total dimensions
dimension.
Limitations determined by performance of
User defined dimension can have up to 25k
calculations and retrieves
members
Application Size 150 GB per instance
Determine by customers hardware size
Security
Utilizes IDM native users in the cloud

Supports direct integration with LDAP and
Groups created in PBCS, assigned to Apps
MSAD
and dimensions
Supports single sign-on
Does not support LDAP or MSAD
Data Integration
Supports integration of data from multiple

sources via flat files
Supports integration of data from multiple

sources via flat files or direct integration
PBCS vs. On-Premise (Data Integration)

TEXT Files Optional
On
Premise
FDMEE Optional
Source
DRM Optional
ODI Optional
Direct Integration
Text files
PBCS
Indirect Integration
Planning
Source
Consider frequency and

automation requirements
PBCS
FDMEE Optional
PBCS vs. On-Premise (Additions!)

File transfer utility available
Uploading data and metadata to the
Oracle Cloud
Diagnostics tools
Tutorials
Data and Master
data import function
New Landing Page
PBCS Landing Page and Navigation
Case Study1
Customer Background
Nonprofit (Higher Education)
Specialized technical institution

25K students
$300M in revenue
Tuition is primary revenue source

Extraordinary growth in enrollment
Several physical locations
Several fields of study and degree programs
Utilized MS Excel spreadsheets as primary planning tool

Customer utilizes Oracle EBS
Product Search
Why PBCS was a good fit
Accommodate growth
Enterprise wide solution
Task driven process
Data-integrity / one version of truth

Robust / easy-to-use analytics
Low IT overhead
Simple administration
No on-premise software
Customer Planning Process

Planning components
LRP (four year long range plan)
Budget (annual operating plan)
Forecast (current year projection)
Fiscal Year: July through June
Relevant financial components

Balance Sheet
P&L (enrollment driven revenue calculations / bottom up expenses)
Cash Flow
Planning executed at Account and Cost Center level
No currency considerations
Project Roadmap
The college favored a crawl-walk-run approach to implementation
Phased implementation approach, allowed for a quick, eight week roll out
Allowed for users to get comfortable with application framework
Allowed decision makers to better understand the capabilities of the tool
Phase 1
P&L and Balance Sheet
Long Range Plan (LRP)
Later Phases
Budget, Forecast
More complex revenue
Cash flow reporting
Staff planning by employee
Phase1: Project Timeline

8 Weeks
Phase1: Project Scope

LRP
Four year detailed
LRP (P&L and
Balance Sheet)
P&L
By account, month,
year, and company
Year 1 derived via

drivers/calcs/inputs
Expenses
calculated via Plan
Method
Years 2, 3, and 4
utilized growth
factors
Revenue utilizes
enrollment statistics
entered as drivers
Data derived via

calculations (use of
drivers, inflation
factors, and entry)
Revenue calculated
for undergraduate,
graduate, PhD, and
other revenue
accounts
Balance Sheet
Reporting
Input and derived by

accounts, but NO
cost center detail
Financial
statements utilize
financial reports
(standardized
reporting packages)
Provides Actual
versus Plan
variance reporting
Application Design
FinPlan Application
MAIN
P&L, Balance sheet, Cash Flow
LRP, Budget, Forecast
By account & company)
STAFF
Salary & Benefit accounts
Budget
By company & employee/position
RPT
Full reporting capabilities
Attribute reporting
Application
Design
HR Data
Oracle EBS
Financials
Full solution
application design
Represents all
implementation
phases
STAFF
MAIN
RPT
(ASO)
Smart View for Office

Financial Reporting
Application
Design
Phase1
HR Data
Oracle EBS
Financials
Represents Phase 1
implementation only
Shows needed
components for LRP
only
STAFF
MAIN
RPT
(ASO)
Smart View for Office

Financial Reporting
Phase1: Dimensions
Dimension
Type
MAIN
RPT
Accounts
Base
Period
Base
Years
Base
Scenario
Base
Version
Base
Company
Base
Fund
Company Attribute
Function
Company Attribute
Officer Code
Company Attribute
FASB
Company Attribute
Scholarship Type
Company Attribute
ESEOR
Company Attribute
Simple model (6 base dimensions & 6 attributes)

Significant reporting required across company attributes
Phase1: LRP Methodology

Revenue
Four main revenue accounts (Undergraduate, Graduate, PhD & Other)
Revenue driven by enrollment data and rates
Calculated using simple Price x Quantity
Expenses
Expenses calculated using prior year actuals as a base
Derived using nine expense growth factors

Growth Factor Percent accounts entered via input forms
LRP automated via a business rule:

For Revenue: Users enter rates and quantities
For Expenses: Users pick enter percents and choose growth method
Phase1: LRP Expense Calc Methods

Method
LRP Year1 Logic
Out Years
Ratio from Tuition
("Basis" of account) * (AC610B->"LRP"->"YearTotal") /

("Basis" of "AC610B"->"YearTotal")
Out years calculate the

same
Growth Rate Housing
("Basis" of account) * (1 + housing growth rate ->begbalance)
Compound on last LRP
Growth Rate Wages
("Basis" of account) * (1 + wages growth rate ->begbalance)
Growth Rate Benefits
("Basis" of account) * (1 + benefits growth rate ->begbalance)
Growth Rate General
("Basis" of account) * (1 + general growth rate ->begbalance)
Growth Rate
Maintenance
("Basis" of account) * (1 + maintenance growth rate >begbalance)
Growth Rate XXXXX
("Basis" of account) * (1 + XXXXX growth rate ->begbalance)
Growth Rate Interest
("Basis" of account) * (1 + interest growth rate ->begbalance)
Growth Rate
Depreciation
("Basis" of account) * (1 + depreciation growth rate >begbalance)
Manual Entry
Accounts are not calculated -- any data must be entered
Manual entry
Phase1: Task List Items
Customer Benefits
Provided single source of truth and all data residing in
databases, instead of spreadsheets
Standardized reporting of financial statements across

dimensions and attributes
Improved analysis via Smart View and Financial Reports
PBCS calculation engine used to DERIVE plan data, instead
of pure inputs and excel
Versioning
Low set up cost; no infrastructure needed
Very quick implementation timeline (eight weeks)
Oracle PBCS client support was efficient and responsive
Case Study2
Customer Background
Publically traded company
Medical device technology
$600-$700M in annual revenue
Experiencing revenue/product growth; recent acquisition

International & currency components
Utilizes MS Excel spreadsheets as primary planning and
reporting tool
Customer utilizes Oracle EBS
Engagement just underway

Customer Pain Points & Needs

Pain Points
Planning executed on dozens of spreadsheet templates
Utilizing email and Excel functionality to consolidate and report
Process is manually intensive and time consuming
Customer Needs
Customer looking to make process more efficient and more timely
Must accommodate Budget, AOP, Forecast, LRP (P&L / BS)
Customer anticipates growth, acknowledges that current methods

are not scalable
STAFF planning for labor expenses, and PRODUCT LINE planning
for revenue
Considering a level of customer detail
Application
Design
Dimensions
Dimensionality shows our confidence in scalability!
Dimension
STAFF
MAIN
Accounts
Period
Years
Scenario
Version
Cost Center
Location
Company
SubAccount
Product Line
Employee
Job Title
Project Timeline
Larger/More complex scope longer duration
13-15 Weeks
Summary
PBCS Need to Knows

Think big, but start small (i.e. case study1)
Start with limited scope
Expand application as needed
Rapid deployment provides for quick use of subscription!
Customer to be actively involved in full life cycle

PBCS is really same as on premise with just a few
differences
Be mindful of data integration capabilities; especially in

regard to frequency or automation of data
When building an application remember, no exposed
Essbase and Essbase components; instead utilize
PBCS functionality
Questions
Reminder: KSCOPE15 !!!
Keep in Touch!
Blog
http://blog.performancearchitects.com
Twitter
@PerfArchitects
Facebook
http://www.facebook.com/
PerformanceArchitects
Learning Center
(for archived webinar and
presentation materials)
http://www.performancearchitects.com/
learning_center
YouTube HowTo Channel
http://www.youtube.com/user/
PerformanceArchHowTo
Chuck Persky
chuck.persky@performancearchitects.com
Appendix
Reporting on Attributes
Data Form - Assign Attributes (Smart

Lists) to Cost Centers (Entities)
XXXXX
Assign Attributes (Smart Lists) to Cost Centers (Entities)
XXXXX
Map SmartList to ASO Dimension

UGF9091 - Persky-OOW 2014 PBCS Hyperion Planning in The Cloud PDF

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

UGF9091 - Persky-OOW 2014 PBCS Hyperion Planning in The Cloud PDF

Transféré par

Droits d'auteur :

Formats disponibles

Oracle PBCS

Planning & Budgeting

September 28, 2014

Proficient in Oracle EPM Hyperion

2014 Performance Architects, Inc. Proprietary & Confidential Page 2

Source: Performance Architects

2014 Performance Architects, Inc. Proprietary & Confidential Page 3

2014 Performance Architects, Inc. Proprietary & Confidential Page 4

2014 Performance Architects, Inc. Proprietary & Confidential Page 5

What is The Cloud

Oracle Cloud Services

Source: Performance Architects

2014 Performance Architects, Inc. Proprietary & Confidential Page 6

Planning and Budgeting Cloud Service

Source: Performance Architects

2014 Performance Architects, Inc. Proprietary & Confidential Page 7

No infrastructure / capital investments Data integration with other systems

Longer term TCO uncertain

Streamlined implementation capable

Scalability (adding apps, etc.)

Frequent automatic upgrades

Frequent automatic upgrades

Source: Performance Architects

2014 Performance Architects, Inc. Proprietary & Confidential Page 8

Provides (2) environments

Each provides ability to create several plan types for each

Capable rapid implementation

Enterprise grade security, availability, scalability

Source: Performance Architects

2014 Performance Architects, Inc. Proprietary & Confidential Page 9

Same foundation as on-premise Hyperion Planning

Familiar Planning Components

2014 Performance Architects, Inc. Proprietary & Confidential Page 10

PBCS vs. On-Premise

Two Environments / Instances

Single planning application

Multiple planning applications

No exposed access to Essbase. Many

Traditional Essbase administration tool

Six pre-defined dimensions with the ability

Application Size 150 GB per instance

Determine by customers hardware size

Utilizes IDM native users in the cloud

Supports integration of data from multiple

Source: Performance Architects

Supports integration of data from multiple

2014 Performance Architects, Inc. Proprietary & Confidential Page 11

PBCS vs. On-Premise (Data Integration)

Consider frequency and

Source: Performance Architects

2014 Performance Architects, Inc. Proprietary & Confidential Page 12

PBCS vs. On-Premise (Additions!)

Source: Performance Architects

2014 Performance Architects, Inc. Proprietary & Confidential Page 13

PBCS Landing Page and Navigation

Source: Performance Architects

2014 Performance Architects, Inc. Proprietary & Confidential Page 14

2014 Performance Architects, Inc. Proprietary & Confidential Page 15

Specialized technical institution

Tuition is primary revenue source

Utilized MS Excel spreadsheets as primary planning tool

Source: Performance Architects

2014 Performance Architects, Inc. Proprietary & Confidential Page 16