Solution

The consulting team took over the project by starting with a redesign focusing on the Hyperion Enterprise application, including Hyperion Reports/Hyperion Retrieve for production reporting and HAL for data integration. This was the tactical plan. All work that was built and defined at this point was documented and saved for the HFM design that was to happen after the company spinoff. Strategically, the plan was still to move to HFM, when resources and hardware issues could be addressed.

The issue here was that they needed an immediate consolidation system. Since user access and time were both at a premium, changing into a new system should not have been the priority.

During the project, all of the users who needed access to Budget and Forecast data realized they would want access. This created an issue for the project team. First, they were flooded with reports and requests. Second, there was not a planned budget for training the additional users. The team was forced to change gears and strategy for training. They moved to a “train the trainer” approach so they could cover the entire set of end users.