Thereare many different ways of implementing a KBEor an “automated”solution.

What is it about?

There are many different ways of implementing a KBE or an “automated” solution. It is not a trivial exercise to find the one approach that best fits your application and at the same time possesses some desirable “ease of use” features, such as most robust, the simpler, etc.. Examples of different ways of implementing automated solutions are: One can build an application using KTI/ICAD IDL language. Many of us --old timers have done that. One can do an application in VBA, many of us done that too. One can built an application in VB Scripts. Some of us have done the same using in KnowledgeWare Tools. Some of us had done it using PKT/GScript Language. Some of us have done using CATIA V5 Templates. In fact, there are many ways of doing (building a KBE application) even within our CATIA KnowledgeWare tools set (KWA, KWE, PKT and BKT). Then, the real question is how should we build this “automated” application so that a resulting “KBE” application exhibits the following characteristics? That a resulting application is dynamic. Rules reconfigure themselves or the outputs based on input changes. That it (my application) is Generic.—many new, known or unknown cases can be derived from one model or a “just-one” code representation. That it’s generative.-- new rule bodies (or models) are created automatically from the old ones (e.g. model templates) based on changes in input specifications. That it’s high level. A small amount of KBE code (in the form of high-level instructions or language) produces significant results (manipulating a large number of objects) That it’s demand-driven. System (knowledge-engine) knows the sequence in which rules become active and controls how those rules get fired.

Featured Image

Why is it important?

Demo–Salient points•Initialize parameters•SmartParts pulled and Rules added•Specs parameters & constraints passed from “systems” to “subsystems”, to “components,” to “parts” during “decomposition” and vice versa during “aggregation”•SmartParts were “instantiated” and constraints satisfied•Solution is reconfigurable for changing spec requirements (16) An Iterative Decision-Based Technique for Finding Topologically-Feasible Solution Sets Quickly | Request PDF. Available from: https://www.researchgate.net/publication/259334677_An_Iterative_Decision-Based_Technique_for_Finding_Topologically-Feasible_Solution_Sets_Quickly [accessed Oct 19 2018].

Perspectives