gs33y05q10-32e

GeneralSpecifications

Models SSS7700,SSS7710, SSS7711,SSS7720, SSS7750Plant Resource Manager

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

GS 33Y05Q10-32E

GS 33Y05Q10-32ECopyright July 26, 20061st Edition July 26, 2006

R3GENERALPRM is a software tool that supports the daily business activities of maintenance personnel. This Plant Resource ManagerPackage for the digital network era efficiently handles field device management and maintenance work for the Foundationfieldbus and HART devices, which helps reduce Total Cost of Ownership (TCO) in your plant.This package also can support conventional analog devices with manual registration; it can provide integrated manage-ment of conventional analog, Foundation fieldbus and HART devices.

FUNCTION SPECIFICATIONSPlant Resource Manager (PRM) consists of the following components:

PRM Server Collect and store the data for device diagnostic such as device parameters, device alarms and Inspection Memo. Implements centralized management of device information such as the device list, inspection record and schedule, user-

created electronic documents, and parts lists. This function can generate maintenance alarms for necessary information (phenomena, causes, action) and can distribute

this maintenance alarm information to personnel who want it.

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. Performs automatic device recognition and

registration (Plug and Play), monitors device health status with maintenance alarm functions, monitors communicationerror, monitors advanced diagnosis of device, process interface diagnosis and Unit diagnosis, etc. by PRM AdvancedDiagnosis application, allows tuning of device parameters, and performs device diagnosis (DD Menu, DeviceViewer,PLUG-IN Application, DTM Works, etc.).

Online device adjustment/setting from the PRM Client can be performed on the screen with the same user interface as thatof on-site adjustment setting tool FieldMate.

Possible to exchange data between FieldMate and PRM. The status display icon appears beside the device icon changes depending on communication and device status. This

provides an easy-to-understand overview of device health status. For a device with an unconfirmed maintenance alarm status (device health status), a confirmation status icon appears next

to the device icon. The user can freely define the device icon displayed in the device navigator.

Moreover, the user can select one from three sizes of icons and fonts, and can customize the characters and the iconsaccording to the screen size or on the users request.

In addition to Maintenance Alarm Function and standard diagnostic functions, Yokogawa provides Acquisition Navigatorand Diagnostic Tool as components of the PRM Advanced Diagnosis package. With these software components, you cancarry out advanced predictive, proactive and preventive maintenance using a field network.

Allows not merely Foundation fieldbus-compliant devices and HART-compliant devices but also conventional analog fielddevices to be registered together for true, centralized device management.

Allows using the third-party, such as device vendors, software as a PLUG-IN Application in addition to Yokogawasproduct, DeviceViewer (*1, *2) and PLUG-IN ValveNavi. PRM Client can start up a calibration tool or a diagnosis tool thatis uniquely designed by device vendors as PLUG-IN Application.

*1: DeviceViewer is a build-in PLUG-IN Application for self-diagnostic of Foundation fieldbus devices and HART devices into PRMClient. The way to use the product differs from regular PLUG-IN Application. To be able to run the DeviceViewer of a device fromeach vendor, definition files must be obtained from that device vendor.

*2: DeviceViewer can be displayed on CS 1000/CS 3000 HIS. However, for displaying DeviceViewer, the CS 1000/CS 3000Operation and Monitoring Functions must be R3.07 or later release.

2All Rights Reserved. Copyright 2006, Yokogawa Electric Corporation

GS 33Y05Q10-32E July 26, 2006-00

Field Communications ServerPRM supports two types of field communication (Foudation fieldbus and HART).PRM can communicate with FF devices via FF communication module in CENTUM system and in STARDOM system.When connecting to HART devices, two system configuration types are available.One is Control bus connection via AI/AO modules with HART Communication in CENTUM CS 3000 system, in ProSafe-RSsystem and in STARDOM System. Another one is Serial port connection via 3rd Vendor HART Multiplexer. For serial portconnection, PRM supports HART multiplexers supplied from four vendors (P+F, MTL, ELCON and STAHL). HART modemand HART multiplexer can be connected to the multiple COM ports at the same time. By using serial port connection, PRMcan be easily added on existing HART system.

Supported Configuration FF communication modules for CS 1000/CS 3000 AI/AO Modules with HART Communication for CS 3000 FF communication modules for STARDOM AI/AO Modules with HART Communication for STARDOM AI/AO Modules with HART Communication for ProSafe-RS 3rd vendor HART Multiplexer

PRM Advanced Diagnosis (Option)PRM Advanced Diagnostic Server is an optional package available with PRM. It provides an environment for executing thediagnostic algorithm of field devices.By using diagnostic algorithm applications, you can execute diagnosis with the acquired parameters for possible anomalies.By using PRM Advanced Diagnostic Application Software Development Kit (PAA-SDK) in addition to the package, you cancreate and execute diagnostic applications containing advanced diagnostic algorithms for process interface, device and unitthat have been difficult to realize with field devices alone.Note that PRM advanced diagnostic applications (PAA) are available as diagnostic applications initially provided by devicevendors or third-party vendors. For details of PRM Advanced Diagnosis, see GS 33Y05Q21-32E SSS7740 PRM AdvancedDiagnosis Server.

Multi-server SwitchoverThe scope of PRM management generally corresponds to a CS 1000/CS 3000 project, ProSafe-RS project or STARDOMproject.However, if a wider range of integrated management is required, multi-server functions can be used to select the PRM serverthat is referenced by a PRM client. This allows centralized remote monitoring of large-scale plants with some CENTUMprojects.

3

All Rights Reserved. Copyright 2006, Yokogawa Electric Corporation GS 33Y05Q10-32E July 26, 2006-00

SYSTEM CONFIGURATIONA single database server is the unit for management (e.g. for search operations). At least one PRM Server and one FieldCommunications Server are required for a CENTUM CS 1000/CENTUM CS 3000 project.PRM can manage the FF-H1 devices and the HART devices together.

