Is it best practice to split budgeting, forecasting, and reporting into 3 separate models?

I am working on a project where budgeting, forecasting and reporting all happen in 3 separate models (and 3 separate apps) within a workspace. Is this best practice? each model is rather large 50-100 modules, so from a visibility standpoint this makes sense. However, it causes a significant amount of re-work and imports to sustainably maintain all three. Thoughts?

Accepted answers

All comments

rob_marshall

@adham1103

No, i wouldn't do that from a pure scalability perspective. If you broke them out, there would not be an opportunity to do any variance analysis or reporting amongst the versions.

luke_e

Would be less concerned with the number of modules and more concerned with the volume of calculations/sizing/performance. Also sounds like you're introducing some significant maintenance overheads, especially if the models are structually identical.

As a point of reference, we have an FP&A model with ~530 modules for budgeting, forecasting and reporting (plus some).

Unless you're running into performance or sizing issues (or the use cases are completely different), keeping it within the same model would be preferable.

Quick Links

Can you help?

Unanswered questions

Create a Filter to show all the elements of that level based on selection in hierarchy
Hello Community members, Requirement Details: I have 5 levels of composite hierarchy list (A1, A2, A3, A4, A5). I have published a module in UX, Now the requirement is If user select a list member from A4 level in the context selector or Custom Filter I have to display all the list members under that A4 level. How can I…
import monthly data with months in columns
is there a way to import data with months in columns (usual excel table view)? I have to transform the data so there are rows to cover each period in the upload data form, but I am wondering if there is a better way to just import the data as is with the months in the columns. please let me know what you think. thank you,
Cloudworks Big Query Integration Fail
Hello, I am receiving an 'Anaplan Upload Failed' Status Description when testing my integration with a Big Query dataset. The integration imports data from BQ to our Anaplan model. No other details given in the error log. I suspect that Cloudworks is not even picking up the file but am not sure what we did wrong on the set…