General Specifications

Transcription

1 General Specifications Models SSS7700, SSS7710, SSS7720 Plant Resource Manager GENERAL PRM is a dynamic software tool that supports the daily business activities of maintenance personnel. This Plant Resource Manager Package for the digital network era of fieldbus efficiently handles field device management and maintenance work for the FOUNDATION fieldbus 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 management of conventional analog, FOUNDATION fieldbus and HART devices. PRM R2.02 or later version supports communication with HART devices. FUNCTION SPECIFICATIONS Plant Resource Manager (PRM) consists of the following components: Uses the popular, industrial-strength Oracle database. Maintains a historical record of device parameters, Inspection Schedule and Inspection Memo. Implements centralized management of device information such as the device list, inspection record and schedule, usercreated electronic documents, and parts lists. Can generate the best suited maintenance alarms inside or outside of the PRM system using a maintenance alarm function (*1). This function can acquire the information necessary to diagnose the statuses of various field devices that have been defined and registered in advance. This function can not only acquire device events (e.g., device block alarms) but also generate maintenance alarms for necessary information (phenomena, causes, action) added to acquired device events, and can distribute this maintenance alarm information to personnel who want it. *1: Supported by PRM R2.10 or later version. 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 statuses with maintenance alarm functions, monitors communication error, monitors advanced diagnosis of device, process interface diagnosis and Unit diagnosis, etc. by PRM Advanced Diagnosis application, allows tuning of device parameters, and performs device diagnosis (DD Menu, DeviceViewer, PLUG-IN Application, etc.). Online device adjustment/setting from the can be performed on the screen with the same user interface as that of on-site adjustment setting tool FieldMate. 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 icons according to the screen size or on the user s request. In addition to Maintenance Alarm Function and standard diagnostic functions, Yokogawa provides Acquisition Navigator and Diagnostic Tool as components of the PRM Advanced Diagnosis package. With these software components, you can carry 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 field devices 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 Yokogawa s product, DeviceViewer (*1) (*2) and PLUG-IN ValveNavi (*1). can start up a calibration tool or a diagnosis tool that is uniquely designed by device vendors as PLUG-IN Application. *1: PRM R2.03 or later version supports the DeviceViewer for FOUNDATION fieldbus devices and PRM R2.06 or later version supports the DeviceViewer for HART-devices. *2: DeviceViewer is a build-in PLUG-IN Application for self-diagnostic of FOUNDATION fieldbus devices and HART devices into PRM Client. The way to use the product differs from regular PLUG-IN Application. To be able to run the DeviceViewer of a device from each vendor, definition files must be obtained from that device vendor. Yokogawa Electric Corporation , Nakacho, Musashino-shi, Tokyo, Japan Tel.: Fax.: Copyright Jan th Edition Nov.7,2005

2 2 Field Communications Server PRM 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 and in STAR- DOM System. Another one is Serial port connection via 3rd Vendor HART Multiplexer. For serial port connection, PRM supports HART multiplexers supplied from four vendors (P+F, MTL, ELCON and STAHL). HART modem and HART multiplexer can be connected to the multiple COM ports at the same time. By using serial port connection, PRM can 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 3rd vendor HART Multiplexer Interface to Computerized Maintenance Management System (Option) Plant Resource Manager (PRM) supports interface with MAXIMO, a Computerized Maintenance Management System (CMMS) provided by MRO Software, Inc. This enables PRM to connect with the CMMS and to provide information online. More effective maintenance operation can be achieved by this feature. For details of Interface to Computerized Maintenance Management System, see GS 33Y05Q20-31E SSS7730 Interface for CMMS. PRM Advanced Diagnosis (Option) PRM Advanced Diagnostic Server is an optional package available with PRM. It provides an environment for executing the diagnostic algorithm of field devices. With this package, you can directly acquire parameters from these devices at fixed intervals. 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 can easily create and execute diagnostic applications containing advanced diagnostic algorithms for process interface, loop and unit that have been difficult to realize with field devices alone. Note that PRM advanced diagnostic applications (PAA) are available as diagnostic applications initially provided by device vendors or third-party vendors. For details of PRM Advanced Diagnosis, see GS 33Y05Q21-31E SSS7740 PRM Advanced Diagnostic Server. Multi-server Switchover The scope of PRM management generally corresponds to a CS 1000/CS 3000 project or STARDOM project. However, if a wider range of integrated management is required, multi-server functions can be used to dynamically switch the PRM server that is referenced by a PRM client. This allows centralized remote monitoring of large-scale plants with some CENTUM projects.

