Industrial digital transformation is not simply a matter of adding sensors, analytics, or automation software to existing operations. It also requires a way to connect operational technology (OT), information technology (IT), products, and business expertise so that digital capabilities address real customer and societal needs. Hitachi’s 2019 R&D strategy offers a useful example of how an industrial company organized research and collaboration around that challenge.
The strategy was built around a value-creation cycle: work with customers and partners to identify problems, develop solutions using technology and domain knowledge, and accumulate experience that can inform subsequent projects. For automation leaders, the central lesson is organizational as much as technical: a digital platform creates value when it links the physical operation to useful analysis, implementation, and continued learning.
Industrial digital transformation starts with connected value creation
Hitachi framed its objective as improving quality of life and creating customer value while contributing to social, environmental, and economic outcomes. Its business areas included mobility, smart life, industry, energy, and IT. Across these sectors, the proposed model combined OT, IT, and products, supported by technology platforms and accumulated know-how.
That combination matters in industrial environments because operational data does not automatically explain what action to take. Equipment behavior, process conditions, maintenance experience, and product design knowledge can all be relevant to interpreting a signal. Connecting these sources can help bridge the gap between what is happening on the plant floor and decisions made by engineers, service teams, and managers.
The strategy also treated co-creation as a repeatable process rather than a one-time workshop. Hitachi’s NEXPERIENCE methodology included activities such as ethnography, flow and movement analysis, business evaluation, concept design, prototyping, and proof-of-concept or proof-of-value work. These steps provide a structured route from understanding a problem to testing whether a proposed solution is workable and valuable.
Use co-creation to define and validate industrial solutions
For system integrators and plant teams, early collaboration can clarify the operating context before technology choices are fixed. A production issue may involve equipment, workflows, people, information systems, or several of these at once. Mapping the process and involving relevant stakeholders helps teams define what a solution needs to accomplish and how it will be assessed.
Hitachi’s approach extended beyond direct customer engagement to include startups, universities, government, and industry groups. Its initiatives included open forums, ideathons, hackathons, joint business programs, and collaborative research. The intent was to develop shared visions, explore possible applications, and move promising ideas toward validation and implementation.
One example in the strategy involved remote support and work assistance using edge processing and real-time transmission of on-site information. The described setup brought together cameras and sensors at a work location with a support center. The industrial implication is practical: when evaluating remote operations, teams need to consider how field information is captured, transmitted, combined, and made usable by people providing support.
Build digital platforms around operational needs
Hitachi identified Lumada as a platform and ecosystem for developing and expanding digital solutions. Its strategy described core technologies including AI, sensing, security, robotics, and 5G, alongside application development environments and customer or partner applications. The goal was to develop solution components that could be adapted and extended across customer cases, rather than treating every project as entirely separate.
For industrial automation, platform thinking can support a more consistent path from data collection to application development and deployment. But a platform is not a substitute for understanding the process. The use case, relevant data, operational constraints, and responsibilities for acting on an insight still need to be defined. The strategy’s emphasis on customer cases and accumulated know-how reflects the importance of learning from implementation, not just building technical infrastructure.
Link analytics to equipment and process knowledge
The strategy’s examples show how digital tools can be paired with OT expertise. Predictive failure diagnosis for industrial equipment, for instance, was described as combining AI with product design, maintenance technology, equipment operation data, and maintenance data. This illustrates why predictive maintenance depends on more than a model: the relevant equipment knowledge and history help give operational meaning to the analysis.
Another example applied data modeling to manufacturing, maintenance, and logistics. The proposed approach used information about operations, processes, operators, equipment, and materials to support analysis of work and production data. In practice, a shared view of these relationships can help connect site-level activity with management questions about productivity and value-chain performance.
Balance near-term business with longer-term research
The R&D portfolio described in the strategy covered customer co-creation, common digital platform technologies, product and core technologies, and exploratory research. It also called for expanding resources outside Japan and strengthening links with startups and research institutions. This mix reflects a familiar planning challenge for industrial organizations: maintain the technology and product capabilities required by current operations while also exploring future needs.
Exploratory research was directed at broad societal issues such as climate change, urbanization, resource depletion, digital disruption, and changing demographics. The strategy connected this work with fields including information, materials, and life sciences, as well as collaborations with universities and research organizations. For industrial decision-makers, the broader point is that research horizons and commercial roadmaps need deliberate connections, even when exploratory work is not tied to an immediate deployment.
Practical implications for automation leaders
Organizations applying these ideas can use a few questions to guide their own programs:
- Start with an operational problem. Define the process or customer need before selecting a technology.
- Bring the right expertise together. Include operations, engineering, IT, maintenance, and relevant partners in solution design.
- Validate in stages. Use prototypes and proof-of-concept or proof-of-value work to test technical feasibility and business relevance.
- Connect data to domain knowledge. Combine equipment and process information with the expertise needed to interpret it.
- Plan for reuse and learning. Capture what a project teaches so that solution components and methods can support later work.
Hitachi’s 2019 strategy presents industrial digital transformation as a coordinated effort spanning collaboration, platform development, OT and IT integration, and long-term research. Its practical message for automation teams is to connect technology decisions to operational needs, validate solutions with the people who will use them, and build on implementation experience. That discipline can help turn digital initiatives from isolated projects into a repeatable approach to solving industrial problems.