Skip to content
CodelessOps

/architect · Use cases · Is it any good

Why the model is this size

"Why is Caldergate FP&A 130 million cells?"

Who this is for, and the moment

The workspace is at its limit and someone has to say why. The exports never say how big a list is, how many periods the time range holds or how many versions there are. But every line item’s cell count is the product of its factors, and 278 equations are enough to solve for all of them.

The question

Caldergate FP&A, the largest model in the estate.

The result

ModelCaldergate FP&A
Cells130.0M130,001,662
Modules30278 line items · 171 calculated · 107 inputs
Reproduced278 / 278cell counts, exactly
Over-dimensioned81,307,338 cells they would not have

Where the cells are

ModuleCellsLine itemsShare
CAL05 Opex OLD70,249,5361454.0%
CAL03 Opex30,106,944623.2%
DAT01 Actuals GL20,071,296415.4%
INP03 Headcount5,937,120104.6%
INP02 Opex Drivers1,110,816580.9%
CAL12 Driver Phasing593,712310.5%
CAL02 Revenue435,456120.3%
23 more modules1,496,7821431.2%

The sizes, solved from the cell counts

FactorSizeLine items agreeing
Cost Centres133173 of 173
Accounts26232 of 32
Products4243 of 43
Roles3110 of 10
Departments189 of 9
Currencies84 of 4
Regions635 of 35
Legal Entities415 of 15
Time (Month, Model Calendar)36237 of 237
Versions4222 of 222

What each axis costs

AxisSizeLine items on itCells on itCells it adds
Cost Centres133173128,817,815127,849,260
Time36237129,997,764126,386,715
Accounts26232120,429,872119,970,216
Versions4222129,994,27297,495,704
Roles31105,937,1205,745,600
Products42431,152,3961,124,958
Regions6351,124,952937,460

Over-dimensioned line items, priced

Line itemAppliedRequiredCellsSaved without the extra axes
INP03 Headcount.NI ThresholdCost Centres, Roles, Time, Versionsnone, a constant593,712593,711
INP03 Headcount.NI RateCost Centres, Roles, Time, Versionsnone, a constant593,712593,711
CAL02 Revenue.Actual or ForecastProducts, Regions, Time, VersionsTime36,28836,252
CAL02 Revenue.Revenue LabelProducts, Regions, Time, VersionsProducts, Regions36,28836,036
CAL07 P&L by Cost Centre.Opex BudgetCost Centres, Time, VersionsCost Centres, Time19,15214,364
OUT02 Board Pack.Budget RevenueCost Centres, Time, VersionsCost Centres, Time19,15214,364
OUT02 Board Pack.Old Budget RevenueCost Centres, Time, VersionsCost Centres, Time19,15214,364
CAL01 Volumes.Launched?Products, Time, VersionsProducts, Time6,0484,536

An over-dimensioned line item repeats one value along an axis it applies to; the cells it saves are the cells it would not have without that axis. Whether the repetition is wanted (a rate shown per segment on a view) is the owner's call: mark it and give the reason. Owner note n-9df5c544be says the OUT02 rows keep Versions on purpose, for the board's side-by-side view; note n-adfde53814 says the two NI constants belong in SYS00 Model Settings. 10 formulas aggregate with SUM or its kin to a list the export does not name: on those, the list the aggregation targets is taken as required.

Evidence drawer · what each chip opens

  • Line itemINP03 Headcount.NI ThresholdLine Items export
  • Line itemOUT02 Board Pack.Old Budget RevenueLine Items export
  • Owner notePack views keep Versions on purposen-9df5c544beuser confirmed
  • Owner noteINP03 Headcount: the NI constants are in the wrong placen-adfde53814user confirmed
✓ Sizes are inferred from cell counts, never exported: the sizes found reproduce 278 of 278 cell counts exactly (100%).
A real result, re-set for this page. Real app, fictional estate, 12 October 2026.

Where the cells are, module by module: one module holds 54% and is the subject of Is it safe to delete. The sizes, solved: 133 cost centres, 262 accounts, 36 months, 4 versions, with how many line items agree on each. What each axis costs in cells. Eight over-dimensioned line items, priced: two constants carried across cost centre, role, month and version.

The evidence

The sizes are inferred from the cell counts and the solution reproduces 278 of 278 counts exactly. A size with fewer line items agreeing would be marked; here every one is unanimous. The evidence drawer shows the applied and the required axes on every line item.

What to notice

  • Some repetition is wanted. The two board pack rows keep Versions on purpose so the board sees Actual, Forecast and Budget side by side; an owner note says so, and the row can be marked “keep current design” with that reason. The app then stops raising it.
  • The two NI constants are the clearest fix: one number each, held 593,712 times. The note says where they belong and that the move is safe if the readers are repointed in the same change.
  • A formula that aggregates to a list the export does not name is listed, not judged. The limits are printed under the table.

The Size page: the module treemap, the sizes table and the over-dimensioned rows

Real app, fictional estate, captured 8 October 2026.

Use cases: The 42 checks · The fix list · The estate on day one.

Run Anaplan in-house?

Start with the Model Health Check on your own exports.

The 42 tests and the action plan run free, hosted or on your own machine, and nothing is stored. Then give me 30 minutes and bring the three questions you would ask about your estate.