|
|
|
 |
 |
 |
 |
 |
 |
 |
 |
| |
Realization of an own software suite
Due to the significant reduction of integration efforts, Automation Framework also allows medium-sized companies to present their products together with the corresponding tools on an own platform (suite).
Because Automation Framework provides the open framework for the integration of software tools including their own data management. Due to the possibility to integrate tools of any software manufacturers into the Automation Framework application and to integrate tools especially developed to be used as components in Automation Framework, even most complex and comprehensive automation modules can be created. |
| |
|
| |
 |
The procedure ...
to build a software suite with different tools corresponds, in principle, to the steps when creating (configuring) a tool: Selection of the desired software components (tools) and configuration of the platform via XML data using the Component Configurator utility. |
 |
| |
Integration of software as well as functional engineering are supported in the best possible way. The main benefit is the embracing standardization and reuse when engineering automation software. Particular advantages can be opened up by including sales processes. Automation Framework opens up new prospects from engineering up to marketing of products!
Different Automation Framework tools and suites of different manufacturers are compatible and can be combined. |
 |
| |
|
 |
| |
|
 |
 |
 |
| |
Consistent data management of all tools within the suite
Data consistency is one of the most important basic requirements for the use of the automation platform. Variables, parameters and tags are entered only once and are then available in all various operative areas of the software. In case of changed data, all affected items and locations are updated automatically.
Automation Framework provides two different mechanisms to fulfill these demands for all applications: 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: Consistent data management]
|
 |
| |
 |
 |
 |
| |
Integration levels
Software components can be integrated into AF at different integration levels:
The deepest integration can be achieved with tools that have been developed on the basis of the .NET Framework, i.e. with Automation Framework. In this case, the principles of functional engineering are available to the resulting manufacturer-specific suite for all integrated tools.
Data of existing tools can be integrated at less deeper integration levels via mediators by integrating files and directories according to the database principle, with checking in and out and different observers for data consistency of the tools among each other. Depending on the interfaces of the tools to be integrated, the tools can be started easily without data coupling, data can be handed over via parameters or deep integration of the tool data in Automation Framework can be realized.
Automation Framework supports integration of all Microsoft technologies, from DOS applications to ActiveX controls. |
 |
| |
|
 |
| |
|
 |
| |
 |
 |
 |
| |
Professional catalog handling
Suites, that are based on Automation Framework, allow to summarize project parts in catalogs without being restricted by tool or catalog limits and to reuse these elements. |
 |
| |
|
 |
| |
[AF features: Catalogs]
|
 |
| |
 |
 |
 |
| |
Functional engineering
An engineering suite created on the basis of Automation Framework enables functional engineering. Machines or systems are grouped into automation modules which are not based on specific limits or the purpose of the used tools, but simply on the functional aspects. Automation Framework enables the connection of these modules as well as their different module dates, is responsible for consistent data management and provides the link between data and integrated tools. |
 |
| |
|
 |
| |
[Functional platforms on the basis of Automation Framework]
|
 |
| |
 |
 |
 |
| |
|
|
|
 |
 |
 |
|
KW-Software GmbH
Lagesche Straße 32
32657 Lemgo (Germany)
+49 (0) 52 61 / 93 73-0
info@kw-software.com |
 |
 |
 |
 |
|