3 3 SYSTEM CONFIGURATION A single database server is the unit for management (e.g. for search operations). At least one and one Field Communications 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 fieldbus CENTUM CS 3000 This section shows a large-scale system configuration for Plant Resource Manager. Oracle RDB CMMS (MAXIMO) HIS Exaopc O Interface for HIS Field Communications Server FF-H1 Host Interface H1 Fieldbus (for device adjustment) Coupler Terminator Vnet/IP bus 2 bus 1 FCU FCS FCS ALF111 ALF111 (in service) (stand-by) ESB bus EB401 (dual redundant) SB401 (dual redundant) Local Node HART I/O Module HART devices FieldMate H1 Fieldbus Terminator Coupler HIS : Human Interface Station FCS : Field Control Station FCU : Field Control Unit SB401 : ESB bus Interface (in Local Node) EB401 : ER bus Interface (in Local Node) ALF111 : Foundation Fieldbus Communication Module Field devices Figure: System Configuration (CENTUM CS 3000 system) F01E.EPS

4 4 CENTUM CS 1000 This section shows a small-scale system configuration for Plant Resource Manager. CMMS (MAXIMO) HIS Exaopc O Interface for HIS Ethernet Field Communications Server Oracle RDB FF-H1 Host Interface H1 Fieldbus (for device adjustment) Coupler Terminator VL net FCS ACF11 Terminator H1 Fieldbus Coupler HIS FCS ACF11 : Human Interface Station : Field Control Station : Foundation Fieldbus Communication Module Figure: System Configuration (CENTUM CS 1000 system) Field devices F02E.EPS

5 5 STARDOM This section shows a STARDOM configuration for Plant Resource Manager. The figure below is an example of connecting the STARDOM system to the PRM. Messages from the STARDOM controller are transmitted to the PRM server via the O server. FCN/FCJ O Server for Windows is needed in the system. VDS/HMI PRM HMI Client Logic designer Resource Configurator Enginnering tool Device Management tool HMI Server Data Server FCN/FCJ O Server Ethernet Field Communication Server FCN Controller Control Network PSU CPU NFLF 111 FCJ (with FF-H1 port) Terminator Terminator H1 Fieldbus Coupler H1 Fieldbus Coupler F10E.EPS Figure: STARDOM System Configuration Operating Environment PRM client and HMI client can run on the same. or Field Communication Server cannot run on the in which VDS is already installed. PRM server or Field Communication Server can run on the in which FCN/FCJ O server for Windows is installed. (PRM revision is R2.06 or later) The revision of FCN/FCJ must be R1.40 or later. Oct.4,

6 6 System Configuration When Connecting HART Four 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 Modem Vnet/IP or V net connection via HART Modules (FCS for FIO) in CENTUM System Field communication server communicates with HART devices via HART modules by using the on-demand communication functions of FCS. Oracle RDB CMMS (MAXIMO) Vnet/IP HIS/ENG Exaopc O Interface for HIS Field Communications Server (for device adjustment) HART Modem (VIATOR RS232 Interface) bus 2 bus 1 HART device FCS ESB bus HART I/O module (in service) HART I/O module (stand-by) HART devices DEV1 DEV2 Local Node SB401: ESB bus interface (in Local Node) EB401: ER bus interface (in Local Node) EB501: ER bus interface (in Remote Node) SB401 (dual-redundant) EB401 (dual-redundant) ER bus HART I/O module (in service) HART I/O module (stand-by) HART devices DEV1 Remote Node EB501 (dual-redundant) DEV2 F04E.EPS Figure Vnet/IP Connection via HART Modules (FCS for FIO) in CENTUM System Note: PRM server, PRM client, and Field communication server can run on the same.

7 7 Control Network connection via HART Module in STARDOM System VDS/HMI PRM HMI Client Logic designer Resource Configurator Enginnering tool Device Management tool HMI Server Data Server FCN/FCJ O Server Ethernet Field Communication Server FCN Controller Control Network PSU CPU NFAI 141 NFAI 841 NFAI 135 NFAI 835 HART I/O module HART devices configurator HART device Figure: Control Network connection via HART Module in STARDOM System F11E.EPS May 1,

8 8 Serial port of Field communication server connection via Multiplexer (FCS for RIO) Communicates with HART devices via HART Multiplexer connected with serial port of Field communication server. Oracle RDB CMMS (MAXIMO) Ethernet (*1) Field Communications Server *1: RS-232C/RS-485 converter HIS/ENG V net RS Communication RS-485 HART Multiplexer (commercially available) FCS RIO bus Slave No.2 Slave No.1 AAM11 AAM11 Adopter board HART Devices DEV1 DEV2 Master 4-20 ma HART Digital Signals F05E.EPS 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. May 1,

9 9 Serial port connection via HART Multiplexer (For using P+F Multiplexer) When using P+F Multiplexer, can connect as a stand-alone system configuration as follows. Oracle RDB CMMS (MAXIMO) Ethernet Field Communications Server (*1) RS-485 *1: RS-232C/RS-485 converter HART Multiplexer (Master No.1) HART Multiplexer (Master No.2) HART Multiplexer (Master No.31) Directly connected to Master HART Devices HART Multiplexer (Slave No.1) Connected to Slave 255 (device) x 31 (Master) = 7,905 (Maximum Field Devices) HART Multiplexer (Slave No.15) F06E.EPS Figure An Example of P+F Multiplexer Connection Note: PRM server, PRM client, and Field communication server can run on the same. May 1,

