Skip to content
CodelessOps

/architect · Technical

Model Health Check.

Upload your models' line items, modules and actions. The same 42 tests run on every model, the five most impactful things to do come back as an action plan with the evidence behind each, and nothing is stored. It is the engine the Architect runs on, published on its own, free.

36 seconds, no sound: the upload, the 42 tests, the action plan and the change impact view.

What goes in

  • Line Items exportrequired
  • Modules exportoptional, adds size context
  • Actions exportoptional, adds import and process checks

Standard Anaplan metadata exports, as CSV. A zip of the estate folder, or one model at a time. No planning data, no list members, no model access.

The 42 tests, by area

1

Performance and size · 8

Where calculation time and cells go, and the formula patterns Anaplan documents as expensive.

2

Usage and leftovers · 5

What nothing appears to read: candidates to ask about, never verdicts.

3

Dependencies and change impact · 5

What depends on what, inside a model and between models.

4

Correctness and maintainability · 17

Totals that may be wrong, repeated logic, and formulas the next builder has to decode.

5

Imports, exports and processes · 4

What loads the model, what has stopped running, what sits outside every process.

6

How far to trust the analysis · 3

Checks the report runs on itself, so every finding says how strong its evidence is.

See all 42 run on the example estate

What comes back

  • An action plan. The five most impactful things to do, each with the objects involved, why, the steps, a completion check and the test that found it. Every other candidate follows, with the reason it is not on the plan.
  • Change impact. Pick a module or line item and follow its dependencies either way, with the paths and a clickable diagram.
  • Evidence. Every test with its result (found, clear, or not run and why), then the searchable findings, formulas, model inventory and dependency coverage.

One HTML file. The Architect reads the same engine, pinned by commit, and adds the notes, the conversations, the size solver and the evidence drawer. How it is pinned.

Questions

Does my model data leave my machine?
Online, files are written to a temporary folder for the seconds the analysis takes and deleted before the response is sent; nothing is stored and no names or formulas are logged, and there is no account. If exports can't leave your network at all, run the same engine locally from the repository; then nothing is sent anywhere.
Does it use AI?
No. Every finding is a defined rule over the exports you supply. The same inputs give the same report every time. The AI only enters with the full Architect, and there it explains what the rules found; it never produces the counts.
What does a finding mean?
That a defined test matched something in the exports. It is an observation or a candidate to review, never a verdict: every finding carries its evidence strength, what the exports cannot tell, and the reasons the current design may be right.
Why five actions?
Because a plan you can act on this month is more useful than a list of everything. Every other candidate is still there, ranked, with the reason it is not on the plan; run the tool locally with --top to change the number.
Is this a replacement for Referenced By?
No. Referenced By answers one hop at a time. This follows the whole chain, groups what it finds into candidate actions, and shows the evidence. The architect still decides.
I was expecting a test but it is not on the list. What can I do?
Tell me what you would check on a model by hand and what a hit would look like, and we can build it together. Message me on LinkedIn or open an issue on GitHub; the tests are numbered, so a new one takes the next number in its area.
Is it free?
Yes. MIT licensed, hosted or local. I built it to be useful to model builders and I want to know what it misses.

Public record

What has shipped.

  1. Page/architect site family, nine use cases answered from the exportsOne real question per page on a fictional estate, re-set as HTML with the evidence drawer; the free check, the grammar, the CLI and the engineering record under Technical
  2. LinkedInMy estate review tool now runs 42 tests on your Anaplan models ↗A 36 second walkthrough of the upload, the 42 tests, the five-action plan and the change impact view
  3. Releaseanaplan-estate v0.2.0, 42 numbered tests and a plan of the five most impactful actions ↗Every test listed with its result; seven new tests; checked on eleven real exports before release
  4. PostModel Health Check: what it finds and how to use it
  5. PageAnaplan Estate gets its own page on this siteWhat the report contains, the checks, how to run it hosted or local
  6. Releaseanaplan-estate v0.1.0 public, hosted at anaplan-estate.codelessops.com ↗Action plan with every candidate shown, change impact explorer, evidence tab. MIT.
  7. Releaseanaplan-grammar v0.1.0 public ↗13,214 of 13,214 reference formulas parsed; dependency graph 0.998 precision, 0.994 recall vs Referenced By

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.