System Configuration When Connecting Foundation fieldbusCENTUM CS 3000This section shows an example of system configuration for Plant Resource Manager.

HISExaopcOPC Interface for HIS

PCField Communications ServerFF-H1 Host Interface

PCPRM Client PCPRM Server

Vnet/IPbus 2bus 1

HISFCSFCUSB401EB401ALF111

: Human Interface Station: Field Control Station: Field Control Unit: ESB bus Interface (in Local Node): ER bus Interface (in Local Node): Foundation Fieldbus Communication Module

FF-H1 Fieldbus

Terminator

Coupler

Field devices

ALF111(in service)

ALF111(stand-by)

EB401(dual

redundant)SB401

(dualredundant)

FCU

ESB bus

Local Node

FCS

FieldMate

FCS

FF-H1 Fieldbus (for device adjustment)

HART devices

HART I/O Module

Terminator

Coupler

F01E.EPS

Figure: System Configuration (CENTUM CS 3000 system)


GS 33Y05Q10-32E July 26, 2006-00

STARDOMThis section shows a STARDOM configuration for Plant Resource Manager. The figure below is an example of connectingthe STARDOM system to the PRM. Messages from the STARDOM controller are transmitted to the PRM server via the OPCserver. FCN/FCJ OPC Server for Windows is needed in the system.

HMI Client

FCN/FCJ

HMI ServerData Server

OPC Server

Control Network

Ethernet

FCN

PCPRM Client

PCPRM ServerField Communication Server

Logic designer Resource ConfiguratorEnginnering toolDevice Management tool

Controller

VDS/HMI PRM

CPU NFLF111PSUFCJ

(with FF-H1 port)

F10E.EPS

FF-H1 Fieldbus

Terminator

Coupler

FF-H1 Fieldbus

Terminator

Coupler

Figure: STARDOM System Configuration

Operating EnvironmentPRM client and HMI client can run on the same PC.PRM Server or Field Communication Server cannot run on the PC in which VDS is already installed.PRM server or Field Communication Server can run on the PC in which FCN/FCJ OPC server for Windows is installed. (PRMrevision is R2.06 or later)The revision of FCN/FCJ must be R1.40 or later.

5


System Configuration When Connecting HARTFour system configurations are available for managing HART devices as below: Vnet/IP or Vnet connection via HART Modules in CS 3000 System Control Network connection via HART Modules in STARDOM System Serial port connection via 3rd vendor HART Multiplexer Serial or USB port connection via 3rd vendor HART ModemVnet/IP or V net connection via HART Modules (FCS for FIO) in CENTUM SystemField communication server communicates with HART devices via HART modules by using the on-demand communicationfunctions of FCS.

HIS/ENGExaopc OPC Interface for HIS

Field Communications Server

PRM Client PRM Server

Vnet/IP bus 2bus 1 HART device

F04E.EPS

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)

DEV1

DEV2

HART Modem (VIATOR RS232 Interface)

(for device adjustment)

FCS

Figure Vnet/IP Connection via HART Modules (FCS for FIO) in CENTUM SystemNote: PRM server, PRM client, and Field communication server can run on the same PC.


GS 33Y05Q10-32E July 26, 2006-00

ProSafe-RSThis section shows a ProSafe-RS configuration for Plant Resource Manager. The figure below is an example of connectingthe ProSafe-RS system to the PRM. Message from SCS are transmitted to the PRM server via Exaopc OPC Interface forHIS. HIS and Exaopc OPC interface package for HIS are needed in the system.

HISExaopc OPCInterface package for HIS

PRM ClientPRM ServerField Communication Server

Vnet/IP bus 2bus 1

F15E.EPS

HART device

ProSafe-RS

HART I/OModule

SCS

SENG

Figure ProSafe-RS System Configuration

Note:- PRM client and SENG can run on the same PC.PRM server or Field Communication Server cannot run on the PC in which SENG is installed.

7


Control Network connection via HART Module in STARDOM System

HMI Client

FCN/FCJ

HMI ServerData Server

HART I/O module

HART devices configurator

HART device

OPC Server

Control Network

Ethernet

FCN

PCPRM Client

PCPRM ServerField Communication Server

Logic designer Resource ConfiguratorEnginnering toolDevice Management tool

Controller

VDS/HMI PRM

PSU NFAI141

CPU NFAI841

NFAI835

NFAI135

F11E.EPS

Figure: Control Network connection via HART Module in STARDOM System


GS 33Y05Q10-32E July 26, 2006-00

Serial port of Field communication server connection via Multiplexer (FCS for RIO)The field communication server can communicates with HART devices via HART Multiplexer connected with serial ports ofField communication server.

Ethernet


PRM ClientPRM Server

V net

RIO bus

F05E.EPS

FCS

AAM11AAM11

HIS/ENG

HART Multiplexer(commercially available)

Slave No.2

Slave No.1

Master

RS CommunicationRS-485

(*1)*1: RS-232C/RS-485

converter

DEV1

4-20 mA HART Digital Signals

HART DevicesAdapter board

DEV2

Figure Serial Port Connection via HART Multiplexer (Parallel Connection and Two-way Data Flow)Note: PRM server, PRM client, and Field communication server can run on the same PC.

9


Serial port connection via HART Multiplexer (For using P+F Multiplexer)P+F Multiplexer allows you to construct a stand-alone system as follows;

Ethernet


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)

F06E.EPS

Directly connectedto Master

HART Devices

Connected to Slave

PRM Server

255 (device) x 31 (Master) = 7,905 (Maximum Connectable Field Devices)

Figure An Example of P+F Multiplexer Connection

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

10

All Rights Reserved. Copyright 2006, Yokogawa Electric Corporation

GS 33Y05Q10-32E July 26, 2006-00

Serial port connection via HART Multiplexer (For using MTL Multiplexer)MTL Multiplexer allows you to construct a stand-alone system as follows;

