Latest episode
TM1 to OneStream migration that starts by reading every rule in the cubes.
Constancia, an EPM consultancy, moves groups off TM1 (IBM's planning software, now sold as Planning Analytics) onto OneStream (EPM software). Every rule on every cube is read before the price is fixed.
OneStream at a glance
- Covers
- Planning, financial close and consolidation, reporting and analytics.
- Data in
- Direct integration to Oracle, SAP, Microsoft, IBM, Infor, Workday, Databricks and Snowflake.
- Our record
- 58 implementations over 35 years.
The rules decide a TM1 move, and each cube carries its own.
A TM1 to OneStream migration moves the planning cubes, their rules and the reports on top onto OneStream, for a finance team with a date. TM1 holds its logic in a rules file attached to each cube and in the processes that load it. The rules file is where the migration's time goes, and the cubes follow it.
Each Planning Analytics release carries its own lifecycle date, and the release a group runs sets the date it works to. Constancia has completed 58 OneStream implementations over 35 years and prices a TM1 route after reading the rules files.
Where a cube's rules file has grown for 10 years and its author has left, nobody can say which lines still fire. The survey reads the file end to end and marks each line. The marked file is the first document the design team reads.
6 steps move the TM1 rules, and the cubes are rebuilt once the rules are sorted.
Every step is named for the object it moves. The rules go before the cubes because a cube on OneStream is designed around the calculations that survive.
- 01
List the cubes
We list every cube, its dimensions, the rules file attached to it and the TurboIntegrator processes that load it.
- 02
Read every rule
Each line of each rules file is read and marked as a calculation, a feeder or a load, with the reports that depend on it.
- 03
Sort the rules 3 ways
A named person in FP&A marks each rule as kept, rewritten or dropped, with the reason beside it.
- 04
Design the planning model
The dimensions the cubes shared, and the ones they did not, are designed once as OneStream dimensions the close can use too.
- 05
Rebuild the rules that survive
Kept and rewritten rules become OneStream business rules and member formulas, each traced to the TM1 line it came from.
- 06
Run the plan twice
TM1 and OneStream calculate the same forecast cycle until the outputs agree, and FP&A signs the cut-over.
The dropped rules are listed in the survey document, so a line that turns out to be needed can be found there.
TM1 objects sort into 3 columns, and the feeders fill the third.
The survey puts each object in the TM1 estate into 1 of 3 columns before a cube is designed. The feeders go in the third column because OneStream calculates without them.
| Maps directly | Is rebuilt | Is dropped | |
|---|---|---|---|
| Dimensions | Entity, account, time and version members in use. | Dimensions built differently in 2 cubes, settled to 1. | Elements no view or report has read. |
| Cubes | Input cubes with 1 clear purpose. | Calculation cubes, redesigned as rules on the shared model. | Staging cubes that existed to move data between other cubes. |
| Rules | Simple allocations and roll-ups. | Rules with 2 jobs, split into 2 OneStream rules with a written reason each. | Rules that write to cells no report reads. |
| Feeders | No feeder maps, because OneStream calculates without them. | The calculation each feeder served, checked in the rebuilt rule. | Every feeder line. |
| TurboIntegrator processes | Ledger loads with a 1 to 1 mapping. | Processes that reshape the extract, as OneStream data sources and transformation rules. | Processes for 1-off loads and old chores. |
| Views and reports | Standard management reports. | Excel reports built on cube views, rebuilt as OneStream cube views and dashboards. | Personal views saved by people who have left. |
A TM1 estate with 4 characteristics belongs on this route.
- 01
Cubes older than the team
The rules were written by people who have left, and the plan still runs on them every cycle.
- 02
A close on another system
The group wants the plan and the close on 1 model, and the consolidation still runs in HFM, BPC or a workbook.
- 03
A date from IBM's lifecycle
The lifecycle date on the group's release sets the date the migration works back from.
- 04
A forecast the board wants to trace
The board has asked why the forecast moved, and the answer sits in a rule nobody can point to.
A group that keeps TM1 as its plan and wants a new consolidation reads the implementation page first.
The other 4 source systems have their routes written up separately.
Hyperion to OneStream
An HFM consolidation moves once each hierarchy has a named purpose.
Read the Hyperion routeSAP BPC to OneStream
A BPC model gives up its plan and its close as 2 designs on 1 model.
Read the BPC routeFCCS to OneStream
FCCS moves when a group wants its Oracle applications on 1 model.
Read the FCCS routeAnaplan to OneStream
An Anaplan plan moves onto the same dimensions as a newly designed close.
Read the Anaplan route
See more on our
Subscribe on YouTube
Every Sunday, 6am
The Sunday Close.
Our weekly newsletter on AI in finance.
Yours to enjoy with your Sunday morning coffee.
- AI in finance observations from Alex (CEO) and Brad (COO)
- Newest video from our YouTube channel
- AI in finance trends we have spotted each week
Tell us the date you are working to.
The people who would do the work read every message and reply inside 2 working days.