The architecture under the cockpit — how data flows from many disconnected line, channel and claims systems into one governed truth, how that truth becomes a decision, and how two 360s still deliver over real data gaps.
No big-bang migration. The platform federates each line, channel and claims system, resolves it to one ontology, and serves a single trusted number — then turns that number into a decision, and the decision into an owner's action.
Each line, channel and claims system stays where it is. The platform layers ingestion, master-data resolution, a shared ontology and a semantic layer on top, then serves one governed truth to the apps and AI. Data flows top → bottom.
A single transaction's journey through the stack. A confidence flag and a reconciliation tie-out ride along with it the whole way.
Adapters pull each line, channel & claims system's events on schedule / CDC.
Raw records stored verbatim, with lineage + timestamp.
Codes matched to one canonical entity.
Mapped onto the ontology — classes & relationships.
Native fields → governed metrics; estimates flagged.
One metrics API; reconciliation gates the numbers.
360 views, exec briefs & AI read one truth.
The governed truth doesn't sit in a warehouse — it routes itself to the right view, the right action, and the right owner.
The four value-creation pillars don't just have dashboards — each has a standing agent that reads its governed data products and recommends the next move. Same ground truth, automated.
the ~99% health loss ratio, motor OD/TP economics & GWP vs plan
business_unit · service_line · signal · kpithe combined ratio, loss ratio, EOM cap & the investment-income offset
kpi · vcp · synergy_prog · signalthe Central Bank bancassurance ramp, channel mix & policy retention
customer · customer_source · site · kpiclaims leakage (8–10%), digital issuance & AI adjudication vs target
data_source · ops_metric · project · kpiSome lines and channels aren't fully on the common BaNCS grain yet, so the product→line mapping and branch-grain detail are incomplete. These views still answer — by resolving, allocating-and-flagging, then reconciling. The estimate is labelled, never hidden.
Some channels report at their own grain — so the product → line → legal-entity rollup is partly missing or inferred.
of premium already at true branch grain; the rest labelled & closing as lines move onto BaNCS
For branches not yet on the common grain, provider-network and premium detail isn't available at branch grain — so the branch twin would otherwise be blank.
avg branch-grain coverage today — transparent where it's modelled
Reconciliation runs live on the data. The 2 known breaks below are the plant-grain gap surfaced on purpose — exactly what a CFO or auditor wants flagged, not buried.
Open Data Health →