Ethernet



BPHM64 (One MTL4841-PRM and four MTL4842s are installed)

RS-485Field

terminals(HCU16)

(*1)


F08E.EPS

PRM Server



HART Multiplexer(Master No.31, Slave No.1-4)

HART Multiplexer(Slave No.5-8)

Max.16devices

HART Multiplexer(Slave No.13-16)

BPHM64 (Four MTL4842s are installed)

16 (device) x 16 (slave) x 31 (Master) = 7,936 (Maximum Connectable Field Devices)

Figure: An Example of MTL Multiplexer Connection

11


Serial port connection via HART Multiplexer (For using ELCON Multiplexer)ELCON Multiplexer allows you to construct a stand-alone system as follows;

Ethernet



HPSM/32/MM-01 (MUX2700 is installed)

RS-485(*1)


F09E.EPS

PRM Server

HART Multiplexer(No.1)



Max.32devices

32 (device) x 31 (Master) = 992 (Maximum Connectable Field Devices)

Figure: An Example of ELCON Multiplexer Connection

12


GS 33Y05Q10-32E July 26, 2006-00

Serial port connection via HART Multiplexer (for using STAHL Multiplexer)STAHL Multiplexer allows you to construct a stand-alone system as follows;

Ethernet

PRM Client


PRM Client

F14E.EPS

PRM Server

Max.32devices

*1: RS-232C/RS-485 converter; type 9185/12-45-10. recommended*2: Up to 9 COM ports can be used*3: RS-232C/RS-485 converter; type 9185/12-45-10. recommended; for Zone 1/Div 1: type 9185/11-35-10.*4: RS-485 Repeater, type 9185/12-45-10. recommended; for Zone 1/Div 1: type 9185/11-35-10.

HART Multiplexer type 9192(No.1)

with pac-Carrier type 9195 and signal isolatorsmax 32 channels

32 (device) x 31 (HART MUX) = 992 (Maximum Connectable Field Devices)

RS-485 RS-485

HART Remote I/O Input/Output(No.2)

with type 9461, 9466modules

HART Remote I/O Input/Output(No. 31)



with HART connection board type 9196max 32 channels

IS pac

RS-485

RS-485

(*1)(*2)

(*3)(*2)

(*1)(*2) (*4)


with HART connection board type 9196max 32 channels

Max.128devices

HART Remote I/O Input/Output(No.1)


8 (device) x 16 (Remote I/O modules) x 31 Remote I/O = 3968 (Maximum Connectable Field Devices)

I.S. 1

Figure: An Example of STAHL Multiplexer Connection

13


FUNCTION SPECIFICATIONS Organization of FunctionsThe following figure shows organization of functions.

Device Navigator

PRM

Maintenance Information Management

Audit Trail Management

Adjustment and Diagnosis

Other Functions

Plant ViewNetwork ViewClass ViewCustom View

Device MasterInspection MemoInspection ScheduleParts ListLink to Document

Parameter Tuning and ComparisonFF DD Menu WindowDTM WorksDeviceViewerCalibration Management (Option)

Operation LogEvent Log of DeviceInspection LogRecord filtering

PRM Advanced Diagnosis (Option)

BrowserSecurityExportSelf-documentationPLUG-IN ApplicationDevice TemplateDatabase Maintenance ToolPRM System BackupOnline Manual

Diagnostic NavigatorAcquisition NavigatorPRM Advanced Diagnosis Application (PAA)Data Acquisition FunctionDevice Diagnosis Data HistorianGeneral-purpose Diagnosis Tool

Maintenance Alarm

Message AcquisitionDevice PatrolFiltering

PRM Advanced Diagnostic Application SoftwareDevelopment Kit (Option)

F03E.EPS

Figure: Organization of Functions

14


GS 33Y05Q10-32E July 26, 2006-00

Device NavigatorThe Device Navigator provides Plant View, Network View,Class View and Custom View.Each view displays arrangement of devices, in hierarchicalExplorer-like format. These views can display the devicestatus icon using a maintenance alarm function, thusallowing visual identification of device status. For a devicewith an unconfirmed maintenance alarm, an unconfirmedalarm icon is also displayed.User access to the hierarchy of the device navigator canbe restricted, which will prevent the person who is not incharge of the device from operating the device by mistake.

Plant ViewDisplays the equipment which makes up the plant, andshows its place in the plant hierarchy, in hierarchicalExplorer-like format. You can manage plant organizationintuitively, based on P & ID diagrams. Unused devices inthe plant can be managed by putting them in the SpareFolder, and devices which have failed or are undermaintenance can be placed in the Off-Service (Out ofService) Folder.Network ViewDisplays position of device, related to field networkphysical configuration, in an Explorer-like hierarchicalview. The mark next to the device icon shows thecommunication status and alarm status of the device thecolor of the mark changes if the device fails, so users havean immediate visual view of operating status. Devicestatus and device communication status can also bedisplayed.

Class ViewDisplays devices in an Explorer-like hierarchical view grouped by supplier, model, and revision. For deviceswhich have failed or are under maintenance, you cancheck the (e.g. spares) status of devices of the same typeat a glance. Device templates can be created with thisClass View.

Custom ViewDisplays devices in the hierarchy structure freely createdby users, in an Explorer-like hierarchical view.Devices can be classified according to persons in charge,inspection and replacement schedule, operating state, andfailure state.

Maintenance Alarm FunctionThis function provides a message system for maintenanceinformation and advice guidance. The function transmitsinformation necessary for maintaining devices to mainte-nance personnel to help them in the work to be done. Thefunction can not only transmit device event messages butalso add necessary information, such as phenomena,causes, measures, etc., to these messages.The following functions are provided to strengthen themaintenance information.

Message Acquisition Acquires field device events (for FOUNDATION fieldbus,FF) or events acquired by the CENTUM/STARDOMsystem. User-defined information (message priority level,object information, phenomena, causes, measures, etc.) isautomatically added to raw event information for alarms inPRM. Alarms are sent to an alarm filtering function.

