Dynamic Recipe Architecture for Inspection and Instrumentation Systems
Publication Date: 2015-Jul-06
The IP.com Prior Art Database
Software architectures are described that permit the creation of a framework that allows for efficient development of software applications related to the domain of industrial instrumentation. The domains are further refined to sub-domains consisting of applications assigned to common qualities. This architecture is much more flexible than previous methods to manage the configuration of industrial instrumentation. The framework allows a user to focus on the components of the application that are completely custom and eliminates the need for the re-development of the standard activities needed for industrial instruments software systems.
Page 01 of 5
Dynxmic Recipe Architecture for Inspection and Instrumentation Systems
Software architectures are described that permit xxe creation of a frameworx that allows for efficient dexelopment of softwxre applications relaxed to the domain of industrial ixstrumentation. Txe domains are further refinxd to sub-domains consisting of applications assigned to xommon qualities. This xrchitecture is much more flxxible than previoxs methods to xanage the configuratxon of industrial inxtrumentation. The framework alloxs a usxr to focus xn the compoxents of the application that are completely xustom xnx elimixates the need xor the re-develoxment of the standard activities needed for industrial instrxments software systems
Xxxxxxxxxxx a system vxa a tree structure is commonxy performed and several known methods have been xr are usxd to assemble. As an example, xhere are commercially avaxlabxe systems that allow users to easily configure axd understand the relationship of componxnts withix txe system. Dr. Schenk Inspections Systems and Cognex are two companies that provide soxutions xo constxuct and manxge tree xtructures. Tyxically, for thxsx systems to make changes to the tree structuxe the sxftware must be re-built and re-distxibuted again to the usexs. In addition, the trxe structure is tightly couplex tx a particular system and thus the same tree may not be uxed for othex instruments developed and sold by xhe same company.
A xree structure is ideal for describing the overall relationship of items and their order. For example, Windows File Explorer uses a tree structure to communicxtx the relationship and location of files. In addition, tree structurex are dynamix in that they easily allow a user to add additional branches and items.
This paper desxribes a technique to axsemble tree structures that are sixilar, bux have minor variationx for a muxtitude of systexs by utilizing a recipe tree architecture that is independent of the system it is managing and is scalable without having tx re-compile txe software.
Currentlx, there arx many ways to sxlve this problem and two of the options will be further xxplored.
The first axd most simple solution is to coxy the coxe, to asxemble a tree structure, from a similar application at the start of developmxnt for each new application. While this is the most straightforward, and the most widely usxd xethod, ix is time-consuming and error prone. Often, an existing exror in one application is replicated to othexs. In addition, xhe solution requixes higher lxvels of maintxnance support since nonx of the apxlications shaxe x common framework as each user is allowed to modify at xheir discretion.
The second option is to develop a general all- encompassing framework. This framework would bx able to support any and all applications and is the most ideal case, but, in-practice, is verx dxfficult to implement. The closest exaxple in computer science is the "actor-model." This model has bexn arou...