Latest episode
OneStream managed services that get smaller every year as your team takes over.
Constancia, an EPM consultancy, runs a OneStream (EPM software) application after go-live: releases, model changes, month-end cover and upgrades. The scope is written to fall as your team takes each job over.
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.
OneStream managed services keep a live application running after go-live, through the platform's releases, the group's own model changes and the month-end run. Constancia sells the service on a scope that falls each year, because a scope that grows is paying for runbooks nobody wrote.
- Covers
- OneStream's releases, the group's model changes, month-end support and the upgrades between them.
- Scoped by
- The job, with a date against each one for the group's own team to take it over.
- Ends when
- The group's administrator runs every routine job, and what remains is cover for new work.
Routine running of OneStream passes to your team, and new work stays with us.
OneStream managed services cover the running of a live application for a finance team that has gone live and has no second administrator yet. Releases, model changes and month-end cover are routine, and new work is the fourth kind. A release lands on OneStream's calendar and an acquisition on the board's, and the service covers both.
Constancia has done 58 OneStream implementations over 35 years, and the managed service after each one is scoped by the job. Each job carries a date for the group's team to take it over, and a job the team runs comes off at the next review.
Where the group controller phones the implementer on day 3 of each close to rerun the same load, a runbook is missing. The managed service writes that runbook first and then hands the job back. The controller keeps the runbook, and the job comes off the scope at the next review.
A OneStream managed service carries 6 jobs, and 5 of them have a handover date.
The routine jobs are the ones a trained administrator takes over, and each has a date in the scope. New work stays with the service, because an acquisition is design work with its own survey.
- 01
Release management
Each OneStream release is tested against the group's own model in a copy before it reaches the live application.
- 02
Model changes
New entities, accounts and hierarchy members are added under change control, with the reason for each written next to it.
- 03
Month-end cover
A consultant is on call through the close calendar until the group's administrator has run 3 closes without a call.
- 04
Upgrades
The platform upgrade is planned around the group's close calendar, so the year-end never lands on a new version.
- 05
Monitoring and fixes
Failed loads, slow consolidations and broken reports are found by the service before an entity accountant reports them.
- 06
New work
New work has no handover date, because an acquisition, a new report or a new plan is design work and is priced after a survey.
The scope is reviewed each year, and every job the group's team now runs comes off it. The review is a written document, and the CFO signs it.
4 positions make a group a fit for the managed service.
The 4 positions share 1 feature, which is that the group's own team cannot yet run every job on the list.
- 01
Just live
The application went live this year and the group's administrator is still learning the release cycle.
- 02
1 administrator
The group has 1 person who can run the system, and a holiday or a resignation would stop the close.
- 03
An estate that changes
An acquisition a year, a new ERP or a divestment means the model changes more often than the team can absorb.
- 04
A board that wants a date
The CFO wants a written date for when the finance team runs the system alone, and the scope carries one.
A group with 2 trained administrators and a stable estate needs cover for new work and nothing more.
The scope falls in 3 stages as the group's team takes each job.
The written scope names the stage the group is in and the date it moves to the next. The move happens when the administrator has run the job, and never on a calendar alone.
- 01
We run, you watch
The service runs releases, model changes and month-end cover, and the group's administrator sits in on each one.
- 02
You run, we watch
The administrator runs the routine jobs and the service checks each one, on call through the close.
- 03
You run, we answer
The group runs the application, and the service covers new work and the questions that arrive with an acquisition.
A group that has gone live has 3 more pages worth reading.
Each of the 3 sits 1 step before or after this service in the life of the application.
OneStream training
The 6 jobs the finance team learns, which is what lets the managed service shrink.
Read about trainingOneStream implementation
The build before go-live, with the runbooks written while the work happened.
Read about implementationFinancial close automation
The reconciliations and the calendar that a managed service watches each month.
Read about the close
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.