10 10 Serial port connection via HART Multiplexer (For using MTL Multiplexer) When using MTL Multiplexer, can connect as a stand-alone system configuration as follows. Oracle RDB CMMS (MAXIMO) Ethernet Field Communications Server (*1) RS-485 BPHM64 (One MTL4841-PRM and four MTL4842s are installed) Field terminals (HCU16) *1: RS-232C/RS-485 converter HART Multiplexer (Master No.1) HART Multiplexer (Master No.2) HART Multiplexer (Master No.31, Slave No.1-4) Max.16 devices BPHM64 (Four MTL4842s are installed) HART Multiplexer (Slave No.5-8) 16 (device) x 16 (slave) x 31 (Master) = 7,936 (Maximum Field Devices) HART Multiplexer (Slave No.13-16) F08E.EPS Figure: An Example of MTL Multiplexer Connection May 1,

11 11 Serial port connection via HART Multiplexer (For using ELCON Multiplexer) When using ELCON Multiplexer, can connect as a stand-alone system configuration as follows. Oracle RDB CMMS (MAXIMO) Ethernet Field Communications Server (*1) RS-485 HPSM/32/MM-01 (MUX2700 is installed) *1: RS-232C/RS-485 converter Max.32 devices HART Multiplexer (No.1) HART Multiplexer (No.2) HART Multiplexer (No.31) 32 (device) x 31 (Master) = 992 (Maximum Field Devices) Figure: An Example of ELCON Multiplexer Connection F09E.EPS May 1,

12 12 Serial port connection via HART Multiplexer (for using STAHL Multiplexer) When using STAHL Multiplexer, can connect as a stand-alone system configuration as follows. Oracle RDB CMMS (MAXIMO) Ethernet Field Communications Server (*2) (*1) RS-485 IS pac HART Multiplexer type 9192 (No.1) with pac-carrier type 9195 and signal isolators max 32 channels HART Multiplexer type 9192 (No.2) with HART connection board type 9196 max 32 channels 32 (device) x 31 (HART MUX) = 992 (Maximum Field Devices) HART Multiplexer type 9192 (No.31) with HART connection board type 9196 max 32 channels Max.32 devices (*2) (*3) RS-485 I.S. 1 HART Remote I/O Input/Output (No.1) with type 9461, 9466 modules HART Remote I/O Input/Output (No.2) with type 9461, 9466 modules HART Remote I/O Input/Output (No. 31) with type 9461, 9466 modules 8 (device) x 16 (Remote I/O modules) x 31 Remote I/O = 3968 (Maximum Field Devices) Max.128 devices (*2) (*1) RS-485 (*4) RS-485 *1: RS-232C/RS-485 converter; type 9185/ recommended *2: Up to 9 COM ports can be used *3: RS-232C/RS-485 converter; type 9185/ recommended; for Zone 1/Div 1: type 9185/ *4: RS-485 Repeater, type 9185/ recommended; for Zone 1/Div 1: type 9185/ F14E.EPS Figure: An Example of STAHL Multiplexer Connection May 1,

13 13 Simplified System for Device Adjustment The H1 Fieldbus can be connected directly to the by using the Fieldbus interface board of National Instruments (NI) Corporation. A simplified system for adjustment of the field devices without FCS can be constructed. If you use a card type Fieldbus interface card, a simplified system can be constructed even with a notebook. Field Communication Server Oracle RDB Terminator H1 Fieldbus Coupler Figure: System Configuration (Simplified system for FF-H1 device adjustment) Field devices F12E.EPS Moreover, the HART device can be connected to the easily by using the VIATOR RS232 Interface for HART of MACTek Corporation. A simplified system for adjustment of the HART Device can be constructed. RS-232C Field Communication Server Oracle RDB HART Modem (VIATOR RS232 Interface) Power Supply HART devices F13E.EPS Figure: System Configuration (Simplified system for HART device adjustment) May 1,

14 14 FUNCTION SPECIFICATIONS Organization of Functions The following figure shows organization of functions. PRM Plant View Network View Class View Custom View Device Navigator Maintenance Alarm Message Acquisition Device Patrol Filtering Maintenance Information Management Device Master Inspection Memo Inspection Schedule Parts List Link to Document Audit Trail Management Operation Log Event Log of Device Inspection Log Record filtering Other Functions Browser Security Export Self-documentation PLUG-IN Application Device Template Database Maintenance Tool PRM System Backup Online Manual PRM Advanced Diagnosis (Option) Diagnostic Navigator Acquisition Navigator PRM Advanced Diagnosis Application (PAA) Data Acquisition Function PRM Advanced Diagnosis Application Software Development Kit (Option) Interface to Computerized Maintenance Management System (Option) Adjustment and Diagnosis Parameter Tuning and Comparison FF DD Menu Window HART DD Menu Window HART Offline Parameter DeviceViewer Calibration Management (Option) F03E.EPS Figure: Organization of Functions

