Validation Early and Often
Improving Product Quality and Reliability
This is not a blog post about which tool can deal with a certain situation or what tool you will be able to acquire for the lowest price. Instead this is a post that relates to the need of evolving our methods of working.
Already here, you might start to sense a little bit of resistance, the word evolve is synonymous with change, and a synonym to change is many times resistance. But if we swap “change” with “improve”, there is a likelihood we can remove some of that resistance. Because that is what the text here is about, not changing our way of working but actually improving what really matters – improving product quality, improving reliability and as an icing on the cake, reduce cost while doing so.
With a business outcome as a focus, we start with the result and we do not need to focus on functions, features and the cost of a tool. Those are aspects I understand will have to be part of the equation, but I urge you to bring these aspects into the equation once we have validated that the future involvement of method, is synonym with improvement.
Reduce Lead Times and Development Costs
So, let us get a bit closer to the what it is I would like to convey. Let us go from one form of validation to another. I have lived in the land of validation and verification. I have seen how doing this early and often allows you to reduce lead times and development costs whilst increasing quality of your products.
During the same period discussions around concepts like “Cyber Physical Simulation” was table stakes. Some of today’s most successful industry organisations took simulation to a point where they had plans to simulate the entire system and product before even the first sheet of metal was bent and the first screw was attached.
Simulation is About Business Outcomes
These dialogues did not evolve around functions and features, they evolved around what business outcome the organisation would be able to achieve if they successfully could validate “the correctness” of things earlier in the product lifecycle. Finding errors and inconsistencies early in the development cycle was monumental for every single organisation we were in dialogue with. The number of examples that has been created to show how the costs grows exponentially the further you get into the product lifecycle process before finding an error or inconsistency, is plenty. But I don’t believe the graphs and examples created by people like myself is the best evidence. To a certain extent I believe the majority of organisations out there just have to take a look in the rear view mirror to get a proof point on why evolving the method of working would make sense.
So how does this relate to evolving our methods of working and what PDSVISION is involved in? In the end it comes back to how we as individuals can improve our way of working and in this specific case to how a mechanical engineer can bring in concepts of real-time simulation into their process of working. Yet again this dialogue should not evolve around functions and features, it should evolve around what values and business outcomes you would generate by allowing validation of design to take place in an earlier phase of the product development.
Based on what I have seen and experienced when it comes to validation, I’m convinced that this is something organisations do need to evaluate and consider, but every situation is unique and therefore I leave it up to you to do the maths!
The benefit for those who decide to do the maths is that the functions and features are in place and should not be a hurdle! If you want to know more about simulations in PTC Creo - read our datasheet Creo Simulation Live.