Merged 2026-10-15 for Tell Münzing, to discuss the engagement as one whole rather than as two conversations. It joins:
- the CSO set of 1 October 2026
(
2026-10-01-questions-for-hitachi-rail-cso.md) — 21 questions written for Dr. Shibasaki, CSO Hitachi Rail, deep on the sustainability data layer; and - the first-conversation set of 15 October 2026 — 10 questions written for a mandate conversation with a business leader, in the advisor constellation (Tell Münzing and Katharina Roehrig with N+P, bringing SINE and PCI competencies).
Questions are regrouped by what each one decides, not by where it came
from. Origin is marked [CSO] or [MD]; where the two sets asked the same
thing from different angles, the questions are merged and marked [CSO+MD].
English throughout, because these are meant to be askable as written.
Priority marks: ★ = the seven that carry the most weight if the list has to be cut. ☆ = ask early in any case, because the answer changes which of the rest are worth asking.
I. Which door opens — entry and mandate
I1 ☆ [MD] — Does Customer Zero exist in Mobility?
Customer Zero is described in the Integrated Report for Connective Industries
and Digital Systems & Services. It is never claimed for Mobility. Is that a
presentation gap or an organisational fact? Is there a Rail equivalent — and
if not, who decides whether a Rail topic may run as Customer Zero at a CI or
DSS site?
Why: decides whether the entry runs internally at all, and whether the learning path has to cross a sector boundary. That is an organisational obstacle, not a technical one, and therefore the expensive kind.
I2 ★ [MD] — Has anything completed the Customer Zero route?
When Hitachi validates a solution through Customer Zero: who decides it is
adopted, which budget carries it, and how long is the path from “proven in
our own operations” to “in the offering”? Is there an example that went the
whole way?
Why: a doctrine is cheap to state. If nobody can name a completed example, the entry argument is weaker than the report suggests — and the proposal has to carry its own adoption mechanism.
I3 [CSO] — Where does this sit commercially?
Is circular economy positioned inside Hitachi Rail as a compliance and cost
topic, or does it have a route to becoming a Lumada/HMAX revenue line? Who
would sponsor such a project internally?
Why: Inspire 2027 ties Mobility’s margin expansion (8% → 11%+) explicitly to HMAX. Anything that cannot be told as a Lumada story will struggle for budget. A CSO will know the answer.
I4 ★ [MD] — What has already been tried, and how did it fail?
What have you already attempted in order to obtain primary data from
suppliers, and what stopped it?
Why: the question that makes an advisor useful rather than impressive. It guards against proposing something that has already failed, and a specific failure story is the best brief we can get.
II. The diagnosis — coordination failure or bargaining failure?
This is the section the whole engagement rests on. If the answer is “bargaining”, the problem is about rights, price and leverage, and SINE is the wrong instrument. If it is “coordination” — everyone would be better off with a shared mechanism and nobody can introduce one alone — it is precisely what SINE is built for. Ask these of both counterparts; the answers often differ, and the difference is itself the finding.
II1 ★ [CSO+MD] — What actually blocks supplier primary data?
Hitachi Rail’s FY24 Sustainability Statement reports actual emissions data
from 76 suppliers, covering 14.93% of Scope 3 Category 1. At group level,
428 of 700 procurement partners have set GHG reduction plans and targets.
What is the binding constraint on raising either number — supplier capability
and cost, or supplier unwillingness to disclose what the data would reveal
about cost structure and sourcing?
Why: the two answers imply completely different projects. “Capability” is a tooling problem and not ours. “Unwillingness” is the confidentiality problem. This is the one question worth asking twice, to two different people.
II2 ★ [MD] — Would a proof without the data be enough?
If a supplier could deliver a trustworthy emissions figure without handing
over the underlying data, would that satisfy Hitachi — or do assurers,
customers or internal policy require sight of the raw data itself?
Why: tests whether the product is admissible at all. If an assurance provider insists on raw-data access, a cryptographic proof does not substitute for it. This is one of our own two stated doubts; Hitachi can answer it better than we can.
II3 ★ [MD] — The third-party fleet.
HMAX Mobility runs 2,500 trainsets, over 35% of them built by someone other
than Hitachi. What data do you not get today from those OEMs or operators
that you would need in order to extend services? Is that a question of
rights, of price — or of the counterparty not wanting to carry the disclosure
risk?
Why: this is where the Lumada 80-20 target meets the confidentiality problem, on Hitachi’s own growth path. The three-part answer separates bargaining from coordination directly.
II4 [CSO] — Agentic AI pointed at the supplier process, not the estimate.
Hitachi’s own framing of AI is amplification of human judgement under
incomplete information. The supplier data problem has that shape: roughly 85%
of the purchased-goods footprint is estimated rather than measured. Has
Hitachi considered applying agentic AI to the supplier engagement process —
not to estimate better, but to lower what it costs a supplier to answer, and
to narrow what a supplier has to reveal in order to answer?
III. The data layer in the product
III1 ★ [CSO] — Does the sensor fleet also carry material identity?
With “Enhanced by HMAX” (22 September 2026) Hitachi Rail has committed to
equipping all new rolling stock with proprietary HMAX sensor technology from
2027. Does the onboard data model carry component and material identity —
part number, supplier, batch, material composition — alongside condition and
performance data? Or is it condition and telemetry only? Is there an
intention to make the new fleet a traceability layer as well as a maintenance
layer?
Why: the single highest-leverage question. Hitachi is about to instrument every train it builds. If material identity rides along, the circular-economy data problem is largely solved as a by-product of a decision already taken and already funded. If it does not, that is the specific gap a project is built around.
III2 ★ [MD] — When does the specification freeze?
A fleet-wide commitment from 2027 means the sensor specification is being
fixed now. Who decides its scope, and until when is an addition still free?
Why: the only question in the set with a date behind it. Before the freeze an addition costs a design decision; after it, a retrofit.
III3 [MD] — The site decarbonisation KPI.
The business-site GHG reduction KPI (FY2027 target 75% vs FY2019, FY2025
result 64%) is linked to short-term executive incentives. How is it
calculated today, and what share of the underlying data carries third-party
assurance?
Why: this is the first case the dossier proposes. If the answer is “fully assured already”, the case loses its point. If it is “limited assurance on parts”, the opening is in Hitachi’s own numbers.
III4 [CSO] — Design-time or report-time?
The ETR1000 recyclability improvement is attributed to newly designed
electric motors, so circularity is already an output of design decisions. Is
there a design-time toolchain — LCA linked to PLM/CAD — that gives an
engineer that number while they are designing? Or is it calculated afterwards
for reporting?
III5 [CSO] — The train as its own passport.
If material identity rides on the HMAX data model, the vehicle reports its
own composition continuously rather than being documented at handover. Has
that been considered as a specifiable, sellable product feature of the
next-generation vehicle rather than a reporting obligation?
IV. The published claims
IV1 ★ [CSO] — Which recyclability figure is authoritative?
Three different recyclability/recoverability figures for the ETR1000 are
currently public in Hitachi’s own materials: ~85% on the product page,
94.4% / 95.8% in the FY23 ESG report, and 97.1% / 98.2% in the March 2026
press release. We want to cite Hitachi correctly. Which is the governing
figure, what is the calculation basis (ISO 21106?), and is it third-party
verified or self-declared?
Why: a real, checkable, public inconsistency that only a careful outsider notices. Asked as “we want to cite you correctly” it is a courtesy, not an audit — and the answer reveals whether there is a data process behind the number or a communications process.
IV2 [CSO] — Recycled input content.
Everything Hitachi Rail publishes is end-of-life recyclability — a design
property calculated at the start of life. Is there a recycled input content
figure or target: how much secondary material actually goes into a train
today?
Why: the metric regulation and tenders will ask for, and the one where the sector is almost silent. Hold the competitor fact in reserve — Alstom is the only rail OEM publishing one.
IV3 [CSO] — The ISO 14067 product carbon footprint, concluding this
fiscal year. What system boundary — cradle-to-gate or cradle-to-grave? Will
the result be published or held internally? And is it being built on the
group’s existing PACT/Pathfinder-conformant capability, or separately inside
Rail?
IV4 [CSO] — The Social Product Declaration as the precedent that already
exists. The HTR 412 “Blues” SPD, produced with EPD International, remains
the only SPD in the International EPD System registry worldwide. It assesses
raw-material suppliers from 23 countries on a 1–4 risk scale, is valid to
2028, and Hitachi Rail has described it as the seed of a platform for data
from more than 20,000 suppliers. Is the approach intended to be repeated for
the next product generation, and was supplier response the binding
constraint?
Why: it is a genuine Hitachi first, and it already records the supplier data gap as a risk rating — in Hitachi’s language and under Hitachi’s signature. That is the slot a proof attaches to, which is why this question moved up from “parked” in the October set.
IV5 [CSO] — “Eco-design for all relevant product groups by FY2030”.
How is “relevant product groups” defined for Rail, and what product-level
data does meeting it require that Rail does not have today?
V. Regulation and demand pull
V1 [CSO] — Do you share our reading of the ESPR clock?
Our reading: ESPR (2024/1781) does not cover rolling stock. It covers steel
and aluminium as priority intermediate products, so Digital Product
Passport data would arrive attached to purchased material from roughly 2028
(steel) and 2029/30 (aluminium) — no delegated act adopted yet — and the
rolling-stock OEM carries no DPP duty of its own. Does Hitachi Rail read it
the same way? Who owns the ESPR/DPP watch inside Rail, and what is the
internal planning horizon?
V2 ★ [MD] — CBAM exposure.
How far are Hitachi or its immediate upstream suppliers actually subject to
CBAM declaration duties, and who tracks this internally?
Why: our own stated falsification point. CBAM covers the materials a train is made of, not the train — so exposure runs through the supply chain, which is exactly where Hitachi’s data stops. If the answer is “a long way off”, the regulatory half of the product-side argument falls and only the tender path carries it.
V3 [CSO] — Permanent magnets in traction motors.
Under the Critical Raw Materials Act, permanent magnets carry a
recycled-content declaration duty and minimum recycled content from 2031; the
covered product list is still pending a delegated act and rail traction
motors are not confirmed in scope. Given that the ETR1000’s recyclability
improvement is attributed to newly designed electric motors, is magnet
sourcing and recycled content on the radar, and is Hitachi engaging on the
delegated act?
V4 ★ [CSO] — Is the pull coming from customers?
NS required a material passport in its DDNG double-decker tender, and
EuroSpec (NS, DB, SNCF, ÖBB, SBB, UK) is working to standardise passport
requirements across future tenders. Hamburger Hochbahn required a 94%
recycling rate in its 2022 metro tender. Is Hitachi Rail already seeing
material or circularity requirements appear in tender specifications, and do
you expect them in high-speed tenders?
Why: this converts circular economy from a cost centre into a bid instrument. If the answer is yes, the project has a revenue case and therefore a sponsor.
VI. Where it lives commercially
VI1 [CSO+MD] — Who owns the HMAX roadmap, and is there a slot?
HMAX is described as the realisation of Lumada 3.0, and Mobility’s Inspire
2027 margin path is tied explicitly to service expansion via HMAX. Is there a
roadmap slot for material, origin and lifecycle data in the HMAX module
family, and does that roadmap sit with Rail or with the group HMAX
organisation?
VI2 [CSO] — Residual value in the service contract.
Hitachi Rail already sells availability and maintenance over decades, not
only vehicles. Does a material and residual-value layer have a commercial
home there — end-of-life value, component re-use, refurbishment commitments
written into service contracts?
VI3 [CSO] — Does it generalise?
HMAX began as a Rail product and generalised into Energy, Industry, Cyber and
Data Center. Is there a scenario in which a circular-economy data capability
built for Rail becomes a Lumada offering sold to other asset-heavy
industries? What would have to be true for that to be worth doing?
VII. Getting the right people in the room
These are designed so that a sustainability counterpart cannot fully answer them alone. That is the point: a question only a sustainability person can answer keeps the project in the sustainability box.
VII1 ★ [CSO] — Who is the counterpart in the digital organisation?
Who in GlobalLogic / Hitachi Digital Services, Vantara or R&D would be the
natural counterpart for a circular-economy data capability — and could they
join the next conversation?
VII2 [CSO] — The internal-first-customer route.
Hitachi Rail was the first customer of HMAX Cyber, the agentic SOC built with
Google Cloud. Does the same route exist here: Rail as first internal
customer, the group digital organisation as product owner?
Framing cautions
Carried from the 1 October set, with two additions.
-
Do not lead with regulatory urgency. Nothing in EU law today imposes a direct material/circularity data duty on a rolling-stock OEM, and the indirect dates are 2028+ (ESPR steel), 2029/30 (aluminium), 2031 (CRMA magnets, rail not confirmed in scope). CSRD Art. 40a reaches the Japanese parent at ~FY2028, filed 2029. The Circular Economy Act and the Public Procurement Act (COM(2026) 590) are still pre-legislative. A compliance-driven pitch will not survive contact with their legal team.
-
Lead instead with the decision they have already taken. They are instrumenting every new train from 2027 regardless. The question is only whether that instrumentation also carries material identity. A marginal-cost argument, not a new-programme argument.
-
The competitive facts, held in reserve. Alstom publishes a 40% recycled-content target and is the only OEM that does; Alstom coordinates Rail4EARTH, pre-standardising a battery digital passport; Siemens Mobility runs the Train2Train closed-loop aluminium consortium with DB and Hydro and has no Type III EPD for any train — where Hitachi has several. Hitachi is ahead on declarations and behind on input material. That asymmetry is the conversation.
-
⟨New 2026-10-15⟩ Hold back the gross-profit denominator. The PLEDGES KPI “reduction in GHG emissions intensity through products and services” (target 40%, result 41%) carries the footnote “per gross profit” (Integrated Report, p. 28 — verified). The number therefore improves when gross profit rises, even at unchanged absolute emissions. It is a sharp observation and it is true, but delivered without a mandate it reads as an audit of their KPI. Keep it for the moment someone asks why verifiability is worth anything.
-
⟨New 2026-10-15⟩ State the SINE core as a mechanism, not as governance. The temptation — and the reading an outside analyst will reach for by default — is to describe SINE as developing agreements on data use, confidentiality and access. That places SINE in a crowded market and makes its contribution a document sold by the hour. The core is the opposite: a proof over signed sensor data lets a counterparty verify a figure without obtaining the data beneath it, which removes the need for a whole class of those agreements. The sentence that makes the gap visible: Hitachi can integrate data it is given; for data it is not given, it has no architecture.
-
The engagement mechanic. Do not ask a sustainability counterpart about the digital units; ask questions they cannot close alone, then propose a joint working session as the concrete next step. The ask at the end of the conversation should be a second meeting with a named person from the digital organisation in it.
-
No rail OEM anywhere publishes an absolute per-train carbon footprint. The sector EPD rule (PCR 2009:05, which UNIFE developed with Hitachi Rail among others) uses kg CO₂e per passenger-kilometre, which structurally cannot express embodied carbon. Whoever publishes the first absolute number is first.
What changed in the merge
- Section II is new as a section. Both sets contained its questions; only together do they read as one diagnosis with a binary outcome.
- The SPD question moved from “parked” to IV4. The 13 December 2023 trade coverage ingested on 15 October gives it a factual basis, and the dossier’s product-side argument now rests on it.
- Two questions merged outright: supplier primary data (CSO A3 + MD B1 → II1) and the HMAX roadmap (CSO E2 + MD C1 → VI1).
- Four questions are new in this merge and come from reading Hitachi’s own strategy reading against the dossier: I1, I2, III2 and III3.
- FIRA has been dropped as a question subject and retained only as framing — it is a management-discussion service built with a joint venture, not an industrial platform.