Professional Documents
Culture Documents
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
Who We Are
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
Several definitions
Simply put, the cloud is not a physical thing or place. It is a network of servers
Private Cloud
Oracle Cloud
Build
Managed
Subscribe
Customer owns.
Customer operates.
Customer owns.
Provider operates.
Provider owns.
Provider operates.
PBCS Subscription
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
What is PBCS
Planning & Budgeting framework
What is PBCS
Full power of Hyperion Planning, available in the cloud
Task Lists
Approvals (Process Management)
Business Rules
Dimension/Member security
Reporting
Smart view on client / FR Studio provided via cloud!
Source: Performance Architects
On-Premise
Instances
No limit on environments
Applications
Essbase (EAS)
Dimensions
Security
Data Integration
On
Premise
FDMEE Optional
Source
DRM Optional
ODI Optional
Direct Integration
Text files
PBCS
Indirect Integration
Planning
Source
PBCS
FDMEE Optional
Diagnostics tools
Tutorials
Data and Master
data import function
New Landing Page
Case Study1
Customer Background
Nonprofit (Higher Education)
Product Search
Why PBCS was a good fit
Accommodate growth
Enterprise wide solution
Task driven process
No on-premise software
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
P&L
By account, month,
year, and company
Expenses
calculated via Plan
Method
Years 2, 3, and 4
utilized growth
factors
Revenue utilizes
enrollment statistics
entered as drivers
Revenue calculated
for undergraduate,
graduate, PhD, and
other revenue
accounts
Balance Sheet
Reporting
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)
Application
Design
Phase1
HR Data
Oracle EBS
Financials
Represents Phase 1
implementation only
Shows needed
components for LRP
only
STAFF
MAIN
RPT
(ASO)
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
Expenses
Expenses calculated using prior year actuals as a base
Out Years
Growth Rate
Maintenance
Growth Rate
Depreciation
Manual Entry
Manual entry
Customer Benefits
Provided single source of truth and all data residing in
databases, instead of spreadsheets
Case Study2
Customer Background
Publically traded company
Medical device technology
$600-$700M in annual revenue
Customer Needs
Customer looking to make process more efficient and more timely
Must accommodate Budget, AOP, Forecast, LRP (P&L / BS)
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
Questions
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
XXXXX
Reporting on Attributes
Assign Attributes (Smart Lists) to Cost Centers (Entities)
XXXXX
Reporting on Attributes
Map SmartList to ASO Dimension