IBM Planning Analytics report distribution
No one automates TM1 report distribution like Reportworq.
Reportworq takes the PAfE and Perspectives reports you already built, splits each one by your TM1 subsets, and delivers every recipient their own version by email, SharePoint, Teams or a shared folder. It runs on a schedule or the moment your load chore finishes, every send is logged, and your model doesn’t change.
Watch
One report, every market
One IBM Planning Analytics (TM1) report goes out as a personalized version to every recipient, and every send is logged.
How it works
Everything after the model, running on your IBM Planning Analytics data.
Your cubes and rules stay exactly as you built them. Your reports do too. Everything after that point runs on Reportworq.
One complete output, even when half the numbers live outside TM1.
Your board package needs IBM Planning Analytics figures next to SQL and third-party data. Today someone stitches them together by hand.
IBM Planning Analytics data and your SQL and Excel sources come together in a single report, so your stakeholder gets one file instead of three.
Every cost center owner gets their own report, without an analyst building each one.
Right now your team rebuilds the same report dozens of times, once per recipient. That is days of analyst time every cycle.
Your existing PAfE and Perspectives reports go to each recipient as a personalized version, on a schedule or on demand.
Split each report by a TM1 subset or dimension. For finer control, use an MDX query.
Budget and forecast inputs go straight back into IBM Planning Analytics.
Today your contributors email spreadsheets back, and someone keys the numbers into TM1 by hand.
Each contributor gets an input form for their slice. Submissions go through approval and write back to your TM1 cubes, and you can see who has submitted at every step.
AI answers about your IBM Planning Analytics numbers, from the reports Finance already approved.
Your analysts already paste numbers into AI tools for quick answers. Nobody can see what went in or what came back.
Assistants like Copilot and Claude answer from your finance-approved reports, not raw cube data.
What you'll gain
No disruption to your model. Live in days.
No model changes
Your cubes and dimensions stay as you built them. Your rules and TI processes do too. Nothing in your TM1 environment gets rebuilt.
Ready in days
Setup connects to your existing IBM Planning Analytics environment. There is no implementation services engagement to wait on.
Governed AI
AI answers come from finance-approved reports, not raw cube data. Every question gets logged, so your team can see what was asked and what came back.
Go deeper
Pick what you need to see.
For your IT team
Built on the infrastructure you already own.
Your IBM Planning Analytics server and BI tools stay exactly where they are. Everything runs alongside them. Access to TM1 runs through the integration credentials you set up, and you decide who receives each report.
Every PA deployment, every security mode
Connections run through the TM1 REST API. Self-hosted servers support every TM1 security mode.
Delivery options
Every place a report can go. Pick one to see what it takes.
Use several destinations on one job. If one fails, the others still deliver and the failure is logged.
For TM1 developers + PA admins
Built for the way your model already works.
You'll be the one asked whether this works with your model. Here is how it connects and what it needs from you. You'll also see what it leaves alone.
Read-only by default
The connection needs only the read access required to refresh your reports. Admin rights are needed once, to install the optional TI process, and you can remove them afterward.
Nothing writes to your cubes unless you set up Contribution or data collection.
Your formulas, as written
The formulas your reports already use refresh on the server.
Custom and Dynamic Reports from PAfE run as built, and so do Quick Reports. Slices and Active Forms from Perspectives run as built too. You choose whether formulas resolve the PAfE way or the Perspectives way.
Burst on subsets and MDX
Drive a job from a dimension or a subset. For finer control, use an MDX expression.
An MDX parameter can reference the element being burst, so each slice is built dynamically. The RWMDX function pulls MDX results straight into a sheet.
Trigger it from TI
Install a sample TI process from the connection settings in Reportworq. Call it at the end of a load chore, and the reports go out when the data is ready.
On v12 it uses ExecuteHttpRequest, with no shell and nothing written to disk. On IBM Cloud, the call relays through the Reportworq Cloud Connector.
Or drive it from anywhere
Run jobs from the Reportworq REST API, then check their status or cancel them.
On any run, override its parameters. You can also change its formats and destinations, or hold the output for review before it goes out.
{
"Name": "Monthly Reporting/Market P&L",
"HoldForDelivery": true,
"Parameters": [{
"Name": "Market",
"Type": "subset",
"Server": "TM1Prod",
"Dimension": "Region",
"Value": "Market Presidents"
}]
}FAQ
Common questions about Reportworq for IBM Planning Analytics
What does Reportworq do for IBM Planning Analytics?
Everything that happens after your TM1 model closes gets automated. Your existing PAfE and Perspectives reports go out as personalized outputs. Budget inputs come back through Excel forms that load straight into IBM Planning Analytics.
Do I need to change my TM1 model or reports?
No. Your cubes and dimensions stay as they are. Your subsets and existing reports stay as they are too. The connection runs on what you already built.
How does Reportworq decide who receives which report?
You split each report by a TM1 subset or dimension, or by an MDX query for finer control. Each version goes to the recipients assigned to it. The split can also come from a SQL query or an Excel sheet.
Does Reportworq apply each recipient's TM1 security?
You control what each recipient sees through the job setup. Reports run with the integration credentials you set up, and each version contains only the slice you split it by, such as one market or one cost center. A recipient's own TM1 security isn't applied, by design: reports often go to people who don't have TM1 access today. You stay in control of who receives each report. Manage that list in TM1 attributes or directly in Reportworq, or drive it from SQL or Excel.
How long does it take to go live?
Most teams are running in days. There is no long consulting engagement, because setup works with your existing IBM Planning Analytics environment.
After the model
Where does your close week actually go?
The cube closes on time. Then someone exports each cost center's view and cleans up the formatting. The numbers get pasted into a deck, and the emails go out one recipient at a time.
None of it needs your team's judgment. All of it takes their time.
Put a number on it for your business case
Pick the answers closest to your team. Starting answers are examples, so change them to match yours.
For reference, Synovus Bank cut two days of manual distribution a week to thirty minutes.
You get a Word document with your numbers filled in, ready to edit. Based on 8-hour days and 220 working days a year.
Put your IBM Planning Analytics numbers to work across the business.
See your own reports go out automatically, straight from TM1. Finance stays in control.
