hyperion planning overview -...

University of California, San FranciscoHyperion Planning Overview

Agenda

Overview and Introductions Hyperion Planning Overview Workspace ‐ Running Financial Reports Planning ‐ Forms/Tasklists/Process Management SmartView

2

Overview of “Dimensions” in Hyperion Planning

3

What is a Dimension ? A dimension can be thought of as a way to describe your data “I look at my data byMonth, by Department, and by Account” Often times when you use the word “by” you are qualifying something by

a dimension

Travel

Meals

Salary

Expense

Accounts

Accounts

“What were our Travel expense numbers in September for Pharmacy?”

Organization

HBS

GSE

VIT

University

HUL

Time

Jul

Aug

Sep

Q1

Year

What is a Member ? A member is an element or item in a dimension. Member names must be unique across an application. Example members are Sep, GSE and Meals


4

Travel

Meals

Salary

Expense

Accounts

AccountsOrganization

HBS

GSE

VIT

University

HUL

Time

Jul

Aug

Sep

Q1

Year

What is a Hierarchy ? A hierarchy describes how the members in a dimension are grouped and

aggregated together. The lowest member of a hierarchy is called Level 0. Dimension and Hierarchy are often used synonymously Multiple hierarchies can be assigned to the same dimension. The hierarchical relationships in the Time dimension show that

Q1 = Jul + Aug + Sep and Expense = Travel + Meals + Salary


5

Travel

Meals

Salary

Expense

Accounts

AccountsOrganization

HBS

GSE

VIT

University

HUL

Time

Jul

Aug

Sep

Q1

Year


6

Hierarchy Concepts – Understanding the Hyperion Family Tree Parents ‐Members with consolidation branch below them

Qtr1, Qtr2, Qtr3, Qtr4 are parent members ‐ containing monthly detail Children ‐Members with parents above them

Jul, Aug, and Sep are children of the parent Qtr1 Siblings ‐Members of the same parent and on the same branch (same level)

Jul, Aug, and Sep are siblings Descendants ‐Members at any level below a parent

Each member that falls in the YearTotal branch is a descendant of YearTotal


7

Year Period Scenario Version Account Entities

Fund Employee Position Project

Required Dimensions Sample Custom Dimensions

What is an Alias? An Alias is used to give a more readable name to a dimension member. Individual alias names cannot exceed 80 characters in length. Like member names, aliases must be unique across the application. Multiple aliases may be assigned to a single member.

As an illustrative example, the member name “19900“could be seen as either “General Funds” or “19900 – General Funds”

On a data input form, for example, you could choose to display members using the default, alias set 1, or set 2. You could not, however, utilize parts of set 1 with parts of set 2 within the same form.

Unless otherwise directed, Planning will use the default alias set.

8

Member Name = 19900

Default Alias Set Value = General Funds

Alias Set #1 Value = 19900 – General Funds


9

$100

Account54100

Fund 19900

Position

52861

Employee000001

VersionFinal

ScenarioBudget

PeriodJuly

YearFY11

Org26301

What is an intersection?A unique combination of dimension membersIn Planning, this intersection consists of a unique value (usually dollars) associated with a member from each dimensionPlanning has an intersection for every possible combination of members across dimensions

The volume of “intersections” we define has a direct correlation with the performance of calculations, data forms, and reports in Hyperion Planning


10

Scenarios vs. Versions

Scenarios Versions

Plan Working

Actual Final

BudgetFinalDraft 1Draft 2

ForecastFinalDraft 1Draft 2

What is the difference?Scenarios and Versions are established by the Planning Administrator and should be consistent across all applications.

Examples of Scenario members include Actual, Budget, Forecast, and Plan

Versions intersect scenario to allow snap‐shots of multiple iterations of a planning cycle and provide modeling/what‐if analysis

Scenarios are only valid for certain points in time, for example forecast is locked down for actual periods

11

Hyperion Planning Architecture

12

Data Entry Templates Collection of Planning data can

be completed by users via the Web or Excel

Data Validation parameters can be setup to notify users of thresholds

Traffic lighting can be setup to provide visual notification of data exceptions

Flexibility to enter data: Adjust button Grid Spread / Mass Allocate Lock Cells Cell text / Supporting Detail

13

SmartView - Integration with Excel All web functionality for

completing plan process is available in Excel: Data Entry Task Lists Workflow Ad-hoc

Users can take plan templates off-line to work remotely

User experience is the same whether deploying in Excel or Web – minimizing training efforts

14

SmartView - Integration with Word (or PowerPoint) Direct real‐time connection

to Hyperion Planning database

Can update data cells and text via Hyperion connection

Can insert Financial Reports or Dashboards into PowerPoint to create management decks with ability to refresh for current month or quarter data.

Workflow / Process Management Hierarchy setup

15

Increased dimensional granularity Supports Scenario, Version, Entity, and one additional dimension

(defined on setup) Support different process management organization based scenario /

version combination Pre defined promotional path Automatically find the next owner in hierarchy Based on Planning Unit Hierarchy owner assignments including

owners and reviewers

Workflow / Process Management User Flexibility

16

Data driven promotional path Support matrix organization Dynamically add reviewers Leverage threshold based submission

Process Management Flexibility Options – Take ownership, out of office, and delegation Additional approvals based on Data Validation Sorting and Filtering based on Planning Unit, Status, or Location

Planning versus Reporting

17

Hyperion Planning should be limited to the level of detail necessary for budgeting

Reporting applications can pick up plan data in real time and place alongside actual data

This actual data may be at a far more granular level

Planning carries no detail on “Contracts & Grants”, while reporting has additional (Actual) members in the hierarchy

hyperion planning overview -...

Documents