15 Device Navigator The Device Navigator provides Plant View, Network View, Class View and Custom View. Each view displays arrangement of devices, in hierarchical Explorer-like format. You can select devices and perform functions in these views. These views can display the device status icon using a maintenance alarm function, thus allowing visual identification of device statuses. For a device with an unconfirmed maintenance alarm, an unconfirmed alarm icon is also displayed. User access to the hierarchy of the device navigator can be restricted, which will prevent the person who is not in charge of the device from operating the device by mistake. Plant View Displays the equipment which makes up the plant, and shows its place in the plant hierarchy, in hierarchical Explorer-like format. You can manage plant organization intuitively, based on P & ID diagrams. Unused devices in the plant can be managed by putting them in the Spare Folder, and devices which have failed or are under maintenance can be placed in the Off-Service (Out of Service) Folder. In addition, device statuses using maintenance functions can be displayed. Network View Displays position of device, related to field network physical configuration, in an Explorer-like hierarchical view. The mark next to the device icon shows the communication status and alarm status of the device the color of the mark changes if the device fails, so users have an immediate visual view of operating status. Device statuses and device communication statuses using the maintenance functions can also be displayed. Class View Displays devices in an Explorer-like hierarchical view grouped by supplier, model, and revision. For devices which have failed or are under maintenance, you can check the (e.g. spares) status of devices of the same type at a glance. Device templates can be created with this Class View. Custom View Displays devices in the hierarchy structure freely created by users, in an Explorer-like hierarchical view. Devices can be classified according to persons in charge, inspection and replacement schedule, operating state, and failure state. Maintenance Alarm Function 15 This function provides a message system for strengthening maintenance information and advice guidance. The function transmits information necessary for maintaining devices to maintenance personnel to help them in the work to be done. The function can not only transmit device event messages but also add necessary information, such as phenomena, causes, measures, etc., to these messages. The following functions are provided to strengthen the maintenance information. Message Acquisition Acquires field device events (for FOUNDATION fieldbus, FF) or events acquired by the CENTUM/STARDOM system. User-defined information (message priority level, object information, phenomena, causes, measures, etc.) is automatically added to raw event information for normalized alarms in PRM. Normalized alarms are sent to an alarm filtering function. Device Patrol Acquires self-diagnosis parameter data from field devices with diagnosis information and adds used-defined information (message priority level, object information, phenomena, causes, and measures) to acquired data to provide alarms normalized in PRM. These normalized alarms are then transmitted to an alarm filtering function. Data are acquired periodically or on demand. Necessary information can also be obtained from devices from which no events are issued. Filtering Function Normalized alarms issued through such functions as the message acquisition, device patrol or advanced diagnostic application, and from messages generated by key entries can be filtered to prevent the notification of alarm event messages that are not in agreement with the specified conditions. It is also possible to change notification messages on a user-by-user basis. Maintenance Information Management Manages the maintenance information of all devices. Device Master Manages an inventory of all devices. You can display a list of all devices, or detailed information on a single device. For devices with communications functions, the device master basic information is automatically created through device recognition and registration (Plug and Play). No user entries are required. Inspection Memo Maintains historical records of device inspection memo, and malfunctions. Moreover, maintenance personnel can save notes about how a failure was handled, as well as warnings or reminders about maintenance check items, in the historical record. This can apply to online remote inspection patrol reports or field inspection patrol reports based on a PRM user.

