what is field bus

TechnicalInformation

<Int> <Ind> <Rev>

Fieldbus Technical Information

TI 38K03A01-01E

TI 38K03A01-01E©Copyright Mar. 19983rd Edition Sep. 2002

Yokogawa Electric Corporation2-9-32, Nakacho, Musashino-shi, Tokyo, 180-8750 JapanTel.: 81-422-52-5634 Fax.: 81-422-52-9802

Blank Page

<Toc> <Ind> <Rev> i

TI 38K03A01-01E

IntroductionFieldbus is an innovative technology for creating field information networks, and isattracting much interest among users and manufacturers of process control systems.

This manual describes how users can introduce Fieldbus into their process control sys-tems, and also describes Yokogawa’s Fieldbus solutions and Yokogawa’s Plant ResourceManager (PRM) software package for managing plant assets in the field network era.

Structure of This ManualThis manual gives an overview of Yokogawa’s Fieldbus Solutions, and explains the ben-efits of adopting them. For the detail specifications for ordering, refer to the relevant Gen-eral Specifications. For engineering, installation, operation, and maintenance of theFieldbus system and products described in this manual, refer to the relevant InstructionManuals.

This manual consists of three parts. Part A outlines Fieldbus prescribed by the FieldbusFoundation and Yokogawa’s Fieldbus-ready products, Part B explains Fieldbus engineer-ing, installation, operation, and maintenance, and Part C outlines the Plant ResourceManager (PRM) software developed by Yokogawa.

Part A consists of four sections. An overview of the functions and progress of internationalstandardization of Fieldbus is given in Section A1, the features of Fieldbus in Section A2,Fieldbus-ready field devices in Section A3, and Yokogawa’s Fieldbus-ready systems inSection A4.

Part B consists of five sections. Managing Fieldbus engineering is described in Section B1,design considerations in Section B2, construction considerations in Section B3, startupconsiderations in Section B4, and maintenance considerations in Section B5.

Part C consists of four sections. An overview and glossary of Plant Resource Manager(PRM) are described in Section C1, the system configuration in Section C2, an overview offunctions in Section C3, and the interface to the computerized maintenance managementsystem in Section C4.

Sep.01,2002-00Media No. TI 38K03A01-01E (MO) 3rd Edition : Sep. 2002 (YK)All Rights Reserved Copyright © 1998, Yokogawa Electric Corporation

ii<Toc> <Ind> <Rev>

TI 38K03A01-01E

Target Readership for This ManualThis manual is mainly intended for:

• Managers who are planning to purchase a control system, Fieldbus, and PlantResource Manager (PRM).

• Instrumentation, electricity, maintenance, and computer engineers who are evaluatingprocess control systems, Fieldbus, and maintenance management systems forpurchase or who will be in charge of installing these systems.

Trademarks• CENTUM is a registered trademark of Yokogawa Electric Corporation.

• Ethernet is a registered trademark of Xerox Corporation.

• Microsoft and Windows are registered trademarks or trademarks of MicrosoftCorporation in the United States and/or other countries.

• “FOUNDATION” in “FOUNDATION Fieldbus” is a registered trademark of the FieldbusFoundation.

• NI-FBUS Monitor is a registered trademark of National Instruments Corporation.

• HART is a registered trademark of the HART Communication Foundation.

• Oracle is a registered trademark of Oracle Corporation.

• MAXIMO is a registered trademark of MRO Software, Inc.

• Other product and company names may be registered trademarks of their respectivecompanies (the TM or ® mark is not displayed).

Sep.01,2002-00

Toc A -1<Int> <Ind> <Rev>

TI 38K03A01-01E

Fieldbus Technical InformationPart A Overview of Fieldbus and

Yokogawa’s Fieldbus-ready Products

CONTENTS

Sep.01,2002-00

TI 38K03A01-01E 3rd Edition

A1. Progress of International Standardization of Fieldbus ....................... A1-1A1.1 What is Fieldbus? ......................................................................................... A1-1

A1.2 Progress of Fieldbus Standardization ......................................................... A1-2

A1.3 Fieldbus Standard Specifications ................................................................ A1-4

A1.4 Yokogawa’s Efforts for Fieldbus Standardization ....................................... A1-5

A2. Features of Fieldbus ............................................................................. A2-1A2.1 Comparison with Conventional Communication ........................................ A2-2

A2.2 Reduced Wiring Cost .................................................................................... A2-4

A2.3 Improved Transmission Accuracy ............................................................... A2-6

A2.4 Enhanced Data Transmission ...................................................................... A2-8

A2.5 Distributed Functions ................................................................................... A2-9

A2.6 Interoperability ............................................................................................ A2-10

A3. Fieldbus-ready Field Devices ............................................................... A3-1A3.1 Changes in Transmitters .............................................................................. A3-3

A3.1.1 Accuracy Improvement due to Digitalization.................................... A3-4

A3.1.2 Multi-sensing Function Equipment .................................................. A3-6

A3.1.3 Multifunction Equipment ................................................................. A3-7

A3.2 Actuator ......................................................................................................... A3-8

A3.3 Using Self-diagnostics Function................................................................ A3-10

A3.4 Yokogawa’s Fieldbus-ready Field Devices Line-up .................................. A3-11

A4. Yokogawa’s Fieldbus-ready Systems .................................................. A4-1A4.1 Fieldbus Support in Yokogawa’s CENTUM Control Systems..................... A4-1

A4.1.1 Fieldbus Support in FCS for FIO of CENTUM CS 3000 ................... A4-2

A4.1.2 Fieldbus Support in FCS for RIO and Compact FCS ofCENTUM CS 3000 ......................................................................... A4-4

A4.1.3 Fieldbus Support in CENTUM CS 1000 .......................................... A4-6

A4.1.4 Fieldbus Support in CENTUM CS ................................................... A4-8

A4.2 Connection of FF Devices from Other Vendors toYokogawa’s CENTUM Control Systems .................................................... A4-10

Blank Page

<A1. Progress of International Standardization of Fieldbus> A1-1

TI 38K03A01-01E

A1. Progress of InternationalStandardization of FieldbusThis section describes what is Fieldbus, the progress of standardization of Fieldbus,Fieldbus standard specifications, and Yokogawa’s efforts toward standardization ofFieldbus.

A1.1 What is Fieldbus?The Fieldbus Foundation gives the following definition: “Fieldbus is a digital, two-way, multi-drop communication link among intelligent measurement and control devices.” Fieldbus isgradually replacing 4 to 20 mA standard instrumentation signals used to transfermeasurement and control data between control room and plant floor. It is one of severallocal area networks dedicated for industrial automation.

Modern industries in the 21st century could not survive without information technologiesand networks. From production line to enterprise level, digital communication supports alleconomic and social activities with powerful modern technologies. Fieldbus is one suchtechnology and cannot be separated from others. Fieldbus is at the lowest level in thehierarchy and exchanges information with higher-level databases.

IEC (International Electrotechnical Commission) prescribes the following seven definitionsstandardized by the standard organizations (shown by their trademarks) as internationalstandards of Fieldbus:

• FOUNDATION Fieldbus and HSE

• ControlNet

• PROFIBUS and PROFInet

• P-NET

• WorldFIP

• INTERBUS

• SwiftNet

FOUNDATION Fieldbus, which is one of the seven definitions, is a standard defined by theFieldbus Foundation. Yokogawa, a member of the board of directors of the FieldbusFoundation since its inception, has participated closely in developing the Fieldbusspecifications.

Unfortunately, the Fieldbus standards of IEC list the definitions of many standard organiza-tions. In practice, all major makers and users are now participating in the Fieldbus Founda-tion, and many products based on the FOUNDATION Fieldbus specifications are devel-oped and marketed.

Yokogawa considers that FOUNDATION Fieldbus will be used as widely as the fieldbus forprocess control systems in industry. Yokogawa’s CENTUM CS 3000, CENTUM CS 1000,and CENTUM CS support FOUNDATION Fieldbus.

FOUNDATION Fieldbus H1 (Low Speed Voltage Mode) is called FOUNDATIONFieldbus, Fieldbus, H1 Fieldbus, FF, or FF-H1 in this manual.

The sophisticated communication functions of Fieldbus allow distributed control viaFieldbus devices and optimal control by interfacing with a field control station (FCS).

Sep.01,2002-00

<A1. Progress of International Standardization of Fieldbus>

TI 38K03A01-01E

A1-2

A1.2 Progress of Fieldbus StandardizationThe international standards of Fieldbus have been unified by IEC/TC65/SC65C WG6(International Electrotechnical Commission/Technical Committee 65/Sub-Committee 65C/Working Group 6), ISA (The International Society for Measurement & Control) SP50Committee (which defined 4 to 20 mA analog signals as the standard electronicinstrumentation signal), and the Fieldbus Foundation.

Recently, the Fieldbus Foundation, a private organization formed to promote Fieldbus, issupporting the international unification of Fieldbus standards. Yokogawa, a member of theboard of directors of the Fieldbus Foundation since its inception, is also promotingFOUNDATION Fieldbus worldwide.

Recognition as a Standardization Work ItemIn 1984, the standardization concept for the next-generation digital communication protocolfor field devices was first proposed to the IEC, which is to replace the 4 to 20 mA analogtransmission. In 1985, IEC/TC65/SC65C recognized the digital communication protocol asa new standardization work item and named it Fieldbus. IEC/TC65/SC65C WG6, and theISA SP50 Committee, which had already commenced discussions on Fieldbus standard-ization, consented to jointly standardize Fieldbus.

Establishment of the Fieldbus FoundationThe standardization of Fieldbus will have a great effect on industry. Many views werepresented at the ISA SP50 Committee, delaying the standardization of Fieldbus.

To make up for lost time and promote the production of Fieldbus, ISP (Interoperable Sys-tems Project) was organized by Yokogawa, Fisher Control, Rosemount, and Siemens inAugust 1992. In February 1993, ISP became ISP Association.

In March 1993, WorldFIP (Factory Instrumentation Protocol) was jointly created byHoneywell, A-B (Allen-Bradley), CEGELEC, Telemechanique, and several othercompanies.

A consensus was then obtained amongst customers that Fieldbus should conform to theinternationally unified standard. In September 1994, in accordance with this decision, theISP Association and WorldFIP North America were combined to form the Fieldbus Founda-tion.

Sep.01,2002-00


TI 38K03A01-01E

Process of StandardizationIEC/TC65/SC65C WG6 and the ISA SP50 Committee started Fieldbus standardization. Byestablishing the Fieldbus Foundation, a structure has been built to develop internationallyunified instrumentation specifications.

The process of Fieldbus standardization is shown below.

• 1984 The standardization concept of digital communication protocol for field devices was proposed to IEC.

• 1985 In IEC/TC65/SC65C, the new standardization work item was recognized and named Fieldbus.

• 1990 The ISA SP50 Committee and IEC/TC65/SC65C/WG6 decided to collaborate on Fieldbus standardization.

• August, 1992 ISP was organized.

• March, 1993 WorldFIP was established.

• September, 1994 The ISP Association and WorldFIP North America were combined into The Fieldbus Foundation. Since then, The Fieldbus Foundation has developed the internationally unified instrumentation specifications. The Fieldbus standardization structure is configured by IEC, ISA, and The Fieldbus Foundation.

• August, 1996 Fieldbus Foundation defined and published FOUNDATION Fieldbus H1 standard (low speed voltage mode).

1985 1990 1992.8 1993.3 1994.9 1996.8

ISASP50

Committee

IEC

1984

WorldFIPNorth

America

ISPThe FieldbusFoundation

A010201E.EPS

FF-H1 standard is defined and published.

Figure Process of Fieldbus Standardization

Sep.01,2002-00

<A1. Progress of International Standardization of Fieldbus>

TI 38K03A01-01E

A1-4

A1.3 Fieldbus Standard SpecificationsThere are two kinds of Fieldbus physical layer specifications standardized by IEC61158-2and ISA S50.02: low-speed and high-speed Fieldbus specifications. But the high-speedFieldbus specification is not adopted and High Speed Ethernet (HSE) specification isadded as additional type.

IEC/ISA Standard SpecificationsThe low-speed and high-speed Fieldbus specifications are standardized as shown in thetables below.

Table Fieldbus Specifications (Standard)

Item Low-Speed FieldbusFF-H1

High-speed FieldbusFF-H2

Transmission Speed 31.25 kbps1.0 Mbps (in 1 Mbps mode or high-speed current mode) 2.5 Mbps (in 2.5 Mbps mode)

Number of Connectable devices Max. 32 devices/segment

Max. 32 devices/segment(Using repeaters increase the number of connectable devices.)

Cable • Twisted pair cable (shielded) • Optical Fiber

• Twisted pair cable (shielded)

Power supply to connected devices Enabled Enabled

Intrinsic safety Enabled Enabled

Redundancy No (*1) Enabled

Example of connected devices

Transmitter, control valve, field multiplexer, etc.

Multicomponent analyzer, PLC, remote I/O, etc.

High-speed FieldbusFF-HSE (High Speed Ethernet)

100 Mbps

Positioning Field device integration Subsystem integrationSubsystem integrationData Server integration

Number of connectable devicesdepend on the subsystem integrated by FF-HSE.

• Twisted pair cable (shielded) • Optical Fiber

No

No

Enabled

Multicomponent analyzer, PLC, remote I/O, etc.

A010301E.EPS

*1: Yokogawa has developed dual-redundant configuration of ALF111 Fieldbus Communication Module for FF-H1.

Table Type of Low-speed Fieldbus Cables and Transmissible Length

Type of cable Cable specificationsMax. length of cable

(reference value)

Type A: Individually-shielded twisted pair cable #18AWG (0.82 mm2) 1,900 m

Type B: Overall-shielded twisted pair cable #22AWG (0.32 mm2) 1,200 m

Type C: Unshielded twisted pair cable #26AWG (0.13 mm2) 400 m

Type D: Overall-shielded non-twisted cable #16AWG (1.25 mm2) 200 mA0130302E.EPS

Note: Yokogawa recommends the use of Type A.Usage of Types B and D is restricted.Yokogawa does not recommend the use of Type C.

SEE ALSO

For the cable specifications, refer to Section B2 of Part B.

Sep.01,2002-00


TI 38K03A01-01E Sep.01,2002-00

A1.4 Yokogawa’s Efforts for Fieldbus StandardizationYokogawa, a member of the board of directors of the Fieldbus Foundation, has played aleading role in the international standardization of Fieldbus standards.

Services for Fieldbus Support DevicesYokogawa has worked hard to promote Fieldbus, and provided the following services to addvalue for customers:

Product Development

Yokogawa has developed and provided a variety of products that support Fieldbus, rangingfrom various field devices to an integrated production control system, CENTUM CS 3000.

Development of Field Device Management and Diagnostics Packages

Yokogawa has developed and provided field device management and diagnostics pack-ages which support enhanced field information.

Blank Page

<A2. Features of Fieldbus> A2-1

TI 38K03A01-01E

A2. Features of FieldbusFieldbus is a bidirectional digital communication protocol for field devices. Fieldbustechnology drastically changes process control systems and is gradually replacingthe standard 4 to 20 mA analog transmission that most current field devices employ.

Fieldbus has the following features:

• Because multiple devices can be connected, and multivariables can be trans-mitted on a single cable, thus reducing the number of cables, wiring costs arereduced.

• A digital transmission protocol ensures accurate information processing andhence strict quality control.

• Multiplex communications allow other information as well as process variables(PVs) and manipulated variables (MVs) to be transmitted from field devices.

• Communication between field devices allows truly distributed control.

• Interoperability enables devices from different manufacturers to be combined.

• A broad choice of devices from any manufacturer permits flexible systemconstruction.

• Instrumentation systems, electrical devices, FAs, BAs, OAs, and analyzers canbe integrated.

• Some adjustments and inspections of field devices can be performed from thecontrol room.

The following sections explain the advantages of Fieldbus and the effect of Fieldbuson process control systems.

Sep.01,2002-00

<A2. Features of Fieldbus>

TI 38K03A01-01E

A2-2

A2.1 Comparison with Conventional CommunicationThe Fieldbus communication protocol is superior to analog transmissions and hybridcommunications in information accuracy, transmission speed, and transmission amount. Italso offers superiority to those transmissions and communications in functionality, includingthe ability to communicate between connected devices and to communicate bidirectionally.

Analog TransmissionAn analog transmission is an information transmission technique using analog signals witha direct current of 4 to 20 mA. The topology, which is a one-to-one system, allows only onefield device to be connected to a single cable. The transmission direction is one-way.Therefore, two different cables must be provided: one to acquire information from the fielddevice, and the other to transmit control signals to the field device.

