The Tool Builder: Configuring instead of programming

The Tool Builder enables manufacturers of engineering software a simple introduction to object-oriented programming with Microsoft.NET. New software tools can be developed twice as fast with it and are thus much more cost-effective than before. Development of the tools is simplified because tools are now created mainly through configuration and reuse of available objects, instead of programming.

Microsoft.net as a technological basis is going to considerably influence the software development during the next years. Thus, the compatibility of software based on the Tool Builder will be ensured for many years.

The tool construction kit

This is how easily you can create your tool with the Tool Builder

The following graphic gives an overview of the development phases and possibilities to develop a new tool with the Tool Builder via configuration and reusing of a new tool.

Flexible design of the interfaces with the Project Editor

In a first step the user interface can be based on the existing Tool Builder user interface, in other words the Automation Framework Project Editor. We call this process rapid prototyping. Colors, icons, menu bar and toolbar can be adapted to customer needs. The Engineering Step bar allows to structure the user interface according to the given functionality. The development of PlugIns using C# as well as their easy integration ensure a high degree of freedom and flexibility.

Great number of available basic functions
All important basic functions, such as password protection, multi-language, undo, help, error messages, search functions and many more are already implemented.

AF standard PlugIns and own PlugIns
PlugIns integrate their interface, functionality and data management into your tool.
PlugIn tools which you have already created based on the Tool Builder can be easily integrated into your new tool: A PlugIn manager provides all management functions for this deepest integration level.
However, already existing "traditional" software can also be integrated:

• either via adapter PlugIns,
• or with the supplied standard PlugIn "Program Launcher", which enables a simple invocation of each program from the project tree,
• or as ActiveX Controls.

Investments so far into engineering tools are thus not obsolete, but can still be used profitably.

Clear catalog handling
With the help of the Tool Builder, own (device) catalogs can be defined, imported (e.g. in XML, GSD format) and managed hierarchically. In the catalogs, you can derive your specific objects from basic objects, configure and specialize them, manage them and make them available for reuse. Via drag & drop the individual catalog objects can be reused in the project tree of the Project Editor.

Integrated data management
The storage of data and the linking to a data management are already implemented. In the most simple case data are stored in an Access database. XML and OLE DB are available formats. Integrated tools completely transfer their data management to Automation Framework. In case of a .NET-based tool, this happens completely automatic, in case of "traditional" software (also see section "PlugIns" above), on the other hand, the supplied standard PlugIns support data integration.

Online functionality
A Runtime Manager allows to establish an online connection to a device. Based on an OPC connection or using a customer-specific runtime PlugIn, online data transfer is possible.

 [General features of Automation Framework]
 [Technological basics of Automation Framework]
 [Details on catalog handling in Automation Framework]