When you install EB, you will notice that Microsoftís SQL server is also installed. EB uses the SQL database to store all of the static and dynamic data for your project. All data is available to you using the SQL interface within EB. You should not change any data with this third-party program, however, since all of the business-logic between objects is maintained by the EB program. All EB data can be accessed safely via the integrated Visual Basic for Applications (VBA) interface.

You also have to install Microsoftís Visio, since EB uses its stencils, symbols and drawing functions. EB comes with an extensive set of stencils, with master shapes for electro-technical design. And since the world runs on Microsoft, the interface is one that you will already be familiar with.

So if EB uses SQL for the database, and Visio for drawing, what does EB bring to the party? Iíll show you.

I tested the software on a Pentium 4 with 512 megabytes of RAM and Windows 2000. When you install EB, you can use a stand-alone or a network copy. The benefit of the network install is that when you have multiple people working on the project, database updates are immediate since SQL is being used. This real-time team development environment is very cool.

When I use new software, I always start with the help file. But this software came with a quick start guide, as well as a dynamic tutorial introducing the different parts of the program. I found the tutorial lacking in initial value, however, since most of the concepts needed to understand the presentation were unknown at that point.
I then went to the "Getting Results" guide book. This was very helpful, and when I went back to the tutorial, things made a lot more sense.

The help system is context sensitive, so hitting F1 on the keyboard takes you where you need to go. It is a very complete resource, and can be relied on heavily. It has animated sequences to guide you through the steps.
The softwareís object model for the VBA interface can be found in the program directory, so it does not clutter the normal help file.

When you start a new project, you are directed to the main EB window. In the left-hand window, common catalogues, databases and stencils can be found. Project-specific data is under the project tab. How you start a project is up to you. Starting with the drawing or the database can provide you with different entry points, but the results are always the same.

Shapes in Visio are linked to the database to become devices. Once you use a device on the Visio worksheet, the location is stored and the properties associated with the device are shown on the sheet. You can define the device first and then use it, or vice versa.

The database is extensive. All associated data with the device is stored, including where you bought it and its cost.

There is no automatic generation of drawings, but VBA is available to generate scripts to do repetitive tasks. I first created a drawing, then a sheet. I created a new device from the circuit breaker library and identified it as "test device." When I went to edit the drawing, Visio seamlessly popped up with the EB explorer displayed in the left-hand window as an add-in.

I added a three-phase power system and a circuit breaker (shape) from the stencil, and then applied my test device designation to the shape.

As expected, all of the data showed up on the drawing as I had entered it into the database. I generated a BOM, which is dynamic since it is generated from the database. If you make a change on the drawing, the BOM is automatically updated.

There are a few wizards written in VBA. These create devices such as relays for use in your control strategy.
While it is important to view EB as a drawing (or diagramming) database, and not a CAD package, the end result is the same. But I would submit that you get there a lot faster.

The explorer view is well organized, and creating my first drawing was painless. When you select an object or device on the drawing, the associated entry in the database is not selected in the explorer view. Selecting the "Details" tab will show you the device with pins. The command "Find in Equipment" is under development and will be available in a future release. Right mouse clicking, however, will take you to the database entry.
This program is a great effort from Aucotec. It may take a bit of time to master the fundamentals, but the time spent is well worth it.


Jeremy Pollard is a 25-year veteran of the industrial automation industry. He has worked as a systems integrator, consultant and an educator in the field. Jeremy can be reached at This e-mail address is being protected from spambots. You need JavaScript enabled to view it .