This is a case-study blueprint; no deployment results or customer endorsement are claimed.
Business challenge
Claims dashboards need agreed definitions, date handling, grouping, and access boundaries after a platform change.
Migration approach
Review calculated items, report interactions, preparation dependencies, and target feature gaps; propose reviewed measures and layouts.
Deterministic work
Apply approved mappings and checks to the supported report and semantic definitions. Record rule versions, target constraints, and unresolved exceptions; verify outputs against an agreed baseline.
Agentic assistance
Use permitted context to explain calculations, propose mappings, identify gaps, and prepare review questions. Review generated proposals before adopting them as implementation or access rules.
Acceptance evidence
Compare representative claim periods, grouping, totals, filters, identities, and documented redesign decisions.
Delivery time
The 19 months (estimated) assumes the stated migration inventory, accessible source definitions, available reviewers, and an agreed target environment. Plan discovery, design, build, parity testing, business review, and release readiness as separate checkpoints. Re-estimate when access, custom features, data issues, or acceptance scope changes.