Device PatrolAcquires self-diagnosis parameter data from field deviceswith diagnosis information and adds used-definedinformation (message priority level, object information,phenomena, causes, and measures) to acquired data toprovide alarms in PRM. These alarms are then transmittedto an alarm filtering function. Data are acquired periodicallyor on demand. Necessary information can also beobtained from devices from which no events are issued.

Filtering FunctionAlarms issued through such functions as the messageacquisition, device patrol or advanced diagnostic applica-tion, and from messages generated by key entries can befiltered to change notification messages on a user-by-userbasis.

Maintenance Information ManagementManages the maintenance information of all devices.

Device MasterManages an inventory of devices. You can display a list ofall devices, or detailed information on a single device. Fordevices with communications functions, the device masterbasic information is automatically created through devicerecognition and registration (Plug and Play).Inspection MemoMaintains historical records of device inspection memo,and malfunctions. Moreover, maintenance personnel cansave notes about how a failure was handled, as well aswarnings or reminders about maintenance check items, inthe historical record. This can apply to inspection patrolreports based on a PRM user.

15


Inspection ScheduleManages inspection schedules (checking, tuning, calibra-tion, etc.) for each device.Parts ListA device may consist of several parts; the parts listdisplays attributes of each part, and stock information.Enhances efficiency of repair and parts replacement work.For Yokogawa field devices (FF-H1 and HART devices),specific templates are provided.

Link to DocumentThis can display information such as configuration (e.g. P& ID and control drawings), exploded views, onlinemanuals, and graphics, as desired. You can access anddisplay this device-related information using the tag nameas a key. You can also use a URL to access a documentserver connected via Ethernet.

Audit Trail ManagementThis manages and displays the entire operating historyand historical inspection data carried out on a PRM client,and device alarm events using maintenance alarmfunctions as historical messages. A list of these historicalmessages can be displayed in chronological order or on adevice priority level and on a message priority level. Inaddition, device IDs and tag names allow the filtering ofthese messages.

Adjustment and Diagnosis FunctionsSupports device online tuning and diagnostic functions.

Parameter Tuning and ComparisonOnline display and setting of device parameter. Comparesstored device historical records with current device data.Switching of device operating conditions, and resetting topast values, while comparing current and past values.Can upload device data at any time, and store it in thedatabase. A collective upload function that can upload allthe connected devices at a time is also supported.

Tool For Foundation fieldbus

Can switch to DD Menu Window and DeviceViewerWindowDD Menu: Using the Method of DD files provided by a

vendor enables to perform Tuning andDiagnosis. The specifications are depen-dent on field devices.

DeviceViewer: DeviceViewer is a PLUG-IN Applicationthat displays the self-diagnosis result of FF-H1 devices. In many cases upper applica-tion program detects errors in devices byreading multi-parameter, containing the self-diagnosis result, saved in FF-H1 devices. Inthe case of Yokogawa FF devices,DeviceViewer displays not only the self-diagnosis result by reading parameters butalso the data displayed on the FF-H1devices LCD, such as error messages, inuser-friendly format. This allows operatorsto monitor the connected devices from PRMwithout viewing a LCD of field devices.

For HARTCan switch to DTM Works and Device Viewer.DTM Works: DTM in accordance with FDT1.2 specifica-

tions can be started from PRM client.DeviceViewer: The device viewer supports the HART

Device, either. It displays the self-diagnosishardware status and configuration status ofthe HART Device.

Calibration ManagementThe PRM database manages equipment calibration data.Calibration results are registered in databases, andcalibrated values, errors and pass or fail (judgment) maybe displayed. The calibration management functions canrequire the administrator to acknowledge (approve)calibration results. After such acknowledgement ofcalibration results, only the administrator can change theresults.The operation history management functions retain arecord of all downloading and uploading of calibrationdata.If you use the Documenting Calibrator, you can use it todownload or upload calibration data. In addition, calibra-tion results are automatically stored in the database. (*1)

*1: Connection to the Documenting Calibrator is anoptional extra.

16


GS 33Y05Q10-32E July 26, 2006-00

Other FunctionsBrowserCan search for devices using device attribute informationsuch as device ID, device tag name, device tag comment,block name, or parameter value.

SecurityDuring maintenance of field devices, restricts operation tospecific user(s) or restricts range of operations permitted to prevent system trouble due to operator errors, and tomaintain system security.The user name and operation record of the logged-inoperator is recorded in the operation history. User Groupcan be used to assign user privileges to groups of users(i.e. restrict rights) according to job function.Moreover, the Device Security Function allows the devicenavigator to display devices only for the specific group.

ExportCan output a list of all devices (such as device ID, devicetag, and device tag comment) stored in the database to atext file in CSV format. You can use information managedwith PRM on facility management software and the like.

Self-documentationCan collectively print out data stored in the database inreport format. Device information is managed electroni-cally, and can be printed out on demand. Information oneach window can be printed out as individual reports, so areport can be printed out after maintenance work toprovide a maintenance work record.The following print properties can be edited: Printing range Table of contents Header/footer Cover pagePLUG-IN ApplicationThe software package provided by third-party devicevendors which is built into PRM system. The PLUG-INApplication runs on the client PC, and it accesses to fielddevices and database in PRM server via PLUG-INApplication Library.Yokogawa Electric supplies DeviceViewer and the PLUG-IN ValveNavi for Yokogawa Advanced Valve Positioner,YVP110 as a PLUG-IN application. This PLUG-INValveNavi helps users to easily calibration and diagnosethe YVP110.This PLUG-IN ValveNavi also supports Signature functionfor control valve diagnosis.The function is based on standalone ValveNavi (YVP20SYVP Management Software).For its functions, refer to the separate GS 21B04C50-01Efor Model YVP20S YVP Management Software.

