A 12-slide presentation by Anand Birje, CEO of Hitachi’s Digital Engineering & AI Solutions BU and CEO of the merged Hitachi Digital Services + GlobalLogic organization, inside the Digital Systems & Services sector. Page footers read “Hitachi Digital | Q2”, placing it in Hitachi’s Q2 FY2026 reporting cycle. Supplied by Tell Münzing on 2026-11-01 with the Inspire 2027 progress deck, with the brief: understand Hitachi’s digital business development, the implications of the DSS/CI split, and why the digital-business CEO does not talk about driving Lumada 3.0.
Source: sources/hitachi/2026-10-28-hitachi-digital-anand-birje-dss.pdf and
its Markdown twin. Citations are to printed page numbers. Slides 4, 5 and
10 were read as rendered pages because their substance is in layout that the
Markdown twin flattens — in particular slide 5, where the twin detaches two
numbers from their captions and inverts their meaning.
See the entity page: Hitachi Digital.
Who is presenting, and at what altitude
“CEO, the combined Hitachi Digital Services and GlobalLogic organization (Hitachi Digital) · CEO, Digital Engineering & AI Solutions BU, Hitachi · Santa Clara, California” (p. 2)
Appointed to the BU in August 2026 and to the merged organization in September 2026. Track record as stated: Encora (named on the slide as “GlobalLogic competitor”), CEO three years, sold to Coforge for $2.35bn in April 2026; HCLTech 15+ years, most recently President of a $4.5bn Digital Business Services unit, and founding leader of an infrastructure and cloud business that passed $2.5bn within a decade; Emerson Electric and Capgemini — “industrial control systems, SCADA and MES, hands-on IT-OT convergence”. Stated mandate: “Unify GlobalLogic and Hitachi Digital Services capabilities while driving and scaling digital transformation across Global markets and mission critical industries leveraging AI, Data and Cloud”.
⟨Inference, and it governs how the whole deck reads: this is a business-unit CEO inside the DSS sector, not the sector CEO — that is Jun Abe, who presented at the June 2026 Investor Day. The deck is an IT-services strategy, benchmarked against IT-services peers, for a P&L one level below the one that reports a Lumada ratio.⟩
The number that reframes the digital business (p. 5)
The slide is headed “Hitachi Digital and Hitachi: Prepared for the Market — We have the clients, the scale and the Hitachi domain assets. The gap to best-in-class multiples is focus and execution”, in three columns:
| Column | What it says |
|---|---|
| Strengths | +46% YoY ⁽¹⁾ — captioned “Synergy business growth sell-to / sell-with Hitachi Front Business Units and transforming digital capabilities across Hitachi”. Plus “Scale and clients” and “Hitachi domain depth — OT know-how in mission-critical industries, codified in HMAX IP” |
| Opportunities | ”Single-digit, 2-yr CAGR representing 65% of business” — captioned “Hitachi Digital Top 100 accounts historical growth rate”; “Opportunity to drive vendor consolidation”; “data and AI services spend projected to grow at 15% CAGR”. Closing red box: “Evolution need: Strong coherence of strategy, leadership and execution” |
| What We Plan to Scale | 4 growth service lines (Cloud, Data, Physical AI, Enterprise Platforms) · 7 key verticals (Energy, Mobility, Telecom, Pharma & Healthcare, Banking and Financial Services, Auto, Connective Industries) · 200 top customers, grown “through FDE investments, Ecosystem Partners, Industry specific solutions” · IP — “Evolution of HARC ⁽²⁾ for Industry specific ontology and context layer acceleration” |
⁽¹⁾ “FY2026/H1 Actual”. ⁽²⁾ “Hitachi Application Reliability Centers”.
⟨Inference, the central finding of this source: the internal channel is the growth, and the external book is not. Selling to and with Hitachi’s own front business units grew 46% in H1 FY2026; the external top-100 accounts, which are 65% of the business, compound in single digits. A deck that opens by naming its own multiple gap and then shows that split is telling its audience that the re-rating depends on the Hitachi-internal motion working.⟩
⚠ Conversion caution. Marker’s Markdown twin detaches “+46% YoY” from its caption and renders the two figures adjacently, which reads as if the 46% were the top-100 account growth. It is the opposite. Quote from the rendered slide.
HMAX drawn as a stack (p. 4)
“We will Enable Hitachi to tap into this Convergence — Frontline experts and the HMAX platform turn customer know-how into trusted AI across Mission Critical Industries”. Columns across the top: Energy · Mobility · Industry. The layers, top to bottom:
| Layer | Stated function |
|---|---|
| Physical AI FDE service | ”Frontline experts work alongside customers to create value and continuously capture knowledge” |
| ↓ / ↑ between them | ”Frontline rules, know-how and tacit knowledge” down; “Safe and trusted AI utilization of accumulated knowledge” up; the loop labelled “Driving greater value through continuous knowledge circulation” |
| HMAX AI Operations | ”Ensure stable and optimized AI operations while preventing inappropriate AI behavior” |
| HMAX Data Fabric | Data platform: “Capture and manage frontline knowledge as knowledge assets that AI can utilize”. IWIM / AI: “Make decisions based on frontline context and constraints using ontologies and physical models” |
| Existing IT Systems | Cloud and on-premises |
Left margin: “One company operating across the Physical and Digital tech stack — HDS + GlobalLogic · Inside Hitachi’s Digital Engineering & AI Solutions BU · Full-stack digital engineering with IT-OT · External clients plus sell-to / sell-with Hitachi units”.
⟨Inference: this is the clearest statement in any source the wiki holds of what DSS actually owns. The three HMAX products — Energy, Mobility, Industry — belong to the three physical sectors (Inspire deck p. 20). What Birje’s BU owns is the horizontal underneath them: the FDE service, the AI operations layer, and the Data Fabric with its ontologies. The vertical columns here are not his business; they are his customers.⟩
⟨Inference, for SINE: the layer an attestation mechanism attaches to is HMAX Data Fabric — the place where field data becomes “knowledge assets that AI can utilize”. A claim about whether a datum is what it says it is belongs in that layer, not in a vertical solution. And “preventing inappropriate AI behavior” is the adjacent concern one layer up: Hitachi already has a named box for trustworthiness of the model, and none for provenance of the input.⟩
The growth engine (p. 9)
“Aspiration: Dominate Physical and Digital AI-led business transformation”, organised as Core / Multipliers / Amplifiers, drawn as concentric rings — “Verticals × Service lines” at the centre, then “IP-Led Differentiation”, then “Inorganic Growth”, with the outer ring labelled “True One Hitachi” and “Ecosystem Partnerships”:
- 01 Vertical focus — seven priority sectors, top 200 accounts
- 02 AI-era service lines — Physical AI, Data & Intelligence, Cloud & SRE, Enterprise Platforms
- 03 IP-led differentiation — “HMAX and next version of HARC turn know-how into platforms and agents” (framed as “how growth decouples from headcount”)
- 04 Inorganic program — “Acquisitions add Physical AI, data and vertical depth”
- 05 One Hitachi — “Sell-to and sell-with Rail, DSS, Energy, Connective Industries + deploy FDEs”
- 06 Ecosystem partnerships — NVIDIA, Google Cloud, Microsoft, AWS, SAP “and others”
⟨Note: item 05 lists “Rail, DSS, Energy, Connective Industries” as units to sell to, although Birje’s own BU sits inside DSS — the deck’s own shorthand, recorded as written.⟩
Ecosystem partners, and the stack they map onto (p. 10)
IT stack, top to bottom: SaaS+ Agentic · APIs / MCP / Orchestration · Data · Runtime & platform · Infrastructure · Frontier Model / AI. Fifteen named partners, “listed in alphabetical order”: AWS, Boomi, Claude, Databricks, Google Cloud, Microsoft, MuleSoft, NVIDIA, OpenAI, Oracle, PTC, Salesforce, SAP, ServiceNow, Snowflake.
⟨Inference: “MCP” named as a stack layer on a Hitachi investor-cycle slide dates the Model Context Protocol’s arrival in this company’s architecture vocabulary. ⟨Background: MCP is an open protocol for connecting models to tools and data sources.⟩ The relevance is narrow but real — an attestation that travels with a datum has a natural carrier if the integration layer is protocol-shaped rather than bespoke.⟩
Our work: three of four cases are inside Hitachi (p. 11)
| Client | What is claimed |
|---|---|
| Walgreens | ”Modernizing Walgreens’ pharmacy management system, from prescription intake to drug dispatch” |
| Hitachi High-Tech | ”Using Agentic AI to optimize semiconductor maintenance — automating scheduling and inventory, guiding safe steps, and maximizing equipment availability” |
| Hitachi Energy | ”With a focus on Physical AI, we are partnering with NVIDIA to bring intelligence to factory floors and critical infrastructure” |
| Hitachi Rail | ”We are leveraging the FDE model for Smart Operations — including Factory IQ and vehicle manufacturing optimization use cases” |
⟨Inference: the reference slide of the external-facing digital business is three-quarters internal. This is Customer Zero in substance — Hitachi sites as the first deployment — presented as client work. The term “Customer Zero” appears nowhere in the deck.⟩
Path forward (p. 12)
| Step | Horizon | Content |
|---|---|---|
| 01 | FY26 | ”Transform business and leadership” — rebrand to Hitachi Digital around Physical and Digital AI; land the vertical model and new service lines and the HMAX-focused CTO office; launch partnerships; align to One Hitachi |
| 02 | FY27 | ”Scale with AI relevance” — grow top-200 accounts, accelerate AI/data/cloud, add capability through M&A, expand margins through delivery transformation |
| 03 | FY30 | ”Dominate Physical and Digital AI-led business transformation” — growth and margins at best-in-class peer levels, rising revenue per head, IP-led revenue a far larger share of mix |
⟨Inference: the HMAX-focused CTO office, being stood up in FY26, is the most specific counterpart address this source gives. It is the function that would own a horizontal component of the Data Fabric — and it does not exist yet, which is both the opportunity and the reason nobody can be named.⟩
Why Lumada 3.0 is never mentioned
The word Lumada does not occur once in 12 slides. Neither does Inspire 2027, Customer Zero, or any Lumada revenue ratio. ⟨Inference, assembled from this deck and the Inspire 2027 deck, and offered as the answer to the question that motivated the ingest — four reasons, none of which is de-prioritisation:
- Lumada is a reporting attribute, not a platform. It is the tag that makes a yen of sector revenue count as digital for investors. It has no product surface, no roadmap and nothing to sell. The things Birje does name — HMAX, FDE, Data Fabric, IWIM, HARC — are the Lumada machinery, named by its parts.
- Wrong altitude. Lumada ratios are group and sector measures. Birje runs a BU inside DSS; the DSS Lumada ratio is Jun Abe’s number.
- Wrong benchmark. The deck names its own frame: “the gap to best-in-class multiples is focus and execution”, with GlobalLogic/Encora/HCLTech as the implicit comp set. “Lumada” carries no meaning for IT-services investors; verticals, top-200 accounts, revenue per head and IP-led mix do.
- He owns the supply side, not the story. Slide 4 is Lumada 3.0’s engine room with the narrative layer removed.
The practical consequence for SINE is a routing fact, not a strategic one: a proposition pitched as “this advances Lumada 3.0” is pitched in a vocabulary this counterpart does not use. The same proposition pitched as “a trust component in the HMAX Data Fabric that lets frontline data cross a company boundary without disclosure” is in his.⟩
What is absent
No Lumada, no Inspire 2027, no Customer Zero by name, no Lumada ratio, no sector revenue or margin, no circular economy, no carbon, no PCF, no DPP, no supplier data, no standards or standardization, and no security or confidentiality vocabulary anywhere — the only trust word in the deck is “trusted AI”, which refers to model behaviour, not to data provenance.
⟨Inference: the absence of a confidentiality or verifiability vocabulary in the digital business’s own strategy deck is consistent with the pattern the wiki has recorded three times elsewhere — the requirement is stated by the people who hit it in the field and does not reach the strategy layer. See open task 19.⟩
Cross-references
- Hitachi Digital — the entity
- Hitachi, Ltd.
- Inspire 2027 progress deck (27 Apr 2026)
- Mobility
- Customer Zero — present in substance, absent by name
- Hitachi Integrated Report 2026
Sources
sources/hitachi/2026-10-28-hitachi-digital-anand-birje-dss.pdf(+ Markdown twin and extracted figures in the sibling directory)