D2.1\Tspecification of the Amigo Abstract Middleware

Total Page:16

File Type:pdf, Size:1020Kb

D2.1\Tspecification of the Amigo Abstract Middleware IST Amigo Project Deliverable D2.1 Specification of the Amigo Abstract Middleware Architecture Public April 2005 Public Project Number : IST-004182 Project Title : Amigo Deliverable Type : Report Deliverable Number : D2.1 Title of Deliverable : Specification of the Amigo Abstract Middleware Architecture Nature of Deliverable : RE Internal Document Number : Amigo_WP2_D2.1_v10 final.doc Contractual Delivery Date : 28 February 2005 Actual Delivery Date : 11 April 2005 Contributing WPs : WP2 Editor : INRIA: Nikolaos Georgantas Author(s) : INRIA: Sonia Ben Mokhtar, Yérom-David Bromberg, Nikolaos Georgantas, Valérie Issarny, Laurent Réveillère, Daniele Sacchetti, Ferda Tartanoglu FT: Anne Gerodolle, Gilles Privat, Fano Ramparany, Mathieu Vallée Ikerlan: Jorge Parra IMS: Marco Ahler, Viktor Grinewitschus, Christian Ressel Microsoft: Ron Mevissen Philips: Harmke de Groot, Michael van Hartskamp, Peter van der Stok, Bram van der Wal TELIN: Tom Broens, Henk Eertink, Aart van Halteren, Remco Poortinga, Maarten Wegdam TID: Sara Carro Martinez, José María Miranda, Johan Zuidweg VTT: Jarmo Kalaoja, Julia Kantorovitch, Jiehan Zhou Amigo IST-2004-004182 3/227 April 2005 Public Abstract This report elaborates the design of the Amigo abstract architecture focusing on the middleware architecture. The key Amigo property addressed is interoperability and integration of the four application domains of the networked Amigo home, namely, the mobile, personal computing, consumer electronics and home automation domains. Interoperability is pursued: first, by adopting service-orientation as the essential architectural paradigm to enable ad hoc coupling between services; second, by specifying an abstract service-oriented architecture subject to limited technology-specific restrictions to enable representation of the heterogeneous domains and of the diverse related technologies; and, third, by elaborating appropriate interoperability methods within the abstract architecture. Interoperability methods are based on the abstraction of common architectural, including behavioral, features of existing service infrastructures, and on the semantic modeling of these features for making them machine-interpretable. Concrete interoperability methods are elaborated for service composition at application level, and for service discovery and interaction at middleware level. Our elaboration initially draws from the personal computing and mobile domains, where there exist already mature service-oriented architecture paradigms. Nevertheless, the consumer electronics and home automation domains are, then, effectively integrated building on the introduced Amigo abstract architecture. The particularity of these two domains leads as: for the former, to adopt the DLNA guidelines, which establish a number of standard technologies for interoperability targeting the – very demanding in performance – multimedia streaming; and for the latter, to introduce dedicated, low-level, interoperability mechanisms. Finally, within the Amigo abstract architecture, security and privacy is addressed as a principal requirement for the Amigo home. Keyword list ambient intelligence, networked home system, mobile/personal computing/consumer electronics/home automation domain, interoperability, service-oriented architecture, semantic modeling, middleware, service discovery protocols, service composition, context-awareness, quality of service, multimedia streaming, security, privacy. Amigo IST-2004-004182 4/227 April 2005 Public Table of Contents Table of Contents .....................................................................................5 Figures ....................................................................................................11 Tables......................................................................................................14 1 Introduction.......................................................................................15 1.1 Middleware-related properties for the networked home system......................... 15 1.1.1 Interoperability .................................................................................................... 16 1.1.2 Security, privacy and safety................................................................................ 17 1.1.3 Mobility................................................................................................................ 17 1.1.4 Context-awareness............................................................................................. 18 1.1.5 Quality of service ................................................................................................ 20 1.2 Document structure................................................................................................. 20 2 Service-orientation for Amigo .........................................................23 2.1 Service-Oriented Architecture (SOA)..................................................................... 24 2.1.1 Service-oriented architectural style..................................................................... 24 2.1.1.1 Key properties of service-orientation.......................................................................................... 26 2.1.1.2 Reference service-oriented architecture .................................................................................... 27 2.1.1.3 SOA and Web Services ............................................................................................................. 28 2.1.2 Semantic Web and Semantic Web Services ...................................................... 30 2.2 Modeling services for Amigo.................................................................................. 32 2.2.1 Modeling components......................................................................................... 33 2.2.1.1 Example..................................................................................................................................... 35 2.2.2 Modeling connectors........................................................................................... 37 2.2.2.1 Example..................................................................................................................................... 39 2.3 Semantics-based service interoperability ............................................................. 40 2.3.1 Interoperability at connector/middleware level.................................................... 41 2.3.1.1 Conformance relation................................................................................................................. 41 2.3.1.2 Interoperability method .............................................................................................................. 41 2.3.1.3 Example..................................................................................................................................... 42 2.3.2 Interoperability at component/application level................................................... 45 2.3.2.1 Conformance relation................................................................................................................. 45 2.3.2.2 Interoperability method .............................................................................................................. 46 2.3.2.3 Example..................................................................................................................................... 47 2.4 Related work............................................................................................................. 48 2.5 Discussion................................................................................................................ 50 3 Amigo abstract reference service architecture..............................53 3.1 Amigo application layer .......................................................................................... 55 3.1.1 QoS-aware services ........................................................................................... 56 Amigo IST-2004-004182 5/227 April 2005 Public 3.1.2 Context-aware services ...................................................................................... 56 3.2 Amigo middleware layer.......................................................................................... 58 3.2.1 Amigo service discovery ..................................................................................... 59 3.2.1.1 Amigo enhanced service discovery............................................................................................ 63 3.2.1.2 Amigo interoperable service discovery ...................................................................................... 65 3.2.1.3 Mapping between enriched service description and legacy SDPs ............................................. 67 3.2.1.4 Security and privacy for service discovery ................................................................................. 69 3.3 Amigo platform layer ............................................................................................... 69 3.4 Discussion................................................................................................................ 70 4 Application-layer interoperability methods....................................71 4.1 Ad hoc composition of services............................................................................. 72 4.1.1 Abstract composition description ........................................................................ 72 4.1.2 Modeling
Recommended publications
  • Zigbee-Based System for Remote Monitoring and Control of Switches
    Copyright is owned by the Author of the thesis. Permission is given for a copy to be downloaded by an individual for the purpose of research and private study only. The thesis may not be reproduced elsewhere without the permission of the Author. ZigBee-Based System for Remote Monitoring and Control of Switches A thesis presented in partial fulfilment of the requirements for the degree of Master of Engineering at Massey University, Albany, New Zealand. © Matthew Lyon October 2010 1 Abstract Home automation technology has existed for nearly four decades, but is nonetheless mostly absent in the average home today. The systems that do exist are often highly customised and expensive, catering to a very niche market, or overly sophisticated and complicated. Many of these also require extensive, dedicated cabling as their communications backbone and as such are only practical to install during the construction of a new house. The core aims of this project are to develop a cheap and simple home automation system that can be easily installed in new and existing houses. These aims are achieved by creating a centralised system where most of the intelligence is managed by a PC server and the end nodes are kept as simple as possible. The server is responsible for basic security, maintaining awareness of the current system state and providing the user interface. At the outer edge of the system is a ZigBee network of wall switches and, in between, a home gateway provides a protocol translation service between the two. The new, “smart” switches are designed to be entirely compatible with existing wall switches in terms of their mounting and wiring requirements, and so ZigBee is chosen to provide a reliable wireless communication channel between the end nodes and the gateway.
    [Show full text]
  • SMART HOME SYSTEMS with the Contribution Of
    Branko Dvoršak Juraj Havelka Elena Mainardi Hrvoje Pandžić Tea Selič Mario Tretinjak SMART HOME SYSTEMS With the contribution of: Vanja Husein Claudia Pacchiega Goran Švast 2 This publication is part of the SHVET project (https://www.smart-hvet.eu/), and has been made possible with the contribution of (in alphabetical order): Center Republike Slovenije za poklicno Izobraževanje (Slovenia) Centoform (Italy) Ecipa Nordest (Italy) Območna Obrtno-Podjetniška zbornica Krško (Slovenia) Obrtničko učilište – ustanova za obrazovanje odraslih (Croatia) Šolski center Novo mesto (Slovenia) Sveučilište u Zagrebu Fakultet elektrotehnike i računarstva (Croatia) This project has been funded with support from the European Commission. This publication reflects the views only of the authors and the Commission cannot be held responsible for any use which may be made of the information contained therein. 3 TABLE OF CONTENTS page 1 INTRODUCTION 4 1.1 WHAT EXACTLY IS A "SMART HOUSE" 5 1.2 HOME AND BUILDING AUTOMATION 6 1.3 FUNCTIONS YOU CAN DO WITH A SMART HOME SYSTEM 6 2 DIFFERENCE BETWEEN A SMART HOME SYSTEM AND A STANDARD ELECTRIC PLANT 13 2.1 ELEMENTS OF A CLASSIC RESIDENTIAL INSTALLATION 13 2.2 STRUCTURE OF A SMART HOME SYSTEM 18 2.3 MODULES OF A SMART HOME SYSTEM 20 3 SMART HOME SYSTEM TECHNOLOGIES 26 3.1 OVERVIEW OF AUTOMATION AND CONTROL TECHNOLOGIES 25 3.2 WHY KONNEX 28 4 KONNEX 30 4.1 HISTORY OF KNX/EIB AND KONNEX ORGANIZATION 30 4.2 TRANSMISSION MEDIA 30 4.3 NET ARCHITECTURE 32 4.4 TOPOLOGY 35 4.5 ADDRESSES 36 4.6 TELEGRAM 38 4.7 PARAMETERIZATION
    [Show full text]
  • Open Systems for Homes and Buildings: Comparing Lonworks and KNX Alan Kell Peter Colebrook I&I Limited
    Open Systems for Homes and Buildings: Comparing LonWorks and KNX Alan Kell Peter Colebrook i&i limited No part of this publication may be transmitted or reproduced in any form or by any means, electronic or mechanical, for any purpose, without the prior written permission of i&i limited. Trademarks and Logos i&i and Proplan are trademarks of i&i limited. KNX, EIB, European Installation Bus, EHS, European Home Systems and BatiBUS are trademarks of The Konnex Association and its constituent associations; European Installation Bus Association (EIBA), European Home Systems Association (EHSA) and Club BatiBUS International (BCI). Echelon, LON, LONWORKS, LONMARK, LonBuilder, NodeBuilder, LonManager, LonTalk, LonUsers, LonPoint, Digital Home, Neuron, 3120, 3150, LNS, i.LON, LONWORLD, the Echelon logo, and the LonUsers logo are trademarks of Echelon Corporation registered in the United States and other countries. LonMaker, Panoramix, and Networked Energy Services Powered by Echelon are trademarks of Echelon Corporation. All other brand names and product names are trademarks or registered trademarks of their respective holders. About i&i limited Alan Kell was the principal author of the 1993 study by DEGW etl1 entitled “Bus Systems for Building Control” which was the first detailed study in this area to compare, among others, EIB and LONWORKS in the context of building control. Peter Colebrook collaborated closely with Siemens in Regensburg in the late 1980’s, was one of the 12 founder signatories of the European Installation Bus Association (EIBA) and subsequently served as a Director of that Association. He was also one of the founders of the LONMARK Interoperability Association and similarly served as a Director of that Association.
    [Show full text]
  • Low Cost Devices for Home Automation Systems
    INTERNATIONAL SCIENTIFIC JOURNAL "INNOVATIONS" WEB ISSN 2534-8469; PRINT ISSN 1314-8907 LOW COST DEVICES FOR HOME AUTOMATION SYSTEMS Pancho Tomov Technical University, Sofia, Bulgaria email: [email protected] Abstract: The article presents the design of Home Automation System (HAS) with low cost and wireless system. This system is intended to help and supply support so as to meet the requirements of older and disabled in home. Also, the good home conception within the system improves the quality living reception. The switch mode and voice mode square measure accustomed management the house appliances. The video feedback is received within the automaton application that streams the video of IP Camera. The main control system implements wireless technology to provide remote access from smart phone. The design remains the prevailing electrical switches and provides additional safety management on the switches with low voltage activating methodology. The switches standing is synchronized altogether the system whereby each computer program indicates the real time existing switches standing. The system meant to regulate electrical appliances and devices in house with comparatively low price style, user-friendly interface and ease of installation. Keywords: HOME AUTOMATION, AUTOMATION PROTOCOLS, LOW COST CONTROLLERS 1. Introduction Google in May 2011. The system is declared to figure with a mesh Home automation is outlined as single or networked devices and network within the 900MHz frequency bands. Google chose systems that raise the protection and snugness of homes, maintain 900MHz because it is least likely to be crowded than the wi_ 2400 pleasant indoor conditions energy efficiently, facilitate inhabitant’s spectrum. It is assumed that their protocol, announced in the residency and coping of everyday chores and enable.
    [Show full text]
  • Industrial Automation Automation Industrielle Industrielle Automation
    www.infoPLC.net Industrial Automation Automation Industrielle Industrielle Automation 3 Industrial Communication Systems Field bus: standards 3.3 Bus de terrain standard Standard-Feldbusse Prof. Dr. H. Kirrmann 2005 April, HK ABB Research Center, Baden, Switzerland Field busses: Standard field busses 3.1 Field bus types Classes Physical layer Networking 3.2 Field bus operation Centralized - Decentralized Cyclic and Event Driven Operation 3.3 Field bus standards International standard(s) HART ASI Interbus-S CAN Profibus LON Ethernet Automotive Busses Industrial Automation 2 3.3 Standard Field Busses Which field bus ? • A-bus • IEEE 1118 (Bitbus) • Partnerbus • Arcnet • Instabus • P-net • Arinc 625 • Interbus-S * * • Profibus-FMS * • ASI • ISA SP50 • Profibus-PA • Batibus • IsiBus • Profibus-DP • Bitbus • IHS * • CAN • ISP • PDV • ControlNet • J-1708 * • SERCOS • DeviceNet • J-1850 • SDS • DIN V 43322 • LAC • Sigma-i • DIN 66348(Meßbus) * • LON • Sinec H1 • FAIS • MAP • Sinec L1 • EIB • Master FB • Spabus • Ethernet • MB90 • Suconet • Factor • MIL 1553 • VAN • Fieldbus Foundation • MODBUS • WorldFIP • FIP * • MVB • ZB10 • Hart • P13/42 • ... • IEC 61158 • P14 Industrial Automation 3 3.3 Standard Field Busses Worldwide most popular field busses Bus User* Application Sponsor CANs 25% Automotive, Process control CiA, OVDA, Honeywell Profibus (3 kinds) 26% Process control Siemens, ABB LON 6% Building systems Echelon, ABB Ethernet 50% Plant bus all Interbus-S 7% Manufacturing Phoenix Contact Fieldbus Foundation, HART 7% Chemical Industry Fisher-Rosemount, ABB ASI 9% Building Systems Siemens Modbus 22% obsolete point-to-point many ControlNet 14% plant bus Rockwell *source: ISA, Jim Pinto (1999) Sum > 100%, since firms support more than one bus European market in 2002: 199 Mio €, 16.6 % increase (Profibus: 1/3 market share) **source: Elektronik, Heft 7 2002 Industrial Automation 4 3.3 Standard Field Busses Different classes of field busses One bus type cannot serve all applications and all device types efficiently..
    [Show full text]
  • Fieldbus : Industrial Network Real Time Network
    FieldbusFieldbus :: IndustrialIndustrial NetworkNetwork RealReal TimeTime NetworkNetwork Jean-Pierre Thomesse Institut National Polytechnique de Lorraine Nancy, France ETR 2005 - Fieldbus - Industrial Network - Real Time Network Who’sWho’s whowho IEC 61784 PROFInet TT-CAN Hart ISO 8802.5 TTP Profibus-PA Unitelway SNMP Ethernet Batibus WorldFIP MIL 1553B IEC 61158 P-NET CiA BacNET SDS ICCP Sercos CSMA-BA EHS CSMA-DCR FieldBus Foundation EiBUS DeviceNet Interbus Profibus-FMS EN 50254 ControlNet CANOpen ASI M-PCCN TTP-A Profibus-DP DWF TCP-IP FDDI TTP-C Modbus FIPWay EN 50170 TASE2 IEC CASM ISO 8802.4 WDPF MMS ISO 8802.3 Sinec ControlFIP PLAN JBUS FIPIO LON CSMA-CA Seriplex TOP Mini-MAP CAN UCA F8000 CSMA-CD MAP Profisafe Proway Bitbus ARINC UIC 556 Digital Hart M-Bus WITBUS IEC 6375 CIP LocaFIP J1850 VAN Sycoway GENIUS OPTOBUS LIN FTT-CAN Euridis IEEE 802.11 Vnet/IP Anubis Sensoplex AFDX FireWire FlexRay EN 50 295 BlueTooth EPA CAMAC ARCNET Ethercat EtherLink ModBus-RTPS IEC 61 499 UWB ETR 2005 - Fieldbus - Industrial Network - Real Time Network contentcontent z 1st part : history and state of the art – fieldbus origins – development of fieldbus and standards z 2nd part : technical aspects – application relationships – Medium Access Control – Data Link Layer – architectures ETR 2005 - Fieldbus - Industrial Network - Real Time Network prehistoryprehistory z 60s : CAMAC in nuclear experiments z 70s : – MODBUS (PLC network) – WDPF (continuous process) – ARCNET (office communication and data acquisition) – Mil Std 1553B z Data HighWay (Allen
    [Show full text]
  • A Model for Mobile-Instrumented Interaction and Object Orchestration in Smart Environments
    UNIVERSIDAD POLITÉCNICA DE MADRID ESCUELA TÉCNICA SUPERIOR DE INGENIEROS DE TELECOMUNICACIÓN A Model for Mobile-Instrumented Interaction and Object Orchestration in Smart Environments Tesis Doctoral LUCA BERGESIO Ingeniero en Informática Máster en Tecnologías y Sistémas de Comunicaciones 2017 Departamento de Señales, Sistemas y Radiocomunicaciones Escuela Técnica Superior de Ingenieros de Telecomunicación Universidad Politécnica de Madrid A Model for Mobile-Instrumented Interaction and Object Orchestration in Smart Environments Tesis Doctoral Autor: Luca Bergesio Ingeniero en Informática Máster en Tecnologías y Sistémas de Comunicaciones Directores: Ana María Bernardos Barbolla Doctora Ingeniera de Telecomunicación José Ramón Casar Corredera Doctor Ingeniero de Telecomunicación June 28, 2017 “The jump from zero to whatever baud rate is the most important jump you can make. After that everyone always wants to go straight to the speed of light” J. T. Tengdin’s First (and Only) Law of Telecommunications “When you see a good move, look for a better one” Emanuel Lasker, World Chess Champion from 1894 to 1921 Abstract The proliferation of the smartphones has given a considerable boost to the spread of the smart objects and the consequent creation of smart spaces. Smart objects are electronic devices that are able to work interactively and au- tonomously, usually preserving the interaction metaphor of their non-electronic counterpart. Through a network interface, they can cooperate with other objects: their strengths do not lie in their hardware, but in the capabilities to manage in- teractions among them and in the resulting orchestrated behaviour. Smart spaces are environments composed of smart devices, where they work together, producing some behaviour of benefit to the dwellers.
    [Show full text]
  • Yunjie Xiong Dissertation Submitted to the Faculty of the Virginia Polytechnic Institute and State University in Partial Fulfill
    A BIM-based Interoperability Platform in Support of Building Operation and Energy Management Yunjie Xiong Dissertation submitted to the faculty of the Virginia Polytechnic Institute and State University in partial fulfillment of the requirements for the degree of Doctor of Philosophy In Environmental Design and Planning Georg Reichard, Chair Tanyel Bulbul Farrokh Karimi Nazila Roofigari-Esfahan Feb 21, 2020 Blacksburg, VA Keywords: Building Information Modelling (BIM), energy simulation, operational data Copyright © 2020 Yunjie Xiong A BIM-based Interoperability Platform in Support of Building Operation and Energy Management Yunjie Xiong ACADEMIC ABSTRACT Building energy efficiency is progressively becoming a crucial topic in the architecture, engineering, and construction (AEC) sector. Energy management tools have been developed to promise appropriate energy savings. Building energy simulation (BES) is a tool mainly used to analyze and compare the energy consumption of various design/operation scenarios, while building automation systems (BAS) works as another energy management tool to monitor, measure and collect operational data, all in an effort to optimize energy consumption. By integrating the energy simulated data and actual operational data, the accuracy of a building energy model can be increased while the calibrated energy model can be applied as a benchmark for guiding the operational strategies. This research predicted that building information modeling (BIM) would link BES and BAS by acting as a visual model and a database throughout the lifecycle of a building. The intent of the research was to use BIM to document energy-related information and to allow its exchange between BES and BAS. Thus, the energy-related data exchange process would be simplified, and the productive efficiency of facility management processes would increase.
    [Show full text]
  • Fieldbus Technology in Industrial Automation Jean-Pierre Thomesse
    Fieldbus technology in industrial automation Jean-Pierre Thomesse To cite this version: Jean-Pierre Thomesse. Fieldbus technology in industrial automation. Proceedings of the IEEE, Institute of Electrical and Electronics Engineers, 2005, 93 (6), pp.1073-1101. 10.1109/JPROC.2005.849724. inria-00000807 HAL Id: inria-00000807 https://hal.inria.fr/inria-00000807 Submitted on 21 Nov 2007 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. > REPLACE THIS LINE WITH YOUR PAPER IDENTIFICATION NUMBER (DOUBLE-CLICK HERE TO EDIT) < 1 Fieldbus Technology in Industrial Automation Jean-Pierre Thomesse solutions in a given sector. These companies realized the Abstract— Fieldbus technology in industrial automation strategic importance of the fieldbus in the industrial is not only relatively complex because of the number of automation systems. Once their products were developed, solutions possible, but also, and above all, because of the they pushed to have them standardized, and hence we have variety of applications. Ironically, these in turn are responsible for the multitude of solutions available. If the the current vast range of standards, de facto and de jure. analysis of the basic needs is relatively standard, as they will This paper will try to establish the origins and current always involve connecting sensors, actuators, and field status of the fieldbus technology, including technical and controllers with each other, the options in architecture are scientific analysis, and standardization.
    [Show full text]
  • Solutions Towards Domotic Interoperability the Contribution of the OPC Standard
    Institution for communication and information Final year project in computer science 20p Level C Spring term 2007 Solutions towards domotic interoperability The contribution of the OPC Standard Jorge Serrano Betored HS-EA-DVA-2005-001 Solutions towards domotic interoperability This final year project has been submitted by Jorge Serrano Betored to the University of Skövde, as a dissertation towards the degree of Bachelor of Science (B.Sc.) in the School of Humanities and Informatics. The project has been supervised by Anders Dahlbom. 21th May 2007 I hereby certify that all material in this dissertation which is not my own work has been identified and that no work is included for which a degree has already been conferred on me. Signature: _______________________________________________ Solutions towards domotic interoperability Jorge Serrano Betored Abstract This report presents the existence of a set of problems making the growth of the domotic field more difficult. They are mainly the lack of a common communication standard among devices and the existence of a proprietary market, where each provider focuses on developing its own devices, protocols and interfaces. There isn’t a convergence criterion in order to overcome this problem by the main domotic providers. Several studies try to overcome this problem by applying different strategies. This study analyses the main strategies followed in that field, concluding with a model that combines them. The model is based on the use of OPC and web services. Keyword: BAS, OPC, Ambient intelligence, integration, interoperation Acknowledgments The outcome of this research wouldn’t have been possible without the help and feedback provided by my supervisor Anders Dahlbom and my examiner Björn Olsson.
    [Show full text]
  • IEC61158 Technology Comparison State of the Bus Fieldbus Inc
    IEC61158 Technology Comparison State of the Bus Fieldbus Inc. • Provides vendor-neutral fieldbus solutions to End Users, Device Vendors, and Others needing additional fieldbus expertise • For Device Vendors FI can provide: Development tools such as stacks and function blocks Starter Kits Training Customized software and hardware Complete drop-in solutions • For End Users FI can provide: Training System Preparation (RFQ, scope, choosing host system and devices) System Design Installation Assistance System Configuration Assistance Commissioning Assistance Long Term Support (Improve diagnostics, make use of fieldbus data, trouble- shooting, process refinement) Fieldbus Inc. Contact Information Fieldbus Inc. 9390 Research Blvd., Suite I-350 Austin, Texas USA 78759 +1.512.794.1011 www.fieldbusinc.com [email protected] Purpose • Motivation for fieldbus projects • Technical analysis of IEC 61158/61184 • Criteria for fieldbus standard technologies • Comparison of process fieldbus technologies • Technical merits • Global significance • Market for fieldbus Fieldbus defined • fieldbus - an industrial network system for real-time distributed control. • fieldbus - any open, digital, multi-drop communications network for intelligent field devices Viable Standardized Technology • International recognition • Market significance • Global availability (global install base) • Suppliers • Support organizations (local and international) FIELDBUS MOTIVATION 7 The Justification For Fieldbus Well Established • Lower Project cost – helps with
    [Show full text]
  • Buses, Protocols and Systems for Home and Building Automation
    Buses, Protocols and Systems for Home and Building Automation Ondřej Nývlt Evropský sociální fond. Praha & EU: Investujeme do vaší budoucnosti. Department of Control Engineering Faculty of Electrical Engineering Czech Technical University in Prague 2009-2011 Evropský sociální fond. Praha & EU: Investujeme do vaší budoucnosti. Table of contents 1. Basic categorization ......................................................................................................................... 3 1.1. System openness ......................................................................................................................... 3 1.2. System centralization .................................................................................................................. 4 1.3. System complexity and versatility ............................................................................................... 5 1.4. Physical layer – communication medium .................................................................................... 6 2. Closed systems ................................................................................................................................ 7 2.1. ABB Ego-N .................................................................................................................................... 7 2.2. Elko EP iNels ................................................................................................................................ 8 2.3. Eaton/Moeller X-Comfort and Nikobus ......................................................................................
    [Show full text]