Supported PLUG-INDeviceViewer:

FF-H1 devices:DPharp EJA Series: Digital Differential Pressure and

Pressure Transmitter, R2 or laterEJA for Software Download; R1 or laterDPharp EJX Series: Digital Differential Pressure and

Pressure Transmitter, R1 or laterYTA Series: Temperature Transmitter, R2 or laterDY, DYA digital YEWFLO, R1 or laterDY, DYA digital YEWFLO for Software Download, R1

or laterYEWFLO*E: Vortex Flow Meter, R2 or laterADMAG AE Series: Magnetic Flow Meter, R1 or

laterYVP110: Advanced Valve Positioner, R2 or laterYVP110 for Software Download: R1 or laterYPK110: Fieldbus-to-Pneumatic converter, R1 or

laterPH202F: 2-Wire Type pH Meter, R1 or laterSC202F: 2-Wire Type Conductivity Meter, R1 or

laterISC202F: 2-Wire Inductive Conductivity Meter, R1

or laterDAQSTATION DX Series, R3 or laterAXF: Magnetic Flowmeters R1 or laterRCCT3: R1 or laterEJX910: Multivariable Transmitter ,R1 or laterAV550G: Averaging Converter,R1 or laterD0202-F: Dissolved Oxygen Transmitter ,R1 or laterMICROPILOT M: Radar Level Transmitter (Endress

+ Hauser),R3 or laterPROSONIC M: Ultrasonic Level Transmitter

(Endress + Hauser),R3 or laterLEVELFLEX M: Guided Wave Level Transmitter

(Endress + Hauser) ,R3 or laterPromag53: Magnetic Flowmeter (Endress + Hauser)

,R2 or laterPromass83: Mass Flowmeter (Endress + Hauser):

,R2 or laterProsonicFlow93: Ultrasonic Flowmeter (Endress +

Hauser) ,R1 or laterFVP: Valve Positioner (Dresser), R2 or laterFVP for Software Download: R1 or laterDVC5000f: Digital Valve Controller Fisher, R8 or R9)FF-01: Valve Actuator, R2FP302: Fieldbus to Pressure Convertor (SMAR),

R4 or later5081C/T: Conductivity Transmitter (Rosemount

Analytical), R1 or later5081pH: Conductivity Transmitter (Rosemount

Analytical), R1 or later848T: Eight Input Temperature Transmitter

(Rosemount Inc.), R4644HF: Temperature Transmitter (Rosemount

Inc.), R1 or later752: Remote Indicator (Rosemount Inc.), R13051S: Pressure Transmitter (Rosemount Inc.),

R14 or later3144P: Temperature Transmitter (Rosemount

Inc.), R1 or later

17


8800: Vortex Flowmeter (Rosemount Inc.), R5or later

8742: Mag Flow Meter (Rosemount Inc.), R4 orlater

MVD2700: Mass Flow Sensor (Micro Motion), R3 orlater

3244MV: Temperature Transmitter (RosemountInc.), R5 or later

BA488: Fieldbus Display (BEKA), R1 or laterHART devices:

DPharp EJA Series: Digital Differential Pressure andPressure Transmitter, R1 or later

DPharp EJX Series: Digital Differential pressure andPressure Transmitter, R1 or later

DY, DYA digital YEWFLO, R2 or laterYTA: Temperature Transmitter ,R2 or laterEJX910: Multivariable Transmitter ,R1 or laterAV550G: Averaging Converter,R1 or laterAXFA11: Magnetic Flowmeter Remote Converter ,R1

or laterAXFA14: Magnetic Flowmeter Remote Converter ,R1

or laterPLUG-IN ValveNavi for YVP110 (Rev. 2.1 or later)

Device Template FunctionTemplates in which device information is freely defined aresupplied. These templates can simplify device setting inengineering work.

Database Maintenance ToolThe PRM database capacity increases as the number ofdevices increases. If the operation history and parameterhistory are used for an extended period of time, largequantities of historical data are stored. An increase in thedatabase will have a bad effect on the PRM performance.The database maintenance tool optimizes large databasesto enable effective operation of the PRM.

Online ManualAll instruction manuals are provided in PDF format on CD-ROM. This enables you to view and print the electronicinstruction manuals on-demand.

PRM System BackupPRM provides a simple tool to back up data to meet userenvironments. This tool can back up registry information,PRM databases, advanced diagnosis databases, etc.

18


GS 33Y05Q10-32E July 26, 2006-00

MULTI-SERVER SWITCHOVERThe multi-server switchover functions are used for integrated management of multiple plants. Server Set means a set offield communication servers and PRM servers to which the PRM client is connected. Using a Server Set concept, you canswitch from one Server Set to other Server Set. Server sets are user-defined before use. This allows centralized manage-ment of the facility management data from multiple remote plants.It is also possible to connect PRMs in STARDOM and PRMs in CENTUM system on same Ethernet.

Ethernet

Ethernet

Router

V net

Server Set A

PRMClient

PRM Clientwith Multi-ServerSwitchover function

F07E.EPS

PRMServer

Switchover of Server Set

Field Communication Server

HIS

FCS

Ethernet

V net

Server Set B

PRMClient

PRMServer

Field Communication Server

HIS

FCS

Router

Figure: Multi-Server Switchover

19


Supported FunctionsAll functions can be performed for Foundation fieldbus devices, but there are some restrictions for HART devices.

Table Supported Functions

Device NavigationFunction

Audit Trail Management Function

Adjustment and Diagnosis

Other Functions

HART devices 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 DeviceViewer for Fieldbus. DTM Works and DeviceViewer 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 ViewClass View

Plug_&_Play

Inspection Memo

Parameter Tuning and Comparison

Status Display

Inspection ScheduleParts List

Browse FunctionSecurityPrintingPLUG-IN Application

Calibration

Link To DocumentParameter History

Device EventMessage

Operation History

Tool

