|
|
|
 |
 |
 |
 |
 |
 |
 |
 |
| |
Consistent and common data management ...
... for all tools included in the framework: The data management of each integrated tool is undertaken by the Automation Framework and executed by Automation Framework mechanisms. |
| |
|
| |
ObjectStore and mediators
In order to fulfill the absolute demand for a consistent data management within a software platform created with AF application-wide, Automation Framework provides two different mechanisms: ObjectStore and mediator concept.
The ObjectStore is the basis for the central data management. It builds the technical basis on which specific data models used, for instance, to process device data (e.g. sensor data, I/Os, network configurators, ...) and drive data have been developed. Data storage is done in XML format or in a binary format. Existing devices can be imported, new devices are created using the Catalog Editor and new device classes are specified via UML.
The mediator concept allows the functional coupling of applications, each of which has its own data management. All applications integrated in the automation suite make the relevant part of their data available (variables, tags, parameters). If these data are used in other applications, the mediators ensure that the necessary data updates are performed.
Both methods of data management can be mixed within an automation suite, allowing that already existing software can also be included. |
 |
| |
|
 |
| |
[AF features - basic functionalities]
|
 |
| |
 |
 |
 |
| |
Observers ensure data consistency
The following figure shows an everyday scenario in an application suite: Four tools are linked to a common data management. After the variable 'Speed' has been changed for example in the programming system (named "PLC" in the figure), this change is registered by so-called observers and all participating tools are automatically informed. Thus, changes have to be entered only once and are then permanently available for all tools. |
 |
| |
 |
 |
| |
|
 |
| |
 |
 |
 |
| |
Software platforms over a common data model
In Automation Framework, integration is done using a common model. This especially applies for all data that have to be exchanged between the tools. The model ensures that all tools work for one element type on the same implementation of this type. Each software tool, that is developed based on Automation Framework, can directly use this common data model in order, for example, to realize and define own products. Completed components can immediately work with these products because they have been developed on basis of the data model. Additional properties can be added using new or correspondingly extended components. |
 |
| |
|
 |
| |
|
 |
| |
 |
 |
 |
| |
Data integration levels: From import/export up to complete integration
The first step on the way to a complete integration of existing tools into a software platform are import and export functions. These functions mainly make sense if no high dynamic is required, for example, in case of tools in different areas of applications if data are exchanged between different persons or companies. However, if tools are used together within the same area of application, a higher dynamic is required. The formerly autarkic tools are combined in an integrated environment and specific data have to be exchanged via automated interfaces. |
 |
| |
|
 |
| |
|
 |
| |
 |
 |
 |
| |
|
|
|
 |
 |
 |
|
KW-Software GmbH
Lagesche Straße 32
32657 Lemgo (Germany)
+49 (0) 52 61 / 93 73-0
info@kw-software.com |
 |
 |
 |
 |
|