Key Considerations for a Successful Hyperion Planning Implementation


Published on

Presentation by Mark Hite at Kaleidoscope 2010 on project management best practices for implementing Hyperion Planning.

Published in: Business
  • #Essbase Essbase Tutorial (Videos and Books) Just $24.95
    Are you sure you want to  Yes  No
    Your message goes here
  • More than 5000 registered IT consultants and Corporates.Search for IT online training Providers at
    Are you sure you want to  Yes  No
    Your message goes here
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Key Considerations for a Successful Hyperion Planning Implementation

  1. 1. Key Considerations for a Successful Hyperion Planning Implementation June 29, 2010 Mark Hite, Practice Manager Ranzal & Associates
  2. 2. <ul><li>INTRODUCTIONS </li></ul><ul><li>KEY PROJECT PHASES </li></ul><ul><li>RECOMMENDED BUILD TECHNIQUES </li></ul><ul><ul><li>Application Definition </li></ul></ul><ul><ul><li>Delineate Plan Types </li></ul></ul><ul><ul><li>Define Dimensionality </li></ul></ul><ul><ul><li>Metadata Integration </li></ul></ul><ul><ul><li>Data Integration </li></ul></ul><ul><ul><li>Building a Planning Model </li></ul></ul><ul><ul><li>Development of Forms </li></ul></ul><ul><ul><li>Development of Calculations </li></ul></ul><ul><ul><li>Process Flow / Control </li></ul></ul><ul><ul><li>Define Security </li></ul></ul>Agenda
  3. 3. <ul><ul><li>Introductions </li></ul></ul>
  4. 4. <ul><li>Founded in 1996, Ranzal has implemented Hyperion solutions for 500+ companies (800+ projects since the acquisition) </li></ul><ul><li>Oracle / Hyperion Platinum Partner - Highest Status </li></ul><ul><li>Hyperion “Americas Reseller” & “Partner of the Year” </li></ul><ul><ul><li>1999, 2005 & 2007 </li></ul></ul><ul><li>Certified EPM Consultants & Instructors </li></ul><ul><li>Vertical Expertise with High-Profile Clients from Coast to Coast </li></ul><ul><ul><li>East Coast & West Coast Presence </li></ul></ul><ul><li>Sound Project Methodology Insures Project Success </li></ul><ul><ul><li>Support Business Applications from start to finish </li></ul></ul><ul><li>One of the Largest Hyperion Practices in the U.S.  </li></ul><ul><li>“ Best Planning & Essbase Practices with Best HFM Practice” </li></ul><ul><ul><li>Hyperion Development utilizes Ranzal for Planning, Essbase and HFM product direction </li></ul></ul>About Ranzal Regarded in the industry as one of the &quot;BEST” at leveraging OLAP technology to develop EPM Applications
  5. 5. <ul><li>Our team has been involved in 800+ successful EPM Implementations </li></ul><ul><ul><li>Financial Consolidation & Management Reporting </li></ul></ul><ul><ul><li>Budgeting & Planning </li></ul></ul><ul><ul><li>Profitability Management Solutions </li></ul></ul><ul><ul><li>Business Intelligence and Data Warehousing </li></ul></ul><ul><ul><li>Infrastructure Planning and Performance Tuning </li></ul></ul><ul><ul><li>Business Process and Project Management </li></ul></ul><ul><li>Strong client portfolio across leading Industry Sectors including </li></ul><ul><li>Certified consultants and instructors </li></ul><ul><ul><li>Hyperion Essbase, Hyperion Planning, Hyperion Financial Management, HPCM, Hyperion Enterprise, Hyperion Strategic Finance, Hyperion BI+ (Web Analysis, Financial Reports, Interactive Reporting, Production Reporting), Hyperion Data Relationship Management, Hyperion Financial Data Quality Management, Data Services (including ETL, Warehousing) </li></ul></ul><ul><ul><li>Financial Services </li></ul></ul><ul><ul><li>Insurance </li></ul></ul><ul><ul><li>Retail / Consumer Packaged Goods </li></ul></ul><ul><ul><li>Manufacturing </li></ul></ul><ul><ul><li>Pharmaceutical & Hospital </li></ul></ul><ul><ul><li>Hospitality / Travel / Entertainment </li></ul></ul><ul><ul><li>High Technology / E-business </li></ul></ul><ul><ul><li>Energy / Utilities </li></ul></ul><ul><ul><li>Distribution </li></ul></ul><ul><ul><li>Government </li></ul></ul><ul><ul><li>Other </li></ul></ul>Application & Industries
  6. 6. <ul><ul><li>Key Project Phases </li></ul></ul>
  7. 7. Project Phases Analyze/Design Build Test Rollout Infrastructure Build Application Install Back-End Build Front-End Build
  8. 8. Infrastructure (Simple)
  9. 9. Infrastructure (Complex)
  10. 10. Analyze vs. Design <ul><li>Analyze </li></ul><ul><li>Requirements unknown or undefined </li></ul><ul><li>Existing business processes need to be updated </li></ul><ul><li>Existing business processes not known or documented </li></ul><ul><li>Desire to re-engineer to align with business vision or industry best practices </li></ul><ul><li>Deliverables </li></ul><ul><li>As-Is vs. To-Be Processes </li></ul><ul><li>Functional Requirements </li></ul><ul><li>Technical Requirements </li></ul><ul><li>Project Roadmap & Timeline (High Level) </li></ul><ul><li>Design </li></ul><ul><li>Key requirements are understood </li></ul><ul><li>Future business processes are known </li></ul><ul><li>Basic understanding of technology being used for build </li></ul><ul><li>Deliverables </li></ul><ul><li>Design Document </li></ul><ul><li>Proof of Concept / Prototype * </li></ul><ul><li>Infrastructure Architecture </li></ul><ul><li>Finalize Scope, Schedule & Budget </li></ul><ul><li>Project Strategies (Training, Testing, etc) </li></ul>
  11. 11. Biggest Risks to Planning Projects <ul><li>LACK OF AVAILABLE METADATA & DATA </li></ul><ul><ul><li>Clients often underestimate the effort required to source and validate data and master data, and this is a frequent reason for project delays </li></ul></ul><ul><ul><li>The level of effort must be aligned with the quality of data, number of data sources, and degree of change (e.g., new COA) </li></ul></ul><ul><li>LACK OF CLIENT RESOURCES </li></ul><ul><ul><li>Technical – It is critical to identify the administrators of the new system early on, and ensure they are properly trained for rollout </li></ul></ul><ul><ul><li>Functional - Clients sometimes do not dedicate enough resources to the project effort as the project is viewed as simply a technology implementation </li></ul></ul><ul><li>LACK OF CLARITY IN BUSINESS PROCESSES </li></ul><ul><ul><li>Planning systems by their nature attempt to predict the future. Clients sometimes have difficulty identifying which disparate elements of their planning process should go into the application, particularly if different areas of the organization have different models. </li></ul></ul>
  12. 12. Critical Success Factors <ul><li>Clearly Defined and Communicated Project Goals </li></ul><ul><li>Key Stakeholder Participation and Approval </li></ul><ul><li>Finance and IT Involvement Throughout Entire Project </li></ul><ul><li>Clearly Defined, Reviewed, and Approved Application Design </li></ul><ul><li>Ownership and Accountability for Project Tasks </li></ul><ul><li>Thorough Quality Assurance and Testing </li></ul><ul><li>Communication of Company-wide Benefits </li></ul><ul><li>Proper Administrator and End User Training </li></ul><ul><li>Consistent Project Management </li></ul>
  13. 13. <ul><ul><li>Planning Design </li></ul></ul><ul><ul><li>Recommended Practices </li></ul></ul>
  14. 14. Basic Build Approach <ul><li>Application Definition </li></ul><ul><li>Delineate Plan Types </li></ul><ul><li>Define Dimensionality </li></ul><ul><li>Metadata Integration </li></ul><ul><li>Data Integration </li></ul><ul><li>Building a Planning Model </li></ul><ul><li>Development of Forms </li></ul><ul><li>Development of Calculations </li></ul><ul><li>Process Flow / Control </li></ul><ul><li>Define Security </li></ul>
  15. 15. Application Definition <ul><li>SINGLE PLANNING APPLICATION </li></ul><ul><ul><li>Allows for three custom plan types </li></ul></ul><ul><ul><li>Two “modules” – Workforce & Capex </li></ul></ul><ul><li>APPLICATION SETUP </li></ul><ul><ul><li>Classic </li></ul></ul><ul><ul><li>EPMA </li></ul></ul><ul><li>COMMON PLAN TYPES </li></ul><ul><ul><li>Core – GL Account, Entity </li></ul></ul><ul><ul><li>Revenue – Product, Customer </li></ul></ul><ul><ul><li>Salary / Workforce – Employee, Position </li></ul></ul><ul><ul><li>Capital / Capex – Asset Category, Projects, etc. </li></ul></ul><ul><ul><li>Sales – Customer, Sales Rep </li></ul></ul><ul><ul><li>Balance Sheet / Cash Flow </li></ul></ul>
  16. 16. Application Definition <ul><li>SINGLE APPLICATION BENEFITS </li></ul><ul><ul><li>Metadata is shared across an application </li></ul></ul><ul><ul><li>Common Versioning, Scenarios between plan types </li></ul></ul><ul><ul><li>Business Rule Efficiency within same app (XREF) </li></ul></ul><ul><ul><li>Shared Interface for forms and rules between plan types </li></ul></ul><ul><ul><li>Leverage common set of task lists, right click menus, smart lists, and personal variables </li></ul></ul><ul><li>MULTIPLE APPLICATION USE CASES </li></ul><ul><ul><li>Common for separate operating units w/ disparate planning processes </li></ul></ul><ul><ul><li>Allows for distinct processing windows </li></ul></ul><ul><ul><ul><li>US vs. Intl </li></ul></ul></ul><ul><ul><li>Security – Financials vs. Salary Detail </li></ul></ul><ul><ul><li>Ran out of plan types </li></ul></ul>
  17. 17. Delineate Plan Types <ul><li>WHAT ARE THE CAPEX / WORKFORCE MODULES? </li></ul><ul><ul><li>A set of pre-built forms, rules, and menus for planning Salary and Capital expenditures. </li></ul></ul><ul><ul><li>Pre-built functionality – fully customizable </li></ul></ul><ul><ul><li>Out of the box functionality to calculate: </li></ul></ul><ul><ul><ul><li>WFP – Salaries, Payroll Taxes, Benefits, etc. Based on attributes associated with the employee. </li></ul></ul></ul><ul><ul><ul><li>Capex – Depreciation, Capital Spending by Asset Categorization. </li></ul></ul></ul><ul><li>EXPECTATIONS </li></ul><ul><ul><li>No one will use the modules out of the box with no customization. </li></ul></ul><ul><ul><li>Key is to use out of the box functionality with the right blend of customization. </li></ul></ul><ul><ul><li>Expected customization includes: </li></ul></ul><ul><ul><ul><li>Updating Smart List attributes for use within an organization </li></ul></ul></ul><ul><ul><ul><li>Modification to forms / rules to allow for budget & forecast processes that converge. </li></ul></ul></ul><ul><ul><ul><li>Updating metadata – Employees, Asset Category, etc. </li></ul></ul></ul><ul><ul><ul><li>Adding a requisition number input field </li></ul></ul></ul>
  18. 18. Delineate Plan Types <ul><li>WHEN DO I NEED A NEW PLAN TYPE </li></ul><ul><ul><li>A model needs a different set of dimensionality </li></ul></ul><ul><ul><ul><li>Revenue modeling for the organization is done by product and customer </li></ul></ul></ul><ul><ul><ul><li>Salary modeling is done by employee and position </li></ul></ul></ul><ul><ul><ul><li>Project Planning is done by Project Number </li></ul></ul></ul><ul><ul><ul><li>Capital modeling is done by asset classification </li></ul></ul></ul><ul><ul><li>Inter-dimensional Irrelevance </li></ul></ul><ul><ul><ul><li>Does my Core GL plan type need Product, Employee and / or Project #? </li></ul></ul></ul><ul><ul><ul><li>Impacts performance of forms, business rules, and reports. </li></ul></ul></ul><ul><ul><ul><li>Want to minimize number of stored dimensions for each plan type. </li></ul></ul></ul><ul><li>IMPACTS OF A NEW PLAN TYPE </li></ul><ul><ul><li>Data Movements between Plan Types </li></ul></ul><ul><ul><li>Additional Essbase Cube to optimize </li></ul></ul><ul><ul><li>Metadata & Data Integration Considerations </li></ul></ul>
  19. 19. Define Dimensionality <ul><li>DIMENSION </li></ul><ul><ul><li>Stored hierarchies within an application </li></ul></ul><ul><ul><li>Core – Accounts, Entities, Time, Years, Scenario, Versions </li></ul></ul><ul><ul><li>Revenue – Core + Product, Customer, Sales Person </li></ul></ul><ul><ul><li>Capital – Core + Asset Category, Project </li></ul></ul><ul><ul><li>Salary – Core + Employee, Position </li></ul></ul><ul><li>ATTRIBUTE </li></ul><ul><ul><li>Associated with a base dimension </li></ul></ul><ul><ul><li>A dimension member can be associated with a single attribute member from an attribute dimension. </li></ul></ul><ul><ul><li>Examples </li></ul></ul><ul><ul><ul><li>Start Date (Employee) </li></ul></ul></ul><ul><ul><ul><li>Address (Customer) </li></ul></ul></ul><ul><ul><ul><li>Brand (Product) </li></ul></ul></ul><ul><ul><ul><li>Growth, Productivity, Maintenance (Project) </li></ul></ul></ul>
  20. 20. Define Dimensionality <ul><li>SMART LIST </li></ul><ul><li>A member in an outline (often an account) that is represented as a drop down within the data grid. </li></ul><ul><li>Smart Lists can be used to drive business rules </li></ul><ul><li>Smart Lists cannot be sliced and diced like dimensions * </li></ul><ul><li>Smart Lists can be reported on within Hyperion Reports </li></ul><ul><li>Stored as numeric value in Essbase </li></ul><ul><li>Textual Value show in Planning Forms </li></ul><ul><li>Can be predefined in Essbase </li></ul><ul><li>Smart Lists – No adapter, load right to tables </li></ul><ul><li>11.1.2 supports model to ASO for increased reporting capabilities </li></ul>
  21. 21. Define Dimensionality <ul><li>DATA ELEMENT (TEXT / DATE) </li></ul><ul><li>Allow user to input text and date directly into a cell in Planning </li></ul><ul><li>Can leverage in Hyperion Reports </li></ul><ul><li>Text stored as numeric lookup relationally – HSP_TEXT_CELL_VALUE </li></ul><ul><li>Date stored as number 20090101 </li></ul><ul><li>Can be predefined in Essbase </li></ul><ul><li>No adapter, load right to tables </li></ul>
  22. 22. Metadata Integration <ul><li>METADATA MANAGEMENT VS. ETL TOOLS </li></ul><ul><ul><li>They are not the same thing </li></ul></ul><ul><ul><li>A metadata management tools provides you with a graphical interface to manage your metadata across disconnected applications. </li></ul></ul><ul><ul><li>An ETL tool moves data from one place to another </li></ul></ul><ul><li>METADATA MANAGEMENT TOOLS </li></ul><ul><ul><li>EPMA </li></ul></ul><ul><ul><ul><li>Relatively new tool (BPMA,) </li></ul></ul></ul><ul><ul><ul><li>Essentially “DRM” for EPM Applications </li></ul></ul></ul><ul><ul><ul><li>Ability to synch Planning, HFM & Essbase dimensions across multiple applications </li></ul></ul></ul><ul><ul><ul><li>V11 – Stable, Much Improved </li></ul></ul></ul><ul><ul><ul><li>Update via Interface Tables – ETL, or Flat File </li></ul></ul></ul><ul><ul><ul><li>EPMA File Generator – Creates ADS Files </li></ul></ul></ul><ul><ul><li>DRM </li></ul></ul><ul><ul><ul><li>Full blown metadata management tool </li></ul></ul></ul><ul><ul><ul><li>Supports metadata management across any toolset – Hyperion, ERP, etc. </li></ul></ul></ul><ul><ul><ul><li>Agnostic – read from any source, write to any source </li></ul></ul></ul><ul><ul><ul><li>Does not have adapters to source / target systems </li></ul></ul></ul><ul><ul><ul><li>Flat file extracts created from DRM to load into Planning </li></ul></ul></ul>
  23. 23. Metadata Integration <ul><li>ETL TOOLS </li></ul><ul><ul><li>ODI </li></ul></ul><ul><ul><ul><li>“ HAL Replacement” </li></ul></ul></ul><ul><ul><ul><li>Limited Use ODI Bundled with EPM toolset </li></ul></ul></ul><ul><ul><ul><li>Planning must be a source or target to use </li></ul></ul></ul><ul><ul><ul><li>Relational Staging Repository where a lot of the work is done </li></ul></ul></ul><ul><ul><ul><li>ELT – Extract, Load and Transfer Tool </li></ul></ul></ul><ul><ul><li>DIM </li></ul></ul><ul><ul><ul><li>Adapters that connect directly to Planning </li></ul></ul></ul><ul><ul><ul><li>Additional Licensing Costs </li></ul></ul></ul><ul><ul><ul><li>For Informatica shops </li></ul></ul></ul><ul><ul><ul><li>Functionally very similar to ODI </li></ul></ul></ul><ul><ul><li>HAL </li></ul></ul><ul><ul><ul><li>Not an option for new clients </li></ul></ul></ul><ul><ul><ul><li>Still works in 11X for legacy clients but not supported </li></ul></ul></ul><ul><li>OTHER UPDATE METHODS </li></ul><ul><ul><li>Essbase </li></ul></ul><ul><ul><li>Outline Load Batch Utility </li></ul></ul><ul><ul><li>Manual Update </li></ul></ul>
  24. 24. Data Integration <ul><li>SOURCES </li></ul><ul><ul><li>General Ledger – Lawson, Oracle, Peoplesoft, SAP, Great Plains </li></ul></ul><ul><ul><li>Payroll – Ceridian, Lawson HRIS </li></ul></ul><ul><ul><li>Fixed Assets – Lawson, Oracle Project, Navision </li></ul></ul><ul><ul><li>Project Tracking – Oracle Project, JDE </li></ul></ul><ul><ul><li>Billing System </li></ul></ul><ul><ul><li>Order Management </li></ul></ul><ul><ul><li>EDW </li></ul></ul><ul><ul><li>Manual Load File </li></ul></ul><ul><ul><li>Collect via Planning Form </li></ul></ul><ul><ul><ul><li>Currency Rates </li></ul></ul></ul><ul><ul><ul><li>Benefit Rates (FICA Max, FICA %) </li></ul></ul></ul><ul><li>INTEGRATION OPTIONS </li></ul><ul><ul><li>Essbase Load Rules </li></ul></ul><ul><ul><ul><li>SQL Interface </li></ul></ul></ul><ul><ul><ul><li>Flat Files </li></ul></ul></ul><ul><ul><ul><li>MAXL Automation </li></ul></ul></ul><ul><ul><ul><li>Simple ETL </li></ul></ul></ul><ul><ul><li>ODI / DIM / HAL </li></ul></ul><ul><ul><ul><li>ETL Tools, use when there is heavy file manipulation </li></ul></ul></ul>
  25. 25. Data Integration
  26. 26. Building a Planning Model <ul><li>KEY CONSIDERATIONS </li></ul><ul><li>What data is needed to facilitate input? </li></ul><ul><li>What data needs to be collected from end users? </li></ul><ul><li>Are there supporting drivers that must be input? </li></ul><ul><li>Are there calculations that need to be processed before input? </li></ul><ul><li>Read vs. Write on data form elements </li></ul><ul><li>Are there calculations that need to be processed after input? Before Input? </li></ul><ul><li>TIPS </li></ul><ul><li>Break the process into steps if possible </li></ul><ul><li>Use menus or task lists to drive navigation </li></ul><ul><li>Simplify the user experience, provide tools to facilitate navigation </li></ul><ul><li>Try not to clutter and overcomplicate a form </li></ul>
  27. 27. <ul><ul><li>Development of Forms </li></ul></ul>
  28. 28. Development of Forms <ul><li>PERFORMANCE </li></ul><ul><li>Balance performance with functionality </li></ul><ul><li>Load Performance – 3 seconds or less </li></ul><ul><li>Save Performance – 3 seconds of less </li></ul><ul><li>Hone business rules </li></ul><ul><ul><li>Focus on fewer blocks – FIX (Entity), FIX (Scenario, Version) </li></ul></ul><ul><ul><li>Don’t calculate more than you need to </li></ul></ul><ul><ul><li>Balance form calculations with an hourly ‘sweep’ </li></ul></ul><ul><ul><li>Poorly performing business rules can stack up and kill Essbase performance </li></ul></ul><ul><li>PERFORMANCE TIPS </li></ul><ul><li>Suppress Missing Rows vs. Suppress Blocks </li></ul><ul><li>Rows vs. Columns vs. Page </li></ul><ul><li>Isolate Performance Issue – Form vs. Rules </li></ul><ul><li>Query Issue – Size or Poorly Designed Essbase Cube? </li></ul><ul><li>Block Size Balancing Act – Query vs. Calculations </li></ul>
  29. 29. Development of Forms <ul><li>DESIGN TIPS </li></ul><ul><li>Large Sparse Dims on Rows – (Improvements to GUI in Talleyrand) </li></ul><ul><li>Turn on Attribute Display </li></ul><ul><ul><li>Suppress Missing Block </li></ul></ul><ul><li>Show member formulas </li></ul>
  30. 30. Development of Forms <ul><li>DESIGN TIPS </li></ul><ul><li>Startup Message to Guide Blank Forms </li></ul><ul><li>Column Definition </li></ul><ul><ul><li>Drivers & Commentary in BegBalance Member </li></ul></ul><ul><ul><li>Data Values in IDESC (YearTotal) </li></ul></ul>
  31. 31. Development of Forms <ul><li>Use Flag Members to drive form layout </li></ul><ul><ul><li>Smart List to drive Flag </li></ul></ul><ul><ul><li>UDA’s to drive form definition </li></ul></ul><ul><ul><li>Flag Member – Set flag based on UDA definition and Smart List Selection </li></ul></ul>
  32. 32. Development of Forms <ul><li>Simple Form </li></ul><ul><li>Enhanced Forms </li></ul>
  33. 33. Development of Forms <ul><li>Control Navigation with a Menu </li></ul>
  34. 34. <ul><ul><li>Development of Calculations </li></ul></ul>
  35. 35. Development of Calculations <ul><li>TIPS & TRICKS </li></ul><ul><li>Calculations & Forms Should be Developed in Tandem </li></ul><ul><li>Calculation Manager </li></ul><ul><ul><li>Graphical Web Based Rules Builder </li></ul></ul><ul><ul><li>Pre-built Templates </li></ul></ul><ul><ul><li>Requires EPMA Integration (Talleyrand support for Classic) </li></ul></ul><ul><ul><li>Ability to Convert HBR to CM Rules </li></ul></ul><ul><li>Alternatives to Drive Calculations </li></ul><ul><ul><li>Member Formulas </li></ul></ul><ul><ul><li>Business Rules / Calc Manager Rules </li></ul></ul><ul><ul><li>Essbase Member Calc Formula </li></ul></ul>
  36. 36. Development of Calculations <ul><li>Essbase Member Formula </li></ul><ul><li>Simple Member Calculation </li></ul><ul><li>Dependencies - Outline Order Important </li></ul><ul><li>Calculations that don’t require user input </li></ul><ul><li>Calculations don’t require moving data between plan types </li></ul><ul><li>Can be run upon save of form – ‘Calc members on form’ </li></ul>
  37. 37. Development of Calculations <ul><li>Business Rules </li></ul><ul><li>Allow for user input to the rule </li></ul><ul><li>Allow for passing through variables from the form to the rule </li></ul><ul><li>Multiple Members Calculated Upon Form Save with Dependencies </li></ul><ul><li>Can be launched on save, or from a right click menu </li></ul><ul><li>Typically more procedural than member formula </li></ul><ul><li>Leverage BR to move data between plan types </li></ul>
  38. 38. Development of Calculations <ul><li>Essbase Member Calc Script </li></ul><ul><li>Write multiple member formula’s in an Essbase member </li></ul><ul><li>Place member on form, and hide </li></ul><ul><li>Allows for procedural member formulas ala Business Rules </li></ul><ul><li>Run on save of form </li></ul><ul><li>Cannot allow user input to calc </li></ul><ul><li>Cannot move data between plan types </li></ul>
  39. 39. Development of Calculations <ul><li>DESIGN CONSIDERATIONS </li></ul><ul><li>Minimize Calculations </li></ul><ul><ul><li>Run Time Prompts – Align w/ Page </li></ul></ul><ul><ul><li>IANCESTORS (Run Time Prompt) to aggregate instead of CALC DIM </li></ul></ul><ul><li>Beware Run on Save / Load </li></ul><ul><li>Launch Rules from Right Click Menu </li></ul><ul><li>Sequences </li></ul><ul><ul><li>Calculation in Current Plan Type </li></ul></ul><ul><ul><li>XREF Data to Core Plan Type </li></ul></ul><ul><li>XREF Dangers </li></ul><ul><ul><li>Slow across applications </li></ul></ul><ul><ul><li>Create Block Issues </li></ul></ul><ul><ul><ul><li>Create Blocks in Business Rule </li></ul></ul></ul><ul><ul><ul><li>Schedule hourly “sweep” to catch any issues - DATAEXPORT </li></ul></ul></ul><ul><li>Currency Conversion Limitations </li></ul><ul><ul><li>Rates stored High </li></ul></ul><ul><ul><li>Manual Input of Rates </li></ul></ul><ul><ul><li>Pros – Entity has requirement to plan in different local currencies </li></ul></ul>
  40. 40. <ul><ul><li>Process Flow / Control </li></ul></ul>
  41. 41. Process Flow / Control <ul><li>Form / Folder Organization </li></ul><ul><ul><li>Logically name forms and folders </li></ul></ul><ul><ul><li>Order based on ‘Steps’ </li></ul></ul><ul><li>Right Click Menus </li></ul><ul><ul><li>Jump to other forms </li></ul></ul><ul><ul><li>Launch Rules </li></ul></ul><ul><ul><li>Launch Reports </li></ul></ul><ul><li>Task Lists </li></ul><ul><ul><li>Guide user through a task list </li></ul></ul><ul><ul><li>User can check off items as they complete </li></ul></ul><ul><ul><li>Review completed vs. outstanding tasks </li></ul></ul><ul><li>Workflow </li></ul><ul><ul><li>Being rewritten due to current limitations </li></ul></ul><ul><ul><li>Targeted for Talleyrand (next release) </li></ul></ul>
  42. 42. <ul><ul><li>Security </li></ul></ul>
  43. 43. Define Security <ul><li>PROCESS </li></ul><ul><ul><li>Setup Groups & Users in Shared Services </li></ul></ul><ul><ul><li>Assign Access in Planning & Workspace </li></ul></ul><ul><ul><li>Push Security to Essbase </li></ul></ul><ul><li>SETUP USERS & GROUPS IN SHARED SERVICES </li></ul><ul><li>Define Groups </li></ul><ul><ul><li>ALL_PLANNING_GROUP - Handles basic provisioning tasks – Version, Scenario, Accounts </li></ul></ul><ul><ul><li>ENTITY_PLANNING_GROUPS - Most detail security occurs along the Entity dimension </li></ul></ul><ul><ul><li>FUNCTIONAL_PLANNING_GROUPS - In charge of a functional area – for example – margin detail </li></ul></ul><ul><li>Assign Users to Groups </li></ul><ul><li>PITFALLS / SUGGESTIONS </li></ul><ul><li>Groups within Groups </li></ul><ul><li>AD Groups vs. Planning Level Groups </li></ul><ul><li>11X – Apply Security to Folders </li></ul>
  44. 44. Mark Hite [email_address] Questions
  45. 45. Key Considerations for a Successful Hyperion Planning Implementation June 30, 2010 Mark Hite, Practice Manager Ranzal & Associates