Inspection MemoHistory

Register from Host_File_Set

Device Master

Specification RemarksFF-H1 HARTConventionalDevices(*1)Function

T05E.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.

20


GS 33Y05Q10-32E July 26, 2006-00

OPERATING ENVIRONMENT Hardware RequirementsThe necessary amounts of main memory and disk space depend on the number of devices registered. This section dis-cusses the minimum hardware requirements when no more than 3,000 devices are connected. If more than 3,000 devicesneed to be connected, consult Yokogawa.

PRM ServerIBM PC/AT-compatible: See the table below.Main memory: See the table below.Disk capacity: See the table below.Other requirements:

DAT drive (for backup).Ethernet card

Display: 256 colors or more are mandatoryPRM Server Hardware Requirements (without Advanced Diagnosis Server)

Number of Devices

T20E.EPS

300 units or less 1000 units or less 3000 units or less

CPU Pentium 1GHz or higher required

Pentium 1GHz or higher requiredPentium 42.8GHz or higher recommended

Pentium 42.8GHz or higher requiredXeon Dual2.8GHz or higher recommended

Main storage capacity 512MB or greater required 512MB or greater required1GB or greater recommended1GB or greater required2GB or greater recommended

Disc capacity 3GB or greater free area5GB or greater free area requiredHigh-speed disc such as SCSI and RAID recommended

10GB or greater free area requiredHigh-speed disc such as SCSI and RAID recommended

PRM database (*1) 600MB 2 GB 6 GB

*1: Device database capacity indicates disc capacity required for a year. It is calculated based on the assumption that the workupdating parameter value on a parameter comparison window and saving it is done for five times in a year for every block ofevery device.

For hardware requirements for servers with advanced diagnosis, refer to GS 33Y05Q21-32E.PRM Client

IBM PC/AT-compatible: Pentium 1 GHz or higherMain memory: 256 MB or greater, 512 MB or greater recommended.Disk capacity: At least 2 GB must be free.Other requirement: Ethernet cardDisplay: 1024 x 768 (256 colors) or more are mandatory

Field Communications ServerPC: IBM PC/AT-compatibleMain memory: See the table below.Disk capacity: See the table below.

Main Storage Capacity and Communication Device of Field Communication Server

T21E.EPS

CS 1000/CS 3000 connection systemProSafe-RS connection system STARDOM connection system

Main storage capacity

FCS/SCS 1~16 units (100+80 x number of FCS/SCS) MB or greater recommended FCS/SCS 17~48 units (1380+10 x number of FCS/SCS) MB or greater recommended

FCN/FCJ 1~16 units (100+60 x number of FCN/FCJ) MB or greater recommended FCN/FCJ 17~48 units (1060+5 x number of 16-FCN/FCJ) MB or greater recommended

Communication devices

Eternet card Control bus interface card (VF701, VI701)

Ethernet card

21


When installing PRM Server, Field Communication Server, and PRM Client in one PC:When all components coexists,

PC: IBM PC/AT compatibleCPU: The greatest CPU requirement among ones for each package or greaterMain Storage Capacity: The total of the required memory capacity for each package or greaterDisc capacity: The total of the required disc capacity for each package plus approximately 1 GB of virtual memory area or

greaterDisplay: 1024 x 768 256 colors or more

OPC Server (for STARDOM system)IBM PC/AT-compatible: Pentium 300 MHz or 400 MHz or faster recommendedMain memory: 256 MB or 512 MB or greater recommendedDisk capacity: There must be at least 1 GB of free space.Ethernet card: 100BASE-TX, 10BASE-T, 10BASE-5

Two communications devices are needed to separate the STARDOM information network from its control network.

HART MultiplexerWhen using P+F Multiplexer:

Multiplexer (Master): KFD2-HMM-16 (P+F) (*1)Multiplexer (Slave): KFD0-HMS-16 (P+F)Cable (connecting Master or Slave to terminal block): K-HM 26 (P+F)Cable (connecting Master to Slave): K-HM 14 (P+F)Terminal Block: FI-**-PFH-Y... (** is specified depending on users need) (P+F)Power Supply: KFD2-EB2 (P+F)Power Rail (an equipment to be used for fixing Multiplexer to a terminal board)Recommended RS-232C/RS-485 Converter:

IC108A (BLACK BOX)MA-45 (Westermo)

Cable (connecting Master to converter): Twisted pair cable (category 5)Cable (connecting converter to PC):

EVNBMC (BLACK BOX)DB25 male DB9 female (inch screw thread), Straight connection

*1: Number of Multiplexer (Master): Max.31Number of connectable devices: Max.255 per one Master

When using MTL Multiplexer:Multiplexer (Master): MTL4841-PRM (MTL)

MTL4841 (standard type) and MTL4841-AMS cannot connect to PRM.Multiplexer (Slave): MTL4842 (MTL)Back plane: BPHM64 (MTL)HART connection Unit (16ch HART Inputs/Outputs ):

HCU16 (MTL)Recommended RS-232C/RS-485 Converter:


Cable for connection between Master and Slave (4 or less):Not required (connectable on BPHM64)

Cable for connection between Master and Slave (5 or more):Connector type:10 way DIN41651 bump polarizedCable: 0.05 inch pitch standard ribbonMaximum length: 4 mCable for connection between Master and Master:

Not specially specified (normal RS-485 cable is used)Cable for connection between BPHM64 and HCU16:Connector type: 20 way DIN41651 bump polarizedCable: 0.05 inch pitch standard ribbonMaximum length: 15 m

22


GS 33Y05Q10-32E July 26, 2006-00

When using P+F ELCON Multiplexer:Multiplexer (Master and Slave):

MUX2700-E (P+F ELCON) or MUX2700-G (P+F ELCON)Board for connection: HPSM/32/MM-01 (P+F ELCON)Recommended RS-232C/RS-485 Converter:


Cable: Only normal RS-485 cable is required