16 Inspection Schedule Manages inspection schedules (checking, tuning, calibration, etc.) for each device. Parts List A device may consist of several parts; the parts list displays 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 Document This can display information such as configuration (e.g. P & ID and control drawings), exploded views, online manuals, and graphics, as desired. You can access and display this device-related information using the tag name as a key. You can also use a URL to access a document server connected via Ethernet. Audit Trail Management This manages and displays the entire operating history and historical inspection data carried out on a PRM client, and device alarm events from devices using maintenance alarm functions as historical messages. A list of these historical messages can be displayed in chronological order or on a device priority level and on a message priority level. In addition, device IDs and tag names allow the filtering of these messages; therefore, a specific device s operating history can be easily retrieved. Adjustment and Diagnosis Functions Supports device online tuning and diagnostic functions. Parameter Tuning and Comparison Online display and setting of device parameter. Compares stored device historical records with current device data. Facilitates safe switching of device operating conditions, and resetting to past values, while comparing current and past values for safety. Can upload device data at any time, and store it in the database. A collective upload function that can upload all the connected devices at a time is also supported. Tool For FOUNDATION fieldbus Can switch to DD Menu Window and DeviceViewer Window DD Menu: Using the Method of DD files provided by a vendor enables to perform Tuning and Diagnosis. The specifications are dependent on field devices. 16 DeviceViewer: DeviceViewer is a PLUG-IN Application that displays the self-diagnosis result of FF- H1 devices. In many cases upper application program detects errors in devices by reading multi-parameter, containing the selfdiagnosis result, saved in FF-H1 devices. In the case of Yokogawa FF devices, DeviceViewer displays not only the selfdiagnosis result by reading parameters but also the data displayed on the FF-H1 device s LCD, such as error messages, in user-friendly format. This allows operators to monitor the connected devices from PRM without viewing a LCD of field devices. For HART Can switch to DD Menu Window and HART Offline Parameters Window. These windows are equivalent to HART Handheld Terminal. DD Menu: Construe and execute the items of Menu in HART DD. Refer/set parameters or execute Method. Record Start/Stop of only this window as operation messages. The executed result of this window is not recorded in the database or the operation message. HART Offline Parameters: List and display Offline Parameters or Upload Variables described in HART DD. Change the parameter values. Record Start/Stop of only this window as operation messages. Specify a file for each device and save the parameter values; read the parameter values from the files. DeviceViewer: The device viewer supports the HART Device, either. It displays the self-diagnosis hardware status and configuration status of the HART Device. Calibration Management The PRM database manages equipment calibration data. Calibration results are registered in databases, and calibrated values, errors and pass or fail (judgment) may be displayed. The calibration management functions can require the administrator to acknowledge (approve) calibration results. After such acknowledgement of calibration results, only the administrator can change the results. The operation history management functions retain a record of all downloading and uploading of calibration data. If you use the Documenting Calibrator, you can use it to download or upload calibration data. In addition, calibration results are automatically stored in the database. (*1) *1: Connection to the Documenting Calibrator is an optional extra.

17 Other Functions Browser Can search for devices using device attribute information such as device ID, device tag name, device tag comment, block name, or parameter value. Security During maintenance of field devices, restricts operation to specific user(s) or restricts range of operations permitted to prevent system trouble due to operator errors, and to maintain system security. The user name and operation record of the logged-in operator is recorded in the operation history. User Group can 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 device navigator to display devices only for the specific group. Export Can output a list of all devices (such as device ID, device tag, and device tag comment) stored in the database to a text file in CSV format. You can use information managed with PRM on facility management software and the like. Self-documentation Automatically creates device documentation for management. Can collectively print out data stored in the database in report format. Device information is managed electronically, and can be printed out on demand. Information on each window can be printed out as individual reports, so a report can be printed out after maintenance work to provide a maintenance work record. The following print properties can be edited: Printing range Table of contents Header/footer Cover page PLUG-IN Application The software package provided by third-party device vendors which is built into PRM system. The PLUG-IN Application runs on the client, and it accesses to field devices and Oracle database in PRM server via PLUG-IN Application Library. Yokogawa Electric supplies DeviceViewer and the PLUG- IN ValveNavi for Yokogawa Advanced Valve Positioner, YVP110 as a PLUG-IN application. This PLUG-IN ValveNavi helps users to easily calibration and diagnose the YVP110. This PLUG-IN ValveNavi also supports Signature function for control valve diagnosis. The function is based on standalone ValveNavi (YVP20S YVP Management Software). For its functions, refer to the separate GS 21B04C50-01E for Model YVP20S YVP Management Software. 17 Supported PLUG-IN DeviceViewer: FF-H1 devices: DPharp EJA Series: Digital Differential Pressure and Pressure Transmitter, R2 or later EJA for Software Download; R1 or later DPharp EJX Series: Digital Differential Pressure and Pressure Transmitter, R1 or later YTA Series: Temperature Transmitter, R2 or later DY, DYA digital YEWFLO, R1 or later DY, DYA digital YEWFLO for Software Download, R1 or later YEWFLO*E: Vortex Flow Meter, R2 or later ADMAG AE Series: Magnetic Flow Meter, R1 or later YVP110: Advanced Valve Positioner, R2 or later YVP110 for Software Download: R1 or later YPK110: Fieldbus-to-Pneumatic converter, R1 or later PH202F: 2-Wire Type ph Meter, R1 or later SC202F: 2-Wire Type Conductivity Meter, R1 or later ISC202F: 2-Wire Inductive Conductivity Meter, R1 or later DAQSTATION DX Series, R3 or later FVP: Valve Positioner (Dresser), R2 or later FVP for Software Download: R1 or later DVC5000f: Digital Valve Controller Fisher, R8 or R9) FF-01: Valve Actuator, R2 FP302: Fieldbus to Pressure Convertor (SMAR), R4 or later 5081C/T: Conductivity Transmitter (Rosemount Analytical), R1 or later 5081pH: Conductivity Transmitter (Rosemount Analytical), R1 or later 848T: Eight Input Temperature Transmitter (Rosemount Inc.), R4 644HF: Temperature Transmitter (Rosemount Inc.), R1 or later 752: Remote Indicator (Rosemount Inc.), R1 3051S: Pressure Transmitter (Rosemount Inc.), R14 or later 3144P: Temperature Transmitter (Rosemount Inc.), R1 or later 8800: Vortex Flowmeter (Rosemount Inc.), R5 or later 8742: Mag Flow Meter (Rosemount Inc.), R4 or later MVD2700: Mass Flow Sensor (Micro Motion), R3 or later 3244MV: Temperature Transmitter (Rosemount Inc.), R5 or later BA488: Fieldbus Display (BEKA), R1 or later HART devices: DPharp EJA Series: Digital Differential Pressure and Pressure Transmitter, R1 or later DPharp EJX Series: Digital Differential pressure and Pressure Transmitter, R1 or later DY, DYA digital YEWFLO, R2 or later PLUG-IN ValveNavi for YVP110 (Rev. 2.1 or later)

