Skip to content
CodelessOps

/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.

Who it is for, the evidence, what to notice
Explain this estate

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

FromToStateImportsTargets
Caldergate Data HubCaldergate FP&Ainferred5DAT01 Actuals GL, DAT02 Actuals Volumes, SYS02 Cost Centre Attributes, SYS04 Product Attributes, SYS03 Account Attributes
Caldergate Data HubWorkforce Planninginferred1Data - Cost Centre Map
Workforce PlanningCaldergate FP&Ainferred1INP03 Headcount
Caldergate FP&ABoard Reportinginferred2DAT01 P&L, DAT02 Board Lines
Workforce PlanningBoard Reportinginferred1DAT03 Headcount
Caldergate FP&AWorkforce Planningretired1Inputs - 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

ModelRoleScale
Caldergate Data HubLoads 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&APlans 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 PlanningHolds 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 ReportingKPI 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

ModelCellsShare of estate
Caldergate FP&A130,001,66289.94%
Caldergate Data Hub8,060,6985.58%
Workforce Planning6,343,5594.39%
Board Reporting137,8820.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:

  1. The FX file has not been loaded since November 2023, so FP&A is running on a hardcoded rate.
  2. Workday is loaded twice, once by Caldergate Data Hub and once by Workforce Planning, so the employee lists can drift.
  3. Budget v2 DO NOT USE is 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
✓ checked · 10 cited · 16 unchecked · figures 27/27 traced
A real answer, re-set for this page. Real app, fictional estate, 30 September 2026. The app also draws the feeds as a diagram under the answer.

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.