Fieldbuses and interoperability
Identifieur interne : 001D15 ( Istex/Corpus ); précédent : 001D14; suivant : 001D16Fieldbuses and interoperability
Auteurs : Jean Pierre ThomesseSource :
- Control Engineering Practice [ 0967-0661 ] ; 1999.
English descriptors
- Teeft :
- Actuator, Application architectures, Application development, Application entities, Application interoperability, Application layer, Application process, Application programs, Automation architectures, Automation system, Automation systems, Benkhellat, Building automation, Canonical tester, Cenelec, Communication system, Communication systems, Companion standards, Complete application, Comput, Computer control systems, Conformance, Conformance classes, Conformance testing, Conformance testing methods, Constraint, Controller area network, Data item, Data link layer, Data link service, Data rate, Design stage, Digital data communications, Dynamic behaviour, Dynamic scheduling, Eldbus, Eldbus networks, Eldbus services, Eldbus solution, Eldbuses, Elsevier science, Engineering practice, Factory communication systems, Factory instrumentation protocol, Fieldbus, Fieldbus foundation, Function blocks, Functional architecture, German draft, Gestion technique, Global system, Heterogeneous devices, High communications subsystems, Ieee, Industrial automation, Industrial control systems, International level, Interoperability, Interoperability guidelines, Interoperability testing, Interoperable, Layer, Layer interoperability, Manufacturing message, Master stations, Medium access control, Much work, National standards, Network layer, Network management, Networks isdn systems, Operational architecture, Orkshop, Other hand, Other kinds, Other services, Passive testing, Performance testing, Physical layer, Presentation layer, Protocol, Protocol point, Real time, Real time applications, Real time communications, Real time systems, Realistic models, Response time, Same protocols, Same time, Same view, Semiconductor manufacturing, Sensor, Small data packages, Software, Specialized magazines, Spinal column, Standardization, Standards interfaces, State values, Task force, Temporal aspects, Temporal mechanisms, Thomesse, Time coherence, Time coherences, Time constraints, Time window, Timing constraints, Transport layer, Typical exchanges, User layer, User requirements, Users group, Usual mechanism, Voltage switchgear, Worldfip.
Abstract
Abstract: Fieldbuses are playing a more and more important role in automation systems, in embedded systems and in building automation. This paper presents the state of the art of fieldbuses. The analysis starts with fieldbus history, as this explains the reasons for the proliferation of fieldbuses. Different points of view were considered, and then developed by different proposers, 10 or 15 years ago. Therefore, more than 50 different names of products or standards appear in various conference proceedings, in specialized magazines or in exhibitions. Starting from this history, the paper presents a synthesis of the different fieldbuses. It describes the requirements for fieldbuses, their main traffic characteristics, the typical time constraints to be met, and the most current profiles defined in major products and standards. An analysis of services and protocols is given. Finally, the property of interoperability is analysed from the viewpoint of the reasons that may lead to an incompatibility between devices. The methods of building and testing or proving interoperability are then briefly presented. Some perspectives for research, as well as for development, are underlined, with regard to the application architectures, their modelling and validation.
Url:
DOI: 10.1016/S0967-0661(98)00140-3
Links to Exploration step
ISTEX:7CF12D6073E1C98E1163B7BFEEB6FFC31DFDCDBBLe document en format XML
<record><TEI wicri:istexFullTextTei="biblStruct"><teiHeader><fileDesc><titleStmt><title>Fieldbuses and interoperability</title><author><name sortKey="Pierre Thomesse, Jean" sort="Pierre Thomesse, Jean" uniqKey="Pierre Thomesse J" first="Jean" last="Pierre Thomesse">Jean Pierre Thomesse</name><affiliation><mods:affiliation>LORIA INPL, ENSEM, 2 Avenue de la forêt de haye, F-54516 Vandœuvre, France</mods:affiliation></affiliation><affiliation><mods:affiliation>E-mail: thomesse@loria.fr</mods:affiliation></affiliation></author></titleStmt><publicationStmt><idno type="wicri:source">ISTEX</idno><idno type="RBID">ISTEX:7CF12D6073E1C98E1163B7BFEEB6FFC31DFDCDBB</idno><date when="1999" year="1999">1999</date><idno type="doi">10.1016/S0967-0661(98)00140-3</idno><idno type="url">https://api.istex.fr/ark:/67375/6H6-WJGS35F0-B/fulltext.pdf</idno><idno type="wicri:Area/Istex/Corpus">001D15</idno><idno type="wicri:explorRef" wicri:stream="Istex" wicri:step="Corpus" wicri:corpus="ISTEX">001D15</idno></publicationStmt><sourceDesc><biblStruct><analytic><title level="a">Fieldbuses and interoperability</title><author><name sortKey="Pierre Thomesse, Jean" sort="Pierre Thomesse, Jean" uniqKey="Pierre Thomesse J" first="Jean" last="Pierre Thomesse">Jean Pierre Thomesse</name><affiliation><mods:affiliation>LORIA INPL, ENSEM, 2 Avenue de la forêt de haye, F-54516 Vandœuvre, France</mods:affiliation></affiliation><affiliation><mods:affiliation>E-mail: thomesse@loria.fr</mods:affiliation></affiliation></author></analytic><monogr></monogr><series><title level="j">Control Engineering Practice</title><title level="j" type="abbrev">CONPRA</title><idno type="ISSN">0967-0661</idno><imprint><publisher>ELSEVIER</publisher><date type="published" when="1999">1999</date><biblScope unit="volume">7</biblScope><biblScope unit="issue">1</biblScope><biblScope unit="page" from="81">81</biblScope><biblScope unit="page" to="94">94</biblScope></imprint><idno type="ISSN">0967-0661</idno></series></biblStruct></sourceDesc><seriesStmt><idno type="ISSN">0967-0661</idno></seriesStmt></fileDesc><profileDesc><textClass><keywords scheme="Teeft" xml:lang="en"><term>Actuator</term><term>Application architectures</term><term>Application development</term><term>Application entities</term><term>Application interoperability</term><term>Application layer</term><term>Application process</term><term>Application programs</term><term>Automation architectures</term><term>Automation system</term><term>Automation systems</term><term>Benkhellat</term><term>Building automation</term><term>Canonical tester</term><term>Cenelec</term><term>Communication system</term><term>Communication systems</term><term>Companion standards</term><term>Complete application</term><term>Comput</term><term>Computer control systems</term><term>Conformance</term><term>Conformance classes</term><term>Conformance testing</term><term>Conformance testing methods</term><term>Constraint</term><term>Controller area network</term><term>Data item</term><term>Data link layer</term><term>Data link service</term><term>Data rate</term><term>Design stage</term><term>Digital data communications</term><term>Dynamic behaviour</term><term>Dynamic scheduling</term><term>Eldbus</term><term>Eldbus networks</term><term>Eldbus services</term><term>Eldbus solution</term><term>Eldbuses</term><term>Elsevier science</term><term>Engineering practice</term><term>Factory communication systems</term><term>Factory instrumentation protocol</term><term>Fieldbus</term><term>Fieldbus foundation</term><term>Function blocks</term><term>Functional architecture</term><term>German draft</term><term>Gestion technique</term><term>Global system</term><term>Heterogeneous devices</term><term>High communications subsystems</term><term>Ieee</term><term>Industrial automation</term><term>Industrial control systems</term><term>International level</term><term>Interoperability</term><term>Interoperability guidelines</term><term>Interoperability testing</term><term>Interoperable</term><term>Layer</term><term>Layer interoperability</term><term>Manufacturing message</term><term>Master stations</term><term>Medium access control</term><term>Much work</term><term>National standards</term><term>Network layer</term><term>Network management</term><term>Networks isdn systems</term><term>Operational architecture</term><term>Orkshop</term><term>Other hand</term><term>Other kinds</term><term>Other services</term><term>Passive testing</term><term>Performance testing</term><term>Physical layer</term><term>Presentation layer</term><term>Protocol</term><term>Protocol point</term><term>Real time</term><term>Real time applications</term><term>Real time communications</term><term>Real time systems</term><term>Realistic models</term><term>Response time</term><term>Same protocols</term><term>Same time</term><term>Same view</term><term>Semiconductor manufacturing</term><term>Sensor</term><term>Small data packages</term><term>Software</term><term>Specialized magazines</term><term>Spinal column</term><term>Standardization</term><term>Standards interfaces</term><term>State values</term><term>Task force</term><term>Temporal aspects</term><term>Temporal mechanisms</term><term>Thomesse</term><term>Time coherence</term><term>Time coherences</term><term>Time constraints</term><term>Time window</term><term>Timing constraints</term><term>Transport layer</term><term>Typical exchanges</term><term>User layer</term><term>User requirements</term><term>Users group</term><term>Usual mechanism</term><term>Voltage switchgear</term><term>Worldfip</term></keywords></textClass><langUsage><language ident="en">en</language></langUsage></profileDesc></teiHeader><front><div type="abstract" xml:lang="en">Abstract: Fieldbuses are playing a more and more important role in automation systems, in embedded systems and in building automation. This paper presents the state of the art of fieldbuses. The analysis starts with fieldbus history, as this explains the reasons for the proliferation of fieldbuses. Different points of view were considered, and then developed by different proposers, 10 or 15 years ago. Therefore, more than 50 different names of products or standards appear in various conference proceedings, in specialized magazines or in exhibitions. Starting from this history, the paper presents a synthesis of the different fieldbuses. It describes the requirements for fieldbuses, their main traffic characteristics, the typical time constraints to be met, and the most current profiles defined in major products and standards. An analysis of services and protocols is given. Finally, the property of interoperability is analysed from the viewpoint of the reasons that may lead to an incompatibility between devices. The methods of building and testing or proving interoperability are then briefly presented. Some perspectives for research, as well as for development, are underlined, with regard to the application architectures, their modelling and validation.</div></front></TEI><istex><corpusName>elsevier</corpusName><keywords><teeft><json:string>interoperability</json:string><json:string>eldbus</json:string><json:string>eldbuses</json:string><json:string>thomesse</json:string><json:string>worldfip</json:string><json:string>fieldbus</json:string><json:string>engineering practice</json:string><json:string>standardization</json:string><json:string>actuator</json:string><json:string>time constraints</json:string><json:string>cenelec</json:string><json:string>protocol</json:string><json:string>application layer</json:string><json:string>interoperable</json:string><json:string>ieee</json:string><json:string>orkshop</json:string><json:string>software</json:string><json:string>comput</json:string><json:string>benkhellat</json:string><json:string>interoperability testing</json:string><json:string>industrial control systems</json:string><json:string>constraint</json:string><json:string>networks isdn systems</json:string><json:string>communication system</json:string><json:string>data link layer</json:string><json:string>companion standards</json:string><json:string>physical layer</json:string><json:string>real time systems</json:string><json:string>conformance classes</json:string><json:string>application architectures</json:string><json:string>conformance</json:string><json:string>network layer</json:string><json:string>design stage</json:string><json:string>high communications subsystems</json:string><json:string>presentation layer</json:string><json:string>automation systems</json:string><json:string>fieldbus foundation</json:string><json:string>communication systems</json:string><json:string>functional architecture</json:string><json:string>manufacturing message</json:string><json:string>operational architecture</json:string><json:string>temporal aspects</json:string><json:string>application entities</json:string><json:string>real time communications</json:string><json:string>response time</json:string><json:string>building automation</json:string><json:string>application process</json:string><json:string>small data packages</json:string><json:string>sensor</json:string><json:string>complete application</json:string><json:string>state values</json:string><json:string>national standards</json:string><json:string>specialized magazines</json:string><json:string>temporal mechanisms</json:string><json:string>time coherences</json:string><json:string>time window</json:string><json:string>time coherence</json:string><json:string>other services</json:string><json:string>spinal column</json:string><json:string>medium access control</json:string><json:string>real time</json:string><json:string>typical exchanges</json:string><json:string>usual mechanism</json:string><json:string>data rate</json:string><json:string>semiconductor manufacturing</json:string><json:string>dynamic scheduling</json:string><json:string>automation architectures</json:string><json:string>heterogeneous devices</json:string><json:string>transport layer</json:string><json:string>timing constraints</json:string><json:string>master stations</json:string><json:string>dynamic behaviour</json:string><json:string>protocol point</json:string><json:string>data item</json:string><json:string>computer control systems</json:string><json:string>layer interoperability</json:string><json:string>elsevier science</json:string><json:string>conformance testing</json:string><json:string>eldbus services</json:string><json:string>global system</json:string><json:string>application programs</json:string><json:string>same protocols</json:string><json:string>application interoperability</json:string><json:string>other kinds</json:string><json:string>interoperability guidelines</json:string><json:string>function blocks</json:string><json:string>user layer</json:string><json:string>same time</json:string><json:string>passive testing</json:string><json:string>conformance testing methods</json:string><json:string>canonical tester</json:string><json:string>performance testing</json:string><json:string>much work</json:string><json:string>application development</json:string><json:string>realistic models</json:string><json:string>network management</json:string><json:string>controller area network</json:string><json:string>factory instrumentation protocol</json:string><json:string>eldbus solution</json:string><json:string>users group</json:string><json:string>voltage switchgear</json:string><json:string>gestion technique</json:string><json:string>industrial automation</json:string><json:string>real time applications</json:string><json:string>automation system</json:string><json:string>task force</json:string><json:string>international level</json:string><json:string>eldbus networks</json:string><json:string>german draft</json:string><json:string>other hand</json:string><json:string>factory communication systems</json:string><json:string>user requirements</json:string><json:string>standards interfaces</json:string><json:string>digital data communications</json:string><json:string>data link service</json:string><json:string>same view</json:string><json:string>layer</json:string></teeft></keywords><author><json:item><name>Jean Pierre Thomesse</name><affiliations><json:string>LORIA INPL, ENSEM, 2 Avenue de la forêt de haye, F-54516 Vandœuvre, France</json:string><json:string>E-mail: thomesse@loria.fr</json:string></affiliations></json:item></author><subject><json:item><lang><json:string>eng</json:string></lang><value>Fieldbus</value></json:item><json:item><lang><json:string>eng</json:string></lang><value>protocols</value></json:item><json:item><lang><json:string>eng</json:string></lang><value>profiles</value></json:item><json:item><lang><json:string>eng</json:string></lang><value>automation architectures</value></json:item><json:item><lang><json:string>eng</json:string></lang><value>timing constraints</value></json:item><json:item><lang><json:string>eng</json:string></lang><value>periodic and aperiodic traffic</value></json:item><json:item><lang><json:string>eng</json:string></lang><value>interoperability</value></json:item></subject><arkIstex>ark:/67375/6H6-WJGS35F0-B</arkIstex><language><json:string>eng</json:string></language><originalGenre><json:string>Full-length article</json:string></originalGenre><abstract>Abstract: Fieldbuses are playing a more and more important role in automation systems, in embedded systems and in building automation. This paper presents the state of the art of fieldbuses. The analysis starts with fieldbus history, as this explains the reasons for the proliferation of fieldbuses. Different points of view were considered, and then developed by different proposers, 10 or 15 years ago. Therefore, more than 50 different names of products or standards appear in various conference proceedings, in specialized magazines or in exhibitions. Starting from this history, the paper presents a synthesis of the different fieldbuses. It describes the requirements for fieldbuses, their main traffic characteristics, the typical time constraints to be met, and the most current profiles defined in major products and standards. An analysis of services and protocols is given. Finally, the property of interoperability is analysed from the viewpoint of the reasons that may lead to an incompatibility between devices. The methods of building and testing or proving interoperability are then briefly presented. Some perspectives for research, as well as for development, are underlined, with regard to the application architectures, their modelling and validation.</abstract><qualityIndicators><score>9.256</score><pdfWordCount>9590</pdfWordCount><pdfCharCount>60685</pdfCharCount><pdfVersion>1.2</pdfVersion><pdfPageCount>14</pdfPageCount><pdfPageSize>546 x 768 pts</pdfPageSize><refBibsNative>false</refBibsNative><abstractWordCount>188</abstractWordCount><abstractCharCount>1271</abstractCharCount><keywordCount>7</keywordCount></qualityIndicators><title>Fieldbuses and interoperability</title><pii><json:string>S0967-0661(98)00140-3</json:string></pii><genre><json:string>research-article</json:string></genre><host><title>Control Engineering Practice</title><language><json:string>unknown</json:string></language><publicationDate>1999</publicationDate><issn><json:string>0967-0661</json:string></issn><pii><json:string>S0967-0661(00)X0040-8</json:string></pii><volume>7</volume><issue>1</issue><pages><first>81</first><last>94</last></pages><genre><json:string>journal</json:string></genre></host><namedEntities><unitex><date><json:string>1981</json:string><json:string>1993</json:string><json:string>1998</json:string><json:string>1994</json:string><json:string>1983</json:string><json:string>1999</json:string><json:string>1990</json:string><json:string>1980</json:string><json:string>1980s</json:string><json:string>1996</json:string></date><geogName></geogName><orgName><json:string>International Electrotechnical Commission IFG</json:string><json:string>France LAC, Gixinet, Factor</json:string><json:string>Research Even</json:string><json:string>Fieldbus Foundation</json:string><json:string>Draft International Standard</json:string><json:string>Grenoble University</json:string><json:string>Elsevier Science Ltd.</json:string><json:string>Open Fieldbus Consortium PLAN</json:string><json:string>Germany, and ASI</json:string></orgName><orgName_funder></orgName_funder><orgName_provider></orgName_provider><persName><json:string>Petri Nets</json:string><json:string>Soutif</json:string><json:string>J.P. Thomesse</json:string><json:string>P.Net</json:string><json:string>Line Message</json:string><json:string>Tom Phinney</json:string><json:string>P. Thomesse</json:string><json:string>Patricio Leviti</json:string></persName><placeName><json:string>Germany</json:string><json:string>Periodicity</json:string><json:string>US</json:string><json:string>Europe</json:string><json:string>America</json:string><json:string>Denmark</json:string><json:string>France</json:string></placeName><ref_url></ref_url><ref_bibl><json:string>see also (ISO/IEC, 1996</json:string><json:string>Leviti, 1995</json:string><json:string>SERCOS (IEC, 1994</json:string><json:string>Burns, 1991</json:string><json:string>DIN, 1990</json:string><json:string>LON, 1995</json:string><json:string>Kopetz and Grundsteidl, 1994</json:string><json:string>Zeng et al. (1988, 1989)</json:string><json:string>Arakawa et al., 1972</json:string><json:string>DS, 1990</json:string><json:string>Thomesse et al., 1991</json:string><json:string>DIN, 1995</json:string><json:string>PLAN, 1993</json:string><json:string>in WorldFIP (AFNOR, 1989</json:string><json:string>EHS, 1991</json:string><json:string>ASI, 1996</json:string><json:string>Lecuivre, 1995</json:string><json:string>Bonnes, 1988</json:string><json:string>BITBUS, 1991</json:string><json:string>June 1982</json:string><json:string>Benkhellat and Thomesse, 1994</json:string><json:string>CENELEC, 1996b, c</json:string><json:string>Le Lann and Rivierre, 1994</json:string><json:string>SDS, 1997</json:string><json:string>Berge et al., 1995</json:string><json:string>Ostroff, 1992</json:string><json:string>Lorenz and Mammeri, 1994</json:string><json:string>AFNOR, 1989</json:string><json:string>BATIBUS,1991</json:string><json:string>Castanet and Kone (1993)</json:string><json:string>Bender,1993</json:string><json:string>December 1996</json:string><json:string>Raja, 1993</json:string><json:string>Staroswiecki et al., 1994</json:string><json:string>Lenzini and Zoccolini, 1992</json:string><json:string>ISO, 1994, 1996</json:string><json:string>Soutif, 1982</json:string><json:string>Dakroury and Elloy, 1989</json:string><json:string>Cardeira and Mammeri, 1995</json:string><json:string>Benkhellat and Thomesse (1992, 1994)</json:string><json:string>ISO, 1990</json:string><json:string>in Interbus-S (DIN, 1995</json:string><json:string>CNMA, 1989</json:string><json:string>Berthet et al., 1995</json:string><json:string>Elloy et al., 1995</json:string><json:string>ISO, 1995</json:string><json:string>Thomesse and Noury, 1989</json:string><json:string>Song et al., 1995</json:string><json:string>Simonot-Lion et al., 1995</json:string><json:string>SimonotLion et al., 1995</json:string><json:string>Alur and ´ Hensinger, 1991</json:string><json:string>Laurance, 1992</json:string><json:string>CENELEC, 1996a</json:string><json:string>Benkhellat (1995)</json:string><json:string>Zimmermann, 1980</json:string><json:string>BSI, 1996</json:string><json:string>Paret, 1996</json:string><json:string>EIBUS, 1991</json:string><json:string>Gault and Lobert, 1985</json:string><json:string>Vega-Saenz and Thomesse, 1996</json:string><json:string>Bolognesi and Brinksma, 1987</json:string><json:string>IEC, 1996a, b</json:string><json:string>IEC, 1993</json:string><json:string>Mammeri and Lorenz, 1994</json:string><json:string>Thomesse, 1993</json:string><json:string>Saba et al., 1993</json:string><json:string>ISO, 1988</json:string><json:string>Alimi, 1995</json:string><json:string>Witteman and Van Wuijtswinkel (1993)</json:string><json:string>October 1997</json:string><json:string>EMUG, 1989</json:string><json:string>DIN, 1996</json:string><json:string>CEN, 1995</json:string><json:string>Vega-Saenz and Thomesse, 1995</json:string><json:string>OLCHFA, 1995</json:string><json:string>Tindell et al., 1995a, b</json:string><json:string>Gadre et al. (1990)</json:string><json:string>Decotignie et al., 1993</json:string><json:string>Grant, 1992</json:string></ref_bibl><bibl></bibl></unitex></namedEntities><ark><json:string>ark:/67375/6H6-WJGS35F0-B</json:string></ark><categories><wos><json:string>1 - science</json:string><json:string>2 - engineering, electrical & electronic</json:string><json:string>2 - automation & control systems</json:string></wos><scienceMetrix><json:string>1 - applied sciences</json:string><json:string>2 - engineering</json:string><json:string>3 - industrial engineering & automation</json:string></scienceMetrix><scopus><json:string>1 - Physical Sciences</json:string><json:string>2 - Mathematics</json:string><json:string>3 - Applied Mathematics</json:string><json:string>1 - Physical Sciences</json:string><json:string>2 - Engineering</json:string><json:string>3 - Electrical and Electronic Engineering</json:string><json:string>1 - Physical Sciences</json:string><json:string>2 - Computer Science</json:string><json:string>3 - Computer Science Applications</json:string><json:string>1 - Physical Sciences</json:string><json:string>2 - Engineering</json:string><json:string>3 - Control and Systems Engineering</json:string></scopus><inist><json:string>1 - sciences appliquees, technologies et medecines</json:string><json:string>2 - sciences exactes et technologie</json:string><json:string>3 - sciences et techniques communes</json:string><json:string>4 - sciences de l'information. documentation</json:string></inist></categories><publicationDate>1999</publicationDate><copyrightDate>1999</copyrightDate><doi><json:string>10.1016/S0967-0661(98)00140-3</json:string></doi><id>7CF12D6073E1C98E1163B7BFEEB6FFC31DFDCDBB</id><score>1</score><fulltext><json:item><extension>pdf</extension><original>true</original><mimetype>application/pdf</mimetype><uri>https://api.istex.fr/ark:/67375/6H6-WJGS35F0-B/fulltext.pdf</uri></json:item><json:item><extension>zip</extension><original>false</original><mimetype>application/zip</mimetype><uri>https://api.istex.fr/ark:/67375/6H6-WJGS35F0-B/bundle.zip</uri></json:item><istex:fulltextTEI uri="https://api.istex.fr/ark:/67375/6H6-WJGS35F0-B/fulltext.tei"><teiHeader><fileDesc><titleStmt><title level="a">Fieldbuses and interoperability</title></titleStmt><publicationStmt><authority>ISTEX</authority><publisher scheme="https://scientific-publisher.data.istex.fr">ELSEVIER</publisher><availability><licence><p>©1999 Elsevier Science Ltd</p></licence><p scheme="https://loaded-corpus.data.istex.fr/ark:/67375/XBH-HKKZVM7B-M">elsevier</p></availability><date>1999</date></publicationStmt><notesStmt><note type="research-article" scheme="https://content-type.data.istex.fr/ark:/67375/XTP-1JC4F85T-7">research-article</note><note type="journal" scheme="https://publication-type.data.istex.fr/ark:/67375/JMC-0GLKJH51-B">journal</note></notesStmt><sourceDesc><biblStruct type="inbook"><analytic><title level="a">Fieldbuses and interoperability</title><author xml:id="author-0000"><persName><forename type="first">Jean</forename><surname>Pierre Thomesse</surname></persName><email>thomesse@loria.fr</email><note type="biography">Tel.: +33 3 83 59 55 76; fax: +33 3 83 44 07 63</note><affiliation>Tel.: +33 3 83 59 55 76; fax: +33 3 83 44 07 63</affiliation><affiliation>LORIA INPL, ENSEM, 2 Avenue de la forêt de haye, F-54516 Vandœuvre, France</affiliation></author><idno type="istex">7CF12D6073E1C98E1163B7BFEEB6FFC31DFDCDBB</idno><idno type="ark">ark:/67375/6H6-WJGS35F0-B</idno><idno type="DOI">10.1016/S0967-0661(98)00140-3</idno><idno type="PII">S0967-0661(98)00140-3</idno></analytic><monogr><title level="j">Control Engineering Practice</title><title level="j" type="abbrev">CONPRA</title><idno type="pISSN">0967-0661</idno><idno type="PII">S0967-0661(00)X0040-8</idno><imprint><publisher>ELSEVIER</publisher><date type="published" when="1999"></date><biblScope unit="volume">7</biblScope><biblScope unit="issue">1</biblScope><biblScope unit="page" from="81">81</biblScope><biblScope unit="page" to="94">94</biblScope></imprint></monogr></biblStruct></sourceDesc></fileDesc><profileDesc><creation><date>1999</date></creation><langUsage><language ident="en">en</language></langUsage><abstract xml:lang="en"><p>Abstract: Fieldbuses are playing a more and more important role in automation systems, in embedded systems and in building automation. This paper presents the state of the art of fieldbuses. The analysis starts with fieldbus history, as this explains the reasons for the proliferation of fieldbuses. Different points of view were considered, and then developed by different proposers, 10 or 15 years ago. Therefore, more than 50 different names of products or standards appear in various conference proceedings, in specialized magazines or in exhibitions. Starting from this history, the paper presents a synthesis of the different fieldbuses. It describes the requirements for fieldbuses, their main traffic characteristics, the typical time constraints to be met, and the most current profiles defined in major products and standards. An analysis of services and protocols is given. Finally, the property of interoperability is analysed from the viewpoint of the reasons that may lead to an incompatibility between devices. The methods of building and testing or proving interoperability are then briefly presented. Some perspectives for research, as well as for development, are underlined, with regard to the application architectures, their modelling and validation.</p></abstract><textClass><keywords scheme="keyword"><list><head>Keywords</head><item><term>Fieldbus</term></item><item><term>protocols</term></item><item><term>profiles</term></item><item><term>automation architectures</term></item><item><term>timing constraints</term></item><item><term>periodic and aperiodic traffic</term></item><item><term>interoperability</term></item></list></keywords></textClass></profileDesc><revisionDesc><change when="1999">Published</change></revisionDesc></teiHeader></istex:fulltextTEI><json:item><extension>txt</extension><original>false</original><mimetype>text/plain</mimetype><uri>https://api.istex.fr/ark:/67375/6H6-WJGS35F0-B/fulltext.txt</uri></json:item></fulltext><metadata><istex:metadataXml wicri:clean="Elsevier converted-article found"><istex:xmlDeclaration>version="1.0" encoding="utf-8"</istex:xmlDeclaration><istex:docType PUBLIC="-//ES//DTD journal article DTD version 4.5.2//EN//XML" URI="art452.dtd" name="istex:docType"></istex:docType><istex:document><converted-article version="4.5.2" docsubtype="fla"><item-info><jid>CONPRA</jid><aid>896</aid><ce:pii>S0967-0661(98)00140-3</ce:pii><ce:doi>10.1016/S0967-0661(98)00140-3</ce:doi><ce:copyright type="full-transfer" year="1999">Elsevier Science Ltd</ce:copyright></item-info><head><ce:title>Fieldbuses and interoperability</ce:title><ce:author-group><ce:author><ce:given-name>Jean</ce:given-name><ce:surname>Pierre Thomesse</ce:surname><ce:cross-ref refid="COR1">*</ce:cross-ref><ce:e-address>thomesse@loria.fr</ce:e-address></ce:author><ce:affiliation><ce:textfn>LORIA INPL, ENSEM, 2 Avenue de la forêt de haye, F-54516 Vandœuvre, France</ce:textfn></ce:affiliation><ce:correspondence id="COR1"><ce:label>*</ce:label><ce:text>Tel.: +33 3 83 59 55 76; fax: +33 3 83 44 07 63</ce:text></ce:correspondence></ce:author-group><ce:date-received day="5" month="12" year="1997"></ce:date-received><ce:date-accepted day="20" month="8" year="1998"></ce:date-accepted><ce:abstract><ce:section-title>Abstract</ce:section-title><ce:abstract-sec><ce:simple-para>Fieldbuses are playing a more and more important role in automation systems, in embedded systems and in building automation. This paper presents the state of the art of fieldbuses. The analysis starts with fieldbus history, as this explains the reasons for the proliferation of fieldbuses. Different points of view were considered, and then developed by different proposers, 10 or 15 years ago. Therefore, more than 50 different names of products or standards appear in various conference proceedings, in specialized magazines or in exhibitions. Starting from this history, the paper presents a synthesis of the different fieldbuses. It describes the requirements for fieldbuses, their main traffic characteristics, the typical time constraints to be met, and the most current profiles defined in major products and standards. An analysis of services and protocols is given. Finally, the property of interoperability is analysed from the viewpoint of the reasons that may lead to an incompatibility between devices. The methods of building and testing or proving interoperability are then briefly presented. Some perspectives for research, as well as for development, are underlined, with regard to the application architectures, their modelling and validation.</ce:simple-para></ce:abstract-sec></ce:abstract><ce:keywords><ce:section-title>Keywords</ce:section-title><ce:keyword><ce:text>Fieldbus</ce:text></ce:keyword><ce:keyword><ce:text>protocols</ce:text></ce:keyword><ce:keyword><ce:text>profiles</ce:text></ce:keyword><ce:keyword><ce:text>automation architectures</ce:text></ce:keyword><ce:keyword><ce:text>timing constraints</ce:text></ce:keyword><ce:keyword><ce:text>periodic and aperiodic traffic</ce:text></ce:keyword><ce:keyword><ce:text>interoperability</ce:text></ce:keyword></ce:keywords></head></converted-article></istex:document></istex:metadataXml><mods version="3.6"><titleInfo><title>Fieldbuses and interoperability</title></titleInfo><titleInfo type="alternative" contentType="CDATA"><title>Fieldbuses and interoperability</title></titleInfo><name type="personal"><namePart type="given">Jean</namePart><namePart type="family">Pierre Thomesse</namePart><affiliation>LORIA INPL, ENSEM, 2 Avenue de la forêt de haye, F-54516 Vandœuvre, France</affiliation><affiliation>E-mail: thomesse@loria.fr</affiliation><description>Tel.: +33 3 83 59 55 76; fax: +33 3 83 44 07 63</description><role><roleTerm type="text">author</roleTerm></role></name><typeOfResource>text</typeOfResource><genre type="research-article" displayLabel="Full-length article" authority="ISTEX" authorityURI="https://content-type.data.istex.fr" valueURI="https://content-type.data.istex.fr/ark:/67375/XTP-1JC4F85T-7">research-article</genre><originInfo><publisher>ELSEVIER</publisher><dateIssued encoding="w3cdtf">1999</dateIssued><copyrightDate encoding="w3cdtf">1999</copyrightDate></originInfo><language><languageTerm type="code" authority="iso639-2b">eng</languageTerm><languageTerm type="code" authority="rfc3066">en</languageTerm></language><abstract lang="en">Abstract: Fieldbuses are playing a more and more important role in automation systems, in embedded systems and in building automation. This paper presents the state of the art of fieldbuses. The analysis starts with fieldbus history, as this explains the reasons for the proliferation of fieldbuses. Different points of view were considered, and then developed by different proposers, 10 or 15 years ago. Therefore, more than 50 different names of products or standards appear in various conference proceedings, in specialized magazines or in exhibitions. Starting from this history, the paper presents a synthesis of the different fieldbuses. It describes the requirements for fieldbuses, their main traffic characteristics, the typical time constraints to be met, and the most current profiles defined in major products and standards. An analysis of services and protocols is given. Finally, the property of interoperability is analysed from the viewpoint of the reasons that may lead to an incompatibility between devices. The methods of building and testing or proving interoperability are then briefly presented. Some perspectives for research, as well as for development, are underlined, with regard to the application architectures, their modelling and validation.</abstract><subject><genre>Keywords</genre><topic>Fieldbus</topic><topic>protocols</topic><topic>profiles</topic><topic>automation architectures</topic><topic>timing constraints</topic><topic>periodic and aperiodic traffic</topic><topic>interoperability</topic></subject><relatedItem type="host"><titleInfo><title>Control Engineering Practice</title></titleInfo><titleInfo type="abbreviated"><title>CONPRA</title></titleInfo><genre type="journal" authority="ISTEX" authorityURI="https://publication-type.data.istex.fr" valueURI="https://publication-type.data.istex.fr/ark:/67375/JMC-0GLKJH51-B">journal</genre><originInfo><publisher>ELSEVIER</publisher><dateIssued encoding="w3cdtf">1999</dateIssued></originInfo><identifier type="ISSN">0967-0661</identifier><identifier type="PII">S0967-0661(00)X0040-8</identifier><part><date>1999</date><detail type="volume"><number>7</number><caption>vol.</caption></detail><detail type="issue"><number>1</number><caption>no.</caption></detail><extent unit="issue-pages"><start>1</start><end>150</end></extent><extent unit="pages"><start>81</start><end>94</end></extent></part></relatedItem><identifier type="istex">7CF12D6073E1C98E1163B7BFEEB6FFC31DFDCDBB</identifier><identifier type="ark">ark:/67375/6H6-WJGS35F0-B</identifier><identifier type="DOI">10.1016/S0967-0661(98)00140-3</identifier><identifier type="PII">S0967-0661(98)00140-3</identifier><accessCondition type="use and reproduction" contentType="copyright">©1999 Elsevier Science Ltd</accessCondition><recordInfo><recordContentSource authority="ISTEX" authorityURI="https://loaded-corpus.data.istex.fr" valueURI="https://loaded-corpus.data.istex.fr/ark:/67375/XBH-HKKZVM7B-M">elsevier</recordContentSource><recordOrigin>Elsevier Science Ltd, ©1999</recordOrigin></recordInfo></mods><json:item><extension>json</extension><original>false</original><mimetype>application/json</mimetype><uri>https://api.istex.fr/ark:/67375/6H6-WJGS35F0-B/record.json</uri></json:item></metadata><serie></serie></istex></record>Pour manipuler ce document sous Unix (Dilib)
EXPLOR_STEP=$WICRI_ROOT/Wicri/Lorraine/explor/InforLorV4/Data/Istex/Corpus
HfdSelect -h $EXPLOR_STEP/biblio.hfd -nk 001D15 | SxmlIndent | more
Ou
HfdSelect -h $EXPLOR_AREA/Data/Istex/Corpus/biblio.hfd -nk 001D15 | SxmlIndent | more
Pour mettre un lien sur cette page dans le réseau Wicri
{{Explor lien
|wiki= Wicri/Lorraine
|area= InforLorV4
|flux= Istex
|étape= Corpus
|type= RBID
|clé= ISTEX:7CF12D6073E1C98E1163B7BFEEB6FFC31DFDCDBB
|texte= Fieldbuses and interoperability
}}
| This area was generated with Dilib version V0.6.33. |  |