Hybrid CommunicationA hybrid communication is a communication technique in which field device information issuperimposed as digital signals on the conventional 4 to 20 mA analog signal. In addition toanalog transmission capabilities, it is possible to remotely set up the field device range andzero-point adjustment. Also, maintenance information such as self-diagnostics of the fielddevice can be obtained using a dedicated terminal.

Hybrid communication protocols were developed independently by each manufacturer, andso devices from different manufacturers cannot communicate with each other. With theYokogawa BRAIN system or the hybrid communication systems of other manufacturers, theself-diagnostics information cannot be exchanged between field devices from differentmanufacturers. A hybrid communication mainly supports 4 to 20 mA analog transmission,though it also allows digital data communication. The digital data communication speedthrough the hybrid communication is slower than that through the Fieldbus communication.

Sep.01,2002-00


TI 38K03A01-01E

Fieldbus CommunicationThe Fieldbus communication protocol, which is different from analog transmissions orhybrid communications, supports a perfect digital signal communication system. In addi-tion, the Fieldbus communication supports bidirectional communication, thus allowing moretypes and a larger amount of data to be transmitted in comparison to analog transmissionand hybrid communication.

This communication removes the restriction which allows only one field device to be con-nected to a single cable in an analog transmission system. Multiple field devices can beconnected to a single Fieldbus cable. Also, since this communication is internationallystandardized, interoperability of field devices is guaranteed.

Fieldbus solves the problems of hybrid communications, such as slow digital transmissionspeeds and lack of interoperability.

A comparison between the conventional 4 to 20 mA analog transmission, hybrid communi-cation, and Fieldbus communication protocols is shown below.

Table Comparison of Communication Protocols

Fieldbus Hybrid Analog

A020101E.EPS

Topology Multi-drop One-to-one One-to-one

Transmissionmethod

Digital signal

4 to 20 mA DCanalog signal

+digital signal

4 to 20 mA DCanalog signal

Transmissiondirection

Bidirectional

One-way(analog signal),

bidirectional(digital signal)

One-way

Type of signal Multiplex signalPartially multiplex

signalSingle signal

Standard Standardized in 1996.Differs dependingon manufacturers

Standardized

Sep.01,2002-00


TI 38K03A01-01E

A2-4

A2.2 Reduced Wiring CostThe introduction of Fieldbus reduces wiring cost by means of multi-drop connections andmultivariable transmission.

Multi-drop ConnectionsConnecting multiple field devices to a single cable is known as multi-drop connections, andthe reduction in the number of cables has many advantages. An example of multi-dropconnections is shown below.

Field device Field device

To the system

A020201E.EPS

Multi-drop connectionFieldbus

Figure Multi-drop Connections

In a conventional analog transmission system, only one field device can be connected to asingle cable that leads to a system. Multi-drop connections connect multiple field devices toa single cable, and so allow additional field devices to be connected to a cable which hasalready been laid.

In the past, it was costly to connect multiple field devices. Using a Fieldbus communicationsystem, it is possible to connect a large number of field devices to the Fieldbus because oflow wiring cost by multi-drop connections. This expands the scale of process controlsystems and promotes a higher level of plant automation.

Sep.01,2002-00


TI 38K03A01-01E Sep.01,2002-00

Multivariable Detection and TransmissionMultivariable means multiple measured variables, and multivariable detection means thatone field device can detect multiple measured variables, which is also called multi-sensing.

A conventional analog transmission system requires one cable for each measured variable.Fieldbus supports multivariable transmission. Therefore, a field device can transmit allmeasured variables detected by the field device via a single cable.

The difference in wiring a control valve between analog and Fieldbus communicationsystems is shown below.

Conventional Analog Transmission System Fieldbus Communication System

Positioner Positioner

Control valve

• Positioner control signal• Valve opening signal• Upper/lower limit signal Total

Control valve

Number of cables

• Fieldbus : 1 pair

Number of cables

: 1 pair: 1 pair: 2 pairs: 4 pairs

A020202E.EPS

Positioner control signalLower limit signalValve opening signalUpper limit signal

Positioner control signal

Lower limit signal

Valve opening signal

Upper limit signal

Fieldbus

Figure Difference in Detection and Transmission between Analog Transmission and FieldbusCommunication Systems

In the conventional analog transmission system, the control output signal to the positioneris usually transmitted. In a Fieldbus communication system, multiple pieces of informationsuch as control signals, limit signals, and valve opening signals can all be detected andtransmitted.

Multivariable detection and transmission can be used for:

• Monitoring the condition of the steam heat tracing of differential pressure transmittersby ambient temperature information.

• Detecting clogging in impulse lines by static pressure information.

Many other pieces of information will also be used to expand measurement and controlcapabilities.


TI 38K03A01-01E

A2-6

A2.3 Improved Transmission AccuracyFieldbus improves transmission accuracy by eliminating errors that occur during datatransmission in the conventional analog transmission system.

Removing Error FactorsThe following three factors cause errors in the conventional analog transmission system.

• D/A conversion in the field device

• Analog signal transmission

• A/D conversion in the system

For example, if data is transmitted from a field device with a microprocessor in the conven-tional analog transmission system, an error may result during A/D and D/A data conversion.Fieldbus eliminates transmission errors and conversion errors during data transmission.

The difference in transmission accuracy between the conventional analog transmissionsystem and the Fieldbus communication system is shown below.

Upgrade to Fieldbus

Data transmission direction

Data transmission direction

4 to 20 mA analog signal

Digital signal

PVs with transmission errors

Sensor µP ModemModem

Conventional Analog Transmission System

Fieldbus Communication System

System

PVs without transmission errors

System

Sensor µP A/DD/A

A020301E.EPS

Error due to data conversionError due to data conversion

Error due to analog signal transmission

Figure Difference in Transmission Accuracy between Analog Transmission and FieldbusCommunication Systems

Fieldbus transmits data using digital signals. Signal transmission errors rarely occur indigital signal transmission, unlike analog signal transmission. In addition, Fieldbus does notneed A/D and D/A conversions because data is always transmitted digitally. Fieldbusremoves these three error factors, improving transmission accuracy.

System reliability also improves as a result of higher transmission accuracy, which allowsstricter quality control and greater production efficiency.

Sep.01,2002-00


TI 38K03A01-01E

Making the Most of Field Device AccuracyImproved data transmission means accurate transmission of data which is detected by fielddevices. Especially, digital field devices reduce transmission errors and conversion errors ofdigital signals detected by sensors. Therefore, a Fieldbus communication system can takeadvantage of the performance of high-accuracy field devices.

Sep.01,2002-00


TI 38K03A01-01E

A2-8

A2.4 Enhanced Data TransmissionIn a Fieldbus communication system, many pieces of field information as well as PVs andMVs can be exchanged between field devices. Fieldbus can transmit many kinds of databidirectionally, so the system offers more advanced functionality than a conventionalanalog transmission system.

Various Types of Data TransmissionFieldbus can transmit various types of data.

The conventional analog transmission system cannot transmit data other than PVs andMVs. Although hybrid communication, an analog communication protocol with a digital datatransmission function, allows various types of data transmission, the hybrid communicationprotocol has the following problems:

• The transmission speed is slow.

• Only one-to-one communication between a system and a field device is possible.

Fieldbus solves the problems associated with hybrid communication.

• The transmission speed is fast.

• Multiple pairs of devices can simultaneously communicate among a system and fielddevices, and between field devices.

Transmission of various types of data allows the following advanced functionalities.

• Since past maintenance information can be easily acquired, maintenance efficiencyimproves.

• Device management such as field device master file creation can be automated.

Bidirectional CommunicationFieldbus transmits multiplexed digital information. This enables the system to performbidirectional communication, which is not possible with the conventional analog transmis-sion system.

Data Exchange between Field DevicesDistribution of control to field devices is made possible by exchanging data between them.

Sep.01,2002-00


TI 38K03A01-01E

A2.5 Distributed FunctionsThe use of Fieldbus implements integrated control over the entire plant and autonomousdistributed control.

Installing Advanced Functions in Field DevicesFieldbus allows the exchange of field information used for control in addition to PVs andMVs.

Field devices with a calculation function and other functions can thus be adjusted from asystem. Although some functions such as correction computation have been installed incurrent field devices, various functions that use more information are expected to beincluded in future field devices.

By doing this, a field device such as a positioner will be able to field-adjust valve controlcharacteristics.

Distributing Functions to the FieldDepending on the requirements of the processes to be controlled, field devices areequipped with advanced functions that provide some control functionality that used to beprovided by a system.

Distribution of control to field devices will change system functions.

Functions of Field Devices and SystemBy increasing the functionality of field devices and distributing control functions, the func-tions will vary between field devices and system.

For example, the user can install the PID function for each control object in a field device ora system.

If the relation between loops is tight and they cover a wide range in a large-scale plant, thePID function will be generally installed in the system. Conversely, if the loops are relativelyindependent in a small-scale plant, the PID function may be installed in a field device.

In an oil refinery or a petrochemical, for example, the PID function is closely related tocomplex control, advanced control, optimized control, and integrated control over the entireplant. Therefore, excluding some independent control loops, the PID function will be in-stalled in the system.

Sep.01,2002-00


TI 38K03A01-01E

A2-10

Sep.01,2002-00

A2.6 InteroperabilityConventional hybrid communications can transmit digital signals, but information exchangebetween devices of different manufacturers is difficult because each device uses itsmanufacturer’s protocol.

In Fieldbus communication, international standardization of the protocol ensures theInteroperability between FF devices including FF interface card in host system. FF devicesallow digital data to be exchanged between devices from different manufacturers. There-fore, the freedom to configure the process control system increases since there is no needto choose one device manufacturer.