18 18 Device Template Function Templates in which device information is freely defined are supplied. These templates can simplify device setting in engineering work. In addition, the engineering items which require actual devices can be reduced. Database Maintenance Tool The PRM database capacity increases as the number of devices increases. If the operation history and parameter history are used for an extended period of time, large quantities of historical data are stored. An increase in the database will have a bad effect on the PRM performance. The database maintenance tool optimizes large databases to enable effective operation of the PRM. By using this tool, the database maintenance work is executed more easily than when using Database Maintenance Command of Oracle directly. Online Manual (R2.02 or later) From R2.02, all instruction manuals are provided in PDF format on CD-ROM. This enables you to view and print the electronic instruction manuals on-demand. PRM System Backup PRM provides a simple tool to back up data to meet user environments. This tool can back up registry information, PRM databases, advanced diagnosis databases, etc.

19 19 MULTI-SERVER SWITCHOVER The multi-server switchover functions are used for integrated management of multiple plants. Server Set means a set of field communication servers and PRM servers to which the PRM client is connected. Using a Server Set concept, you can dynamically switch from one Server Set to other Server Set. Server sets are user-defined before use. This allows centralized management of the facility management data from multiple remote plants as well as management of multiple facilities data in large-scale plants. It is also possible to connect PRMs in STARDOM and PRMs in CENTUM system on same Ethernet. with Multi-Server Switchover function Ethernet Router Switchover of Server Set Router PRM Client PRM Server PRM Client PRM Server Ethernet Ethernet HIS Field Communication Server HIS Field Communication Server V net V net FCS Server Set A FCS Server Set B F07E.EPS Figure: Multi-Server Switchover

20 20 Supported Functions All functions can be performed for FOUNDATION fieldbus devices, but there are some restrictions for HART devices. Table Supported Functions Function Conventional Devices(*1) FF-H1 HART Specification Remarks Device Navigation Function Plant View Network View Class View Device Master HART device s Detail part is different from other devices. Plug_&_Play Maintenance Information Management Functions Register from Host_File_Set Inspection Memo Inspection Schedule Parts List Link To Document Parameter History (*2) Audit Trail Management Function Inspection Memo History Operation History Record the Start/Stop of only Menu Window Adjustment and Diagnosis Other Functions Device Event Message Parameter Tuning and Comparison Status Display Tool Calibration Browse Function Security Printing PLUG-IN Application : Supported : Partly supported : Not applicale (*2) Take several ten seconds until this function is executed because of the performance of HART communications. Device Method and DeviceViewer 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. T05E.EPS *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.

21 OPERATING ENVIRONMENT Hardware Requirements The necessary amounts of main memory and disk space depend on the number of devices connected. This section discusses the minimum hardware requirements when no more than 1,000 devices are connected. If more than 1,000 devices need to be connected, consult Yokogawa. IBM /AT-compatible: Pentium 300 MHz or higher, Pentium III 1 GHz or higher recommended Main memory: 256 MB or greater, 512 MB or greater recommended. 1 GB or greater when using Oracle 10g Disk capacity: 12 GB or greater total disk space (at least 5 GB must be free.) Other requirements: DAT drive (for backup). Ethernet card Display: 256 colors or more are mandatory IBM /AT-compatible: Pentium 300 MHz or higher, Pentium III 1 GHz higher recommended Main memory: 64 MB or greater, 128 MB or greater recommended. Disk capacity: 8 GB or greater total disk space (at least 200 MB must be free.) Other requirement: Ethernet card Display: 1024 x 768 (256 calor) or more are mandatory Field Communications Server IBM /AT-compatible: Pentium 300 MHz or higher, Pentium III 1 GHz higher recommended Main memory: The necessary amount of main memory is shown below. Number of FCSes Recommended Memory Size 1 to x (number of FCSes) 17 to x (number of FCSes 16) T18E.EPS Disk capacity: 4 GB or greater total disk space (at least 200 MB must be free.) Other requirements: VF701 (Vnet) or VI701 (Vnet/IP) card, Ethernet card When connecting FF-H1 Fieldbus directly: The following cards of National Instruments Corporation are used. AT-FBUS ISA bus connection MCIA-FBUS MCIA Card NI I-FBUS/2 I bus connection 21 When 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 user s 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 ): EVNBMC (BLACK BOX) DB25 male DB9 female (inch screw thread), Straght connection *1: Number of Multiplexer (Master): Max.31 Number 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: IC108A (BLACK BOX) MA-45 (Westermo) 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 polarized Cable: 0.05 inch pitch standard ribbon Maximum length: 4m Cable 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 polarized Cable: 0.05 inch pitch standard ribbon Maximum length: 15m When using P+F ELCON Multiplexer: Multiplexer (Master and Slave): MUX2700 (P+F ELCON) Board for connection: HPSM/32/MM-01 (P+F ELCON) Recommended RS-232C/RS-485 Converter: IC108A (BLACK BOX) MA-45 (Westermo) Cable: Only normal RS485 cable is required

