High Level Implementation Plan for Hyperion Products

on Tuesday, 01 January 2013. Posted in Blog, Oracle Financial Applications

High Level Implementation Plan for Hyperion Products


As I have received multiple requests lately on Hyperion Planning, Hyperion FDM -Financial Data management and HFM - Hyperion Financial Management. I decided to provide you with the high level steps for a typical example of an HFM implementation along with estimated timeframes for each step.  Note that the Hyperion Planning and FDM follows a similar plan and these steps are based on average implementation times (Should differ by company). 


One important point that the company must dedicate a minimum of one resource to the project to assist with the application and rules definitions, data tie-out, report building and other tasks related to the implementation. 



-          Design Meeting and BluePrint – 10-20 days

o   This stage is designed to gather all of Companies requirements.  This will include an analysis of the current and future reporting needs as well as getting an understanding of the underlying source systems and their accounting segments. 

o   An analysis of the data load requirements as they relate to FDM is performed in the blueprint phase.


-          Prototyping – 20-30 days

o   During this stage a prototype of the application will be built to demonstrate the critical features of the application.  This will ensure that the requirements were properly understood, as well as solidify the design concepts to the Company personnel.



-          System Build – 60  - 90days

o   During this stage, the full application will be built and loaded with data.  The metadata will be built based on the current EBS structure.  Rules are also built to accommodate the calculations that will be required within the system.  These rules will include elements such as currency conversion, special consolidation rules (if required), cash flow calculations, validation rules, etc.

o   Historical data will also be loaded and tied out during this stage which will allow us to test the system logic.

o   The timing of this stage is quite variable, as it will depend on the availability of the company resources.  There is also a high variability based on the cleanliness of the source data.  The amount of time related to data tie out should not be underestimated.


-          System Testing 10-15 days

o   This stage will include a full system test with users.

-          Training 5-10 days

-          Rollout Support 5-10 days

A typical HFM implementation varies between 4- 9 months depending on the complexities and number of RICE(Reports, Interfaces and Extension).

ZOO Comment

Copyright 2018 Appsconsultant.com. All rights reserved.