Illustrative case
Expert knowledge as an API
Calculation rules available to other systems, with a record of every run.Problem
Critical calculations were in legacy spreadsheets. They lacked controls to audit changes and versions. Maintenance depended on specific people.
Solution
We moved the rules to an API: an interface that other systems can query. We validate and version each rule. We record each run. We can expand the catalog without changing the core.
Current operation
- Every result is traced: what was calculated, with which data and which version
- The catalog grows without touching what is already validated
- Where it fits: technical calculations, rate setting, quotes, scoring
Origin: standards-based calculation
View architecture
Calculations based on technical standards were in spreadsheets. Auditing rules, controlling versions and reusing them across projects was difficult.
Every run is traced, and the calculation catalog grows without touching the core.
