The architecture under the cockpit — how data flows from many disconnected division, site and Toyota-group 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 division, site & Toyota-group 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 division, site and Toyota-group 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 division, site & Toyota-group 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.
record PAT, trading margin & the recurring / anchor supply mix vs plan
business_unit · service_line · signal · kpithe BD pipeline, new OEM mandates & the TKM anchor concentration vs target
opportunity · pipeline_stage · customer · projectCleanMax capacity, TREI rare-earth offtake & the recycling loop
ma_target · synergy_prog · brand_cohort · goalnet debt/EBITDA, debtor days & working-capital velocity
kpi · ar_aging · debt_tranche · covenant_qtrSome divisions and units aren't fully on the common SAP grain yet, so the unit→division mapping and site-grain detail are incomplete. These views still answer — by resolving, allocating-and-flagging, then reconciling. The estimate is labelled, never hidden.
Some units report at their own grain — so the unit → site → division → legal-entity rollup is partly missing or inferred.
of revenue already at true site grain; the rest labelled & closing as divisions move onto SAP
For units not yet on the common grain, per-asset, recurring-supply and revenue detail isn't available at site grain — so the site twin would otherwise be blank.
avg site-grain coverage today — transparent where it's modelled
Reconciliation runs live on the data. The 1 known break below is the site-grain gap surfaced on purpose — exactly what a CFO or auditor wants flagged, not buried.
Open Data Health →