While “may you live in interesting times” may be a curse of apocryphal Chinese origins, the COVID-19 pandemic is certainly not.
Pre-crisis, industrial digitalization was an important subject on the strategic “to-do” list of many manufacturing companies. The most-touted benefits of Industry 4.0, increased productivity, lower production costs, and faster time to market, were powerful arguments for its adoption. But equally, the very vagueness of the term “Industry 4.0” obfuscated the apparent value of industrial digital transformation. Many business managers simply couldn’t make a connection between the benefits of Industry 4.0 and the operations of their organization.
In an attempt to bridge this gap many businesses attempted to base their approach to digitalisation on a credible cost analysis of the return on technology investment. However, traditional ROI calculation methods based on speculative business cases do not work well for investments in ‘soft’ propositions such as “increased productivity” or “faster time to market”. There is simply too much room for the inherent guesswork and opinion to be incessantly debated within an organisation, leading to digital transformation becoming bogged down.
This has been the status quo for many industrial companies, with market surveys indicating that while the majority recognise the potential of Industry 4.0, a small minority have actually been successful at doing anything about it. After all, in the old world everyone was busy with normal life and there was no particular urgency. But now the world has changed and for many businesses the situation has become nothing if not urgent. As is the nature of these things, at a time when business managers typically retreat from pursuing new initiatives, the benefits of Industry 4.0 have moved from “nice to have” to “essential for survival”. Realistically, there is no longer time to debate the assumptions underlying a speculative business case for digital transformation. An Industry 4.0 initiative can’t be treated as just another IT project or plant-level initiative. Furthermore, a vital part of Industry 4.0 is about achieving a continuous, flexible scalability towards changing circumstances and new business opportunities.
To deal with this the leadership of a company must adopt an entrepreneurial state of mind: recognise that the company’s frame of reference has changed, that uncertainty is the order of the day; believe that digitalisation offers the company a path through the chaos, a way of competing and prospering in unpredictable circumstances ahead of specific supporting evidence.
And yet, even in the new world, the company’s business management still may not be able to make a connection between the needs of their business, digital transformation, Industry 4.0 and its underlying technologies. However, that is a problem that can be solved by working with industry experts who can help analyse the objectives of a business and devise appropriate digital transformation initiatives. We’re not talking grand plans here, either. Successful digitalisation programs focus on addressing low hanging fruit and achieving short term wins: involve, pilot, evaluate, deploy, repeat.
“Business cases should be the consequence of industrial digitalisation and not a justification for it”
Attempting to use business cases and ROI calculations to justify digital transformation was always a time consuming work of fiction. In the new world there is no time for fiction. The fact is that industrial digitalisation breeds its own success. It gives birth to new and potentially surprising business opportunities. It is the gateway to surviving and competing in the new world. Therefore, business cases should be the consequence of industrial digitalisation and not a justification for it.
This article originally appeared in Bits & Chips magazine.
Read also
An outbreak of hubris
Software is the medium of digitalisation. If you don’t understand software, you have no hope of coming up with a decent digitalisation strategy.
Software is not a component of a vehicle
Automotive OEMs have evolved to become highly efficient outsourcing and system integration organizations. Everything related to a vehicle is thought of as a component, including software. The whole automotive system engineering process treats software as a component of a vehicle. This prevents them thinking about the software as a whole system.
Abstraction versus Vagueness in Software Engineering
Some software engineering teams have a problem understanding the difference between abstraction and vagueness. Since one is essential to the architecture and design of complex systems and the other leads to technical debt and poor software quality, software teams must grok the difference.