HomeSectorsContact Talk to a consultant
  1. Home
  2. Services

Oracle EPM Cloud implementation and migration

S1 · Working paper

Oracle EPM Cloud implementation

From model design to go-live, with the finance team inside the project from day one.

01

Design

The close process exactly as it is today: who supplies each figure, who reviews it and by when. The dimensional model and the calendar, written down and validated with finance. It comes from the process, not from a template.
02

Build

Business judgement on the rules that are open to interpretation. The module configured in short iterations, shown working rather than on slides.
03

Testing

Your own figures and your own close calendar. The cycle tested end to end with those figures, not with sample data.
04

Go-live

The first real close on the new system. The consultant inside that close, not on the other side of a ticket.
05

Support

The team that will own the model. The handover so that team can maintain it without depending on us.

S2 · Working paper

On-Premise migration

Moving off Hyperion and other local installations to Oracle EPM Cloud, without losing history or the logic that already works.

01

Inventory

Access to the current environment and to the person who actually knows it. The catalogue of what is really built: rules, hierarchies, reports, and whatever nobody uses any more.
02

Criteria

The decision on what gets retired. That one is not ours to make. The proposal of what moves as is, what gets redesigned and what gets switched off, with the cost of each option.
03

Transfer

The reference closes to reconcile against. Metadata, history and rules moved across and reconciled against the source system.
04

Parallel run

One period closed twice, in the old system and the new one. The comparison between the two, difference by difference, until none is left unexplained.
05

Decommission

Shutting down the local environment and its licences. The new environment with a full period already closed in it.

What we get hired for

The project with a clock of its own: end of support for Hyperion on-premise sets the date, and the migration will not wait for the next budget.