/architect · Use cases
Nine questions, answered from the exports.
Every one is a real question put to a fictional estate of four models and answered by the real app. The result, the evidence drawer behind it, and what the exports cannot prove, printed with the answer. Pick the seat you are in.
The estate on day one
Four models, 144.5M cells, who feeds whom, the three risks nobody ticketed.
Brief
This is a four-model Anaplan estate with Caldergate Data Hub, Caldergate FP&A, Workforce Planning and Board Reporting. The estate holds 144,543,801 cells in the exported metadata, calculated as 8,060,698 in Caldergate Data Hub + 130,001,662 in Caldergate FP&A + 6,343,559 in Workforce Planning + 137,882 in Board Reporting; Caldergate FP&A is 89.94% of that. The operating flow is hub to planning, planning to reporting: Caldergate Data Hub feeds Caldergate FP&A and Workforce Planning; Workforce Planning feeds headcount cost into Caldergate FP&A; Caldergate FP&A and Workforce Planning feed Board Reporting. All live-looking model feeds are still inferred from import action names, except Caldergate FP&A to Workforce Planning, which is retired because owner note n-ff27724850 says HR analytics now keys the assumptions by hand. The main handover risks are the stopped FX file, duplicate Workday loads, and Budget v2 DO NOT USE still being selected by a board pack line, from owner note n-07669fb656.
How the models fit together
| From | To | State | Imports | Targets |
|---|---|---|---|---|
Caldergate Data Hub | Caldergate FP&A | inferred | 5 | DAT01 Actuals GL, DAT02 Actuals Volumes, SYS02 Cost Centre Attributes, SYS04 Product Attributes, SYS03 Account Attributes |
Caldergate Data Hub | Workforce Planning | inferred | 1 | Data - Cost Centre Map |
Workforce Planning | Caldergate FP&A | inferred | 1 | INP03 Headcount |
Caldergate FP&A | Board Reporting | inferred | 2 | DAT01 P&L, DAT02 Board Lines |
Workforce Planning | Board Reporting | inferred | 1 | DAT03 Headcount |
Caldergate FP&A | Workforce Planning | retired | 1 | Inputs - Settings |
All arrows are dashed because the feeds are inferred from import action names, or retired. There are no owner-confirmed live feeds in list_models. The retired feed is important. Caldergate FP&A still has an import-name relationship into Workforce Planning, but owner note n-ff27724850 says Import from Caldergate FP&A - Assumptions into Inputs - Settings has not run since August 2022 and HR analytics key the rates by hand.
What each model does
| Model | Role | Scale |
|---|---|---|
Caldergate Data Hub | Loads NetSuite, Salesforce and Workday, then feeds the spokes. Confirmed in owner note n-5f84264ff2. | 12 modules, 63 line items, 8,060,698 cells, 8 imports |
Caldergate FP&A | Plans revenue, opex, headcount cost and cash, and produces management and board packs. Confirmed in owner note n-5f84264ff2. | 30 modules, 278 line items, 130,001,662 cells, 10 imports |
Workforce Planning | Holds employee-level cost. Data - Employees is loaded from Workday, Calcs - Cost inflates salary and adds NI and pension, and Calcs - Headcount by CC is what FP&A imports into INP03 Headcount. Confirmed in owner note n-ff27724850. | 9 modules, 55 line items, 6,343,559 cells, 3 imports |
Board Reporting | KPI layer for the board dashboard, refreshed from FP&A and Workforce after each close. Confirmed in owner note n-5f84264ff2. | 7 modules, 30 line items, 137,882 cells, 3 imports |
Where the size sits
| Model | Cells | Share of estate |
|---|---|---|
Caldergate FP&A | 130,001,662 | 89.94% |
Caldergate Data Hub | 8,060,698 | 5.58% |
Workforce Planning | 6,343,559 | 4.39% |
Board Reporting | 137,882 | 0.10% |
That means most size work should start in Caldergate FP&A, not in Board Reporting.
What to know before changing it
Ownership is split. Caldergate FP&A and Caldergate Data Hub sit with Finance Systems, Workforce Planning belongs to HR analytics, and Board Reporting is Dan’s model. Owner note n-cdfac253fb says any import change must be agreed with the receiving model’s owner and made in a development copy first.
Build history matters. Owner note n-6029978175 says Caldergate Data Hub and Caldergate FP&A were built in 2019 by the first partner using DISCO naming, Workforce Planning was built in 2021 by a second partner using its own naming, and Board Reporting was built in-house by Dan in 2023. The conventions do not agree, and nobody has renamed objects because saved views may break.
Do not treat every long formula as bad. Owner note n-d1f2fe4d49 says CAL10 Depreciation.Charge is correct, reconciles to the fixed asset register, and should not be touched without the asset schedule.
Main handover risks
Owner note n-07669fb656 flags three risks that are not ticketed:
- The FX file has not been loaded since November 2023, so FP&A is running on a hardcoded rate.
- Workday is loaded twice, once by
Caldergate Data Huband once byWorkforce Planning, so the employee lists can drift. Budget v2 DO NOT USEis still selected by a board pack line.
I would treat those as control risks before doing cosmetic cleanup.
What the export does not prove
The export does not show saved views, UX pages, dashboards, selective access, list members and subsets, planning data, model history, or whether a number is correct. It shows structure, formulas, actions, dependencies and parsed metadata. So this is enough to explain the estate and prioritise investigation, but not enough to certify the output values.
Evidence drawer · what each chip opens
- ModelCaldergate Data Hublist_modelsobserved
- ModelCaldergate FP&Alist_modelsobserved
- ModelWorkforce Planninglist_modelsobserved
- ModelBoard Reportinglist_modelsobserved
- Owner noteWhat the estate is fornotesuser confirmed
- Owner noteHandover risks nobody has ticketednotesnot established
- Owner noteWho built what, and whennotesuser confirmed
- Owner noteOwners, and the rule for changing a feednotesuser confirmed
- Owner noteWorkforce Planning: naming and the missing effort columnnotesuser confirmed
- Owner noteDepreciation Charge: correct, long, do not touch without the schedulenotesuser confirmed
What nothing reads
Seven unread modules, one of them 54% of the biggest model, and the reason it is still there.
| Test | What it looks for | Result | By model |
|---|---|---|---|
| 2.1 | Modules nothing reads. A module with two or more calculated line items that no formula outside it reads and no export action uses. | found · 7 | Caldergate FP&A 3 · Caldergate Data Hub 2 · Workforce Planning 1 · Board Reporting 1 |
| 2.2 | Unread modules that repeat a module in use. An unread module whose calculated line items match, in formula and context, line items of a module that is read. | clear · 0 | |
| 2.3 | Calculated line items nothing reads. A calculated line item of 50,000 cells or more that no formula reads, outside the modules above and outside output-style modules. | found · 5 | Caldergate FP&A 5 |
| 2.4 | Data loaded but never read. A module that an import action loads, none of whose line items is read by any formula or used by an export action. | found · 1 | Caldergate Data Hub 1 |
| 2.5 | Names that say leftover. Modules, line items, actions and referenced list items whose name carries a leftover marker (OLD, TEMP, COPY, BACKUP, DO NOT USE, v2, 'Copy of', default names). | found · 4 | Caldergate FP&A 3 · Workforce Planning 1 |
The largest of them, as the action plan carries it
Find out whether anyone still uses the module CAL05 Opex OLD in Caldergate FP&A
A module that no formula reads and no export uses may be left over from earlier work, or it may be read only by pages and views, which the exports do not show. Until someone checks, it can neither be removed nor trusted. In Caldergate FP&A, no formula outside the module CAL05 Opex OLD reads any of its 14 line items and no export reads it; it occupies 70.2M cells and 50.8% of the model's measured calculation effort. That is what it takes up now, not a saving.
- Ask the page builder whether any page, dashboard, saved view or line item subset still uses
CAL05 Opex OLD. - Ask whether another model imports from a saved view on it.
- Record the decision: keep, or retire. If retire: make the change in a development copy first, keep the original for comparison, check the owner's key outputs over a full cycle, then sign off.
Done when every question above has a recorded answer and the owner has signed a keep-or-retire decision. Found by test 2.1; findings F1, F26, F48. Role: model owner with a page builder.
Why it is an investigation and not a change: the evidence is partial. The exports cannot see pages, saved views or subsets, so "nothing reads it" is true of formulas and export actions only. The owner note on this module already says why it is kept.
Evidence drawer · what each chip opens
- RuleG-UNUSEDanaplan-estate checks.py
- RuleH-LEFTOVERanaplan-estate checks.py
- Action planFind out whether anyone still uses the module 'CAL05 Opex OLD'Action plan · #3
Why it was built this way
The first partner did not want an editable table. A note says so, and the plan agrees.
Forecast Opex: why the mapping is in the formula
The account-to-driver mapping lives in the IF chain because the first partner did not want a mapping table the business could edit. There is an open request to add a thirteenth branch for legal fees. Moving the mapping to a small lookup module is agreed in principle; nobody has had the time.
The action plan reaches the same place from the exports, without the reason:
Consider replacing the long chain of IF tests in the line item CAL03 Opex.Forecast Opex with a lookup table
5.0M cells · 16.0% of the model's effort · found by test 4.6, formulas with more than 10 IFs · done when every cell is equal before and after, the table holds every case the chain held, and the measured effort is no worse.
Three more notes a new architect reads on day one
The FX file stopped in November 2023; the hardcoded rate is the stop-gap
Import FX from Treasury file was always run by hand, outside any process, because Treasury's file is sometimes late and the actuals load must not wait for it. It has not been run since November 2023. The 1.27 USD rate hardcoded in CAL02 Revenue is the stop-gap since then, not a design choice.
Versions in FP&A, and Budget v2
Four versions: Actual, Forecast, Budget and Budget v2 DO NOT USE. Budget v2 was the mid-year re-cut in FY24 and was never approved. It is still selected by OUT02 Board Pack.Old Budget Revenue; ask Dan before removing the version, the board pack comparatives may still read it.
CAL05 Opex OLD is kept on purpose, for now
Replaced by CAL03 Opex in 2021 when driver-based opex went in. Kept until the FY22 audit file is closed, because the auditors' working papers reference its numbers. Nothing reads it; the cells and the calculation time are the price of keeping it. Once the audit is signed off it can go.
One decision, recorded
Caldergate FP&A → Workforce Planning
Owner note n-ff27724850 says Import from Caldergate FP&A - Assumptions into Inputs - Settings has not run since August 2022, HR analytics key the NI and pension rates by hand each year instead, and the import names make FP&A look like a feed into Workforce but it is not unless someone reinstates it.
19 notes on this estate: 5 purpose, 6 conclusion, 4 constraint, 3 decision, 1 procedure. 15 confirmed by the owner, 4 working assumptions. None flagged by the last export.
Evidence drawer · what each chip opens
- Owner noteForecast Opex: why the mapping is in the formulan-f2327b3be0working assumption
- Owner noteThe FX file stopped in November 2023; the hardcoded rate is the stop-gapn-04d0598b25working assumption
- Owner noteVersions in FP&A, and Budget v2n-eaeed7ba09user confirmed
- Owner noteCAL05 Opex OLD is kept on purpose, for nown-e6ddcfdc13user confirmed
- Action planConsider replacing the long chain of IF tests in 'Forecast Opex' with a lookup tableAction plan · #2
The reach of a change
27 line items, 7 modules, 8 links deep, two exports, ending in the board pack.
Caldergate FP&A › CAL03 Opex.Forecast Opex 5,017,824 cells · 16.04% of the model's effortModules in reach
| Module | Line items | Nearest | Cells |
|---|---|---|---|
CAL03 Opex | 4 | 1 | 20,071,296 |
CAL07 P&L by Cost Centre | 6 | 3 | 114,912 |
CAL06 Department Summary | 3 | 3 | 7,776 |
CAL11 Reporting Prep | 3 | 4 | 57,456 |
CAL08 Cash Flow | 6 | 5 | 3,456 |
OUT01 Management Pack | 4 | 5 | 76,608 |
OUT02 Board Pack | 1 | 7 | 19,152 |
The path to the board pack
Actions touching modules in reach
| Action | Kind | Module | Process | Last run |
|---|---|---|---|---|
| Export P&L to Board Reporting | export, reads | CAL07 P&L by Cost Centre | Publish Board Pack | 2026-09-08 |
| Export Board Pack | export, reads | OUT02 Board Pack | Publish Board Pack | 2026-09-08 |
Other models, inferred from import names
Board Reporting inferred 2 import actions into DAT01 P&L, DAT02 Board Lines · Workforce Planning inferred 1 import action into Inputs - Settings
Reach stays inside the model: the exports carry no line-item mapping across models, so other models are listed from the import names, as inferred, and never counted as line items. Actions are linked at module level. Saved views, pages, dashboards and line item subsets are not in the exports. Reach describes formula references; it does not prove a value will change.
Evidence drawer · what each chip opens
- Line itemCAL03 Opex.Forecast OpexLine Items export
- ActionExport P&L to Board ReportingActions export
- ActionExport Board PackActions export
Is it safe to delete
Nothing in the model reads it. The auditors still do. A note says so.
Brief
Do not delete CAL05 Opex OLD yet unless the FY22 audit file is signed off. The owner note n-e6ddcfdc13 says it is kept on purpose because auditors’ working papers reference its numbers, and that it can go once the audit is closed. From the dependency export, CAL05 Opex OLD has 0 downstream line items and 0 module-level actions touching it in Caldergate FP&A, so the model logic does not appear to need it. The prize is large: CAL05 Opex OLD contains 14 line items and 70,249,536 cells.
What the export says
| Check | Result |
|---|---|
| Line items in module | 14 |
| Cells in module | 70,249,536 |
| Downstream line items | 0 |
| Direct downstream line items | 0 |
| Indirect downstream line items | 0 |
| Actions touching the module | 0 |
The module note also says: “Replaced by CAL03 in 2021. Keep until the FY22 audit is closed.”
What blocks deletion
The blocker is not model dependency. It is audit evidence.
Owner note n-e6ddcfdc13 says CAL05 Opex OLD was replaced by CAL03 Opex in 2021, but is kept until the FY22 audit file is closed because auditors’ working papers reference its numbers. That note also says nothing reads it, and once the audit is signed off it can go.
What to check before deleting
- FY22 audit file is signed off.
- Nobody still needs the old module for audit queries.
- Any saved views, UX pages or dashboards that might show
CAL05 Opex OLDhave been checked manually. These are not in the exports. - Delete it first in a development copy of
Caldergate FP&A.
Recommendation
If FY22 audit is still open, keep CAL05 Opex OLD.
If FY22 audit is signed off, delete CAL05 Opex OLD in a development copy, regression check CAL03 Opex, CAL07 P&L by Cost Centre, OUT01 Management Pack and OUT02 Board Pack, then promote the change.
Named without being looked up this conversation: CAL03 Opex, CAL07 P&L by Cost Centre, OUT01 Management Pack, OUT02 Board Pack.
Evidence drawer · what each chip opens
- ModuleCAL05 Opex OLDimpactobserved
- Owner noteCAL05 Opex OLD is kept on purpose, for nownotesuser confirmed
- ModelCaldergate FP&Alist_modelsobserved
The 42 checks
42 tests in six areas: 33 found something to review, 9 clear, 0 not run.
| Area | Tests | Found | Clear |
|---|---|---|---|
| 1 Performance and size. Where calculation time and cells go, and the formula patterns Anaplan documents as expensive. | 8 | 8 | 0 |
| 2 Usage and leftovers. What nothing appears to read: candidates to ask about, never verdicts. | 5 | 4 | 1 |
| 3 Dependencies and change impact. What depends on what, inside a model and between models. | 5 | 5 | 0 |
| 4 Correctness and maintainability. Totals that may be wrong, repeated logic, and formulas the next builder has to decode. | 17 | 13 | 4 |
| 5 Imports, exports and processes. What loads the model, what has stopped running, what sits outside every process. | 4 | 3 | 1 |
| 6 How far to trust the analysis. Checks the report runs on itself, so every finding says how strong its evidence is. | 3 | 0 | 3 |
Every test
| # | Test | Result |
|---|---|---|
| 1.1 | Where calculation effort concentrates | found · 3 Workforce Planning not run: needs the Calculation Effort column |
| 1.2 | SUM combined with LOOKUP or SELECT | found · 1 |
| 1.3 | Large text line items | found · 5 |
| 1.4 | FINDITEM on a large line item | found · 1 |
| 1.5 | Text joins on a large line item | found · 2 |
| 1.6 | Per-item functions repeated on every cell | found · 10 |
| 1.7 | Line items with a dimension their formula does not use | found · 12 |
| 1.8 | Where the cells are | found · 4 |
| 2.1 | Modules nothing reads | found · 7 |
| 2.2 | Unread modules that repeat a module in use | clear |
| 2.3 | Calculated line items nothing reads | found · 5 |
| 2.4 | Data loaded but never read | found · 1 |
| 2.5 | Names that say leftover | found · 4 |
| 3.1 | Line items with the widest change impact | found · 1 |
| 3.2 | Pass-through chains | found · 4 |
| 3.3 | Circular references | found · 1 |
| 3.4 | Which model feeds which | found · 6 feeds |
| 3.5 | Dimensions shared across models | found · 7 |
| 4.1 | The same calculation under two names | found · 2 |
| 4.2 | Line items that only copy another | found · 14 |
| 4.3 | Formulas that differ in exactly one place | clear |
| 4.4 | Identical formula text that cannot be compared | clear |
| 4.5 | The same line item and formula in more than one model | found · 8 |
| 4.6 | Formulas with more than 10 IFs | found · 1 |
| 4.7 | Hard-coded numbers in formulas | found · 9 |
| 4.8 | Very long formulas | found · 1 |
| 4.9 | SELECT on a fixed period or version | found · 4 |
| 4.10 | DIVIDE() where a zero divisor shows Infinity | found · 15 |
| 4.11 | Subsidiary views used in calculation | found · 2 |
| 4.12 | Summaries on line items nothing reads | found · 37 |
| 4.13 | Modules with more than 50 line items | found · 1 |
| 4.14 | Empty modules | found · 1 |
| 4.15 | Modules without notes | found · 4 |
| 4.16 | Percentages whose totals are added up | clear |
| 4.17 | The odd one out in a run of matching formulas | clear |
| 5.1 | Imports and exports outside every process | found · 12 |
| 5.2 | Imports and exports with no recent run | found · 7 |
| 5.3 | Imports and exports never run | clear |
| 5.4 | Several imports loading one target | found · 1 |
| 6.1 | Formulas the parser did not follow | clear · 0 |
| 6.2 | Agreement with Anaplan's own Referenced By | clear · 0 |
| 6.3 | Input checks on the files | clear · 0 |
A test that found something is an observation or a review candidate, never a verdict; clear means the pattern was not found in these exports; not run means an export or column the test needs is missing, never that the model is clear.
Evidence drawer · what each chip opens
- Test6.2 Agreement with Anaplan's own Referenced Byclear
- Test6.1 Formulas the parser did not followclear
- Rule42-test catalogue, anaplan-estate v0.2.0checks.py
The fix list
43 candidates, 8 met the bar, 5 on the plan, each with its steps and its done-when.
Stop repeating text-to-item lookups (FINDITEM) on every cell in Caldergate FP&A (1 formula)
DAT01 Actuals GL.Journal Cost Centre · 5.0M cells · 6.2% of the model's effort · test 1.4
- Open the line item 'Journal Cost Centre' in the module 'DAT01 Actuals GL' (6.2% of measured effort) and note which list its value actually changes with (often Time, or one list).
- In a development copy of the model, create a small system module with just that list, put the formula there, and point the places that used the old formula at the new one. Keep the old line item until the check below passes.
- Compare the results before and after, and read the Calculation Effort column before and after.
Done when every value that used the result still matches the original, cell for cell, and the measured effort share has fallen.
Consider replacing the long chain of IF tests in the line item 'Forecast Opex' in the module 'CAL03 Opex' with a lookup table
CAL03 Opex.Forecast Opex · 5.0M cells · 16.0% of the model's effort · test 4.6
A long chain of 'if this then that' tests is hard to maintain: each new case means editing the formula, and the mapping is easier to check when it sits as rows in a small table read with one lookup. Whether the table also calculates faster depends on the engine and the formula (Anaplan documents that IF stops at the first true branch), so treat the performance side as something to measure, not assume.
Done when every cell is equal before and after, the table holds every case the chain held, and the measured effort is no worse.
Find out whether anyone still uses the module 'CAL05 Opex OLD' in Caldergate FP&A
CAL05 Opex OLD · 70.2M cells · 50.8% of the model's effort · test 2.1 · that is what it takes up now, not a saving
Find out whether anything reads these calculated line items in Caldergate FP&A (3 modules)
CAL03 Opex, DAT01 Actuals GL, CAL02 Revenue · 15.1M cells · 10.0% of the model's effort · test 2.3
Move per-cell text and lookups into small system modules in Caldergate Data Hub (2 line items)
DAT01 GL Transactions.Source System, DAT06 Sales Orders.Last Order Ref · 2.0M cells · materiality medium · tests 1.3 to 1.6
What "worth doing" means here
- A change is worth doing when its evidence is not merely inferred, its scope is bounded, and its materiality is at least medium (1% of its model's measured effort, or 1M cells, or a test that ranks high by nature, such as a total that may be wrong).
- An investigation is worth doing only when its materiality is high (5% of its model's measured effort, or 50M cells, or a test that ranks high by nature): asking someone to check a small module is not a good use of their time.
- A test about upkeep (naming, long formulas, hard-coded numbers, housekeeping of actions) never competes for the plan; its findings are listed below it and under Evidence.
Marking an action done records a decision. It does not verify anything in Anaplan. A proposal from the architect is a suggestion over the evidence it cites; it carries no state until the owner takes it on. 43 candidates: 43 to review, 0 investigating, 0 done, 0 kept as current design.
Evidence drawer · what each chip opens
- Line itemDAT01 Actuals GL.Journal Cost CentreLine Items export
- Line itemCAL03 Opex.Forecast OpexLine Items export
- ModuleCAL05 Opex OLDModules export
- Test1.4 FINDITEM on a large line itemfound
- Test4.6 Formulas with more than 10 IFsfound
Why the model is this size
The list sizes solved from the cell counts, each axis priced, 278 of 278 counts reproduced.
Where the cells are
| Module | Cells | Line items | Share |
|---|---|---|---|
CAL05 Opex OLD | 70,249,536 | 14 | 54.0% |
CAL03 Opex | 30,106,944 | 6 | 23.2% |
DAT01 Actuals GL | 20,071,296 | 4 | 15.4% |
INP03 Headcount | 5,937,120 | 10 | 4.6% |
INP02 Opex Drivers | 1,110,816 | 58 | 0.9% |
CAL12 Driver Phasing | 593,712 | 31 | 0.5% |
CAL02 Revenue | 435,456 | 12 | 0.3% |
| 23 more modules | 1,496,782 | 143 | 1.2% |
The sizes, solved from the cell counts
| Factor | Size | Line items agreeing |
|---|---|---|
| Cost Centres | 133 | 173 of 173 |
| Accounts | 262 | 32 of 32 |
| Products | 42 | 43 of 43 |
| Roles | 31 | 10 of 10 |
| Departments | 18 | 9 of 9 |
| Currencies | 8 | 4 of 4 |
| Regions | 6 | 35 of 35 |
| Legal Entities | 4 | 15 of 15 |
| Time (Month, Model Calendar) | 36 | 237 of 237 |
| Versions | 4 | 222 of 222 |
What each axis costs
| Axis | Size | Line items on it | Cells on it | Cells it adds |
|---|---|---|---|---|
| Cost Centres | 133 | 173 | 128,817,815 | 127,849,260 |
| Time | 36 | 237 | 129,997,764 | 126,386,715 |
| Accounts | 262 | 32 | 120,429,872 | 119,970,216 |
| Versions | 4 | 222 | 129,994,272 | 97,495,704 |
| Roles | 31 | 10 | 5,937,120 | 5,745,600 |
| Products | 42 | 43 | 1,152,396 | 1,124,958 |
| Regions | 6 | 35 | 1,124,952 | 937,460 |
Over-dimensioned line items, priced
| Line item | Applied | Required | Cells | Saved without the extra axes |
|---|---|---|---|---|
INP03 Headcount.NI Threshold | Cost Centres, Roles, Time, Versions | none, a constant | 593,712 | 593,711 |
INP03 Headcount.NI Rate | Cost Centres, Roles, Time, Versions | none, a constant | 593,712 | 593,711 |
CAL02 Revenue.Actual or Forecast | Products, Regions, Time, Versions | Time | 36,288 | 36,252 |
CAL02 Revenue.Revenue Label | Products, Regions, Time, Versions | Products, Regions | 36,288 | 36,036 |
CAL07 P&L by Cost Centre.Opex Budget | Cost Centres, Time, Versions | Cost Centres, Time | 19,152 | 14,364 |
OUT02 Board Pack.Budget Revenue | Cost Centres, Time, Versions | Cost Centres, Time | 19,152 | 14,364 |
OUT02 Board Pack.Old Budget Revenue | Cost Centres, Time, Versions | Cost Centres, Time | 19,152 | 14,364 |
CAL01 Volumes.Launched? | Products, Time, Versions | Products, Time | 6,048 | 4,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
What did you test
The architect explains its own coverage: 42 run, 9 clear, one partial gap and why.
Brief
The report ran 42 tests across Caldergate Data Hub, Caldergate FP&A, Workforce Planning and Board Reporting: 33 found something to review, 9 came back clear, and 0 were wholly not run. Clear means the pattern was not found in these exports, not proof it cannot exist. The only partial gap is test 1.1, where calculation effort could not be assessed for Workforce Planning because the export lacks the Calculation Effort column, which matches owner note n-ff27724850. The strongest coverage checks came back clear: test 6.1 found 0 unparsed formulas, test 6.2 found 0 Referenced By agreement issues, and test 6.3 found 0 input guard issues.
What was tested?
| Area | Tests run | Found | Clear | Not run |
|---|---|---|---|---|
| 1 performance and size | 8 | 8 | 0 | 0 |
| 2 usage and leftovers | 5 | 4 | 1 | 0 |
| 3 dependencies and change impact | 5 | 5 | 0 | 0 |
| 4 correctness and maintainability | 17 | 13 | 4 | 0 |
| 5 imports, exports and processes | 4 | 3 | 1 | 0 |
| 6 how far to trust the analysis | 3 | 0 | 3 | 0 |
| Total | 42 | 33 | 9 | 0 |
Which tests found something?
The 33 tests that found something are review candidates, not automatic defects. The largest: 4.12 summaries on line items nothing reads, 37 hits; 4.10 DIVIDE() where a zero divisor shows Infinity, 15; 4.2 line items that only copy another, 14; 1.7 line items with a dimension their formula does not use, 12; 5.1 imports and exports outside every process, 12.
What came back clear?
| Test | Title | Result |
|---|---|---|
| 2.2 | Unread modules that repeat a module in use | 0 hits |
| 4.3 | Formulas that differ in exactly one place | 0 hits |
| 4.4 | Identical formula text that cannot be compared | 0 hits |
| 4.16 | Percentages whose totals are added up | 0 hits |
| 4.17 | The odd one out in a run of matching formulas | 0 hits |
| 5.3 | Imports and exports never run | 0 hits |
| 6.1 | Formulas the parser did not follow | 0 hits |
| 6.2 | Agreement with Anaplan's own Referenced By | 0 hits |
| 6.3 | Input checks on the files | 0 hits |
What could not be run?
No test was wholly not run: the test catalogue reports 0 not-run tests out of 42.
There is one partial coverage gap. Test 1.1, where calculation effort concentrates, could not assess Workforce Planning because it needs the Calculation Effort column. Owner note n-ff27724850 says the Workforce Planning export was taken before Calculation Effort existed, so ask for a fresh export before judging where calculation time goes in Workforce Planning.
What is outside the exports?
The exports do not show saved views and filters, UX pages, dashboards, selective access, list members and subsets, planning data values, model history, or who changed what. That means these tests can review structure, formulas, dependencies, actions and metadata, but they cannot prove whether a reported number is correct or whether a line item is used only by a page or saved view.
Evidence drawer · what each chip opens
- ModelCaldergate Data Hublist_modelsobserved
- ModelCaldergate FP&Alist_modelsobserved
- ModelWorkforce Planninglist_modelsobserved
- ModelBoard Reportinglist_modelsobserved
- Owner noteWorkforce Planning: naming and the missing effort columnnotesuser confirmed
Fictional estate (Caldergate Distribution Group: a data hub, FP&A, workforce planning and board reporting; four models, 426 line items), real app, results read back from it on the dates shown.
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.

