Written 2026-11-01 for Tell Münzing, after ingesting the two DSS sources that were not available when the consolidated set was merged:
- Anand Birje, Hitachi Digital / Digital Systems & Services, 28 Oct 2026 — the BU level: HMAX Data Fabric, AI Operations, IWIM, FDE, HARC, and an HMAX-focused CTO office listed as an FY26 deliverable.
- Jun Abe, DSS Sector Business Strategy, Hitachi Investor Day, 10 Jun 2026 — the sector level above it: the four HMAX pillars (Domain Knowledge × AI, Talent, Security, Data Infrastructure / Data Fabric), the Physical AI FDE Team, and the ¥30bn FY2026 organic investment whose first technology bullet is “enhance data fabric capabilities”.
This file extends 2026-10-15-questions-hitachi-consolidated.md; it does
not replace it. Section VII of that set (“Getting the right people in the
room”) asked who is the counterpart in the digital organisation? without
being able to say what that counterpart would be responsible for. These four
can.
Same conventions: ☆ = ask early, the answer changes which of the rest are
worth asking. ★ = carries the most weight if the list is cut.
VIII. The digital organisation — what the counterpart would own
VIII1 ★☆ — Who is drawing the HMAX Data Fabric architecture, and is anyone responsible for data provenance in it? Birje’s path forward lists an HMAX-focused CTO office as an FY26 deliverable; Abe funds “enhance data fabric capabilities” out of the ¥30bn FY2026 organic investment. Both describe the layer. Neither names a person, and neither mentions provenance.
Why: the cheapest question on the list — it costs an insider one sentence, and only an insider can answer it. The answer is a name, which is the thing the engagement currently lacks. It is also a question about architecture, not about sustainability, which keeps it out of the sustainability box.
VIII2 ★ — Does the Data Fabric have a cross-company arrow planned? Abe p. 16 gives three value examples for the Data Fabric — green-power-linked production, dynamic railway power optimisation, production–logistics synchronisation. All three run Hitachi sector to Hitachi sector. None reaches a supplier, an operator, a customer or an assurer. Is a supplier-to-Hitachi or Hitachi-to-assurer path out of scope, or simply not yet drawn?
Why: the single most load-bearing unknown. “Cross-industry data utilization” is the Data Fabric’s own stated purpose, but on the evidence it means across Hitachi’s own industries. If a cross-company path is planned, SINE is a component of it; if it is out of scope, the conversation is a different one. Rail’s number — actual emissions data from 76 suppliers, 14.93% of Scope 3 Category 1 — sits exactly where the arrows stop.
VIII3 — Does the Security pillar cover provenance, or only availability? Abe names Security as one of four HMAX pillars: “ensuring the safety of mission-critical infrastructure that must never stop”, and funds “expand OT security services”. Birje’s October stack has no security layer at all. Within the pillar, is there anything that answers can this figure be checked by someone not allowed to see the underlying data — or does security here mean keeping the system running?
Why: tests whether an existing owner is already adjacent to the problem. As stated the pillar means operational safety, not provenance between parties — adjacent, not identical. If the answer is “availability only”, the gap is confirmed from inside. If there is a provenance remit, that is the door, and it already has a budget.
VIII4 — Who owns what leaves a customer’s site? The business model Birje describes is continuous knowledge circulation: frontline rules and tacit knowledge become reusable knowledge assets, applied across seven verticals. Customers whose know-how is the input eventually ask what leaves their site and what may be resold. Who answers that today — contracts, the FDE team, the CTO office, or nobody yet?
Why: reframes provenance as an unblocker for the growth engine rather than as a compliance feature, which is the version a P&L owner hears. It is also the general case of the supplier problem: a supplier asked for primary emissions data is asking the identical question one tier up.
Routing note
VIII1 and VIII3 are askable of the Physical AI FDE Team — the crossing point between DSS and the sectors, per Abe p. 15, and already inside Rail on Factory IQ per Birje p. 11 — without needing the CTO office to exist. VIII2 and VIII4 want an architect or a BU owner.
Section VII of the consolidated set should be read as asking who; this section supplies what to ask them once found.