Blog by Matt Klassen, Solutions & Product Marketing Manager, MKS
The role of software is changing and nowhere is that more evident than in the world of product manufacturers. Software brings huge benefits, but at the same time significant challenges. In an article by Michael Azoff of Ovum in the Technology Spectator, he asserts that, “Warranty Direct shows that electrical faults in cars, including software defects, are on the rise, representing 27 per cent of all faults (averaged across all models).” The reality is that software is on an aggressive growth path, or as Azoff terms this, an “exponential rise” within automobiles and many other manufactured products. Unfortunately, complexity is tending to mirror this trajectory as well, according to many of our customers across automotive, electronics and high tech, medical devices, and aerospace and defense.
So how can product organizations solve this? Azoff goes on to say that “Car manufacturers need to understand better how to create reliable embedded software by defining a role for software lifecycle management in the product world.” This is not only true in the world of automotive, but these other verticals as well. Research from other sources including Gartner, in a recent paper entitled Application Life Cycle Management Matters Where Diversity Persists, clearly show that software/application lifecycle management provides significant value to enterprises including:
Agility — Through collaboration and application of “just enough” process
Predictability — Through better estimation, better communication and more repeatable processes
Auditability — Traceability of work back to business needs, accountability for each change or decision made, and the ability to separate concerns
Quality — Through more-effective management of requirements, design and quality processes
Productivity — Through the reduction of rework and continuous improvement of processes and practices, and more-effective use of resources
There are many other implications and advantages that software can provide manufacturers including:
– A huge reduction in the cost of mass manufacturing
– Flexibility to affect change in a product very late in the development cycle
– The ability to create many more industry and customer specific product variants
– Delivery of new features in their products after they have been purchased (e.g. iPhone)
– The ability for customers to receive fixes and patches during the service lifecycle much more rapidly, without having to bring their device to a service center and at a fraction of the cost of traditional service
This last point is critical and a huge opportunity for all manufacturers as Azoff notes, “the typical enterprise IT user is used to downloading software patches regularly, but this is not the practice for car owners (at least not yet).” So why have we not seen more device manufacturers adopt this strategy? Well of course, the device whether it be a phone or automobile, must be architected for this dynamic software upgrade and service model. But another significant impediment is the ability to manage software engineering more like a first class engineering process and less like a growing, critical, differentiating, and valuable afterthought.