Why is “Knowledge Automation” useful

Knowledge Automation is the term used to describe various technologies and techniques that capture knowledge that is integral to the running of your business and make it available, in an automated manner, to people who need it. Quoting an article from LinkedIn, “Knowledge Automation is a new way to make sure every individual at your company has what they need for the daily battle.”

An interesting study done by the McKinsey Global Institute on the potential economic impact in 2025 of various “Technology Waves”, forecasts that the “Automation of knowledge work” will potentially have the highest impact – see the image, below:

This is hardly surprising. When the expert knowledge that is inherent to any complex technology is captured and then deployed with an easy-to-use interface that hides the underlying technical terminology, the power of this technology is made available to non-experts. A ubiquitous example of this is the Navigation App on your cell phone! Consider for a moment how easy it is for anyone to use this App and all its complex technologies that have vanished behind a simple interface! Indeed, this is exactly the goal of Simulation Automation Templates.

A simulation template is set up to answer one or more questions about a design at some predefined level of model fidelity. It captures the (simulation) expertise that is required to drive various simulation tools to accurately and robustly provide the answers. It must also ensure that the automated use of the template (its use without the manual intervention of experts) is “safe”. A non-expert user of the template is forced to use it within predefined acceptable bounds and when that is enforced, the results that are obtained are accurate within some known error tolerance.

In summary, a well-designed Simulation Automation Template will satisfy the following requirements:

This is not easy to accomplish, especially when you add a further requirement that the template must work robustly not only across a significant portion of the design space, but also across an entire product family that shares a common functional architecture.

Hold this critical thought – we will get back to it often in future blogs!