The Fieldbus Foundation prescribes the interoperability test procedure calledInteroperability Test (IT) to ensure the Interoperability for the FF devices, and the FF de-vices that passed the IT are registered to the Foundation, and published on the FieldbusFoundation’s web site (http://www.fieldbus.org/). Yokogawa registered EJA series transmit-ter as the world’s first vendor.

Fieldbus Foundation started the Host Interoperability Support Test (HIST) for host com-puter in September 2000. On September 14, 2000, Yokogawa’s CENTUM series werecertified as the system able to execute the Host Interoperability Support Test (HIST),becoming the world’s first vendor to carry out the HIST. The HIST is to prove theinteroperability between the host computer and devices. The various devices from differentmanufacturers has been tested by the CENTUM series with the HIST procedure, and theinteroperability has been proved.

<A3. Fieldbus-ready Field Devices> A3-1

TI 38K03A01-01E Sep.01,2002-00

A3. Fieldbus-ready Field DevicesWhen Fieldbus is introduced, the type and amount of transmissible information willdrastically increase. Also, bidirectional communication of digital information cantake place between a field device and a system, and between field devices. To makethe most of communication improvements and to satisfy more advanced needs, bigchanges are taking place with field devices. This section explains the differences infield devices when Fieldbus is introduced in a communication system.

Difference between Analog Transmission and Fieldbus CommunicationSystems

The Fieldbus communication system transmits information differently from the conventionalanalog transmission system. It has the following capabilities:

• A large amount of information can be transmitted.

• There are many types of transmissible information, both control and non-controlinformation.

• Digital information can be transmitted.

• Bidirectional communication is possible between a field device and a system.

• Bidirectional communication is possible between field devices.

According to those differences, the information handled by field devices (field information)changes significantly.

The differences between analog transmission and Fieldbus communication systems isshown below.

One variableOne way

Controller

Sequencer

Fieldbus

Control bus

A030001E.EPS

Remote I/O card,terminal board

MultivariableBidirectional

Sequencergateway

Controlstation

Fieldjunction box

Computergateway

Conventional Analog Transmission System Fieldbus Communication System

4 to 20 mA analogcommunicationcable

Control valve

Control valve

Flowmeter

Flowmeter

Bidirectional communicationis possible between thecontrol valve and flowmeters.

Figure Difference between Analog Transmission and Fieldbus Communication Systems

<A3. Fieldbus-ready Field Devices>

TI 38K03A01-01E

A3-2

Sep.01,2002-00

Advanced Functionality of Field DevicesBy making the most of Fieldbus communication system features, it is possible to have moreadvanced control over the system. As a result, more advanced functionality is required infield devices.

For example, by transmitting self-diagnostics information from a field device to the system,with the appropriate timing, the system can control the field device according to its statusand can predict a problem in the field device. Also, by exchanging data (PV, MV, etc.)between field devices, autonomously distributed control of multiple field devices will bepossible.

Once the main power to the process control systems was changed from air to electricity,new electric-powered field devices appeared on the market. Similarly, when processcontrol systems are changing from analog transmission to Fieldbus communication, newfield devices that support Fieldbus communication capabilities are appearing on the mar-ket.

Field devices are primarily categorized into transmitters and actuators. Fieldbus will bringabout changes in both components. The following sections describe what changes willoccur in transmitters and actuators.


TI 38K03A01-01E Sep.01,2002-00

A3.1 Changes in TransmittersThe Fieldbus communication system can transmit digital information in a single line. There-fore, the function of a transmitter is changing greatly.

In a conventional analog transmission system, transmitters are primarily designed totransmit the PV value to be measured to the system. This is because the analog transmis-sion system performs one-way communication, from a field device to a system, or viceversa.

By using the Fieldbus communication system, the type and amount of information beingtransmitted through a single cable will increase drastically, and will be far greater than thatof a conventional analog transmission system. In addition, bidirectional communication canbe performed between a field device and a system, and between field devices. Since digitalinformation can be transmitted to field devices without conversion, information will be muchmore reliable.


TI 38K03A01-01E

A3-4

Sep.01,2002-00

A3.1.1 Accuracy Improvement due to DigitalizationSince the Fieldbus communication system transmits information digitally, it can transmit themeasured data from a transmitter to the system with minimum error. Many transmitters withdrastically higher accuracy come to market.

Improvement of Transmission AccuracyA transmitter with the conventional analog transmission handled a PV value as a percent-age (0 to 100 % relative value) of the measuring range, and transmitted this value to thesystem after converting to a 4 to 20 mA analog signal. The system converted the 4 to 20mA analog signal that was transmitted to the digital signal in engineering unit, and used it.

Errors occur during these signal conversion.

In contrast, a transmitter with the Fieldbus communication handles a PV value in engineer-ing units and transmits this value, without conversion, to the system as a digital signal. Thesystem uses the digital signal as it was transmitted. The Fieldbus communication systemdoes not require signal conversion, thereby eliminating conversion errors that occur duringtransmission of measured data.

The Fieldbus communication system provides for higher data transmission accuracycompared to the analog transmission system.

Using the example of the orifice flowmeter which uses a differential pressure transmitter,the difference in transmission accuracy between the analog transmission and Fieldbuscommunication systems is described below.

In a conventional analog transmission system, the differential pressure generated at theorifice, proportional to the square of the flow rate, was measured by a differential pressuretransmitter and transmitted to the system after converting to a 4 to 20 mA signal. If thedifferential pressure, �P at the orifice is 2 kPa when the flow rate is 20 Nm3/h, the outputsignal of the differential pressure transmitter will be as shown in the table below. Theanalog transmission system generates an error when this output signal is converted to adigital signal in the system side.

If the differential pressure is converted to a flow rate on the system side, the transmissionerror will be changed by the flow rate because this conversion is not linear as shown inFigure below.

Table Analog Signal Data

OutputDifferentialpressure

Flow rate

4 mA 0 kPa 0 Nm3

m3

/h

20 mA 2 kPa 20 N /h

A030101E.EPS

Differentialpressure

Flow rate

A030102E.EPS

Figure Relationship between Differential Pressure and Flow Rate


TI 38K03A01-01E Sep.01,2002-00

In contrast, the Fieldbus communication system transmits the flow signal in engineeringunits as a digital signal. Therefore, there is no error during transmission. In this example,the differential pressure generated by the orifice is calculated and converted to a flow rateby the microprocessor of the differential pressure transmitter. The flow signal in engineeringunit is transmitted to the system as a digital signal without conversion.

Improvement of Transmitter Measuring AccuracyIf the transmission accuracy is improved by the Fieldbus communication, the improvementof transmitter measuring accuracy will be a factor in improving the accuracy of the entireprocess control system. To perform measurements at higher accuracy, field devices thatemploy a superior measurement principle will be widely used.

For example, conventional mechanical flow meters and level meters will be replaced byelectric flow meters and level meters that employ digital technology.

Since the Fieldbus communication system transmits the measured data in engineeringunits, without dependence on measuring range, a transmitter with a wide measuring rangewill show the original measuring performance. The width of the measuring range is one ofthe most important factors in determining the quality of transmitters.


TI 38K03A01-01E

A3-6

Sep.01,2002-00

A3.1.2 Multi-sensing Function EquipmentThe function used to measure multiple variables with a single transmitter is known as themulti-sensing function.

In a Fieldbus communication system, it is possible to transmit multiple pieces of informationover a single cable. To make the most of this Fieldbus feature, users will demand transmit-ters equipped with a multi-sensing function.

In a conventional analog transmission system, a transmission cable with a pair of wires isrequired to transmit one measured value. For example, a transmitter that can performmultiple measurements, such as the Coriolis flowmeter, requires multiple cables to transmitmultiple measurement variables.

The Fieldbus communication system allows the Coriolis flowmeter to transmit multiplemeasurement variables via a single cable.

Transmitters that have been used to perform only one measurement are enhanced toperform the multi-sensing function using the Fieldbus communication system.

For example, the differential pressure transmitter is able to measure process pressure,ambient temperature, etc., in addition to flow rate, which was the transmitter’s originalfunction. If a temperature sensor for measuring the process temperature is combined withthis differential pressure transmitter, all flow rate, pressure, and temperature variablesnecessary for process control will be measurable by the transmitter alone.

Possible data that will be gained by multi-sensing function for the main transmitters areshown below.

• Differential pressure flowmeter: Mass flow, volume flow, pressure, temperature

• Magnetic flowmeter: Volume flow, conductivity, temperature

• Vortex flowmeter: Mass flow, volume flow, temperature, pressure

• Coriolis flowmeter: Mass flow, volume flow, density, temperature

• Differential pressure level meter: Liquid level, density and specific gravity, tankinternal pressure, temperature

• Ultrasonic level meter: Liquid level, temperature

• Temperature transmitter: Humidity, ambient temperature, vibration

• pH meter: pH, temperature

• Conductivity meter: Conductivity, temperature


TI 38K03A01-01E Sep.01,2002-00

A3.1.3 Multifunction EquipmentA Fieldbus communication system can transmit other information in addition to the PVvalue. To make the most of this feature, the transmitter is expected to calculate the multiplevalues and process them into the required information for control.

A transmitter that incorporates multiple functions, such as the calculation function, is knownas a multifunction transmitter. Multifunction transmitters increase for a Fieldbus communi-cation system.

The main function of transmitters used in a conventional analog transmission system is tomeasure a PV value at high-accuracy and transmit it. To do this, additional devices areused for converting the measured PV value into the information necessary for control.

A multifunction transmitter can calculate the PV value in engineering units required by theuser and transmit it to the system.

If a multifunction transmitter is used in combination with the above multi-sensing function, itis possible to drastically simplify the process control system.

For example, assume that there is a differential pressure transmitter which can multi-sensethe flow rate, pressure, and temperature. If a calculation function is added to this differentialpressure transmitter, it allows the transmitter to calculate the mass flow rate after tempera-ture-pressure compensation using the measured flow rate, pressure, and temperature, andbefore executing transmission.

To attain the above functions, a conventional analog transmission system would requirethree transmitters, one each for flow rate, pressure, and temperature, and an additionalcalculator for temperature-pressure compensation. A single multifunction transmitter withmulti-sensing can process all of this.

This will not only drastically reduce the instrumentation cost, but will also improve thereliability.


TI 38K03A01-01E

A3-8

Sep.01,2002-00

A3.2 ActuatorFieldbus is expected to offer many possibilities for actuators.

This section explains, using a typical control valve actuator, the changes that are takingplace in actuators.

Control Valve ChangesThe progress brought about by Fieldbus communication will drastically change the role ofthe control valve.

A control valve with a conventional analog transmission controls a valve using a positioneraccording to the MV value transmitted from the system.

On the other hand, a control valve with Fieldbus communication does not only control thevalve to a constant opening, but also returns the valve opening value back, with respect tothe MV value, and outputs limit signals to the system. This will promise more stabilizedcontrol of the system without valve opening meter and limit switches separately.

Also, this valve and its positioner are able to perform valve characteristic modifications,temperature compensations, etc., which were usually made by the system. This will make itpossible to compensate for valve operation as close to the process state as possible, whilemonitoring the valve characteristics.

If this positioner and valve are combined with a flowmeter, the feedback control of a controlvalve, which is currently handled by the system, will be handled by only the control valve.

Features of control valves with the Fieldbus communication are summarized next.


TI 38K03A01-01E Sep.01,2002-00

Features of Control Valves with the Fieldbus Communication• Improvement of valve controllability (detects stroke cycle, open-close time, etc. to

predict clogging, sticking, leakage, etc.)

• Remote monitoring of control valves

• Modification and improvement of valve characteristics

• Stabilized control together with operability and complete closure of valves

• Improved valve stability

• Ease-to-operate adjustment and stabilization of valve characteristics

• Reduction of valve accessories

The following figure shows the compensation curves of valve flow characteristics. By usingthe control valve with the Fieldbus communication, the following valve flow characteristicswill be change easily. In addition, it is possible to adopt the customized characteristics.

Flow rate

Valve openingA030201E.EPS

Intrinsic flow characteristics (from ISA Hand Book of Control Valve)

Qui

ck o

pen

Square root

Equal

perce

nt

Linea

r

Hyperbolic

Figure Modification of Valve Flow Characteristics


TI 38K03A01-01E

A3-10

Sep.01,2002-00

A3.3 Using Self-diagnostics FunctionThe Fieldbus communication system can predict a problem in a field device using the self-diagnostics function.

Integration of Instrumentation and Self-diagnostics FunctionsThe conventional analog transmission system can handle only one signal on a singlecable. The system handles the PV or MV value and the self-diagnostics information ascompletely different data, even if it is information from the same field device.

The Fieldbus communication system can handle multiple signals on a single cable. Thesystem can handle the PV or MV value and the self-diagnostics information in the sameenvironment. Instrumentation and self-diagnostics will be performed under the sameenvironment by integrating work in the field into a single network.

This idea is far different from the conventional one which has separated instrumentationfrom self-diagnostics.

Problem Prediction FunctionSince Fieldbus handles the measured values in engineering units, it allows the system toaccurately measure slight changes in pressure and temperature, other than the PV value.This enables the system to detect the symptoms of problems that were difficult to predict.

For example, suppose the system cannot judge whether the self-diagnostics result of afield device is abnormal or normal. The conventional analog transmission system cantransmit a self-diagnostics result as either abnormal or normal. Therefore, if a result cannotbe judged as being abnormal or normal, the system always handles it as abnormal forsafety. If a minor abnormality is generated in field devices, a number of alarms will bedisplayed on the panel in the control room. However, if minor abnormalities in field devicesare handled as normal to reduce alarms in the control room, the symptom of a majorproblem may not be detected.

If a self-diagnostics result cannot be judged as abnormal or normal, Fieldbus communica-tion system can transmit the status information to the system. In addition, Fieldbus com-munication system will be able to monitor the information which influences measurementand control, such as clogging, vibration, etc. The use of this information allows the systemto chronologically analyze changes in field devices and predict their problems.

Using the dedicated package software will make the maintenance work easier.


TI 38K03A01-01E

A3.4 Yokogawa’s Fieldbus-ready Field Devices Line-up

Differential Pressure/Pressure Transmitter DPharp EJA Series (suffix codefor output: F)

Function Block: Two (2) AI function blocks

One (1) PID function block (option: /LC1)

Link Master function (option: /LC1)

Hazardous area certification for FM, CENELEC, CSA, or JIS is available. FISCO model forFM or CENELEC intrinsically safe is also available.

(See GS 01C22T02-00E for the detail.)

Vortex Flowmeter YF100 (YEWFLO*E) (suffix code for output: F)

Function Block: One (1) AI function block



(See GS 01F02F04-00E for the detail.)

Magnetic Flowmeter ADMAG AE (with option code /FB)

Function Block: One (1) AI function block



Hazardous area certification for CENELEC ATEX is available.

(See GS 01E07F01-00E for the detail.)

Temperature Transmitter YTA320 (suffix code for output: F)

Function Block: Four (4) AI function blocks

One or two (1 or 2) PID function block(s) (option: /LC1 or /LC2)

Link Master function: with one (1) PID function block (option: /LC1)

with two (2) PID function blocks (option: /LC2)

Hazardous area certification for FM, CENELEC, CSA, SAA, or JIS is available. FISCOmodel for CENELEC intrinsically safe is also available.

(See GS 01C50T02-00E for the detail.)

Sep.01,2002-00


TI 38K03A01-01E

A3-12

Advanced Valve Positioner YVP110

Function Block: One (1) AO function block

Two (2) DI function block

One (1) OS (Output Splitter) function block



Signature Function:(option: /BP)

Hazardous area certification for FM, CENELEC, CSA, or JIS is available. FISCO model forFM or CENELEC intrinsically safe is also available.

(See GS 21B04C01-01E for the detail.)

YVP Management Software <Model: YVP20S>

This software package offers a variety of functions to help users to easily set up and tuneYVP110.

This software needs National Instruments FBUS fieldbus communication interface card.

(See GS 21B04C50-01E for the detail.)

Paperless Digital Recorder DAQSTATION (with option code /CF1)

Function Block: Eight (8) AI function block (1-channel each)

One (1) MAO function block (8-channel)

Link Master function

(See GS 04L01A01-00E for the detail.)

Sep.01,2002-00

<A4. Yokogawa’s Fieldbus-ready Systems> A4-1

TI 38K03A01-01E Sep.01,2002-00

A4. Yokogawa’s Fieldbus-ready SystemsThe control system that uses Fieldbus communication handles more advancedinformation than the conventional analog transmission system. Information recep-tion, display and record management are more important factors in control systems.

This section describes the Yokogawa systems that support Fieldbus.

The “H1 Fieldbus Communication Protocol” and “H1 Fieldbus” indicated in thissection and Part B are the “FOUNDATION Fieldbus H1 (Low Speed Voltage Mode)”of the Fieldbus Foundation.

A4.1 Fieldbus Support in Yokogawa’s CENTUMControl SystemsThe CENTUM CS 3000 Integrated Production Control System, CENTUM CS 1000 Produc-tion Control System, and CENTUM CS Integrated Production Control System supportFieldbus.

This section describes a typical system configuration for each CENTUM Fieldbus system.

These systems are connected to field devices via I/O modules which support 1-5 V DC/4-20 mA I/Os, thermocouple and resistance temperature detector inputs, digital I/O, andcommunication. The Fieldbus Communication Module can also be combined with suchconventional analog I/O modules.

<A4. Yokogawa’s Fieldbus-ready Systems>

TI 38K03A01-01E

A4-2

Sep.01,2002-00

A4.1.1 Fieldbus Support in FCS for FIO of CENTUM CS 3000Fieldbus support in FCS for FIO of CENTUM CS 3000 is shown below. FCS for FIO can beconnected via an ALF111 Fieldbus Communication Module installed in a node unit to FFtransmitters and FF valve positioners.

A040101E.EPS

HIS

V net

Ethernet

ALF111(in service)

ALF111(stand-by)

EB401(dual

redundant)

SB401(dual

redundant)

FCU

ESB bus

Fieldbuspower supply unit (optional)

Local Node

ER bus

Terminator

FCS

IS barrier or lightning arrester

(optional)H1 fieldbus segment

Terminator(optional)

ALF111(in service)

ALF111(stand-by)

EB501(dual

redundant)

Fieldbuspower supply unit (optional)

Remote NodeTerminator

IS barrier or lightning arrester

(optional)H1 fieldbus segment


ACB41

HIS: Human Interface stationPRM: Plant Resource ManagerFCS: Field control stationFCU: Field control unitSB401: ESB-bus interface (in Local Node)EB401: ER-bus interface (in Local Node)EB501: ER-bus interface (in Remote Node)ALF111: Foundation Fieldbus communication moduleACB41: I/O expansion cabinet for FIO

PRM

Operation and monitoring functionEngineering function(system generation)Fieldbus tools: • Engineering tool • Device management tool

Figure Fieldbus Support in FCS for FIO of CENTUM CS 3000


TI 38K03A01-01E Sep.01,2002-00

ALF111 Fieldbus Communication Module SpecificationsNumber of ALF111s per FCS:

Standard FCS control function: Max. 16 (*1) modules (8 pairs for a dual-redundant configuration) per FCS

Enhanced FCS control function: Max. 32 (*2) modules (16 pairs for a dual-redundant configuration) per FCS

Number of ALF111 ports: Max. 4 ports per ALF111 (One port is connectedto one segment (*3).)

Number of field devices per segment (*3): Max. 32 units per segment (including anALF111 as one unit)

Number of FF faceplate blocks: Max. 250 blocks for Standard FCS (general-purpose database)Max. 600 blocks for Enhanced FCS (general-purpose database)

ALF111 dual-redundant support: Dual-redundant configuration possible with twoadjacent ALF111s in a node

Link active scheduler (LAS) function: Available

Time master function: Available

The number of field devices per segment varies significantly depending on the cablelength, power supply capacity, existence of a barrier, etc. For details, refer to Section B2.2of Part B.

Other Fieldbus specifications are in accordance with the specifications for the FOUNDA-TION Fieldbus.

*1: For the standard FCS control function, the maximum number of ALF111s may be two depending on thedatabase type selected as the FCS database. For details, refer to GS, “Control Function for Standard FieldControl Station (for FIO)” (GS 33Q03K30-31E).

*2: For the enhanced FCS control function, when “remote node expanded” is selected as the database type, themaximum number of ALF111s is 32. In the other database type, the maximum number of ALF111s is 16. Fordetails, refer to GS, “Control Function for Enhanced Field Control Station (for FIO)” (GS 33Q03K31-31E).

*3: A segment is an engineering unit consisting of several Fieldbus devices and ALF111 port to be connected toone H1 Fieldbus.

SEE ALSO

For details of the ALF111 Fieldbus Communication Module, refer to GS 33Q03L60-31E.


TI 38K03A01-01E

A4-4

Sep.01,2002-00

A4.1.2 Fieldbus Support in FCS for RIO and Compact FCS ofCENTUM CS 3000Fieldbus support in FCS for RIO and Compact FCS of CENTUM CS 3000 is shown below.FCS for RIO and Compact FCS can be connected via an ACF11 Fieldbus CommunicationModule installed in an I/O module nest to FF transmitters and FF valve positioners.

A040102E.EPS

V net

HIS: Human Interface StationPRM: Plant Resource ManagerLFCS: Standard FCSSFCS: Compact FCSRIO bus: Remote I/O busNIU: Node Interface UnitACF11: Fieldbus Communication Module

NIU ACF11

LFCS SFCS

RIO bus

ACF11

Externalpower supply

(optional)Intrinsic safety barrier /

arrester(optional)

Field devices

HIS

Ethernet

PRM


Terminator (optional)

CouplerH1 Fieldbus

Fieldbus

Coupler

Terminator

Figure Fieldbus Support in FCS for RIO and Compact FCS of CENTUM CS 3000


TI 38K03A01-01E Sep.01,2002-00

ACF11 Fieldbus Communication Module Specifications of CENTUM CS3000

The main specifications of the ACF11 Fieldbus Communication Module of CENTUM CS3000 are shown below.

For LFCS (FCS for RIO)

Number of ACF11s per FCS: Max. 80 modules per FCS

Number of ACF11s per AMN33 nest: Max. two modules per nest

Number of segments (*1) per ACF11: Max. one segment

Number of field devices per segment (*1): Max. 32 units per segment (including anACF11 as one unit)



Fieldbus power supply: Available (supply current: max. 80 mA)

For SFCS (Compact FCS)








*1: A segment is an engineering unit consisting of several Fieldbus devices and ACF11 to be connected to one H1Fieldbus.

SEE ALSO

For details of the ACF11 Fieldbus Communication Module of CENTUM CS 3000, refer to GS 33Q03L50-31E.


TI 38K03A01-01E

A4-6

Sep.01,2002-00

A4.1.3 Fieldbus Support in CENTUM CS 1000Fieldbus support in CENTUM CS 1000 is shown below. FCS can be connected via anACF11 Fieldbus Communication Module installed in an I/O module nest to FF transmittersand FF valve positioners.

VL net

HIS: Human Interface StationPRM: Plant Resource ManagerPFCS: Control StationACF11: Fieldbus Communication Module

ACF11

Externalpower supply

(optional)Intrinsic safety barrier /

arrester(optional)

Field devices

PFCS

A040103E.EPS

HIS

Ethernet

PRM



CouplerH1 Fieldbus

Coupler

Terminator

Figure Fieldbus Support in CENTUM CS 1000


TI 38K03A01-01E Sep.01,2002-00

ACF11 Fieldbus Communication Module Specifications of CENTUM CS1000

The main specifications of the ACF11 Fieldbus Communication Module of CENTUM CS1000 are shown below.









SEE ALSO

For details of the ACF11 Fieldbus Communication Module of CENTUM CS 1000, refer to GS 33S03L50-31E.


TI 38K03A01-01E

A4-8

Sep.01,2002-00

A4.1.4 Fieldbus Support in CENTUM CSFieldbus support in CENTUM CS is shown below. FCS can be connected via an ACF11Fieldbus Communication Module installed in an I/O module nest to FF transmitter and FFvalve positioners.

A040104E.EPS

V net

ICS: Information and Command StationACG: Communication Gateway UnitFCS: Field Control StationFCU: Field Control UnitRIO bus: Remote I/O busNIU: Node Interface UnitACF11: Fieldbus Communication Module

NIU

FCU

ACF11External

power supply (optional)

Intrinsic safety barrier / arrester (optional)

PC

FCS

Field devices

Ethernet

ACG

ICS EWS

RIO bus


CouplerH1 Fieldbus

Terminator

Coupler

Fieldbus tools• Engineering tool• Device Management tool

System generation function

Operation and monitoring function

Figure Fieldbus Support in CENTUM CS


TI 38K03A01-01E Sep.01,2002-00

ACF11 Fieldbus Communication Module Specifications of CENTUM CSThe main specifications of the ACF11 Fieldbus Communication Module of CENTUM CSare shown below.









SEE ALSO

For details of the ACF11 Fieldbus Communication Module of CENTUM CS, refer to GS 33G6K40-01E.


TI 38K03A01-01E

A4-10

Sep.01,2002-00

A4.2 Connection of FF Devices from Other Vendorsto Yokogawa’s CENTUM Control SystemsFF devices from other vendors can be connected to CENTUM under the following condi-tions:

Use devices registered by the Fieldbus Foundation

The Fieldbus Foundation prescribes the interoperability test procedure calledInteroperability Test (IT) to ensure interoperability between the FF devices. The FF devicesthat passed the IT are registered to the Foundation, and information about them is pub-lished on the Fieldbus Foundation’s web site (http://www.fieldbus.org/).

The field devices from other vendors, which are registered to Fieldbus Foundation, can beconnected to CENTUM. Yokogawa recommends to use the IT4.0 (or later version) registra-tion devices including the Capabilities File and Device Description (DD) File.

For the Fieldbus accessories (e.g. cables, external bus power supply units, barriers, andarresters), there is no system of registering to the Fieldbus Foundation; these accessoriesshould be used according to the conditions provided by their vendors.

Yokogawa informs users of field-proven Fieldbus accessories as recommended devices.Contact Yokogawa sales for the Fieldbus accessories if necessary.

Use devices as instructed

Use devices according to the conditions provided by their vendors. The vendors assumeresponsibility for the quality, performance and warranty of their field devices.

Test devices

A user who uses field devices from other vendors is responsible for testing them.

Yokogawa, if required, will provide assessment information on connecting other vendors’devices to CENTUM, to assist users in device selection.

Yokogawa supports only standard Fieldbus specifications, not manufac-turer-specific extensions

Yokogawa’s systems support information and functions that meet the standard specifica-tions prescribed by the Fieldbus Foundation. They may not support another manufacturer’sproprietary functions.

The Fieldbus standardization facilitates operation and maintenance of field devices fromdifferent manufacturers. Yokogawa can meet a variety of user needs, including startup andmaintenance work on process control systems including products (components) from othervendors, based on accumulated know-how about devices and their usage.

Toc B -1<Int> <Ind> <Rev>

TI 38K03A01-01E

Fieldbus Technical InformationPart B Fieldbus Engineering

CONTENTS

Sep.01,2002-00


B1. Managing Fieldbus Engineering .......................................................... B1-1B1.1 Fieldbus Engineering Process ..................................................................... B1-1

B1.2 Difference between Fieldbus and Analog Signal Process ControlSystems ......................................................................................................... B1-4

B1.3 Software Packages for Fieldbus .................................................................. B1-5

B2. System Design Considerations ........................................................... B2-1B2.1 Considerations in Basic and Overall Design............................................... B2-2

B2.2 Detail Design Considerations ...................................................................... B2-3

B2.2.1 Investigation of Number of Field Devices connected toan H1 Segment ............................................................................... B2-4

B2.2.2 Selection of Fieldbus Cable and Wiring Method .............................. B2-5

B2.2.3 Design of FF Device Grouping per Segment ................................... B2-8

B2.2.4 Expansion and Modification of Existing System .............................. B2-8

B3. System Construction Considerations ................................................. B3-1B3.1 New Construction of Fieldbus Process Control System ............................ B3-1

B3.1.1 Mounting Terminators ..................................................................... B3-3

B3.1.2 Mounting Couplers ......................................................................... B3-3

B3.1.3 Cabling ........................................................................................... B3-4

B3.1.4 Installing an Intrinsic Safety Barrier ................................................. B3-4

B3.1.5 Handling the Shield Mesh ............................................................... B3-4

B3.1.6 Connecting the Fieldbus Cable and Handling the Shield Mesh forFieldbus Communication Module .................................................... B3-4

B3.2 Reusing Existing Cables .............................................................................. B3-5

B4. System Startup Considerations ........................................................... B4-1B4.1 Tool Necessary for Startup ........................................................................... B4-1

B4.2 Technologies and Expertise Necessary for Startup ................................... B4-2

B4.3 Labor Savings in Startup Work .................................................................... B4-3

B5. System Maintenance Considerations .................................................. B5-1B5.1 Daily Maintenance......................................................................................... B5-1

B5.2 Inspection and Maintenance ........................................................................ B5-2

B5.3 Maintenance Management (Maintenance Plan, Device Management,Audit Trail) ..................................................................................................... B5-3

B5.4 Evolution of Maintenance ............................................................................. B5-3

Blank Page

<B1. Managing Fieldbus Engineering> B1-1

TI 38K03A01-01E Sep.01,2002-00

B1. Managing Fieldbus EngineeringIn a process control system that uses Fieldbus, the engineering process differs fromthat of a process control system that uses conventional analog signals. This sectionexplains the engineering process in a process control system using the H1 (31.25kbps) Fieldbus.

B1.1 Fieldbus Engineering ProcessThe engineering of a process control system that employs Fieldbus is divided into fivesteps: design, production, construction, startup, and maintenance. Each step has multipletask processes and each task process includes detailed task items.

The example of engineering process for the process control system using Fieldbus tech-nology is shown below.

START

Basic design

Overall design

Detail design

Hardware production

Witness inspection

Shipping

Delivery

Acceptance inspection

Installation work

Unit startup

Production

Witness inspection

Shipping

Delivery

Acceptance inspection

Installation work

Unit startup

FF parameterconfirmation

System startup

Trial operation

Plant operation

System Field devices

Startup

Design

Production

Construction

Maintenance

Performed by contractor,system integrator or user.

Maintenance

Software production

B010101E.EPS

Figure Example of Engineering Process Using Fieldbus

<B1. Managing Fieldbus Engineering>

TI 38K03A01-01E

B1-2

Sep.01,2002-00

DesignThe specifications of the process control system are verified by completing the basicdesign, overall design, and detail design for the system.

SEE ALSO

For detailed information about designing the process control system using Fieldbus, refer to Section B2,“System Design Considerations.”

ProductionAccording to the specifications that are confirmed in the design process, the system andfield devices are produced. Production work is completely performed by Yokogawa. Noother work needs to be performed by the user.

ConstructionThe manufactured system and field devices are delivered to the user’s site. Then, accord-ing to the system layout that has been clarified in the design step, wiring such as Fieldbuscabling is installed.

Acceptance inspection is performed for the field devices before installation. The processcontrol system using Fieldbus needs to be closely inspected. The following items requireespecially close inspection.

• Parameter settings (PD tag names (*1), node addresses (*1)) required for Fieldbuscommunication

• Parameter settings specific to field devices

After inspection, the system is installed in the control room, and field devices in the field.The system and field devices are connected to the Fieldbus.

*1: For “PD tag name” and “node address”, refer to Section C1.1 “Glossary.”

SEE ALSO

For detailed information about constructing a process control system using Fieldbus, refer to Section B3,“System Construction Considerations.”


TI 38K03A01-01E Sep.01,2002-00

StartupIn the startup step, unit startup, system startup and the trial operation are performed.

Startup (Unit and System)

The following checks are required.

• Unit identification for all field devices

• Confirmation of data input/output between system and field devices(The input/output definition on the system side must be completed by this time.)

• Adjustment of various control constants and parameters of FF devices by devicemanagement package on a system computerThese parameters are for the built-in function blocks in field devices and for thefunction blocks managed by control function in a system computer.

Trial Operation

This includes adjustment of control parameters such as P, I, D constants of the built-in PIDfunction blocks in FF devices.

SEE ALSO

For detailed information about starting up the process control system using Fieldbus, refer to Section B4,“System Startup Considerations.”

MaintenanceDuring plant operation, the field device status is managed using a device managementfunction which is supported by the Plant Asset Management (PAM) system such asYokogawa’s Plant Resource Manager (PRM – see Part C “Overview of Plant ResourceManager”) from the control room or maintenance room.

Also, error generation is monitored using the self-diagnostics function of field devices if thefield device has such a self-diagnostics function.

With maintenance work, parameters can be confirmed by directly connecting field devicemanagement tools to field devices or by a field device management function on PAMsystem. The communication status can be checked by directly connecting the FieldbusMonitor (*1) to Fieldbus.

Some field devices may have a maintenance record function of their own. The mainte-nance record data on the field device is uploaded and managed them into the PAM system.

*1: Yokogawa recommends “NI-FBUS Monitor Package” from National Instruments Co. as Fieldbus Monitor.Contact National Instruments Co. (http://www.ni.com/).

SEE ALSO

For detailed information about maintaining the process control system using Fieldbus, refer to SectionB5, “System Maintenance Considerations.”


TI 38K03A01-01E

B1-4

Sep.01,2002-00

B1.2 Difference between Fieldbus and Analog SignalProcess Control SystemsProcess control systems using Fieldbus differ greatly from those using a conventionalanalog signal, in that the parameters for Fieldbus configuration definitions also need to beset.

Setting Parameters Specific to Field DevicesVarious FF block parameters for field devices must be set up.

The following main parameters for FF function block (FFB) must be set:

• Range parameters (XD_scale, OUT_scale and engineering unit for each scale)

• Compensation parameters (Direct, Indirect, Indirect Sqr Root)

• Input filter process parameters (PV_FTIME)

Setting Parameters for Fieldbus Communication and Its FunctionsNew parameters for Fieldbus communication and its functions have been added.

The following main parameters must be set:

• PD tag name (*1)

• Node address (*1)

• FF function block definition

• Link information (connecting block, output parameter, etc.)

*1: For “PD tag name” and “node address”, refer to Section C1.1 “Glossary.”


TI 38K03A01-01E Sep.01,2002-00

B1.3 Software Packages for FieldbusYokogawa offers various packages that support engineering and maintenance for Fieldbusprocess control systems.

Fieldbus Package TypesYokogawa offers the following types of packages for Fieldbus depending on the conditionsof use.

• Fieldbus package type for desktop PC: Fieldbus engineering and maintenance pack-ages for field devices in the central control room

• Fieldbus package type for portable PC: Field device maintenance package in the fieldsite.

An example of use of Fieldbus package types is shown below.

In practice, these packages can be run on the same PC.

B010301E.EPS

Fieldbus monitor

FF-H1 support tool (includes device management

tool function and device tool function)

Field device

Field device

Ethernet

V net

H1 Fieldbus

Supply air

HISHIS for builder (includes Fieldbus engineering function)

Remark

Desktop typeFieldbus package

Portable typeFieldbus package

Plant Resource Manager (PRM)

FCS

Figure Example of Use of Fieldbus Package Types


TI 38K03A01-01E

B1-6

Sep.01,2002-00

Fieldbus Engineering and Field Device Maintenance in Central Control Room

The Fieldbus package for desktop PC is designed for Fieldbus engineering and field devicemaintenance work in the central control room.

• Fieldbus engineering in integration with the systemThis package, which is added to conventional system configuration function, registersdevices to Fieldbus segments and links FF function blocks. The Device ManagementTool (DMT) or Plant Resource Manager (PRM) also executes remote parametersetting (tuning), and remote diagnosis of field devices.

• Parameter setting and tuning, and diagnosis for the field devicesDMT or PRM executes remote parameter setting and diagnosis for field devices.

Field Device Maintenance in the Field

The Fieldbus package for portable PC is designed for tuning Fieldbus devices in the field.

The FF-H1 support tool is installed in a portable PC (such as notebook PC), which isconnected to Fieldbus to monitor the statuses of field devices. It is also used to tune pa-rameters and check operation of field devices before actual plant operation.

<B2. System Design Considerations> B2-1

TI 38K03A01-01E Sep.01,2002-00

B2. System Design ConsiderationsWhen designing a process control system that uses the Fieldbus communicationprotocol, it is necessary to thoroughly understand the design considerations,including Fieldbus. This section describes the design considerations of a processcontrol system that employs Fieldbus technology.

Importance of Process Control System DesignTo design a process control system, the design procedure should follow these steps:

• Basic design

• Overall design for common specifications

• Detail design for individual components

First perform the basic design, then the overall design for the specified system. If the basicand overall design have not been completed, inconsistencies with specifications may occurand require returning to an earlier step. The more sophisticated the process control systembecomes, the more important the basic and overall design will be.

During the detail design, the individual components to be designed are identified on thebasis of the basic and overall design.

Designing Process Control Systems with Fieldbus TechnologyIn designing Fieldbus process control systems, more items need to be considered than forsystems using conventional analog signals.

However, this does not mean that it is difficult to design Fieldbus process control systems.Although Fieldbus-related items need to be added to the design items of conventionalprocess control systems, a conventional design method can be used.

<B2. System Design Considerations>

TI 38K03A01-01E

B2-2

Sep.01,2002-00

B2.1 Considerations in Basic and Overall DesignDuring the basic design of a process control system that uses Fieldbus, it is necessary toproperly consider the purpose of the system and its construction costs. Also, in the overalldesign, the process control system configuration and the integrating or grouping range andextent must be carefully considered.

Basic Design ConsiderationsDuring the basic design of a process control system that uses Fieldbus, the following mustbe taken into consideration.

• Purpose of the process control system

• Cost of system implementation (total estimation including the construction cost)

• Delivery period of the system implementation

• Safety concept

• Operation procedure

• Maintenance procedure

Overall Design ConsiderationsDuring the overall design of the process control system that uses Fieldbus, includingcommon specifications, take the following into consideration.

• Configuration of the process control system (hardware and software configuration)

• Integrating or grouping range and scope

• Safety design and reliability design

• Measures under abnormal situations

• Interface design

• Future expansion


TI 38K03A01-01E Sep.01,2002-00

B2.2 Detail Design ConsiderationsIn detail design, the contents of the basic design and overall design are realized. Thissection describes major considerations in designing individual components.

In detail design, the considerations for limit and restriction items depending on cable length,power supply capacity and so forth are also important.

There are also many items to be considered other than those described here.

Integrating or Grouping Range and Scope• Integration of buses between the process control system and other systems

• Consistency of operation types between the process control system and other sys-tems

• System integration through upper-level communication and lower-level communica-tion

• Connectable number of field devices and their grouping

• Clarification of hardware and software configuration with system configuration draw-ings

Safety Design and Reliability Improving Design• Selecting devices and construction in hazardous area (power supply method for

intrinsic safety devices)

• Assignment of Fieldbus I/O and conventional I/O for the system functionalityFor example, the emergency shutdown system should be assigned to the conven-tional analog control system.

• Selection of type of cables, field devices, and redundancy of FF power supply unit andFieldbus interface module

• Fail-safe design, safety measurements using diagnostics technologies, and equip-ment diagnostics design

• Selection of noise resistant devices and wiring route to minimize noise (affected byhigh voltage or motors)

• Selection of fieldbus accessories such as FF power supply unit, terminator, barrierand arrester

• Design of a Link Master (LM) device with Link Active Scheduler (LAS) capability andbackup LM devices with LAS capability.


TI 38K03A01-01E

B2-4

Sep.01,2002-00

B2.2.1 Investigation of Number of Field Devices connected to anH1 SegmentThe number of field devices that can be connected to an H1 segment is restricted by thepower supply current capacity of the segment, macrocycle corresponding to the controlperiod, and Fieldbus cable length. For details of the restriction by Fieldbus cable length,refer to Section B2.2.2, “Selection of Fieldbus Cable and Wiring Method.”

Restriction by Power Supply Current CapacityThe sum of the current consumption of field devices connected to one Fieldbus segmentcannot exceed the current supply capacity of the power supply.

In an intrinsic safety system, the sum of the current consumption of field devices connectedto one Fieldbus segment can not exceed the current supply capacity of the power supply orlimitation value of the safety barrier unit.

Restriction by Macrocycle Corresponding to Control PeriodThe number of field devices that can be connected to an H1 segment should be decided bythe macrocycle corresponding to the control period.

A macrocycle is the period of the control or measurement and the unit is 1/32 ms (1 sec =32000 units). The scheduled control and communication on macrocycle is executed by theLM device with LAS capability.


TI 38K03A01-01E Sep.01,2002-00

B2.2.2 Selection of Fieldbus Cable and Wiring MethodData on several types of cables are given below for reference only. Yokogawa recom-mends using Type A cable.

The Fieldbus cable specifications are important in Fieldbus system design. The voltagedrop restrictions of Fieldbus should also be considered.

Yokogawa investigates Fieldbus cable specifications in various aspects. Use the datadescribed in this manual for reference only.

Consideration of Voltage Drop RestrictionsThe voltage drop limits are set so that the minimum output voltage of the power supply, lessthe voltage drop in the cable resistance, is not less that the minimum operating voltage ofthe device, even considering the voltage fluctuation. Yokogawa recommends minimum 9.5volts as operating voltage design.

Cable Type and its Resistance

The typical resistances per unit length of the various cable types that can be used forFieldbus are shown below. The following resistance values are for reference only. For actualvalues, contact the cable manufacturer.

Type A (individually shielded twisted-pair cable): 22 ohm/km

Type B (multi-pair twisted-pair cable, with outer shield): 56 ohm/km

Type D (multi-pair cable, no twist, with outer shield): 20 ohm/km

The following general formula is used to check whether the minimum supply voltage issecured.

Minimum Power Supply Voltage � (resistance per unit length � cable length) � device current � minimum operating voltage

This calculation must be performed for each Fieldbus device.

Selection of Wiring CablesConsider noise, cost, flexibility, and explosion-proof.

Insulating Material of Twisted Pair CableThe insulating material such as polyethylene is appropriate.

Selection of Bus Topology and Maximum Number of FF Devices perSegment

Consider the bus topology, such as serial link and tree link, and maximum number ofdevices per segment.


TI 38K03A01-01E

B2-6

Sep.01,2002-00

Selection of Cable Type and Total LengthIf using a twisted-pair cable for the main line, carefully consider the kind and total length ofcabling.

The total length of cabling for Fieldbus is as follows:

• Type A (Individually-shielded twisted pair cable) 1900 m

• Type B (Overall-shielded twisted pair cable) 1200 m

• Type D (Overall-shielded non-twisted cable) 200 m

Some Type B cables attenuate signals largely. To secure sufficient signal amplitude, nomore than 20 field devices must be connected with a maximum total cable length of 600 m,or no more than 10 field devices must be connected with a maximum total cable length of1,200 m.

When using Type D cables, up to two pairs of cables must be used for Fieldbus and eachpair must be separated from each other to prevent interference.

When using multi-core cables, do not send signals other than Fieldbus signals or analogsignals (including hybrid communication) through the same cable.


TI 38K03A01-01E

Number of Branch Cables and Total LengthIn tree type wiring, carefully consider the total length of cabling in accordance with thenumber of spur (branch) cables (number of field devices to be connected).

The typical maximum total lengths of spur cables shown in the IEC and ISA standard (*1)are given below.

• 1-12 field devices connected: 120 m





The number of connected field devices may be restricted by power supplies, communica-tion performance and other conditions.

In principle, the total lengths of spur cables should be made less than the typical maximumlengths shown above. However, in some applications these maximum lengths are ex-ceeded, so Yokogawa was requested to assess whether this is viable. Considering thatthose typical lengths shown in IEC and ISA standard are recommended ones, Yokogawahas assessed the lengths and obtained the following result.

Assuming that Yokogawa CENTUM is used as Fieldbus host system, the spur cablelengths can be increased under the following conditions.

• Use of Fieldbus Type A cable

• Number of field devices connected to a segment:max. 16 devices (Yokogawa understandsthe number of devices per segment isactually 16 or less.)

• Maximum length of spur cable: 120 m

• Maximum total length of spur cable: 960 m

• Maximum length of trunk cable: 1900 m - total length of spur cable

There is no restriction on the number of junction boxes used to connect field devices viaspur cables.

*1: The typical maximum total lengths of spur cables are shown in the standard IEC61158-2 and ISA - S50.02Annex C (informative).

Sep.01,2002-00


TI 38K03A01-01E

B2-8

B2.2.3 Design of FF Device Grouping per Segment• Assess the communication and control performance considering transmission speed,

control period, communication period and number of communication items betweenfield devices and system computer.

• Arrangement of information type and quantity (essential, expected, and convenientinformation)

• Future expansion (Consider the installation of spare wiring and devices.)

B2.2.4 Expansion and Modification of Existing System• Clarification of the purpose and extent of expansion, investigation of influence on the

existing system, and merit of system construction

• Tentative feasibility study for introduction of Fieldbus

• Design of interface with existing devices (analog/digital conversion)

• Investigation of the usability of existing wiring

TIP

Fieldbus is still being introduced. Therefore, in designing a process control system that uses Fieldbus,consider the following in addition to usual design considerations.

• Field operation records of each system and field device

• Effect to process control caused by a segment (bus) fail

• Specifications of wiring cables

Sep.01,2002-00

<B3. System Construction Considerations> B3-1

TI 38K03A01-01E Sep.01,2002-00

B3. System Construction ConsiderationsWhen designing a process control system that uses Fieldbus, it is necessary tothoroughly understand construction considerations for Fieldbus. This sectiondescribes considerations in constructing a process control system that employsFieldbus.

B3.1 New Construction of Fieldbus Process ControlSystemFor wiring a process control system that uses Fieldbus, new construction examples oftypical system wiring configurations “serial link type” and “tree type” are explained below.

Example of Serial Link Type WiringIn serial link type wiring construction, the power supply and system are installed in thecontrol room. A Fieldbus segment is installed from the Fieldbus Communication Module(ALF111 or ACF11), which is connected to the system, and goes out to a number of fielddevices. Various types of field device may be connected to this Fieldbus.

A terminator is also connected to both ends of the segment. A terminator at the field sidemay be mounted at the end of a bus cable in the field junction box.

An example of serial link type wiring is shown below.

B030101E.EPS

Intrinsicsafety barrier/arrester

(optional)

External power supply

Field device

Required if the terminator is not installed in the ALF111.

FCU: Field Control UnitNU: Node unit for FIOALF111: Fieldbus communication module

Intrinsic safety barrier: Required only if intrinsically safe construction is required.Arrester: Required for measure against lightning

FCU

NU

ALF111FCU

Coupler


Coupler

Field junction box

Terminator

H1 Fieldbus

Figure Example of Serial Link Type Wiring

<B3. System Construction Considerations>

TI 38K03A01-01E

B3-2

Sep.01,2002-00

Example of Tree Type WiringIn tree type wiring construction, various types of field device are connected to Fieldbussegment via the field junction box. This wiring topology is applied generally. In this case, thelength of brunch cable should be considered. A terminator at the field side is mounted onthe end of a truck cable in the field junction box.

SEE ALSO

The maximum length of cables in tree type wiring is the same as that in serial link type. For details, referto Section B2.2.2, “Selection of Fieldbus Cable and Wiring Method.”

B030102E.EPS

External power supply

Field deviceRequired if the terminator is not installed in the ALF111.

Intrinsic safety barrier: Required only if intrinsically safe construction is required.Arrester: Required for measure against lightning


FCU

NU

ALF111FCU

Terminator

Field junction box

Intrinsic safetybarrier/arrester

(optional)

Terminator(optional) H1 Fieldbus

Coupler

Coupler

Branch cable

Figure Example of Tree Type Wiring


TI 38K03A01-01E Sep.01,2002-00

B3.1.1 Mounting TerminatorsTerminators must always be mounted on both ends of a trunk cable. Various types ofterminator such as a field device built-in type and a stand-alone type are marketed bydifferent manufacturers.

Install terminators in a pull box or a field junction box to improve resistance and preventmechanical shock, or use the field device built-in type.

B030103E.EPS

Instrument room side

Field device side

Conduit

Fieldbus cable

TerminatorShielded wireRun the wire through a field junction box and isolate it from the box.(Do not connect to the FG.)Field junction box

Coupler

Figure Mounting Terminator in Field Junction Box

B3.1.2 Mounting CouplersEach field device is connected to Fieldbus via a coupler and branch cables. To preventmechanical shock, a coupler is mounted inside a pull box or a field junction box.

B030104E.EPS

Branch cable

Coupler

Branch cable

Fieldbus main line cable

Conduit

Pull box

Figure Mounting Couplers


TI 38K03A01-01E

B3-4

Sep.01,2002-00

B3.1.3 CablingTo protect the Fieldbus cable, use standard conduits. If the Fieldbus cable is stored in thecable rack or wiring duct, separate the cable as far from the other cable as possible, thesame as when installing low-level signal cables.

SEE ALSO

For more information, refer to Section 1.6, “Cabling Requirements” in “CENTUM CS 3000 InstallationGuide (TI 33Q01J10-01E).”

B3.1.4 Installing an Intrinsic Safety BarrierIf intrinsically safe application is required, install an intrinsic safety barrier at the closestplace to the field in the rack room. The cables in the non-hazardous area and hazardousarea must be wired separately.

Note that the intrinsic safety barrier attenuates signals.

Recently new intrinsically safe products for Fieldbus are marketed, however, they are notintroduced here.

B3.1.5 Handling the Shield MeshIf using a shielded cable, consider the following when handling the shield mesh.

• Connection of shield mesh at the coupler

• Grounding location and number of grounds

As a rule, the shielded Fieldbus cable must be grounded at one point in the building in therack room.

B3.1.6 Connecting the Fieldbus Cable and Handling the ShieldMesh for Fieldbus Communication ModuleFor connecting the Fieldbus cables and handling the shield meshes for the ALF111Fieldbus Communication Module, refer to Section 3.6.4 “Inplementation and Cable Con-nection of Fieldbus Communication Module ALF111” in “CENTUM CS 3000 InstallationGuidance (TI 33Q01J10-01E)” , or Section B3.5.4 in “Input & Output Modules (IM33YO6K01-01E).”

For connecting the Fieldbus cable and handling the shield mesh for the ACF11 FieldbusCommunication Module, refer to Section 3.7.9 “Connecting the Fieldbus Cable and Han-dling the Shield Mesh for Fieldbus Communication Module ACF11” in “CENTUM CS 3000Installation Guidance (TI 33Q01J10-01E)”, or Section A4.3.3 in “Input & Output Modules(IM 33YO6K01-01E).”


TI 38K03A01-01E Sep.01,2002-00

B3.2 Reusing Existing CablesIf the cables of the existing process control systems are reused, examine the existing cableto be reused for the Fieldbus digital communication. Also, check the existing cables forinsulation deterioration and fatigue.

Here, the reuse of existing cables is explained using a typical example of a process controlsystem in an oil refinery plant or petrochemical plant.

In an oil refinery or a petrochemical plant, the cables equivalent to the overall-shieldeduntwisted 2-core cable CVVS-1.25 mm2 have been installed since explosion-proof con-struction was required. Also, from the field junction box to the Fieldbus CommunicationModule (ALF111 or ACF11), the cables equivalent to the overall-shielded non-twisted multi-core cable CVVS-1.25 mm2 have been installed. An example of existing cables in an oilrefinery or a petrochemical plant is shown below.

Multi-core cableField junction box

Field device Field device

B030201E.EPS


FCU

NU

ALF111FCU

Cable equivalent toCVVS-1.25mm2-2C

Figure Example of Fieldbus Segment Configuration Using Existing Wiring


TI 38K03A01-01E

B3-6

Sep.01,2002-00

Reusing the Cables from Field Devices to Field Junction BoxMost of the existing cables (spur (branch) cables), from field devices to the field junctionbox, use the overall-shielded non-twisted 2-core cable CVVS-1.25 mm2. In this case themaximum cable length depends on the type of cable and the number of field devicesconnected.

The following tables list the types of cables and specifications and the maximum length ofspur (branch) cables according to the number of devices on the Fieldbus, respectively.

Table Types of Cables (Reference value)

Types of cables Cable size Max. length of cable

B030202E.EPS

Type A (Individually shielded twisted pair cable) 0.82 mm2

0.32 mm2

1.25 mm2

1,900 m

Type B (Overall-shielded twisted pair cable) 1,200 m

Type D (Overall-shielded non-twisted cable) 200 m

Table Maximum Length of Spur Cables (Reference value)

Number of devices on Fieldbus Max. length (total) of branch cables

B030202E.EPS

1 to 12

15 to 18

19 to 24

25 to 32

120 m

13 to 14 90 m

60 m

30 m

0 m

SEE ALSO

For cable types and spur (branch) cables, refer to Section B2.2.2, “Selection of Fieldbus Cable andWiring Method.”

Reusing the Cables from Field Junction Box to Control RoomMost of the existing cables (trunk (main line) cables), from the field junction box to thecontrol room (relay terminal board), use the overall-shielded non-twisted multi-core cableCVVS-1.25 mm2. Up to the maximum length of cable listed in the table, “Types of Cables(Reference value)” can be reused.

This cable can be used for Fieldbus because noise interference due to cross talk is usuallywithin the permissible range.

If multiple types of cables are connected, the maximum length of each cable is shorter thanthat in the table, “Types of Cables (Reference value).”

<B4. System Startup Considerations> B4-1

TI 38K03A01-01E Sep.01,2002-00

B4. System Startup ConsiderationsBefore starting up a Fieldbus control system, it is necessary to thoroughlyunderstand all aspects concerning system startup. This section describes the toolsand technologies required for starting up the Fieldbus system, and the differencesin the startup processes between Fieldbus system and conventional analog system.

B4.1 Tool Necessary for StartupFor startup of a Fieldbus control system, use tools that are different from those of aconventional analog system. This section describes a variety of tools required to start upthe system.

Instrument of Digital Signal MeasurementTo start up Fieldbus control system, the instruments for digital signal measurement arerequired.

These digital signal instruments are connected to field devices or Fieldbus interface mod-ules, and which check digital signals. As digital measuring instruments, the digital multim-eter, digital oscilloscope, and Fieldbus testers (*1) from Relcom Inc. are used to checkrelated network communication items such as the current, volts, LAS status, number ofconnected devices, signal level and noise level etc.

*1: Yokogawa recommends “Fieldbus Network Testers (FBT-3 etc.)” from Relcom Inc. as Fieldbus testers. ContactRelcom Inc. (http://www.relcominc.com/).

Fieldbus MonitorFor starting up a process control system that uses the Fieldbus communication protocol, aFieldbus Monitor (*1) is necessary for measuring signal data on the Fieldbus. The FieldbusMonitor is equipped with a troubleshooting function which can track down the source of acommunication problem between devices connected to segment.

*1: Yokogawa recommends “NI-FBUS Monitor Package” from National Instruments Co. as Fieldbus Monitor.Contact National Instruments Co. (http://www.ni.com/).

Field Device Maintenance ToolFor startup of a Fieldbus system, a field device maintenance tool for parameter setting(especially remote setup) to field devices is required.

This maintenance tool is built into a desktop or portable PC.

<B4. System Startup Considerations>

TI 38K03A01-01E

B4-2

Sep.01,2002-00

B4.2 Technologies and Expertise Necessary forStartupTo start up a Fieldbus control system, technologies and expertise that are different fromthose for a conventional analog system are required. This section describes thetechnologies and expertise required to start up a Fieldbus system.

Wiring TechnologyWiring is greatly changed by using Fieldbus. One of the main advantages of Fieldbus isthat it minimizes wiring. However, greater care is required in the termination of communica-tion cables. Since many signals are handled on a Fieldbus cable, wiring problems willgreatly affect the system. It is therefore necessary to carefully check whether wiring com-plies with communication-cable and field-device specifications including communicationtransmission quality.

Technology for Field DevicesAlthough measuring methods (measuring principles) for pressure and flow rate are notdifferent from that of a conventional transmitter, output signals from sensors are digitized,making field devices easier to handle.

Remote maintenance by the field device maintenance tool saves labor in field device signalprocessing, such as operation checks, device adjustment, setting modifications, and datamaintenance management.

Knowledge of System SoftwareFieldbus is a communication system. Therefore, startup engineers must have knowledgeabout communication software setup, communication protocol, etc.

Knowledge of Application SoftwareIn a Fieldbus control system, there are the following three control methods:

• All control is performed on the field device side, and only monitoring is performed onthe system side.

• All control signals are transmitted to the system, and control is performed on thesystem side.

• A combination of the above two methods allows the best control for specificapplications.

These control methods promote distributed control more than conventional control systemswhere all control is performed on the system side. For example, by assigning simple controlto field devices, the system can perform higher-level control (such as multivariable controland advanced control). Startup engineers must have knowledge about advanced control.Because of distributed control, a system will be closer to a control computer, therefore thestartup engineers are also required to have knowledge about information processing inaddition to conventional control and instrumentation.


TI 38K03A01-01E Sep.01,2002-00

B4.3 Labor Savings in Startup WorkIn the startup of a process control system that uses Fieldbus, labor savings can beachieved in some processes, unlike in a conventional analog system. This sectiondescribes the processes in which labor savings can be achieved.

Loop Check

Loop Check of Process Control System That Uses a Conventional AnalogSignal

Usually two types of loop check were conducted: indoor loop check and total loop check.

In the indoor loop check, the loop from the marshalling rack to the process control systemis tested to check for incorrect indoor wiring and poor signal quality. In the total loop check,a loop check is performed to check for incorrect wiring and poor signal quality between afield device and the process control system. Troubleshooting in the total loop check ismade easier by performing the indoor loop check.

This procedure, however, requires many man-hours since these checks must be per-formed on all loops.

<B4. System Startup Considerations>

TI 38K03A01-01E

B4-4

Sep.01,2002-00

Loop Check of Process Control System That Uses Fieldbus

In a loop check of a process control system that uses Fieldbus, man-hours can be saved inthe following ways, as compared with a conventional system.

There is no need to check twice, indoor loop check and total loop check, as describedabove.

If Fieldbus is connected from field devices directly to the system, only the total loop check isrequired. In this total loop check, a digital signal oscillator can be connected to a field deviceto pass signals from the field device to Fieldbus. Since the check can be performed withoutdisconnecting any wiring, a more reliable check will be ensured.

High accuracy and high stability of transmitters are guaranteed thanks to digitization, anddeterioration of accuracy in transmission need not be considered. If the operation ofdevices has been confirmed through the single unit test after the assembling or bench test,there is no need for actual environment tests by applying pressure or connecting a resistorwith an equivalent temperature.

For conventional analog devices, output signal checks of three or five points are necessary.However, the FF devices suffer no accuracy deterioration in transmission, so the outputsignal check need be performed at only one point if the instrument range is correct. Inthese ways, the time spent on loop checks can be reduced.

B040301E.EPS

Operator station

Control unit Control unit

Standard current/voltage generatorDigitalMultimeter

Indoor loopcheck

Marshallingrack

CPU

Total loopcheck

Operationstation

Field controldevice

Computer

Digital signalgenerator

Total loopcheck

Field junction boxField junction box

Field junction box

Past Future

Marshallingrack


FCU

NU

ALF111FCU

Fieldbus

Figure Loop Check of Process Control System That Uses Fieldbus Communication


TI 38K03A01-01E Sep.01,2002-00

Interlock CheckDuring the interlock check, various plant functions are checked. The functions to bechecked include that for production itself in the plant, and that for maintaining plant safety,etc.

To perform this check, not only is system software modification frequently required, but soare modifications to the relay board and other parts. In a conventional analog transmissionsystem, actual wiring modifications and software modifications were required in about halfof all cases.

In a process control system using Fieldbus, interlock processing can be independentlyimplemented on the field device side. By combining the interlock function of the system, thischeck can be performed by modifying software.

Therefore, the cost and period required for modifying the conventional hardware will beeliminated.

Trial OperationControl tuning parameters including the P, I, D constants of local Fieldbus PID functionblock are adjusted. The advanced diagnostic applications utilizing Fieldbus parametersalso may be added at this phase.

Since Yokogawa has an advanced operation package for start-up and shutdown, it will beused to reduce the time for start-up.

Range Free DevicesThis system uses the actual digital measurement without regard to the “percent of span” or“percent of full scale.”

Blank Page

<B5. System Maintenance Considerations> B5-1

TI 38K03A01-01E Sep.01,2002-00

B5. System Maintenance ConsiderationsSince a process control system that uses Fieldbus is provided with numeroussystem maintenance functions that are superior to those of systems with an analogsignal, labor savings and more efficient maintenance of field devices will bepossible.

This section explains the difference between the maintenance work of processcontrol systems that use Fieldbus and that of conventional systems.

B5.1 Daily MaintenanceIn a process control system that uses Fieldbus, daily maintenance can be performed moreefficiently than in an analog control system.

Daily Field InspectionIn a process control system that uses a conventional analog signal, inspections of the fieldare made by operators at given times to check the operation status of field devices and torecord changes in the installation environments. Daily inspection is performed to detectabnormal states and maintain stable operation of the system.

In a process control system that uses Fieldbus, the type and amount of information to beacquired will increase drastically due to bidirectional digital communication and the multi-sensing function. This allows operators to perform remote monitoring and remoteoperation-status management from the control room, greatly reducing the operators’ dailyinspection workload.

Maintenance during System OperationIn a process control system that uses conventional analog signals, daily maintenance workduring system operation (such as check for zero-point of field devices, check for devicestatus, and parameter adjustment) must be performed in the field.

In a process control system that uses Fieldbus, maintenance work can be performedremotely from the control room. The daily maintenance information can be acquired inrealtime using the self-diagnostics function and bidirectional digital communication functionof field devices. Therefore, daily maintenance information will be effectively used to deter-mine which items require maintenance during the inspection activity.

<B5. System Maintenance Considerations>

TI 38K03A01-01E

B5-2

Sep.01,2002-00

B5.2 Inspection and MaintenanceIn a process control system that uses Fieldbus, periodic inspection and maintenance will beperformed more effectively than in a system that uses analog signals.

Function and Accuracy CheckDue to technological progress and the introduction of Fieldbus, which offers high accuracy,high stability, improved reliability, and improved maintenance of field devices, there are thefollowing advantages.

Maintainability Improvement by Remote Operation

In a process control system that uses Fieldbus, range setup and zero adjustment of fielddevices can made remotely, thus improving maintainability. Also, device management worksuch as field device master file creation is automated.

Disassembly and Consumables ReplacementIn a process control system that uses Fieldbus, instrumentation equipment can bemaintained and replaced using CBM in addition to TBM, due to the improved device statusmonitoring function and diagnostics function.

Time-Based Maintenance (TBM)

This is a method for maintaining/replacing based upon all devices every periodic cycle,which is determined based on the shutdown cycle of a plant or a system, according toregulations and the service life of devices.

Condition-Based Maintenance (CBM)

This is a method for maintaining/replacing based upon individual devices according to thestatus of each device by monitoring the device status. It is also referred to as statusmonitoring maintenance.

In conventional time-based maintenance, maintenance/replacement is usually performedin shorter cycles than the device life to avoid damage. Therefore, a device with no problemmay be disassembled for maintenance or replaced.

In a process control system that uses Fieldbus, sufficient maintenance/replacement isperformed according to the status of each device. This reduces extra costs caused by toomuch maintenance being performed.

<B5. System Maintenance Considerations> B5-3

TI 38K03A01-01E Sep.01,2002-00

B5.3 Maintenance Management (Maintenance Plan,Device Management, Audit Trail)In a process control system that uses Fieldbus, device status information such as the PDtag name, serial number, internal parameters, maintenance record, and self-diagnosticsresults can be acquired in real-time from each field device. If that information is stored inthe maintenance database of device management tools, it is possible to perform devicemanagement of all field devices and to continually monitor the status of field devices.

This allows the users to perform preventive maintenance with respect to each field devicestatus and to determine the periodic maintenance plan based on maintenance data.

B5.4 Evolution of MaintenanceWith the introduction and acceptance of Fieldbus, a variety of maintenance supportsystems have been developed using Fieldbus features such as bidirectional digitalcommunication, multi-sensing, multifunction, bidirectional communication between fielddevices, and interoperability. These systems have contributed to the productivity increases,safety improvements, and maintainability improvements expected by users.

Yokogawa provides the Plant Resource Manager (PRM) software package, which isexplained in Part C, for managing plant assets in the field network era.

Blank Page

Toc C -1<Int> <Ind> <Rev>

TI 38K03A01-01E

Fieldbus Technical InformationPart C Overview of Plant Resource Manager (PRM)

CONTENTS

Sep.01,2002-00


C1. Overview of Plant Resource Manager (PRM) ...................................... C1-1C1.1 Glossary ........................................................................................................ C1-2

C1.2 PRM Software Configuration........................................................................ C1-4

C1.3 PRM Positioning ........................................................................................... C1-6

C1.4 Devices Managed by PRM ............................................................................ C1-7

C2. PRM System Configuration .................................................................. C2-1C2.1 System Configuration when Connecting

FOUNDATION Fieldbus (FF-H1) ................................................................... C2-2

C2.2 System Configuration when Connecting HART .......................................... C2-4

C3. Overview of PRM Functions ................................................................. C3-1C3.1 PRM System Size .......................................................................................... C3-1

C3.2 Overview of PRM Functions ......................................................................... C3-2

C3.2.1 Device Navigator ............................................................................ C3-3

C3.2.2 Maintenance Information Management ........................................... C3-5

C3.2.3 Audit Trail Function ......................................................................... C3-5

C3.2.4 Tuning and Diagnosis Functions ..................................................... C3-6

C3.2.5 Utilities ............................................................................................ C3-7

C3.3 PRM Supported Functions for Conventional, FF-H1 andHART Devices ............................................................................................... C3-8

C4. Connection with Computerized Maintenance ManagementSystem (CMMS) .................................................................................... C4-1C4.1 Supported Functions Related to MAXIMO................................................... C4-1

C4.2 Role Sharing between PRM and CMMS ....................................................... C4-2

Blank Page

<C1. Overview of Plant Resource Manager (PRM)> C1-1

TI 38K03A01-01E Sep.01,2002-00

C1. Overview of Plant Resource Manager(PRM)The Plant Asset Managemant (PAM) system, Plant Resource Manager (hereinafterreferred as PRM) is used to manage field devices in real-time, and makes devicemaintenance more efficient and computerized. With the PRM function, it is possibleto perform intelligent operations, such as remote access, device parameter manage-ment, and device diagnostics and tuning, for devices that have the field communica-tion function including devices compatible with Fieldbus (FOUNDATION Fieldbus).PRM classifies and manages various device maintenance information such asinspection schedules, inspection memos, and configuration information of devices,and this information can then be used for versatile maintenance.

PRM can also acquire operating information of devices in a field via the Fieldbus andsystem bus, which can then be used for maintaining the field devices. This helpsreduce the maintenance cost and TCO (Total Cost of Ownership).

<C1. Overview of Plant Resource Manager (PRM)>

TI 38K03A01-01E

C1-2

Sep.01,2002-00

C1.1 GlossaryIn addition to standard terminology, the following terms are used in Part C.

Control Module

The smallest unit that can perform a function in a system, i.e., if broken down any further itwill not be able to perform a function, is referred to as a control module. All control moduleshave unique serial numbers (device ID).

Example:Valve positioner, differential pressure flow meter, electromagnetic flow meter,analyzer

Equipment Module

A device consisting of one or more control modules is referred to as an equipment module.

Example:A valve main body and a valve positioner are two “control modules,” and the “valve”obtained by combining them is an “equipment module.”

Device ID

A device ID is an ID assigned to a physical device. It is sometimes called a manufacturingserial number. It is always assigned uniquely to a device. A device ID is determineduniquely when a device is manufactured and never changes until it is discarded. Thedevice ID remains the same even if the device is removed, or placed again in a differentposition in a plant.

Legacy devices and static devices are also required to be registered in the device list.

PD Tag Name (Physical Device Tag Name)

A PD tag name (or simply called a “device tag”) is a logical name assigned to an equipmentmodule or control module, and is determined such that it corresponds to the function towhich the equipment module or control module is assigned or which it implements. Thedevice tag names described in plant design documents such as P&I (Piping and InstrumentDiagram) correspond to these names. A device tag name is assigned according to theplacement of an equipment module or control module in a plant. If the placement ischanged, for instance when the equipment module or control module is replaced, thedevice tag name will also change.

Node address

The node address is specified by a unique address number within a segment.

Device with Field Communication Capability

This means the control module, which supports the communication scheme compliant withthe FOUNDATION Fieldbus, HART and PROFIBUS standards.

Conventional Device

This means the control module (field device) of analog type such as 4 to 20 mA, 1 to 5 V,mV input/output. A conventional device does not have any digital communication functionsdevice. Pneumatic control module may be also referred as a conventional device.


TI 38K03A01-01E Sep.01,2002-00

Static Device

This means the static equipment without electric circuits or active elements.

Example:Orifice, pressure gauge, heat exchanger

Plug & Play Function

The Plug & Play function automatically recognizes control modules having FF and HARTcommunication functions that are connected to a field network, thus simplifying registrationin the database.


TI 38K03A01-01E

C1-4

C1.2 PRM Software ConfigurationPRM consists of the following three software products. An example of PRM softwareconfiguration is shown below.

PRM Server• Uses the popular, industrial-strength Oracle 8i database.

• Maintains a historical record of device parameters and maintenance records.

• Implements centralized management of device management information such as thedevice master (device profile), inspection record and schedule, and parts lists.

• Automatically acquires device events (e.g. alarms) in real-time, twenty-four hours perday, and saves them in the database. Thus the operating status of field devices canbe monitored continuously.

PRM Client• User-friendly Windows-based operating environment, with Explorer-like “Navigator”

for selecting a specific device.

• Uses bidirectional, all-digital field networks such as FOUNDATION Fieldbus. Performsautomatic device recognition and registration (Plug & Play), monitors device status,displays device events (e.g. alarms), allows tuning of device parameters, and performsdevice diagnosis (DD menu).

• The display color of device icons changes depending on the device status. Thisprovides an easy-to-understand overview of the device operating status.

• Allows not only devices with field communication capability but also conventionaldevices to be registered together for centralized device management.

• Allows third-party software, such as that of device vendors, to be used as PLUG-INApplications in addition to Yokogawa’s product, Device Viewer (*1). PRM Client canexecute a tuning tool or a diagnosis tool that is uniquely designed by the devicevendor.

*1: PRM R2.03 or later supports Device Viewer. Device Viewer is a built-in PLUG-IN Application of PRM Client.

Sep.01,2002-00


TI 38K03A01-01E

Field Communications ServerThe Field Communications Server consists of the field communication function and systembus (control bus) communication function. The system bus (control bus) communicationfunction communicates with Fieldbus (field network).

PRM server

C010201E.EPS

PRM client(instrumentation and control)

Parameter settingperformed by operator

PRM client(maintenance)

Input of inspectionand control data

Field communication server

Foundation Fieldbus DevicesHART Devices

Online setting andacquisition of various

parameters

• Inspection memo• Inspection schedule• Audit trail of device parameters

• Device master• Maintenance information• Parts list• Related information• Historical information• Device setting information

Figure Example of PRM Software Configuration

Sep.01,2002-00


TI 38K03A01-01E

C1-6

C1.3 PRM PositioningThis section explains the position of PRM in a plant system and the devices managed byPRM. The following figure shows the relationship between PRM and the ComputerizedMaintenance Management System (CMMS).

PRM(Plant Resource

Manager)

Functions for field network support

Computerized Maintenance Management System(CMMS)

DCS (plant operation function)

Productionmanagement

function

Operationand

monitoring

Engineeringfunctions

Control functions

C010301E.EPS

Field network

Fieldbus PC tool

Plant

Enterprise Resource Planning (ERP)

Figure PRM Positioning

Along with the Fieldbus engineering tools, PRM provides functions for supporting the fieldnetwork (including functions for supporting field devices). While the purpose of the Fieldbusengineering tools is to build a Fieldbus system, the purpose of PRM is to maintain andmanage the control module statuses (device statuses) and the parameters of the controlmodules (field devices) on the field network.

Furthermore, while CMMS takes care of general management of the plant facilities, includ-ing asset management, PRM supports and manages the tasks of inspecting the controlmodules within the plant.

TIP

The Computerized Maintenance Management System (CMMS) deals with the plant facilities (such aspiping, electric devices, and control modules (field devices). The device management system, on theother hand, is concerned with the plant’s control modules (field devices) and provides software functionsfor supporting real-time management and inspection works of the control modules (field devices).

Sep.01,2002-00


TI 38K03A01-01E

C1.4 Devices Managed by PRMPRM manages the following devices:

• Conventional devices

• Static devices

• Devices with field communication capability (FOUNDATION Fieldbus, PROFIBUS,HART and Modbus compliant devices)

Note that it is possible to manage devices without fieldbus communication capability,conventional devices and static devices, as well as devices not connected to the system(spare devices in stock). However, only the offline functions are used for conventionaldevices and static devices that do not support field communication.

Devices Managed by PRM and Online Function SupportThe table below lists managed devices and the availability of online function support bycommunication.

Table Devices Managed by PRM and Online Function Support

Devices Managed by PRM Online Function Support

FF-H1 device

HART device

Yes

Yes

Remark

FIO only

PROFIBUS device No

No

No

No

Modbus device

Conventional device

Static device

C010401E.EPS

SEE ALSO

For PRM supported functions for conventional, FF-H1 and HART devices, refer to Section C3.3.

TIP

Online functions mean online tuning and diagnostic functions such as read/write of device parametersand automatic detection of devices.

Sep.01,2002-00

Blank Page

<C2. PRM System Configuration> C2-1

TI 38K03A01-01E Sep.01,2002-00

C2. PRM System ConfigurationThis section explains the system configuration in which PRM runs.

SEE ALSO

• For more information about PRM system configuration, refer to “Plant Resource Manager (GS33Y05Q10-31E).”

• For PRM supported functions for conventional, FF-H1 and HART devices, refer to Section C3.3.

<C2. PRM System Configuration>

TI 38K03A01-01E

C2-2

Sep.01,2002-00

C2.1 System Configuration when ConnectingFOUNDATION Fieldbus (FF-H1)A large-scale CENTUM CS 3000 and small-scale CENTUM CS 1000 system configurationwhen connecting FF-H1 are explained as follows.

Large-scale CENTUM CS 3000 System Configuration when ConnectingFF-H1

The following figure shows a large-scale CENTUM CS 3000 system configuration whenconnecting FF-H1.

Ethernet

HIS PCPRM Client (Oracle 8i)Field Communications Server

PCPRM Client(Oracle 8i)

PCPRM Server(Oracle 8i)

V net

HISFCSFCURIO busNIUACF11SB401EB401ALF111

: Human Interface Station: Field Control Station: Field Control Unit: Remote I/O bus: Node Interface Unit: FOUNDATION Fieldbus Communication Module: ESB bus Interface (in Local Node): ER bus Interface (in Local Node): FOUNDATION Fieldbus Communication Module

H1 Fieldbus

Terminator

Coupler

Field devices

ALF111(in service)

ALF111(stand-by)

EB401(dual

redundant)

SB401(dual

redundant)

FCU

ESB bus

Local Node

FCS

RIO bus

NIU

FCU

H1 Fieldbus

ACF11

FCS

Terminator

Coupler

Field devices

C020101E.EPS

I/O node

PCCMMS(MAXIMO)

Figure Large-Scale CENTUM CS 3000 System Configuration when Connecting FF-H1


TI 38K03A01-01E Sep.01,2002-00

Small-scale CENTUM CS 1000 System Configuration when ConnectingFF-H1

The following figure shows a small-scale CENTUM CS 1000 system configuration whenconnecting FF-H1.

VLnet

HISFCSACF11

H1 Fieldbus

: Human Interface Station: Field Control Station: FOUNDATION Fieldbus Communication Module

Terminator

Coupler

Field devices

Ethernet

HIS

C020102E.EPS

PCPRM Client (Oracle 8i)PRM Server (Oracle 8i)Field Communications Server

ACF11

FCS

PCCMMS(MAXIMO)

Figure Small-Scale CENTUM CS 1000 System Configuration when Connecting FF-H1


TI 38K03A01-01E

C2-4

Sep.01,2002-00

C2.2 System Configuration when Connecting HARTTwo system configurations are available for managing HART devices:

• Vnet connection via HART Modules (FCS for FIO)

• Serial port connection via third-party vendor HART Multiplexer

Vnet Connection via HART Modules (CENTUM CS 3000 FCS for FIO)The Field Communication Server communicates with HART devices via HART modules byusing the on-demand communication functions of FCS.

Ethernet

HIS/ENG PRM Client Field Communications Server

PRM ClientPRM Server

V net

C020201E.EPS

FCS

SB401 (dual-redundant)EB401 (dual-redundant)

HART I/O module (in service)HART I/O module (stand-by)

HART I/O module (in service)HART I/O module (stand-by)

EB501 (dual-redundant)

DEV1

DEV2

HART devices

HART devices

Local Node

Remote Node

ESB bus

ER bus

SB401: ESB bus interface (in Local Node)EB401: ER bus interface (in Local Node)EB501: ER bus interface (in Remote Node)

PCCMMS(MAXIMO)

DEV1

DEV2

Figure Vnet Connection via HART Modules (CENTUM CS 3000 FCS for FIO)

Note: The PRM server, PRM client, and field communication server can run on the same PC.


TI 38K03A01-01E Sep.01,2002-00

Serial Port Connection via HART Multiplexer (CENTUM CS 3000 FCS forRIO)

PRM communicates with HART devices via the HART Multiplexer connected to the serialport of the PRM field communication server.

Ethernet

PRM Client Field Communications Server

PRM ClientPRM Server

V net

RIO bus

C020202E.EPS

FCS

AAM11AAM11

HIS/ENG

HART Multiplexer(commercially available)

Slave No.2

Slave No.1

Master

RS CommunicationRS-485

(*1)

*1: RS-232C/RS-485converter

DEV1

4-20 mA HART Digital Signals

HART Devices

PCCMMS(MAXIMO)

DEV2

Figure Serial Port Connection via HART Multiplexer



TI 38K03A01-01E

C2-6

Sep.01,2002-00

Serial Port Connection via HART Multiplexer (using P&F HART Multi-plexer)

When using the P&F HART Multiplexer, the PRM system can be connected as followswithout connecting the CENTUM system.

Ethernet

PRM Client Field Communications Server

PRM Client PRM Client

RS-485(*1)

*1: RS-232C/RS-485converter

HART Multiplexer(Master No.1)



HART Multiplexer

(Slave No.1)

HART Multiplexer

(Slave No.15)

C020203E.EPS

Directly connectedto Master

HART Devices

Connected to Slave

PRM Server PCCMMS(MAXIMO)

Figure Example of P&F HART Multiplexer Connection


<C3. Overview of PRM Functions> C3-1

TI 38K03A01-01E Sep.01,2002-00

C3. Overview of PRM FunctionsThis section describes the PRM system size and the functions that constitute PRM.

SEE ALSO

For details of the PRM operating environment, refer to “Plant Resource Manager (GS 33Y05Q10-31E).”

C3.1 PRM System SizeThis section explains the relationship between PRM and a CENTUM CS 3000/CENTUMCS 1000 project and system size supported by PRM.

Relationship between System and CENTUM CS 3000/CENTUM CS 1000Project

One PRM database should be assigned to one CENTUM CS 3000 or CENTUM CS 1000project. The PRM management unit and the plant operation range of a CENTUM CS 3000/CENTUM CS 1000 project correspond one to one. PRM manages control modules (fielddevices) and equipment modules within the operation and monitoring range of a CENTUMCS 3000/CENTUM CS 1000 project.

SEE ALSO

For a CENTUM CS 3000 project, refer to “CENTUM CS 3000 System Overview (TI 33Q01B10-01E).”

Number of Control Modules Managed by PRMThe number of devices subject to PRM control is determined by the purchased license. Ifthe number of devices exceeds the licensed number, the exceeded part cannot be regis-tered.

Table Number of Control Modules Managed by PRM

Option type Number of control modules managed by PRM

Standard

Option 1

Max. 100 modules

Max. 1000 modules

Option 2 Max. 3000 modules (*1)

C030101E.EPS

*1: When the number of modules managed by PRM exceeds 3,000, contact Yokogawa sales.

Number of Users and ClientsThe number of users and the number of clients who can use PRM are determined by thelicense purchased for Oracle. The number of users refers to the number of terminals thatcan be used at the same time and the number of clients refers to the number of terminalsthat can be installed.

<C3. Overview of PRM Functions>

TI 38K03A01-01E

C3-2

Sep.01,2002-00

C3.2 Overview of PRM FunctionsThere are five groups of PRM plant asset management functions: device navigator, mainte-nance information management, audit trail, tuning and diagnosis, and utilities.

The following figure shows a schematic view of the functions that constitute the PRMdevice management functions. This section describes an overview of these functions.

PRM

Device navigation functions

Plant View

Maintenance informationmanagement functions

Device master

Inspection memo

Inspection schedule

Parts list

Link to document

Audit trail functions

Parameter audit trail

Inspection memoaudit trail

Operation audit trail

Device eventmessage Calibration

Tuning and diagnosticfunctions

Parametercomparison

ToolDD Menu

ToolDevice Viewer

PLUG-INApplication

Utilities

Browser

Security

Export

Online manual

Self-documentation

Network View Class View

C030201E.EPS

Figure Schematic View of PRM Functions


TI 38K03A01-01E Sep.01,2002-00

C3.2.1 Device NavigatorThe Device Navigator provides Plant View, Network View, and Class View.

In hierarchical Explorer-like format, these views display the arrangement of devices in theplant, physical network configuration, and device type, respectively. Target devices can beselected and device management functions can be performed via these views.

Plant ViewDisplays the equipment which makes up the plant, and shows its place in the plant hierar-chy, in hierarchical Explorer-like format. The equipment can be intuitively managed by plantorganization based on P & I diagrams. Unused devices in the plant can be managed byputting them in the “Spare” folder, and devices that have failed or are under maintenancecan be placed in the “Off-Service” (Out of Service) folder.

An example of plant view is shown below.

Device Navigator 1

Plant

PLANTSITE01

AREA01

Network Class

Off-Service

FI100

CELL01UNIT01

FI100

S

C030202E.EPS

A

C

U

E

J8-123871234DF

Spare

812703ER798730455945430003J0000369 (FI1004)

Figure Plant View


TI 38K03A01-01E

C3-4

Sep.01,2002-00

Network ViewDisplays the position of devices, related to the field network physical configuration, in anExplorer-like hierarchical view. The device icon next to the device name shows theoperating status of the device: the color of the device icon changes if the device fails, sousers have an immediate visual view of the operating status.

An example of a network view is shown below.

Device Navigator 1

Plant

PLANT

Network Class

PROFIBUS

C030203E.EPS

MODBUSHART

Foundation FieldbusBOILER-0101-10111-1

DAQSTATION (Ready)EJA001 (Ready)FI1002 (Ready)YFL001 (Ready)YTA001 (Ready)YVP001 (Ready)

R302DME-0103-10113-1

HART

Figure Network View

Class ViewDisplays devices in an Explorer-like hierarchical view, grouped by supplier, model, andrevision. For devices that have failed or are under maintenance, the status (e.g. spares) ofdevices of the same type can be checked at a glance.

An example of a class view is shown below.

Device Navigator 1

Plant

PLANTFoundation Fieldbus

Yokogawa ElectricAE100

Network Class

HART

YVP001Spare

On-ServiceR2.01

Off-Service

M

DAQSTATIONM

EJA100AM

YF100*EM

YTA320M

YVPM

R

C030204E.EPS

Flow MeterC

Magnetic Flow MeterC

PositionerC

Pressure TransmitterC

RecorderC

Temperature TransmitterC

HART

Figure Class View


TI 38K03A01-01E Sep.01,2002-00

C3.2.2 Maintenance Information ManagementManages the maintenance information of all devices.

Device MasterManages an inventory of all devices. A list of all devices, or detailed information on each,can be displayed.

Inspection MemoReports and manages records of device inspection and malfunctions at the field. Moreover,maintenance personnel can save notes about how a failure was handled, as well as warn-ings or reminders about maintenance check items, in the historical record. This functioncan be used to manage not only device online work records but also device offline workrecords.

Inspection ScheduleMakes and manages inspection schedules (checking, tuning, calibration, etc.) for eachdevice.

Parts ListA device may consist of several parts; the parts list displays the attributes of each part, andstock information. This enhances the efficiency of repair and parts replacement work.

Link to DocumentThis can display information such as configuration (e.g. P & ID and control drawings),instruction manuals, and pictures, as desired. This device-related information can beaccessed and displayed using the tag name as a key.

C3.2.3 Audit Trail FunctionThis keeps a database containing an operation history for devices (parameter setting,parameter data saving, calibration history, inspection memo history), and historical deviceevent messages. Database contents can be displayed in chronological order or by historicalmessage type, in summary or detailed format. The operation records can be filtered bydevice ID or PD tag name, so the operation record for a specific device can be easilydisplayed.


TI 38K03A01-01E

C3-6

Sep.01,2002-00

C3.2.4 Tuning and Diagnosis FunctionsSupport device online tuning and diagnostic functions.

Parameter Tuning and ComparisonOnline device data can be displayed and device parameters can be set by this function.Current device data can be compared with stored device historical records, so deviceoperating conditions can be switched easily and safely by comparing current and pastvalues. The set data can be stored. The device data can be uploaded at any time, andstored in the database.

ToolFor FOUNDATION Fieldbus, display switching to DD Menu and Device Viewer can besupported.

• DD Menu:Using the Method of DD files provided by a vendor, diagnosis and tuning for devicescan be performed. Its specifications are dependent on field devices.

• Device Viewer:Device Viewer is a PLUG-IN Application that displays the self-diagnosis result of FF-H1 devices. In many cases, FF-H1 devices save vendor’s multi-parameters specifiedfor device’s errors. Device Viewer detects and displays errors in devices directly.Device Viewer displays not only the self-diagnosis result by reading parameters butalso the data displayed on the FF-H1 device’s LCD, such as error messages, in auser-friendly format. This allows operators to monitor the connected devices from DCSwithout viewing the LCD of field devices.

SEE ALSO

For the FF-H1 devices supported by Device Viewer, refer to “Plant Resource Manager (GS 33Y05G10-31E).”

CalibrationThe standard calibration can be executed by using parameter tuning function and DDmenu included in the tuning and diagnosis functions.

In addition, original calibration tools, provided by a third party such as device vendors, canbe registered as PLUG-IN Applications and executed from the Application menu.


TI 38K03A01-01E

C3.2.5 UtilitiesConsist of following functions.

BrowserCan search for devices using device attribute information such as device ID, device tagname, device tag comment, block name, or parameter value.

SecurityDuring maintenance of field devices, restricts operation to specific user(s) or restricts therange of operations permitted, to prevent system troubles due to operator errors and tomaintain system security.

The user name and operation record of the logged-in operator are recorded in theoperation history. The user group can be used to assign user privileges to groups of users(i.e. restrict rights) according to job function.

ExportCan output an operation history to a text file in CSV format.

Self-documentationAutomatically creates device documentation for management. Can collectively print outdata stored in the database in report format. Device information is managed electronically,and can be printed out on demand. Information on each screen can be printed out asindividual reports, so a report can be printed out after maintenance work to provide amaintenance work record, thus reducing the workload such as making reports.

PLUG-IN ApplicationsThese are software packages provided by third-party device vendors which are built intothe PRM software package. The PLUG-IN Application runs on the client PC and accessesfield devices and the Oracle database in the PRM server via the PLUG-IN Applicationlibrary.

Online Manual (R2.02 or later)All instruction manuals are provided in PDF format on CD-ROM, and so can be viewed andprinted on-demand.

Sep.01,2002-00


TI 38K03A01-01E

C3-8

C3.3 PRM Supported Functions for Conventional, FF-H1 and HART DevicesAll functions can be performed for FOUNDATION Fieldbus devices, but there are somerestrictions for HART devices. The following table shows the PRM supported functions forconventional, FF-H1 and HART devices.

Table PRM Supported Functions for Conventional, FF-H1 and HART Devices

Device NavigationFunction

Audit Trail Management Function

Adjustment and Diagnosis

Other Functions

HART device’s ‘Detail’ part is different from other devices.

Record the Start/Stop of only Menu Window

Take several ten seconds until this function is executed because of the performance of HART communications.

Device Method and Device Viewer for Fieldbus. Menu and Offline Parameters for HART.The parameter information of HART devices can be acquired by Offline Parameters. The acquired data can be saved in each device in Text format.

Plant View

(*2)

(*2)

Maintenance Information Management Functions

Network View

Class View

Plug_&_Play

Inspection Memo

Parameter Tuning and Comparison

Status Display

Inspection Schedule

Parts List

Browse Function

Security

Printing

PLUG IN Application

Calibration

Link To Document

Parameter History

Device EventMessage

Operation History

Tool

Inspection MemoHistory

Register from Host_File_Set

Device Master

Specification RemarksFF-H1 HARTConventionalDevices(*1)Function

C030301E.EPS: Supported : Partly supported : Not applicale

*1: The conventional device includes the 4 to 20 mA analog devices and the static devices as a motor.*2: Supported by R2.03 or later versions.

Sep.01,2002-00

<C4. Connection with Computerized Maintenance Management System (CMMS)> C4-1

TI 38K03A01-01E Sep.01,2002-00

C4. Connection with ComputerizedMaintenance Management System(CMMS)The computerized maintenance management system (CMMS) evaluates the systemstatus by analyzing a certain amount of data to ensure effective maintenance of theplant. By connecting PRM to CMMS, CMMS can acquire online information ofdevices from PRM, thus enabling more efficient maintenance.

The CMMS which can be connected with PRM is MAXIMO from MRO Software, Inc.

SEE ALSO

For detailed information about connection with CMMS, refer to “Plant Resource Manager (GS 33Y05Q10-31E).”

C4.1 Supported Functions Related to MAXIMOThe following features are offered by connecting PRM to CMMS.

Device Master Synchronization (Offline)

Exports the contents of the Device Master in PRM to CMMS by using the synchronizationtool of Device Master.

Mapping Equipment Hierarchy to Plant Hierarchy (Offline)

Establishes a mapping between the equipment hierarchy for CMMS and the planthierarchy, then imports it to the PRM side.

Send Work Order (Online)

Sends “Work Order” from PRM to CMMS by calling up the “Work Order Input Dialogue” inthe PRM side.

Progress Display (Online)

PRM can call up the “Progress Display” held by the client PC of CMMS.

<C4. Connection with Computerized Maintenance Management System (CMMS)>

TI 38K03A01-01E

C4-2

Sep.01,2002-00

C4.2 Role Sharing between PRM and CMMSOverlapping of functions such as handling the same data occurs when the PRM andCMMS packages are connected. The following table shows which function is enabled whenthe two packages run. For detailed specifications, refer to the instruction manual of CMMS.

Table Role Sharing between PRM and CMMS

Function

Plant Hierarchy/CMMS Structure

Map equipment hierarchy for CMMS to Plant Hierarchy of PRM.

Device Master Device Master is stored in PRM. The contents of Device Master in PRM are exported to the CMMS.

Link to Document "Link to Document" must be set in each package. A user accesses either PRM or the CMMS depending on the online document needed.

Security Proper users are registered in both PRM and the CMMS to set security.

Printing Printing is available in both PRM and the CMMS.

These functions are only available in the CMMS side. However, these are still enabled in PRM side to ensure the system flexibility and upper compatibility.

These are unique function of the CMMS.

: Function is enabled. Data transfer is available. : Function is enabled : Function exists but not usedN/A: No function available

Inspection Memo

Inspection Schedule

Parts List

Work Order/Work Order Schedule

Progress Display

Resource Management

Purchasing Management/ Budget Management

Parameter Tuning and Comparison

Tool/Method

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

PLUG-IN Application

Audit Trail Message

PRM CMMS Description

C040201E.EPS

Ind-1

TI 38K03A01-01E

<Int> <Toc> <Rev>

Fieldbus Technical Information

INDEX

Sep.01,2002-00


AAccuracy Improvement due to Digitalization ..... A3-4ACF11 Fieldbus Communication Module

Specifications of CENTUM CS .............. A4-9ACF11 Fieldbus Communication Module

Specifications of CENTUM CS 1000 ...... A4-7ACF11 Fieldbus Communication Module

Specifications of CENTUM CS 3000 ...... A4-5Actuator ........................................................... A3-8Advanced Functionality of Field Devices .......... A3-2ALF111 Fieldbus Communication Module

Specifications ........................................ A4-3Analog Transmission ....................................... A2-2Audit Trail Function .......................................... C3-5

BBasic Design Considerations ........................... B2-2Bidirectional Communication ........................... A2-8Browser ........................................................... C3-7

CCabling ............................................................ B3-4Calibration ....................................................... C3-6Changes in Transmitters .................................. A3-3Class View ....................................................... C3-4Comparison with Conventional Communication

.............................................................. A2-2Connecting the Fieldbus Cable and Handling the

Shield Mesh for Fieldbus CommunicationModule .................................................. B3-4

Connection of FF Devices from Other Vendors toYokogawa’s CENTUM Control Systems............................................................ A4-10

Connection with Computerized MaintenanceManagement System (CMMS) .............. C4-1

Consideration of Voltage Drop Restrictions ...... B2-5Considerations in Basic and Overall Design ..... B2-2Construction .................................................... B1-2Control Valve Changes .................................... A3-8

DDaily Field Inspection ....................................... B5-1Daily Maintenance ........................................... B5-1Data Exchange between Field Devices ............ A2-8Design ............................................................. B1-2Design of FF Device Grouping per Segment .... B2-8Designing Process Control Systems with

Fieldbus Technology .............................. B2-1Detail Design Considerations ........................... B2-3Device Master .................................................. C3-5Device Navigator ............................................. C3-3Devices Managed by PRM .............................. C1-7Devices Managed by PRM and Online Function

Support .................................................. C1-7Difference between Analog Transmission and

Fieldbus Communication Systems ......... A3-1Difference between Fieldbus and Analog Signal

Process Control System ........................ B1-4Disassembly and Consumables Replacement

.............................................................. B5-2Distributed Functions ....................................... A2-9Distributing Functions to the Field .................... A2-9

EEnhanced Data Transmission .......................... A2-8Establishment of the Fieldbus Foundation ........ A1-2Evolution of Maintenance ................................. B5-3Example of Serial Link Type Wiring .................. B3-1Example of Tree Type Wiring ........................... B3-2Expansion and Modification of Existing System

.............................................................. B2-8Export .............................................................. C3-7

Ind-2

TI 38K03A01-01E

<Int> <Toc> <Rev>

Sep.01,2002-00

FFeatures of Control Valves with the Fieldbus

Communication ..................................... A3-9Features of Fieldbus ........................................ A2-1Field Communications Server .......................... C1-5Field Device Maintenance Tool ........................ B4-1Fieldbus Communication ................................. A2-3Fieldbus Engineering Process ......................... B1-1Fieldbus Monitor .............................................. B4-1Fieldbus Package Types .................................. B1-5Fieldbus Standard Specifications ..................... A1-4Fieldbus Support in CENTUM CS .................... A4-8Fieldbus Support in CENTUM CS 1000 ........... A4-6Fieldbus Support in FCS for FIO of

CENTUM CS 3000 ................................ A4-2Fieldbus Support in FCS for RIO and

Compact FCS of CENTUM CS 3000 ..... A4-4Fieldbus Support in Yokogawa’s CENTUM Control

Systems ................................................ A4-1Fieldbus-ready Field Devices ........................... A3-1Function and Accuracy Check.......................... B5-2Functions of Field Devices and System............ A2-9

GGlossary .......................................................... C1-2

HHandling the Shield Mesh ................................ B3-4Hybrid Communication .................................... A2-2

IIEC/ISA Standard Specifications ...................... A1-4Importance of Process Control System Design

.............................................................. B2-1Improved Transmission Accuracy ..................... A2-6Improvement of Transmission Accuracy ........... A3-4Improvement of Transmitter Measuring Accuracy

.............................................................. A3-5Inspection and Maintenance ............................ B5-2Inspection Memo ............................................. C3-5Inspection Schedule ........................................ C3-5Installing Advanced Functions in Field Devices

.............................................................. A2-9Installing an Intrinsic Safety Barrier .................. B3-4Instrument of Digital Signal Measurement ........ B4-1Insulating Material of Twisted Pair Cable .......... B2-5Integrating or Grouping Range and Scope ....... B2-3

Integration of Instrumentation andSelf-diagnostics Functions ................... A3-10

Interlock Check ................................................ B4-5Interoperability ............................................... A2-10Investigation of Number of Field Devices

connected to an H1 Segment ................. B2-4

KKnowledge of Application Software .................. B4-2Knowledge of System Software ....................... B4-2

LLabor Savings in Startup Work ......................... B4-3Large-scale CENTUM CS 3000 System

Configuration when Connecting FF-H1 .. C2-2Link to Document ............................................. C3-5Loop Check ..................................................... B4-3

MMaintenance .................................................... B1-3Maintenance during System Operation ............ B5-1Maintenance Information Management ............ C3-5Maintenance Management (Maintenance Plan,

Device Managemell¸ Audit Trail) ............ B5-3Making the Most of Field Device Accuracy ....... A2-7Managing Fieldbus Engineering ....................... B1-1Mounting Couplers ........................................... B3-3Mounting Terminators ...................................... B3-3Multi-drop Connections .................................... A2-4Multi-sensing Function Equipment ................... A3-6Multifunction Equipment ................................... A3-7Multivariable Detection and Transmission ........ A2-5

N

Network View ................................................... C3-4

New Construction of Fieldbus Process ControlSystem ................................................... B3-1

Number of Branch Cables and Total Length ..... B2-7Number of Control Modules Managed by PRM

............................................................... C3-1Number of Users and Clients ............................ C3-1

OOnline Manual (R2.02 or later) ......................... C3-7Overall Design Considerations ......................... B2-2Overview of Plant Resource Manager (PRM) ... C1-1Overview of PRM Functions ...................C3-1, C3-2

Ind-3

TI 38K03A01-01E

<Int> <Toc> <Rev>

Sep.01,2002-00

PParameter Tuning and Comparison ................. C3-6Parts List .......................................................... C3-5Plant View........................................................ C3-3PLUG-IN Applications ...................................... C3-7PRM Client ...................................................... C1-4PRM Positioning .............................................. C1-6PRM Server ..................................................... C1-4PRM Software Configuration............................ C1-4PRM Supported Functions for Conventional,

FF-H1 and HART Devices ..................... C3-8PRM System Configuration .............................. C2-1PRM System Size ............................................ C3-1Problem Prediction Function .......................... A3-10Process of Standardization .............................. A1-3Production ....................................................... B1-2Progress of Fieldbus Standardization............... A1-2Progress of International Standardization of

Fieldbus ................................................. A1-1

RRange Free Devices ........................................ B4-5Recognition as a Standardization Work Item .... A1-2Reduced Wiring Cost ....................................... A2-4Relationship between System and CENTUM

CS 3000/CENTUM CS 1000 Project ...... C3-1Removing Error Factors ................................... A2-6Restriction by Macrocycle Corresponding to

Control Period ........................................ B2-4Restriction by Power Supply Current Capacity

.............................................................. B2-4Reusing Existing Cables .................................. B3-5Reusing the Cables from Field Devices to Field

Junction Box .......................................... B3-6Reusing the Cables from Field Junction Box to

Control Room ........................................ B3-6Role Sharing between PRM and CMMS .......... C4-2

SSafety Design and Reliability Improving Design

.............................................................. B2-3Security ........................................................... C3-7Self-documentation .......................................... C3-7Selection of Bus Topology and Maximum Number of

FF Devices per Segment ....................... B2-5Selection of Cable Type and Total Length ........ B2-6Selection of Fieldbus Cable and Wiring Method

.............................................................. B2-5Selection of Wiring Cables ............................... B2-5Serial Port Connection via HART Multiplexer

(CENTUM CS 3000 FCS for RIO) .......... C2-5

Serial Port Connection via HART Multiplexer(using P&F HART Multiplexer) ............... C2-6

Services for Fieldbus Support Devices ............. A1-5Setting Parameters for Fieldbus Communication

and Its Functions ................................... B1-4Setting Parameters Specific to Field Devices ... B1-4Small-scale CENTUM CS 1000 System

Configuration when Connecting FF-H1.............................................................. C2-3

Software Packages for Fieldbus....................... B1-5Startup ............................................................. B1-3Supported Functions Related to MAXIMO ....... C4-1System Configuration when Connecting

FOUNDATION Fieldbus (FF-H1) ........... C2-2System Configuration when Connecting HART

.............................................................. C2-4System Construction Considerations ............... B3-1System Design Considerations ........................ B2-1System Maintenance Considerations ............... B5-1System Startup Considerations ........................ B4-1

TTechnologies and Expertise Necessary for Startup

.............................................................. B4-2Technology for Field Devices ........................... B4-2Tool .................................................................. C3-6Tool Necessary for Startup ............................... B4-1Trial Operation ................................................. B4-5Tuning and Diagnosis Functions ...................... C3-6

UUsing Self-diagnostics Function ..................... A3-10Utilities ............................................................. C3-7

VVarious Types of Data Transmission ................ A2-8Vnet Connection via HART Modules

(CENTUM CS 3000 FCS for FIO) .......... C2-4

WWhat is Fieldbus? ............................................ A1-1Wiring Technology............................................ B4-2

YYokogawa’s Efforts for Fieldbus Standardization

.............................................................. A1-5Yokogawa’s Fieldbus-ready Field Devices Line-up

.............................................................A3-11Yokogawa’s Fieldbus-ready Systems ............... A4-1

Blank Page

i<Int> <Toc> <Ind>

TI 38K03A01-01E

Revision Information● Title : Fieldbus Technical Information

● Manual No. : TI 38K03A01-01E

Mar. 1998/1st EditionNewly publishedNov. 1998/2nd EditionFieldbus support in CS 1000 and CS 3000Fieldbus cable type revisedElectronic format appliedA4.1 Fieldbus-support CS 1000 and CS 3000 addedA4.2 Description revised and addedB1.3 Method of installing Fieldbus tools addedB2.2 Description in wiring method revised and addedB3.1.1 Shielding method addedB3.1.4 Description addedB3.1.5 Fieldbus-shielding method addedB3.2 Cable type addedB4.1 Description correctedB4.2 Description correctedSep. 2002/3rd EditionIntroduction Revised descriptions of “Introduction” and “Trademarks”

Added “Structure of This Manual” and “Target Readership for This Manual”For all sections Revised “system device” to “system”

Revised “analog communication” and “analog communication protocol” to “analog transmis-sion”

Part A Revised “Outline of Fieldbus and Its Support Products” to “Overview of Fieldbus andYokogawa’s Fieldbus-ready Products”

A1. Revised this section title “International Standardization of Fieldbus” to “Progress of InternationalStandardization of Fieldbus”Shifted section A2 in 2nd Edition to section A1Updated description

A1.1 Added this sectionA2. Shifted section A1 in 2nd Edition to section A2

Updated descriptionA2.6 Updated description

Described about “Interoperability Test” of Fieldbus FoundationDescribed about “Host Interoperability Support Test” of Fieldbus Foundation

A3. Updated descriptionA3.4 Revised this section title “Upgrading from BRAIN System” to “Yokogawa’s Fieldbus-ready Field

Devices Line-up”Revised description of this section

A4. Revised this section title “Fieldbus-ready System Devices” to “Yokogawa’s Fieldbus-readySystems”

A4.1 Revised this section title “Fieldbus Support in CENTUM CS 1000, CS3000 and CENTUM CS”to “Fieldbus Support in Yokogawa’s CENTUM Systems”Updated descriptionSectioned from section A4.1.1 to A4.1.4Added section A4.1.1 “Fieldbus Support in FCS for FIO of CENTUM CS 3000”

A4.2 Revised this section title “Fieldbus-ready Field Devices from Other Vendors” to “Connection ofFF Devices from Other Vendors to Yokogawa’s CENTUM Control Systems”Described about Interoperability Test of Fieldbus FoundationUpdated description

Part B Updated descriptions of all sectionsB1.3 Revised this section title “Fieldbus Tools” to “Software Package of Fieldbus”

Updated description

Sep.01,2002-00

ii<Int> <Toc> <Ind>

TI 38K03A01-01E Sep.01,2002-00

Written by Product Marketing Dept.Industrial Automation Systems Business DivisionYokogawa Electric Corporation

Published by Yokogawa Electric Corporation2-9-32 Nakacho, Musashino-shi, Tokyo 180-8750, JAPAN

Printed by Yokogawa Graphic Arts Co., Ltd.

B2.2 Updated descriptionSectioned from section B2.2.1 to B2.2.4Described about limit and restriction items in sections B2.2.1 and B2.2.2

B3.1 Revised this section title “New Construction of Fieldbus” to “New Construction of FieldbusProcess Control System”Updated description

B5.4 Revised this section title “Future Maintenance” to “Evolution of Maintenance”Updated description

Part C Added this part

Subject to change without notice.

what is field bus

Technology

overview of fieldbus

fieldbus foundation

foundation fieldbus

fieldbus system

features of fieldbus

fieldbus engineering

outlines fieldbus

iintroduction fieldbus