When using R. STAHL HART Multiplexer IS pac:Multiplexer: 9192/32-10-10IS pac Carrier: 9195/08H-***-*** or 9195/16H-***-*** or HART Connection Board: 9196/**H-XX0-***Cable (connecting multiplexer to IS pac carrier or connection board): with carrier or board includedCable (connecting HART Multiplexer to converter): shielded twisted pair; plug = Sub-D 9, female; max length = 1200 mRecommended RS-232C / RS-485 converter, suitable for zone 2 / div 2 installation: 9185/12-45-10*Cable (connecting converter to PC): Type F interface cable; max length = 15 m

When using R. STAHL Remote I/O I.S. 1 with ServiceBus:Analog Input or Analog Output Modules HART: 9461/12-08-** or 9466/12-08-11; CPU & Power Module 9440/**Cable (connecting CPU and power module to converter): shielded twisted pair; plug = Sub-D 9, female; max length = 1200

mRecommended RS-232C / RS-485 converter: 9185/12-45-10*RS-232C / RS-485-IS converter for remote I/O zone 1 / div 1 installation: 9185/11-35-10*Cable (connecting converter to PC): Type F interface cable; max length = 15 m

When using simplified system for HART:The following hardware is used VIATOR RS232 HART Interface Model 010001 (MACTek)

Software RequirementsPRM ServerOS:

Windows Server 2003 Service Pack 1Windows Server 2003 R2Windows XP Professional Service Pack 2

Internet Explorer 5.0 or later versionMicrosoft SQL Server (Runtime) is used as a database software and is included in a software media for Plant Resource

Manager.PRM ClientOS:


Software for document: Adobe Reader 6.0, Adobe Reader 7.0.0Field Communications ServerOS:


Vnet/IP or V net (CS 3000) communications driver (*1)VL net (CS 1000) communications driver (*1)

*1: These communications drivers and VF701 (or VI701) are not required when communicating with HART devices via Multiplexer.(without connecting CENTUM system.)

23


Software requirements for connected systemCENTUM CS 1000 / CS 3000

CS1000/CS 3000: R3.01 or laterR3.02 or later to support HART devices

Exaopc OPC interface package (for HIS): R3.01or laterR3.02 or later to support HART devicesR3.07 or later to notify HIS of operatior guide messageR3.08 or later for Consolidated Alarm Management Software for HIS (CAMS for HIS) consolidation

STARDOMSTARDOM: R1.40 or later

R1.60 or later to support HART devicesFCN/FCJ OPC Server for Windows: R1.40 or later

R1.60 or later to support HART devicesProSafe-RS

ProSafe-RS: R1.02 or laterCENTUM CS 3000: R3.06 or laterExaopc OPC interface package (for HIS): R3.06 or later

3.07or later to notify HIS of operatior guide messageR3.08 or later for CAMS for HIS consolidation

24


GS 33Y05Q10-32E July 26, 2006-00

MODELS AND SUFFIX CODESPRM Basic Set (for new installation)

DescriptionModel PRMSET Plant Resource Management Basic Set

Suffix Codes-S Basic Software License and Media fee 1 Always 1 1 English version

Option Codes

/N0025 Maximum number of connected devices: 25/N0100 Maximum number of connected devices: 300/N1000 Maximum number of connected devices: 1000

T06E.EPS

/N3000 Maximum number of connected devices: 3000

Note: The PRM Basic Set includes a Plant Resource Management Client, a Plant Resource Management Server, a Field Communica-tions Server, Software Media for Plant Resource Manager and Electronic Instruction Manual Media for Plant Resource Manager.

PRM Server (for new installation)

DescriptionModel SSS7700 Plant Resource Management Server [Media model: SSSSM02-C11]

Suffix Codes

-S Basic software license-C Multiple software licenses (for 2 or more) 1 Always 1 1 English version

Option Codes/N0300 Maximum Number of connected devices: 300/N1000 Maximum Number of connected devices: 1000/N3000 Maximum Number of connected devices: 3000

T01E.EPS

Note: A PRM server is required for each project.Note: This package cannot be installed in HIS PC. Prepare a PC separate from HIS PC.Note: Exaopc OPC Interface Package for HIS (LHS2411) is required to acquire device events.

PRM Server (for expansion)

DescriptionModel SSS7700 Plant Resource Management Server [Media model: SSSSM02-C11]

Suffix Codes-A Software license for additional devices 1 Always 1 1 English version

Option Codes

/N0003 Expand maximum number of connected devices: 25 to 300/N0010 Expand maximum number of connected devices: 25 to 1000 /N0310 Expand maximum number of connected devices: 300 to 1000

T02E.EPS

/N0030 Expand maximum number of connected devices: 25 to 3000 /N0330 Expand maximum number of connected devices: 300 to 3000 /T01 Add 1000 units of connected devices/T02 Add 2000 units of connected devices

Note: This package cannot be installed in HIS PC. Prepare a separate PC from HIS PC.Note: Exaopc OPC Interface Package for HIS (LHS2411) is required to acquire device events.Note: When you have 1000 unit or more of the connected devices, you can add 1000 or 2000 units furthermore, but the maximum

number must be 3000 units.

25


PRM Client

DescriptionModel SSS7710 Plant Resource Management Client [Media model: SSSSM02-C11]

Suffix Codes


T03E.EPS


DescriptionModel SSS7720 Field Communications Server [Media model: SSSSM02-C11]

Suffix Codes


T04E.EPS

Note: The function for connecting with FOUNDATION fieldbus devices and HART devices is included in the basic specification.Note: This package cannot be installed in HIS PC. Prepare a PC separate from HIS PC.

Any or all Plant Resource Manager (Field Communications Server, Database Server, and Client) can be installed on a singlePC.

Intelligent Calibrator Interface for PRM Client

DescriptionModel SSS7711 Documenting Calibrator Interface [Media model: SSSSM02-C11]

Suffix Codes

-S Basic software license 1 Always 1 1 English version

T11E.EPS

Option Code /FLK01 Calibrator type: Fluke 743B/744

Note: This package can be installed with basic software license in two or more PRM client machines.Software Media for Plant Resource Manager

DescriptionModel SSSSM02 Software Media for Plant Resource Manager

Suffix Codes-C Supplied media: CD-ROM 1 Always 1 1 English version

T13E.EPS

Note: Electric Instruction manual Media for this package is SSSSD02.

26


GS 33Y05Q10-32E July 26, 2006-00

Electronic Instruction Manual Media for Plant Resource Manager

DescriptionModel SSSSD02 Electronic Instruction Manual Media for Plant Resource Manager


T08E.EPS

Note: To install this media, the software media (SSSSM02) is required.Note: No license is required to use the electronic instruction manual media.

PLUG-IN ValveNavi

DescriptionModel SSS7750 PLUG-IN ValveNavi [Media model: SSSAM02-C11]

Suffix Codes

Option Code

-C Multiple software license (for 2 or more) 1 Always 1 1 English version

T09E.EPS

-S Basic software license

/FF-H1 For FOUNDATION fieldbus devices (*1)

Note: This package runs on the personal computer with Plant Resource Manager (Client) (SSS7710).Note: This software cannot support HART devices.*1: To connect with FOUNDATION fieldbus devices, specify the option code /FF-H1.

PLUG-IN Application Media for Plant Resource Manager

DescriptionModel SSSAM02 PLUG-IN Application Media for Plant Resource Manager


T10E.EPS

Note: Electronic instruction manual is included in this media.FCN/FCJ OPC Server for WindowsPlease see GS 34P02Q61-01E for detail.

27


VERSION UPGRADE SOFTWARE LICENSE FROM R2 TO R3Plant Resource Manager (Server) (for Upgrading from R2 to R3)

DescriptionModel SSS7700RU Plant Resource Manager (Server ) Upgrade [Media model: SSSSM02-C11]

Suffix Codes

-S Basic software license-C Multiple software license (for 2 or more) 1 Always 1 1 English version

Option Codes/N0300 Maximum number of connected devices: 300 /N1000 Maximum number of connected devices: 1,000/N3000 Maximum number of connected devices: 3,000

T22E.EPS

Note: Purchase upgrading license from R2 to R3 in accordance with every license (basic as well as multiple) you purchased in R2.Specify the number of connected devices that you purchased in R2 including added ones.

Note: Option Code /N0100 (maximum number of connected devices: 100 units) in R2.10 or before is expanded to maximum 300 unitsof connected devices in R3. When you purchased /N0100 in R2, specify /N0300.

Plant Resource Manager Client (for Upgrading from R2 to R3)

DescriptionModel SSS7710RU Plant Resource Manager (Client) Upgrade [Media model: SSSSM02-C11]

Suffix Codes


T23E.EPS

Note: Purchase upgrading license from R2 to R3 in accordance with every license (basic as well as multiple) you purchased in R2.Documenting Calibrator Interface for PRM Client (for Upgrading from R2 to R3)

DescriptionModel SSS7711RU Documenting Calibrator Interface Upgrade [Media model: SSSSM02-C11]

Suffix Codes-S Basic software license 1 Always 1 1 English version

Option Codes FLK01 Calibrator type: FLUKE 743B/744T24E.EPS

Note: Purchase upgrading license from R2 to R3 in accordance with every license (basic as well as multiple) you purchased in R2.Field Communications Server (for Upgrading from R2 to R3)

DescriptionModel SSS7720RU Field Communications Server Upgrade [Media model: SSSSM02-C11]

Suffix Codes


T25E.EPS

Note: Purchase upgrading license from R2 to R3 in accordance with every license (basic as well as multiple) you purchased in R2.Note: From R3, Field Communications Server includes HART devices as standard function. (Field Communications Server includes

both FF-H1 and HART communications functions). In upgrading license from R2 to R3 it is not necessary to add HART option(There is no HART option).

28


GS 33Y05Q10-32ESubject to change without notice.

July 26, 2006-00

Plant Resource Manager Basic Set (for Upgrading from R2 to R3)

DescriptionModel PRMSETRU Plant Resource Manager Basic Set Upgrade

Suffix Codes

-S Basic software license includes upgrades and media fees 1 Always 1 1 English version

Option Codes/N0300 Number of connected device: 300 units or less/N1000 Number of connected device: 1,000 units or less/N3000 Number of connected device: 3,000 units or less

T26E.EPS

/N0025 Number of connected device: 25 units or less

Note: Basic set (for upgrading from R2 to R3) is used when PRMSET of R2 was ordered. Specify the number of connecting devicesame as the number you purchased in R2.

Note: Basic set includes 1 Plant Resource Manager (Client), 1 Plant Resource Manager (Server), 1 Field Communications Server,software media for Plant Resource Manager and Electronic Instruction Manual Media for Plant Resource Manager.

Note: Option Code /N0100 (maximum number of connected devices: 100 units) in R2.10 or before is expanded to maximum 300 unitsof connected devices in R3. When you purchased /N0100 in R2, specify /N0300.

ORDERING INSTRUCTIONSSpecify model and suffix codes.

TRADEMARKS PRM is a registered trademark of Yokogawa Electric Corporation in the United States and Japan. CENTUM is a registered trademark of Yokogawa Electric Corporation. Pentium is a registered trademark of Intel Corporation. Ethernet is a registered trademark of XEROX Corporation. Windows is a registered trademark of Microsoft Corporation in the United States and/or other countries. Foundation fieldbus is a registered trademark of Fieldbus Foundation. Adobe and Acrobat are registered trademarks of Adobe Systems Incorporated. HART is a registered trademark of the HART Communication Foundation. STARDOM is a trademark. Other product and company names appearing in this document are trademarks or registered trademarks of their respective

holders.