22 When using R. STAHL HART Multiplexer IS pac: Multiplexer: 9192/ IS 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 included Cable (connecting HART Multiplexer to converter): shielded twisted pair; plug = Sub-D 9, female; max length = 1200 m Recommended RS-232C / RS-485 converter, suitable for zone 2 / div 2 installation: 9185/ * Cable (connecting converter to ): 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/ ** or 9466/ ; CPU & Power Module 9440/** Cable (connecting CPU and power module to converter): shielded twisted pair; plug = Sub- D 9, female; max length = 1200 m Recommended RS-232C / RS-485 converter: 9185/ * RS-232C / RS-485-IS converter for remote I/O zone 1 / div 1 installation: 9185/ * Cable (connecting converter to ): Type F interface cable; max length = 15 m When using simplified system for HART: The following hardware is used VIATOR RS232 HART Interface Model (MACTek) 22 When installing, Field Communication Server, and in one : IBM /AT-compatible: Pentium 300 MHz or higher (Pentium III 1 GHz or higher recommended) Main memory: 1 GB (*1) or greater, 2 GB or greater recommended *1: 2 GB minimum, if an advanced diagnostic application coexists. Disk capacity: 12 GB or greater total disk space (at least 5 GB must be free) Other requirements: VF701 (Vnet) or VI701 (Vnet/IP) card, Ethernet card O Server (for STARDOM system) IBM /AT-compatible: Pentium 300 MHz or 400 MHz or faster recommended Main memory: 256 MB or 512 MB or greater recommended Disk 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.

23 23 Software Requirements OS: Windows Server 2003 Service Pack 1 Windows XP Service Pack 1 or 2 Windows 2000 (Server/Professional) Service Pack 4 Internet Explorer 5.0 or later version Oracle 8i: Oracle Database R8.1.6, R8.1.7 Oracle 9i: Oracle Database R9.2.0 Oracle 10g: Oracle Database R Note: Oracle 8i cannot run on Windows XP and Windows Server OS: Windows Server 2003 Service Pack 1 Windows XP Service Pack 1 or 2 Windows 2000 (Server/Professional) Service Pack 4 Oracle Client 8.1.6/8.1.7 Net8i Oracle Client Oracle 10g: Oracle Database R Note: Oracle 8i cannot run on Windows XP and Windows Server Software for document: Adobe Reader 6.0, Adobe Reader The corresponding Oracle versions and Windows are shown below. Windows Windows 2000 Windows XP Windows Server 2003 Oracle Version Oracle 8i Oracle 9i Yes Yes Yes No No Yes No No Yes Oracle 10g Yes Yes Yes T14E.EPS Yes: The version of Oracle supports the version of Windows. No: The version of Oracle does not support the version of Windows. Field Communications Server OS: Windows Server 2003 Service Pack 1 Windows XP Service Pack 1 or 2 Windows 2000 (Server/Professional) Service Pack 4 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.) Types of Oracle Database Server Supported for PRM Standard Edition Enterprise Edition (Personal Edition is not supported) O Server (for STARDOM system) OS: Windows XP Professional Service Pack 1 or 2 Windows 2000 Professional Service Pack 4

24 24 MODELS AND SUFFIX CODES PRM Basic Set (for new installation) Model PRMSET Plant Resource Management Basic Set Suffix Codes Option Codes -S Basic Software License and Media fee 1 Always 1 1 English version /N0025 Maximum number of connected devices: 25 /N0100 Maximum number of connected devices: 300 /N1000 Maximum number of connected devices: 1000 /N3000 Maximum number of connected devices: 3000 Description Note: The PRM Basic Set includes a Plant Resource Management Client, a Plant Resource Management Server, a Field Communications Server, Software Media for Plant Resource Manager and Electronic Instruction Manual Media for Plant Resource Manager. (for new installation) Description Model SSS7700 Plant Resource Management Server [Media model: SSSSM02-C11] Suffix Codes Option Codes -S Basic software license -C Multiple software licenses (for 2 or more) 1 Always 1 1 English version /N0100 Maximum Number of connected devices: 300 /N1000 Maximum Number of connected devices: 1000 /N3000 Maximum Number of connected devices: 3000 Note: A PRM server is required for each project. Note: This package cannot be installed in HIS. Prepare a separate from HIS. Note: This package uses Oracle 8i/Oracle 9i/Oracle 10g for the database. Prepare Oracle 8i/Oracle 9i separately from this package. Note: Exaopc O Interface Package for HIS (LHS2411) is required to acquire device events. (for expansion) T06E.EPS T01E.EPS Description Model SSS7700 Plant Resource Management Server [Media model: SSSSM02-C11] Suffix Codes Option Codes -A Software license for additional devices 1 Always 1 1 English version /N0001 Changes in maximum number of connected devices: 25 to 300 /N0010 Changes in maximum number of connected devices: 25 to 1000 /N0110 Changes in maximum number of connected devices: 300 to 1000 /N0030 Changes in maximum number of connected devices: 25 to 3000 /N0130 Changes in maximum number of connected devices: 300 to 3000 /N1030 Changes in maximum number of connected devices: 1000 to 3000 Note: This package cannot be installed in HIS. Prepare a separate from HIS. Note: This package uses Oracle 8i/Oracle 9i/Oracle 10g for the database. Prepare Oracle 8i/Oracle 9i separately from this package. Note: Exaopc O Interface Package for HIS (LHS2411) is required to acquire device events. T02E.EPS

25 25 Description Model SSS7710 Plant Resource Management Client [Media model: SSSSM02-C11] Suffix Codes -S Basic software license -C Multiple software licenses (for 2 or more) 1 Always 1 1 English version Note: Multiple clients can operate this application with a multiple client package of Oracle 8i/Oracle 9i/Oracle 10g. Field Communications Server Description Model SSS7720 Field Communications Server [Media model: SSSSM02-C11] -S Basic software license -C Multiple software licenses (for 2 or more) Suffix Codes 1 Always 1 1 English version Option Code /HART For HART devices (*1) Note: The function for connecting with FOUNDATION fieldbus devices is included in the basic specification. Note: This package cannot be installed in HIS. Prepare a separate from HIS. *1: R2.02 or later version of Plant Resource Manager supports this option code. When connecting HART devices, specify the option code /HART. T03E.EPS T04E.EPS Any or all Plant Resource Manager (Field Communications Server, Database Server, and Client) can be installed on a single. Intelligent Calibrator Interface for Description Model SSS7711 Documenting Calibrator Interface [Media model: SSSSM02-C11] -S Basic software license Suffix Codes 1 Always 1 1 English version Option Code /FLK01 Calibrator type: Fluke 743B/744 Note: R2.04 or later version of Plant Resource Manager supports this software. Note: This package can be installed with basic software license in two or more PRM client machines. Software Media for Plant Resource Manager T11E.EPS Description Model SSSSM02 Software Media for Plant Resource Manager -C Supplied media: CD-ROM Suffix Codes 1 Always 1 1 English version Note: Electric Instruction manual Media for this package is SSSSD02. T13E.EPS

26 26 Electronic Instruction Manual Media for Plant Resource Manager Description Model SSSSD02 Electronic Instruction Manual Media for Plant Resource Manager -C Supplied media: CD-ROM Suffix Codes 1 Always 1 1 English version Note: R2.02 or later version of Plant Resource Manager supports this software. 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 T08E.EPS Description Model SSS7750 PLUG-IN ValveNavi [Media model: SSSAM02-C11] -S Basic software license Suffix Codes Option Code -C Multiple software license (for 2 or more) 1 Always 1 1 English version /FF-H1 For FOUNDATION fieldbus devices (*1) Note: R2.03 or later version of Plant Resource Manager supports this software. 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 T09E.EPS Description Model SSSAM02 PLUG-IN Application Media for Plant Resource Manager Suffix Codes -C Supplied media: CD-ROM 1 Always 1 1 English version Note: R2.03 or later version of Plant Resource Manager supports this software. Note: Electronic instruction manual is included in this media. FCN/FCJ O Server for Windows Please see GS 34P02Q61-01E for detail. T10E.EPS ORDERING INSTRUCTIONS Specify 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. Oracle is a registered trademark of Oracle Corporation. HART is a registered trademark of the HART Communication Foundation. MAXIMO is a registered trademark of MRO Software, Inc. STARDOM is a trademark. Other product and company names appearing in this document are trademarks or registered trademarks of their respective holders. Subject to change without notice.