
|
Organizers and Guest Editors: Thilo Sauter, Austrian Academy of Sciences and Vienna University of Technology, Austria; and Francisco Vasques, University of Porto, Portugal
Guest Editorial: Communication systems have been an essential part of automation for more than 25 years. In fact, modern automation systems in all their diversity are unthinkable without an equally large diversity of communication systems, filling every application niche. Historically, the need for communication in automation arose when the concept of computer integrated manufacturing (CIM) was introduced in the 1970ies. It defined a hierarchical approach to structure the information flow required for factory and process automation. Clearly, a transparent, multi-level network was needed to achieve this goal [1]. Nevertheless, communication possibilities, let alone computer networks, were limited at that time. Ethernet had just emerged, and dedicated automation networks were not even considered. The evolution of CIM thus went along with the evolution of communication networks, and partially also stimulated it. The need for field-level networking was not clearly perceived and had just slowly become apparent [2]. The late 1980ies and especially the 1990ies saw the development of multiple fieldbus systems tailored to all kinds of application domains, which were proposed together with fierce struggles in the international standardization committees [3]. These dedicated communication networks were in sharp contrast to the already existing local area networks, the distinction relying mostly on the characteristics of the transported data. LANs had high data rates and carried large amounts of data in large packets. Timeliness was not a primary concern, and real-time behavior was not even required. Fieldbus systems, by contrast, were designed for low data rates. Since they mainly transported process data, the size of the data packets was small, and real-time capabilities were important. For some time, these distinction criteria between LANs and field-level networks were adequate and fairly described the situation. Recently, however, drawing the line according to data rates, packet sizes, and timing requirements is no longer applicable. In fact, the boundaries between LANs and fieldbus systems have faded. Today, it is quite common for field-level networks to support applications requiring the transmission of video or voice data, thus reaching the former LAN domain. Nevertheless, the investigation and assertion of real-time behavior has always been an essential topic in research on automation networks [4-9]. After two decades of development, fieldbus systems have found broad acceptance. In recent years, a significant amount of research work has been done to extend fieldbus networks, in order to include wireless segments and mobile nodes [10]. It was demonstrated that an integration of wireless communication channels in traditional fieldbus systems is possible without sacrificing real-time capabilities, albeit with substantial effort [11, 12]. Another important topic of research has been the development of safety networks, which are intended to support distributed applications where reliability and safety issues are of major concern. In addition to the support of traditional process-control applications, recently there is a trend to use specific fieldbus networks also to support safety-related functions, namely to replace the traditional electromechanical protection systems [13, 14]. The most relevant approaches are based on the use of the black-channel concept developed for railway applications [15], where a safety-related middleware provides a set of safe and reliable services to the supported applications. With such approaches, a broad and comprehensive coverage of the field level has been achieved, and not many changes are to be expected in the near future, as far as traditional fieldbus systems are concerned. In a second wave of evolution, however, Ethernet has been penetrating the fieldbus domain for about six years [16, 17]. One of the main arguments for their introduction was the promising integration possibility in company LANs. Although marketing campaigns tried to draw a bright future with Ethernet solving all vertical integration problems, Ethernet on field-level remained disputed mostly due to the lack of real-time capabilities, even for the switched Ethernet solutions common in office LANs. As a response to these inefficiencies, much effort was and is still put in the development of Industrial Ethernet solutions. The target is to create a new generation of fieldbus systems that eventually will replace the traditional ones. Particular emphasis is put on the problems of determinism and real-time capabilities [18-21]. Ethernet is only one example for the impact standards from the office world have had on communication in automation. The evolution of the Internet had an even bigger influence on automation systems, in general, and on their underlying communication systems in particular [3]. Although the Internet consists of much more than the world-wide web, the sheer ubiquity of the WWW and its platform-independent software tools have coined the public perception. Hence it is no wonder that these quasi-standards became attractive for the automation domain. First and foremost, web-based approaches (as well as other Internet-specific protocols) are being used as a means to remotely access automation systems and thus to integrate them into the higher levels of a company hierarchy dominated by office applications. This has finally revived the old CIM idea of vertical integration. Generally speaking, Internet technology seems to make possible what was bound to fail 20 years ago. Examples for this trend are not only the adoption of web standards for business and enterprise integration [22], but also the use of distributed software paradigms – which originated in the Internet – for resource and production planning [23]. This last example is particularly appealing because it bridges the traditional gap between the high-level, information oriented enterprise environment and the low-level, communication oriented factory floor. More related to the actual communication systems, Internet technology is today the basis for device description languages that simplify and unify device and system configuration. At the same time, more and more field devices are equipped with embedded web servers that allow easy remote access via the Internet protocol suite [24]. As a supporting measure, many fieldbus systems have already included in their most recent versions a possibility of tunneling IP traffic over the fieldbus protocol. As a consequence, the traditional multi-level automation hierarchy is dramatically reduced, and the formerly stringent barriers between the levels diminish. In a very abstract functional way, there is a tendency to move ahead into the direction of a flat hierarchy made up of devices, interconnection, and automation applications (Fig. 1). It is also important to recognize that this trend is not restricted to manufacturing or factory automation, but can also be found in other areas like process or building automation, where specific boundary conditions may be different, but the basic tendencies, i.e., the creation of seamless and transparent integration of information management, are identical.
Fig. 1: Reduced functional automation hierarchy As a result, what are the major open issues in automation-related communication? Even though fieldbus systems have reached a mature status, applications have become more demanding, which in turn creates new problems. On the network level, real-time properties and extensions remain an area of interest even for well-known fieldbus systems. Also, the trend at this lower level is the continuously increasing reliability and availability requirements, as they are the core for higher quality and productivity of the supported automation systems. Apart from such low-level aspects, other problems are lurking on the system and application level. One issue is the increasing complexity of automation systems. With the advent of building automation, the usual number of data points has grown, and installations with several thousand nodes are the rule. Not only does this pose a challenge for the communication itself, also the planning and management of such networks is no longer straightforward and requires the application of proper modeling and performance estimation tools. The overwhelming variety of communication systems also necessitated very cumbersome endeavors to unify interfaces and functionalities, at least at the higher level. The definition of the so-called profiles in all kinds of application areas tries to solve this problem [25]. On the other hand, complexity also grows within applications that become increasingly distributed. Concepts like holonic systems or agent-based automation try to increase the flexibility of automation systems throughout the life cycle [23], which in turn requires flexibility from the communication networks. Features like auto-configuration or service brokerage are known from the computer science world and typically demand IP-based means of communication [24, 26]. The last issue currently receiving attention is the security problem that became obvious with the rising degree of interconnection between automation systems. Security had never been given much attention in the fieldbus world, which traditionally consisted of standalone installations [27]. In recent years, however, the connection of automation system and networks to the “outside world” became feasible and (for flexibility and cost reasons) also reasonable. Security becomes an obvious requirement, and solutions tailored to the specific boundary conditions in automation are being investigated on the communication network level [28] as well as for the network interconnections and – on a higher level – the applications [29]. This special section on communication in automation presents, without attempting to give a comprehensive overview, a few aspects of relevant research work being done in this large field. The six papers considered in this special section cover a large range of topics, from the lowest to the highest level of the automation hierarchy. They address real-time communication in both FTDMA and CAN networks, fault-tolerant communication in CAN networks, as well as the modeling and analysis of large building automation networks, QoS-oriented communication scheduling and the use of web services for the vertical integration of enterprise systems. Initially developed for the automotive sector, the Controller Area Network (CAN) is nowadays widespread in distributed embedded systems used at the lowest level of the automation hierarchy, where fault-tolerant and reliable communication using proven-by-use fieldbus systems is an important research issue. The paper “An active star topology for improving fault confinement in CAN networks”, by M. Barranco, J. Proenza, G. Rodríguez-Navas and L. Almeida, presents a new active star topology for CAN networks, called CANcentrate [30]. It is intended to solve some of the dependability problems of CAN networks that are caused by the CAN bus topology. By means of a hub-based approach, the CANcentrate system is able to reduce the number of components whose failure can cause a severe failure of communication, to a unique single point of failure, i.e., the hub. This represents an important step to improve the dependability of CAN networks, as it is easier to improve the dependability for the single hub, than for the many components that may cause a severe failure of communication in a bus topology. The CANcentrate star topology has been implemented and tested, and can be used with any CAN-based protocol. Sharing technology and solutions with the automotive sector has been one of the driven forces for the development of industrial communication solutions, at least for the lowest levels of the communication hierarchy. Common requirements on timeliness, reliability, and availability were one of the enabling factors for such successful interactions. Among the most recent developments from the automotive communication domain, two communication protocols, Byteflight and FlexRay, have been conceived to support high data rates, deterministic behavior, and a high degree of flexibility. Due to the size of the automotive market, low-cost communication products based on these protocols are expected to be available in the near future. Therefore, it is of utmost importance to analyze their underlying concepts, in order to assess their interest and potential to support industrial applications. The paper “On the Properties of the Flexible Time Division Multiple Access Technique”, by G. Cena and A. Valenzano, analyzes the main features of the FTDMA medium access technique used in both Byteflight and FlexRay networks (in FlexRay only for the dynamic segment) [31]. The detailed analysis shows that there is a significant tradeoff between communication efficiency and flexibility, that is, higher flexibility is achieved at the cost of lower performance. Next generation automation systems require the use of communication protocols with both high operational flexibility and increased dependability levels. Such requirements are however in conflict, as the traditional approaches to provide dependability in communication systems consider static table-based traffic scheduling. Such static concepts are not able to adequately support the dynamic communication requirements of an increasing number of applications. The support of dependable communication has been recently addressed in the scope of the FTT-CAN protocol [32]. The paper “Combining Operational Flexibility and Dependability in FTT-CAN”, by J. Ferreira, L. Almeida, J. Fonseca, P. Pedreiras, G. Rodríguez-Navas, J. Rigo and J. Proenza, gathers and reviews the main mechanisms that were recently developed to provide FTT-CAN with an adequate level of dependability, while preserving its high level of operational flexibility provided [33]. In the domain of building automation, networks with tens of thousands of elements, like sensors, controllers or actuators, are common. Even though the individual message streams typically have weak real-time requirements, their huge number may lead to timing-related failures or to communication bottlenecks. In addition, the use of CSMA-based access schemes, where time bounds cannot be guaranteed, can cause instable control cycles, discomfort, and malfunction. The paper “Automated Modeling and Analysis of CSMA Type Access-Schemes for Building Automation Networks”, by J. Ploennigs, P. Bucholz, M. Neugebauer and K. Kabitzsch, proposes an automated modeling approach to deal with large building automation networks, gathering information that is mostly already available from the design tool, and therefore facilitating dimensioning of the system and performance prediction before implementation [34]. The process of automated performance analysis relies on a network model providing the structural details for the analysis, and a traffic model that supplies the parameterization details. It allows the implementation of an efficient and reliable design process, where bottlenecks can be identified at an early stage, and the utilization and latency of the network can be easily computed. The design of hard real-time systems is often hindered by the consideration of worst-case conditions that seldom occur. As a consequence, there is the need to allocate a large amount of computing resources that are hardly ever used at run time. Conversely, for soft real-time systems requiring only statistic timing guarantees, it can be suitable to have a system design based on average-case conditions. However, for IP-based communication systems that are often found in the automation world, providing only statistic deadline guarantees can be unacceptable. For this type of applications, a more precise specification on how the deadline misses are distributed in time is necessary. If the supported applications are able to tolerate a specified percentage of non-consecutive deadline misses, such behavior can be modeled using the (m,k)-firm paradigm. The paper “Providing Real-Time Applications with Graceful Degradation of QoS and Fault-Tolerance according to the (m,k)-firm Model”, by J. Li, Y. Song and F. Simonot-Lion, addresses a question that has received growing interest during the last years, namely, the flexibility to combine QoS (Quality of Service) adaptation with minimum QoS guarantees [35]. The target of the presented work is the provision of dynamic QoS management and fault-tolerance to the supported applications. Finally, on the highest level of the automation hierarchy, flexibility and interoperability are key issues. Internet technology provides the unifying framework for the horizontal and vertical integration of diverse systems and applications both inside a plant and between plants or even different enterprises. The paper “Vertical Integration of Enterprise Industrial Systems Utilizing Web Services”, by A. Kalogeras, J. Gialellis, C. Alexacos, M. Georgoudakis and S. Koubias, addresses the need for uniform interfaces and proposes web services as an easily available and platform-independent middleware technology to solve the problem [36] Flexibility is achieved by a modular structure which decouples the enterprise workflows from the actual web services and links them dynamically with an ontology describing the business logic. A special section like the present one requires the support of many people, and we would thus like to thank all of them: the authors for their contributions and revisions; the reviewers for their careful and thorough review work, which contributed significantly to the quality of the papers that finally made their way into this section, and last not least, the editors of the transactions for guiding the evolution of this section from the first idea until its publication.
References [1] J. P. Thomesse, “Fieldbuses and interoperability”, Control Engineering Practice, vol. 7, 1999, pp. 81-94. [2] M. Mariton, “Local Area Networks and Future Process Control Systems,” IEEE Control Systems Magazine, vol. 6, no. 2, 1986, p. 27. [3] T. Sauter, Fieldbus Systems: History and Evolution, in: R. Zurawski (Ed.), The Industrial Communication Technology Handbook, CRC Press, 2005, pp. 7-1 – 7-39. [4] L. Pinho, F. Vasques, Reliable Real-Time Communication in CAN Networks", IEEE Transactions on Computers, Volume 52, Issue 12, Dec. 2003 Page(s): 1594 - 1607. [5] Cavalieri, S., “Meeting Real-Time Constraints in CAN”, IEEE Trans. on Industrial Informatics, 2005, vol. 1, no. 2, pp. 124-135. [6] Nolte, T.; Nolin, M.; Hansson, H.A., “Real-Time Server-Based Communication With CAN”, IEEE Trans. on Industrial Informatics, 2005, vol. 1, no. 3, pp. 192-201. [7] L. Almeida, E. Tovar, J. Fonseca, F. Vasques, Schedulability Analysis of Real-Time Traffic in WorldFIP Networks: an Integrated Approach, IEEE Transactions on Industrial Electronics, Vol. 49, nº 5, October 2002. [8] E. Tovar, F. Vasques, A. Burns, Communication Response Time in P-NET Networks: Worst-Case Analysis Considering the Actual Token Utilisation", Journal of Real-Time-Systems, 22, 229-249, 2002. [9] E. Tovar, F. Vasques, Real-Time Fieldbus Communications Using Profibus Networks, IEEE Transactions on Industrial Electronics, Vol. 46, nº 6, pp 1241-1251, December 1999. [10]J.-D. Decotignie, “Wireless fieldbusses – a survey of issues and solutions”, 15th IFAC World Congress on Automatic Control, Barcelona, Spain, 2002. [11]M. Alves, E. Tovar, F. Vasques, “On the Adaptation of Broadcast Transactions in Token-Passing Fieldbus Networks with Heterogeneous Transmission Media”, IFAC Int. Conference on Fieldbus Systems and their Applications (FeT’01), 15-16 Nov. 2001, Nancy, France, pp. 278-284. [12]M. Alves, E. Tovar, F. Vasques, G. Hammer, K. Rother, Real-Time Communications over Hybrid Wired/Wireless PROFIBUS-based Networks, 13th Euromicro Conference on Real-Time Systems (ECRTS'02) , Vienna, Austria, June 2002, pp. 142-151. [13]R. Piggin, A Fieldbus for Machine Safety, IEE Review, Volume 46, Issue 4, July 2000 Page(s):33 - 37. [14]R. Piggin, Safety Networking – New technology enables greater flexibility, ISA InTech, May 2004.. [15]IEC 62280-1: Railway Applications – Communications, Signalling and Processing Systems – Part I: Safety Related Communication in Closed Transmission Systems, Ed. 1.0 b: 2002. [16]M. Felser and T. Sauter, “Standardization of Industrial Ethernet – the next battlefield?”, IEEE International Workshop on Factory Communication Systems (WFCS), Wien, 22-24 Sep. 2004, pp. 413-421. [17]L. Lo Bello, O. Mirabella, “Design Issues for Ethernet in Automation”, ETFA 2001, vol. 1, pp. 213-221. [18]LoBello, L.; Kaczynski, G.A.; Mirabella, O., “Improving the Real-Time Behavior of Ethernet Networks Using Traffic Smoothing”, IEEE Trans. on Industrial Informatics, 2005, vol. 1, no. 3, pp. 151-161. [19]Pedreiras, P.; Gai, P.; Almeida, L.; Buttazzo, G.C., “FTT-Ethernet: A Flexible Real-Time Communication Protocol That Supports Dynamic QoS Management on Ethernet-Based Systems”, IEEE Trans. on Industrial Informatics, 2005, vol. 1, no. 3, pp. 162-172. [20]Skeie, T.; Johannessen, S.; Holmeide, O., “Timeliness of real-time IP communication in switched industrial Ethernet networks”, IEEE Trans. on Industrial Informatics, 2006, vol. 2, no. 1, pp. 25-39. [21]R. Moraes, F. Vasques, Probabilistic Timing Analysis of the h-BEB Collision Resolution Algorithm, 6th IFAC International Conference on Fieldbus Systems and their Applications (FeT’2005), November 14-15, 2005, Puebla, México. [22]T. Sauter, “Integration Aspects in Automation – a Technology Survey”, 10th IEEE International Conference on Emerging Technologies and Factory Automation (ETFA), Catania, 19.-22. Sep. 2005, vol. 2, pp. 255-263. [23]J. Peschke, A. Lüder, A. Klostermeyer, A. Bratoukhine, and T. Sauter, Distributed Automation: PABADIS vs. HMS, IEEE Trans. on Industrial Informatics, 2005, vol. 1, no. 1, pp. 31-38. [24]Jammes, F.; Smit, H., “Service-Oriented Paradigms in Industrial Automation”, IEEE Trans. on Industrial Informatics, 2005, vol. 1, no. 1, pp. 62-70. [25]Benzi, F.; Buja, G.S.; Felser, M., “Communication Architectures for Electrical Drives”, IEEE Trans. on Industrial Informatics, 2005, vol. 1, no. 1, pp. 47-53. [26]Lastra, J.L.M.; Delamer, M., “Semantic web services in factory automation: fundamental insights and research roadmap”, IEEE Trans. on Industrial Informatics, 2006, vol. 2, no. 1, pp. 1-11. [27]A. Treytl, T. Sauter, and C. Schwaiger, “Security Measures for Industrial Fieldbus Systems - State of the Art and Solutions for IP-based Approaches”, IEEE International Workshop on Factory Communication Systems (WFCS), Wien, 22.-24. Sep. 2004, pp. 201-209. [28]Long, M.; Wu, C.-H., “Energy-efficient and intrusion-resilient authentication for ubiquitous access to factory floor information”, IEEE Trans. on Industrial Informatics, 2006, vol. 2, no. 1, pp. 40-47. [29]Xu, Y.; Song, R.; Korba, L.; Wang, L.; Shen, W.; Lang, S., “Distributed Device Networks With Security Constraints”, IEEE Trans. on Industrial Informatics, 2005, vol. 1, no. 4, pp. 217-225. [30]M. Barranco, J. Proenza, G. Rodríguez-Navas L. Almeida, “An active star topology for improving fault confinement in CAN networks”, IEEE Trans. Industrial Informatics, 2006, vol. 2, no. 2, pp. ##-##. [31]G. Cena, A. Valenzano, “On the Properties of the Flexible Time Division Multiple Access Technique”, IEEE Trans. Industrial Informatics, 2006, vol. 2, no. 2, pp. ##-##. [32]L. Almeida, P. Pedreiras, J. Fonseca, The FTT-CAN protocol: why and how, IEEE Transactions on Industrial Electronics, Volume 49, Issue 6, Dec. 2002 Page(s):1189 - 1201 [33]J. Ferreira, L. Almeida, J. Fonseca, P. Pedreiras, G. Rodríguez-Navas, J. Rigo, J. Proenza, “Combining Operational Flexibility and Dependability in FTT-CAN”, IEEE Trans. Industrial Informatics, 2006, vol. 2, no. 2, pp. ##-##. [34]J. Ploennigs, P. Bucholz, M. Neugebauer, K. Kabitzsch, “Automated Modeling and Analysis of CSMA Type Access-Schemes for Building Automation Networks”, IEEE Trans. Industrial Informatics, 2006, vol. 2, no. 2, pp. ##-##. [35]J. Li, Y. Song, F. Simonot-Lion, “Providing Real-Time Applications with Graceful Degradation of QoS and Fault-Tolerance according to the (m,k)-firm Model”, IEEE Trans. Industrial Informatics, 2006, vol. 2, no. 2, pp. ##-##. [36]A. Kalogeras, J. Gialellis, C. Alexacos, M. Georgoudakis, S. Koubias, “Vertical Integration of Enterprise Industrial Systems Utilizing Web Services”, IEEE Trans. Industrial Informatics, 2006, vol. 2, no. 2, pp. ##-##. Francisco Vasques (M'00) was born in Porto, Portugal, in 1964. He received the “Licenciatura” degree in electrical engineering from the University of Porto, Portugal, in 1987 and both the MSc and PhD degrees in computer science from LAAS-CNRS, Toulouse, France, in 1992 and 1996, respectively. From 1996 to 2004 he was Assistant Professor of the University of Porto. Since 2004, he is Associate Professor of the University of Porto, where he teaches Real-Time Systems, Safety-Critical Computer Systems and Industrial Communication Systems. His current research interests include real-time communication systems, real-time factory communications, fault-tolerant systems, and real-time system architectures. Additionally, he is also interested in safety-critical computing systems and communications. He served as Program Co-Chairman for the 2000, 2004 and 2006 editions of the IEEE Workshop on Factory Communication Systems. He is author or coauthor of more than 75 technical papers in the area of real-time systems and factory communications.
|
