Feature Process automation
common 'look and feel' among all applications is essential to make the software intuitive by nature. Also important is the use of built-in intelli- gence, for example making objects, tools or data that are related to the cur- rent task appear automatically via pop-up menus, as opposed to making the user search for them. This gives the user the feeling that the software is anticipating each move and in the background shortening the steps to complete certain tasks.
One of the problems associated with working with automation systems has been the management of controller data. PLCs typically offer only simple data structures. As visualisation soft- ware has replaced dedicated displays, the database has moved to operator panels or industrial PCs where data can be manipulated in a freer environ- ment. 'Tags' or virtual data that point to fixed PLC addresses have been cre- ated to allow users to process data in a wide variety of data formats or group dissimilar data types together in logi- cal object-orientated structures. In the past, data management prob- lems were caused by the fact that data 'lived' at no single location but was dispersed among several devices in an automation system including PLCs,
motion controllers, operator panels, IPCs and even some smart field devices. Creating a new data point in one system necessitated the creation of corresponding tags in the other sys- tems if this information was to be shared. The challenge for modern engineering tools is to unite all system data in a single common database that is accessible by all devices and the open framework will support this objective. Such a platform dramati- cally increases the efficiency with which automation systems can now be engineering and deployed.
Long-term planning
As an engineering framework is simply an environment for applica- tions to run and interact with each other, ends users need to make a true commitment when deciding on a framework versus individual applica- tions approach because of future support and compatibility issues. Long-term planning to integrate future software solutions into the framework needs to be recognised as an important consideration if the ultimate benefit of a framework strategy is to be realised. Frameworks need to be 'open' in the sense that they allow users to cus- tomise or automate certain routine
functions and this, for example, would be relevant in the case of a machine builder creating a routine to automati- cally put together blocks of PLC code from a library of program modules. Finally, an engineering framework needs to justify and protect a user's investment by being scalable across current and future applications. It should provide blanket coverage across all applications from PLC to DCS programming, from motion con- trol to field device parameterising, from wireless network setup to field- bus configuration and from operator panel design to safety programming. The benefit of a single engineering environment that releases the true potential of automation technology through software-based engineering tools that can seamlessly interact is clear. It will underpin efforts to achieve real operational efficiencies and production flexibility and create a solid foundation to help manufactur- ers in highly competitive sectors such as food and beverage, pharmaceutical and consumer packaged goods com- pete locally, nationally and globally. Siemens Industry Automation & Drive Technologies T: 0845 7705070
Enter 224
www.siemens.co.uk/automation
Enter 22
Enter 23
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44