<<Contents>> <<Index>>

General Models SSS7700, SSS7710,

Specications SSS7720
Plant Resource Manager
GS 33Y05Q10-31E

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 eldbus efciently handles eld device management and
maintenance work for the FOUNDATION eldbus 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 man-
agement of conventional analog, FOUNDATION eldbus 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:

PRM Server
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,
user-created 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 eld devices
that have been dened 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.

PRM Client
User-friendly Windows-based operating environment, with Explorer-like Navigator for selecting a specic device.
Uses bidirectional, all-digital eld networks such as FOUNDATION eldbus. Performs automatic device recognition and
registration (Plug and Play), monitors device health statuses with maintenance alarm functions, monitors commu-
nication 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.).
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 unconrmed maintenance alarm status (device health status), a conrmation status icon ap-
pears next to the device icon.
The user can freely dene 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 users request.
In addition to Maintenance Alarm Function and standard diagnostic functions, Yokogawa provides Acquisition Navi-
gator and Diagnostic Tool as components of the PRM Advanced Diagnosis package. With these software compo-
nents, you can carry out advanced predictive, proactive and preventive maintenance using a eld network.
Allows not merely FOUNDATION eldbus-compliant devices and HART-compliant devices but also conventional analog
eld 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 Yokogawas
product, DeviceViewer (*1, *2, *3) and PLUG-IN ValveNavi (*1). PRM Client can start up a calibration tool or a diag-
nosis tool that is uniquely designed by device vendors as PLUG-IN Application.
*1: PRM R2.03 or later version supports the DeviceViewer for FOUNDATION eldbus devices and PRM R2.06 or later version sup-
ports the DeviceViewer for HART-devices.
*2: DeviceViewer is a build-in PLUG-IN Application for self-diagnostic of FOUNDATION eldbus 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, denition les must be obtained from that device vendor.
*3: With PRM R2.20 or later release, DeviceViewer can be displayed on CS 1000/CS 3000 HIS. However, for displaying De-
viceViewer, the CS 1000/CS 3000 Operation and Monitoring Functions must be R3.07 or later release.

Yokogawa Electric Corporation GS 33Y05Q10-31E

2-9-32, Nakacho, Musashino-shi, Tokyo, 180-8750 Japan Copyright Jan. 2001
Tel.: 81-422-52-5634 Fax.: 81-422-52-9802 13th Edition Jan. 1,2006
<<Contents>> <<Index>> 2
Field Communications Server
PRM supports two types of eld communication (Foudation eldbus 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 conguration types are available.
One is Control bus connection via AI/AO modules with HART Communication in CENTUM CS 3000 system and in
STARDOM System. Another one is Serial port connection via 3rd Vendor HART Multiplexer. For serial port connec-
tion, 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 Conguration
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 Computer-
ized 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 execut-
ing the diagnostic algorithm of eld devices.
With this package, you can directly acquire parameters from these devices at xed 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 difcult to realize with eld 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.

All Rights Reserved. Copyright 2001, Yokogawa Electric Corporation GS 33Y05Q10-31E Nov. 7, 2005-00
<<Contents>> <<Index>> 3
SYSTEM CONFIGURATION
A single database server is the unit for management (e.g. for search operations). At least one PRM Server 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 Conguration When Connecting FOUNDATION eldbus

CENTUM CS 3000
This section shows a large-scale system conguration for Plant Resource Manager.

PC PC PC
PRM Client PRM Server CMMS
Oracle RDB (MAXIMO)

HIS PC Terminator
Exaopc Field Communications Server
OPC Interface FF-H1 Host Interface
for HIS
H1 Fieldbus
(for device adjustment) Coupler

bus 2
Vnet/IP
bus 1

FCS
FCS
FCU

HART I/O Module

ESB bus

EB401 SB401
ALF111 ALF111 HART
(dual (dual
(in service) (stand-by) devices
redundant) redundant)

Local Node

Terminator HIS : Human Interface Station

FCS : Field Control Station
FCU : Field Control Unit
SB401 : ESB bus Interface (in Local Node)
H1 Fieldbus
EB401 : ER bus Interface (in Local Node)
Coupler ALF111 : Foundation Fieldbus Communication Module

Field devices F01E.ai

Figure: System Conguration (CENTUM CS 3000 system)

All Rights Reserved. Copyright 2001, Yokogawa Electric Corporation GS 33Y05Q10-31E Jan. 1, 2006-00
<<Contents>> <<Index>> 4
CENTUM CS 1000
This section shows a small-scale system conguration for Plant Resource Manager.

PC
CMMS
(MAXIMO)

Ethernet
PC
PRM Client
PRM Server
HIS Field Communications Server Terminator
Exaopc Oracle RDB
OPC Interface for HIS FF-H1 Host Interface

H1 Fieldbus
(for device adjustment) Coupler

VL net

FCS

ACF11 Terminator

H1 Fieldbus

Coupler

HIS : Human Interface Station

FCS : Field Control Station
ACF11 : Foundation Fieldbus Communication Module

Field devices
F02E.ai

Figure: System Conguration (CENTUM CS 1000 system)

All Rights Reserved. Copyright 2001, Yokogawa Electric Corporation GS 33Y05Q10-31E Nov. 7, 2005-00
<<Contents>> <<Index>> 5
STARDOM
This section shows a STARDOM conguration for Plant Resource Manager. The gure below is an example of con-
necting the STARDOM system to the PRM. Messages from the STARDOM controller are transmitted to the PRM
server via the OPC server. FCN/FCJ OPC Server for Windows is needed in the system.

VDS/HMI PRM

HMI Client PC
PRM Client

Logic designer Ethernet

Resource Configurator
Enginnering tool FCN/FCJ
Device Management tool
HMI Server OPC PC
Data Server Server PRM Server
Field Communication Server

Control Network
Controller
FCN

NFLF FCJ
PSU CPU
111 (with FF-H1 port)

Terminator Terminator

H1 Fieldbus H1 Fieldbus

Coupler Coupler

F10E.ai

Figure: STARDOM System Conguration

Operating Environment
PRM 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 in-
stalled. (PRM revision is R2.06 or later)
The revision of FCN/FCJ must be R1.40 or later.

All Rights Reserved. Copyright 2001, Yokogawa Electric Corporation GS 33Y05Q10-31E Oct. 4, 2004-00
<<Contents>> <<Index>> 6
System Conguration When Connecting HART
Four system congurations 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 communi-
cation functions of FCS.

PRM Server PC
PRM Client Oracle RDB CMMS
(MAXIMO)

HIS/ENG Field Communications Server

Exaopc OPC
Interface (for device adjustment)
for HIS
HART Modem
(VIATOR RS232 Interface)
bus 2
Vnet/IP HART device
bus 1

FCS

ESB bus

HART I/O module (in service)

HART I/O module (stand-by)
SB401: ESB bus interface (in Local Node)
EB401: ER bus interface (in Local Node)
Local Node EB501: ER bus interface (in Remote Node)
HART devices
SB401 (dual-redundant)
DEV1 EB401 (dual-redundant)

ER bus
DEV2

HART I/O module (in service)

HART I/O module (stand-by)

Remote Node
HART devices
DEV1 EB501 (dual-redundant)

DEV2

F04E.ai

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

All Rights Reserved. Copyright 2001, Yokogawa Electric Corporation GS 33Y05Q10-31E Nov. 7, 2005-00
<<Contents>> <<Index>> 7
Control Network connection via HART Module in STARDOM System
VDS/HMI PRM

HMI Client PC
PRM Client

Logic designer Ethernet

Resource Configurator
Enginnering tool FCN/FCJ
Device Management tool
HMI Server OPC PC
Data Server Server PRM Server
Field Communication Server

Control Network
Controller
FCN

PSU CPU NFAI NFAI NFAI NFAI

141 841 135 835

HART I/O module

HART devices configurator

HART device F11E.ai

Figure: Control Network connection via HART Module in STARDOM System

All Rights Reserved. Copyright 2001, Yokogawa Electric Corporation GS 33Y05Q10-31E May 1, 2005-00
<<Contents>> <<Index>> 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.
PRM Client
PRM Server PC
Oracle RDB CMMS
(MAXIMO)

Ethernet

Field Communications Server HIS/ENG

(*1)

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

RS Communication FCS
RS-485 HART?Multiplexer
(commercially available)

RIO bus
Slave No.2

Adopter
Slave No.1 board HART Devices
AAM11 DEV1
AAM11 DEV2

Master
4-20 mA
HART Digital Signals

F05E.ai

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.

All Rights Reserved. Copyright 2001, Yokogawa Electric Corporation GS 33Y05Q10-31E May 1, 2005-00
<<Contents>> <<Index>> 9
Serial port connection via HART Multiplexer (For using P+F Multiplexer)
When using P+F Multiplexer, can connect as a stand-alone system conguration as follows.
PRM Client PRM Client
PRM Server PC
Oracle RDB CMMS
(MAXIMO)

Ethernet

Field Communications Server

(*1) RS-485

HART?Multiplexer HART?Multiplexer HART?Multiplexer

*1: RS-232C/RS-485 (Master No.1) (Master No.2) (Master No.31)
converter

Directly connected
to Master

HART?
Multiplexer
HART Devices (Slave No.1)

Connected to Slave

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

HART?
Multiplexer
(Slave No.15)

F06E.ai

Figure An Example of P+F Multiplexer Connection

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

All Rights Reserved. Copyright 2001, Yokogawa Electric Corporation GS 33Y05Q10-31E May 1, 2005-00
<<Contents>> <<Index>> 10
Serial port connection via HART Multiplexer (For using MTL Multiplexer)
When using MTL Multiplexer, can connect as a stand-alone system conguration as follows.
PRM Client PRM Client
PRM Server PC
Oracle RDB CMMS
(MAXIMO)

Ethernet

Field Communications Server BPHM64 (One MTL4841-PRM

and four MTL4842s are installed)
(*1) RS-485
Field
terminals
(HCU16)

*1: RS-232C/RS-485
converter
Max.16
HART Multiplexer HART Multiplexer HART Multiplexer devices
(Master No.1) (Master No.2) (Master No.31,
Slave No.1-4)

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

Figure: An Example of MTL Multiplexer Connection

All Rights Reserved. Copyright 2001, Yokogawa Electric Corporation GS 33Y05Q10-31E May 1, 2005-00
<<Contents>> <<Index>> 11
Serial port connection via HART Multiplexer (For using ELCON Multiplexer)
When using ELCON Multiplexer, can connect as a stand-alone system conguration as follows.
PRM Client PRM Client
PRM Server PC
Oracle RDB CMMS
(MAXIMO)

Ethernet

Field Communications Server HPSM/32/MM-01

(MUX2700 is installed)
(*1) RS-485

*1: RS-232C/RS-485
converter
Max.32
devices
HART Multiplexer HART Multiplexer HART Multiplexer
(No.1) (No.2) (No.31)

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

F09E.ai

Figure: An Example of ELCON Multiplexer Connection

All Rights Reserved. Copyright 2001, Yokogawa Electric Corporation GS 33Y05Q10-31E May 1, 2005-00
<<Contents>> <<Index>> 12
Serial port connection via HART Multiplexer (for using STAHL Multiplexer)
When using STAHL Multiplexer, can connect as a stand-alone system conguration as follows.
PRM Client PRM Client
PRM Server PC
Oracle RDB CMMS
(MAXIMO)

Ethernet

Field Communications Server

(*2) (*1) RS-485

IS pac

HART Multiplexer type 9192 HART Multiplexer type 9192 HART Multiplexer type 9192
(No.1) (No.2) (No.31)
with pac-Carrier type 9195 with HART connection board type 9196 with HART connection board type 9196
and signal isolators max 32 channels max 32 channels
max 32 channels
Max.32
32 (device) x 31 (HART MUX) = 992 (Maximum Field Devices) devices

(*2) (*3) RS-485

I.S. 1

HART Remote I/O Input/Output HART Remote I/O Input/Output HART Remote I/O Input/Output
(No.1) (No.2) (No. 31)
with type 9461, 9466 with type 9461, 9466 with type 9461, 9466
modules modules 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/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.

F14E.ai

Figure: An Example of STAHL Multiplexer Connection

All Rights Reserved. Copyright 2001, Yokogawa Electric Corporation GS 33Y05Q10-31E May 1, 2005-00
<<Contents>> <<Index>> 13
Simplied System for Device Adjustment
The H1 Fieldbus can be connected directly to the PC by using the Fieldbus interface board of National Instruments
(NI) Corporation. A simplied system for adjustment of the eld devices without FCS can be constructed. If you use a
PC card type Fieldbus interface card, a simplied system can be constructed even with a notebook PC.

PRM Client
PRM Server
Terminator
Field Communication Server
Oracle RDB

H1 Fieldbus

Coupler

Field devices
F12E.ai

Figure: System Conguration (Simplied system for FF-H1 device adjustment)

Moreover, the HART device can be connected to the PC easily by using the VIATOR RS232 Interface for HART of
MACTek Corporation. A simplied system for adjustment of the HART Device can be constructed.
PRM Client
PRM Server
Field Communication Server
Oracle RDB

RS-232C

HART Modem (VIATOR RS232 Interface)

HART devices
Power Supply
F13E.ai

Figure: System Conguration (Simplied system for HART device adjustment)

All Rights Reserved. Copyright 2001, Yokogawa Electric Corporation GS 33Y05Q10-31E May 1, 2005-00
<<Contents>> <<Index>> 14
FUNCTION SPECIFICATIONS
Organization of Functions
The following gure shows organization of functions.

PRM

Device Navigator Other Functions

Plant View Browser

Network View Security
Class View Export
Custom View Self-documentation
PLUG-IN Application
Maintenance Alarm Device Template
Database Maintenance Tool
Message Acquisition PRM System Backup
Device Patrol Online Manual
Filtering
PRM Advanced Diagnosis (Option)
Maintenance Information Management
Diagnostic Navigator
Device Master Acquisition Navigator
Inspection Memo PRM Advanced Diagnosis Application (PAA)
Inspection Schedule Data Acquisition Function
Parts List
Link to Document PRM Advanced Diagnosis Application Software
Development Kit (Option)
Audit Trail Management
Interface to Computerized Maintenance
Operation Log Management System (Option)
Event Log of Device
Inspection Log
Record filtering

Adjustment and Diagnosis

Parameter Tuning and Comparison
FF DD Menu Window
HART DD Menu Window
HART Offline Parameter
DeviceViewer
Calibration Management (Option)
F03E.ai

Figure: Organization of Functions

All Rights Reserved. Copyright 2001, Yokogawa Electric Corporation GS 33Y05Q10-31E Nov. 7, 2005-00
<<Contents>> <<Index>> 15
Device Navigator Maintenance Alarm Function
The Device Navigator provides Plant View, Network This function provides a message system for strength-
View, Class View and Custom View. ening maintenance information and advice guidance.
Each view displays arrangement of devices, in hier- The function transmits information necessary for main-
archical Explorer-like format. You can select devices taining devices to maintenance personnel to help them
and perform functions in these views. These views in the work to be done. The function can not only trans-
can display the device status icon using a maintenance mit device event messages but also add necessary
alarm function, thus allowing visual identication of information, such as phenomena, causes, measures,
device statuses. For a device with an unconrmed etc., to these messages.
maintenance alarm, an unconrmed alarm icon is also The following functions are provided to strengthen the
displayed. maintenance information.
User access to the hierarchy of the device navigator Message Acquisition
can be restricted, which will prevent the person who is Acquires eld device events (for FOUNDATION
not in charge of the device from operating the device by eldbus, FF) or events acquired by the CENTUM/
mistake. STARDOM system. User-dened information (message
Plant View priority level, object information, phenomena, causes,
Displays the equipment which makes up the plant, and measures, etc.) is automatically added to raw event
shows its place in the plant hierarchy, in hierarchical information for normalized alarms in PRM. Normalized
Explorer-like format. You can manage plant organiza- alarms are sent to an alarm ltering function.
tion intuitively, based on P & ID diagrams. Unused Device Patrol
devices in the plant can be managed by putting them Acquires self-diagnosis parameter data from eld de-
in the Spare Folder, and devices which have failed or vices with diagnosis information and adds used-dened
are under maintenance can be placed in the Off-Ser- information (message priority level, object information,
vice (Out of Service) Folder. In addition, device sta- phenomena, causes, and measures) to acquired data
tuses using maintenance functions can be displayed. to provide alarms normalized in PRM. These normal-
Network View ized alarms are then transmitted to an alarm ltering
Displays position of device, related to eld network function. Data are acquired periodically or on demand.
physical conguration, in an Explorer-like hierarchical Necessary information can also be obtained from de-
view. The mark next to the device icon shows the com- vices from which no events are issued.
munication status and alarm status of the device the Filtering Function
color of the mark changes if the device fails, so users Normalized alarms issued through such functions as
have an immediate visual view of operating status. De- the message acquisition, device patrol or advanced di-
vice statuses and device communication statuses using agnostic application, and from messages generated by
the maintenance functions can also be displayed. key entries can be ltered to prevent the notication of
Class View alarm event messages that are not in agreement with
Displays devices in an Explorer-like hierarchical view the specied conditions. It is also possible to change
grouped by supplier, model, and revision. For devices notication messages on a user-by-user basis.
which have failed or are under maintenance, you can
check the (e.g. spares) status of devices of the same Maintenance Information Management
type at a glance. Device templates can be created with Manages the maintenance information of all devices.
this Class View.
Device Master
Custom View Manages an inventory of all devices. You can display
Displays devices in the hierarchy structure freely cre- a list of all devices, or detailed information on a single
ated by users, in an Explorer-like hierarchical view. device. For devices with communications functions,
Devices can be classied according to persons in the device master basic information is automatically
charge, inspection and replacement schedule, operat- created through device recognition and registration
ing state, and failure state. (Plug and Play). No user entries are required.
Inspection Memo
Maintains historical records of device inspection memo,
and malfunctions. Moreover, maintenance person-
nel 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 eld inspec-
tion patrol reports based on a PRM user.

All Rights Reserved. Copyright 2001, Yokogawa Electric Corporation GS 33Y05Q10-31E Nov. 7, 2005-00
<<Contents>> <<Index>> 16
Inspection Schedule DeviceViewer: DeviceViewer is a PLUG-IN Applica-
Manages inspection schedules (checking, tuning, cali- tion that displays the self-diagnosis result
bration, etc.) for each device. of FF-H1 devices. In many cases upper
application program detects errors in
Parts List devices by reading multi-parameter, con-
A device may consist of several parts; the parts list taining the self-diagnosis result, saved in
displays attributes of each part, and stock information. FF-H1 devices. In the case of Yokogawa
Enhances efciency of repair and parts replacement FF devices, DeviceViewer displays not
work. For Yokogawa eld devices (FF-H1 and HART only the self-diagnosis result by reading
devices), specic templates are provided. parameters but also the data displayed
Link to Document on the FF-H1 devices LCD, such as error
This can display information such as conguration (e.g. messages, in user-friendly format. This
P & ID and control drawings), exploded views, online allows operators to monitor the connected
manuals, and graphics, as desired. You can access devices from PRM without viewing a LCD
and display this device-related information using the of eld devices.
tag name as a key. You can also use a URL to access For HART
a document server connected via Ethernet. Can switch to DD Menu Window and HART Ofine
Parameters Window.
Audit Trail Management These windows are equivalent to HART Handheld
Terminal.
This manages and displays the entire operating history DD Menu: Construe and execute the items of Menu
and historical inspection data carried out on a PRM in HART DD. Refer/set parameters or
client, and device alarm events from devices using execute Method. Record Start/Stop of
maintenance alarm functions as historical messages. only this window as operation messages.
A list of these historical messages can be displayed in The executed result of this window is not
chronological order or on a device priority level and on recorded in the database or the operation
a message priority level. In addition, device IDs and tag message.
names allow the ltering of these messages; there- HART Ofine Parameters: List and display Of-
fore, a specic devices operating history can be easily ine Parameters or Upload Variables
retrieved. described in HART DD. Change the
parameter values. Record Start/Stop of
Adjustment and Diagnosis Functions only this window as operation messages.
Supports device online tuning and diagnostic functions. Specify a le for each device and save
the parameter values; read the parameter
Parameter Tuning and Comparison values from the les.
Online display and setting of device parameter. Com- DeviceViewer: The device viewer supports the HART
pares stored device historical records with current de- Device, either. It displays the self-diag-
vice data. Facilitates safe switching of device operating nosis hardware status and conguration
conditions, and resetting to past values, while compar- status of the HART Device.
ing current and past values for safety. Can upload
device data at any time, and store it in the database. A Calibration Management
collective upload function that can upload all the con- The PRM database manages equipment calibration
nected devices at a time is also supported. data. Calibration results are registered in databases,
and calibrated values, errors and pass or fail (judg-
Tool ment) may be displayed. The calibration management
For FOUNDATION eldbus functions can require the administrator to acknowledge
Can switch to DD Menu Window and DeviceViewer (approve) calibration results. After such acknowledge-
Window ment of calibration results, only the administrator can
DD Menu: Using the Method of DD les provided by change the results.
a vendor enables to perform Tuning and The operation history management functions retain a
Diagnosis. The specications are depen- record of all downloading and uploading of calibration
dent on eld devices. data.
If you use the Documenting Calibrator, you can use it to
download or upload calibration data. In addition, cali-
bration results are automatically stored in the database.
(*1)
*1: Connection to the Documenting Calibrator is an
optional extra.

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

All Rights Reserved. Copyright 2001, Yokogawa Electric Corporation GS 33Y05Q10-31E Nov. 7, 2005-00
<<Contents>> <<Index>> 18
Device Template Function
Templates in which device information is freely dened
are supplied. These templates can simplify device set-
ting 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 num-
ber 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 Main-
tenance 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.

All Rights Reserved. Copyright 2001, Yokogawa Electric Corporation GS 33Y05Q10-31E Nov. 7, 2005-00
<<Contents>> <<Index>> 19
MULTI-SERVER SWITCHOVER
The multi-server switchover functions are used for integrated management of multiple plants. Server Set means a
set of eld communication servers and PRM servers to which the PRM client is connected. Using a Server Set con-
cept, you can dynamically switch from one Server Set to other Server Set. Server sets are user-dened before use.
This allows centralized management of the facility management data from multiple remote plants as well as manage-
ment 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.
PRM Client
with Multi-Server
Switchover function

Ethernet

Router Router
Switchover of Server Set

PRM PRM PRM PRM

Client Server Client Server

Ethernet Ethernet

HIS Field HIS Field

Communication Communication
Server Server

V net V net

FCS FCS
Server Set A Server Set B

F07E.ai

Figure: Multi-Server Switchover

All Rights Reserved. Copyright 2001, Yokogawa Electric Corporation GS 33Y05Q10-31E Nov. 7, 2005-00
<<Contents>> <<Index>> 20
Supported Functions
All functions can be performed for FOUNDATION eldbus devices, but there are some restrictions for HART devices.

Table Supported Functions

Conventional
Function FF-H1 HART Specication Remarks
Devices(*1)
Plant View XX XX XX
Device Navigation
Network View XX XX
Function
Class View XX XX XX
Device Master XX XX XX HART devices Detail part is different from other devices.
Plug_&_Play XX XX
Maintenance Register from
XX
Information Host_File_Set
Management Inspection Memo XX XX XX
Functions Inspection Schedule XX XX XX
Parts List XX XX XX
Link To Document XX XX XX
Parameter History XX XX (*2)
Inspection Memo
Audit Trail XX XX XX
History
Management
Function Operation History XX XX X Record the Start/Stop of only Menu Window
Device Event Mes-
XX XX
sage
Parameter Tuning
XX XX (*2)
and Comparison
Take several ten seconds until this function is executed
Status Display XX XX
because of the performance of HART communications.
Adjustment and Device Method and DeviceViewer for Fieldbus. Menu and
Diagnosis Ofine Parameters for HART. The parameter information
Tool XX XX of HART devices can be acquired by Ofine Parameters.
The acquired data can be saved in each device in
Text format.
Calibration XX XX
Browse Function XX XX XX
Security XX XX XX
Other Functions Printing XX XX XX
PLUG-IN
XX XX
Application

XX: Supported X: 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.

All Rights Reserved. Copyright 2001, Yokogawa Electric Corporation GS 33Y05Q10-31E Nov. 7, 2005-00
<<Contents>> <<Index>> 21
OPERATING ENVIRONMENT When using P+F Multiplexer:
Multiplexer (Master): KFD2-HMM-16 (P+F) (*1)
Hardware Requirements Multiplexer (Slave): KFD0-HMS-16 (P+F)
Cable (connecting Master or Slave to terminal
The necessary amounts of main memory and disk block): K-HM 26 (P+F)
space depend on the number of devices connected. Cable (connecting Master to Slave): K-HM 14
This section discusses the minimum hardware require- (P+F)
ments when no more than 1,000 devices are connect- Terminal Block: FI-**-PFH-Y... (** is specied
ed. If more than 1,000 devices need to be connected, depending on users need) (P+F)
consult Yokogawa. Power Supply: KFD2-EB2 (P+F)
PRM Server Power Rail (an equipment to be used for xing
IBM PC/AT-compatible: Pentium 300 MHz or higher, Multiplexer to a terminal board)
Pentium III 1 GHz or higher recommend- Recommended RS-232C/RS-485 Converter:
ed IC108A (BLACK BOX)
Main memory: 256 MB or greater, 512 MB or greater MA-45 (Westermo)
recommended. Cable (connecting Master to converter):
1 GB or greater when using Oracle 10g Twisted pair cable (category 5)
Disk capacity: 12 GB or greater total disk space Cable (connecting converter to PC):
(at least 5 GB must be free.) EVNBMC (BLACK BOX) DB25 male
Other requirements: DB9 female (inch screw thread),
DAT drive (for backup). Straght connection
Ethernet card *1: Number of Multiplexer (Master): Max.31
Display: 256 colors or more are mandatory Number of connectable devices: Max.255 per
one Master
PRM Client When using MTL Multiplexer:
IBM PC/AT-compatible: Pentium 300 MHz or higher, Multiplexer (Master): MTL4841-PRM (MTL)
Pentium III 1 GHz higher recommended MTL4841 (standard type) and
Main memory: 64 MB or greater, 128 MB or greater MTL4841-AMS cannot connect to
recommended. PRM.
Disk capacity: 8 GB or greater total disk space Multiplexer (Slave): MTL4842 (MTL)
(at least 200 MB must be free.) Back plane: BPHM64 (MTL)
Other requirement: Ethernet card HART connection Unit (16ch HART Inputs/Out-
Display: 1024 x 768 (256 calor) or more are man- puts ):
datory HCU16 (MTL)
Field Communications Server Recommended RS-232C/RS-485 Converter:
IBM PC/AT-compatible: Pentium 300 MHz or higher, IC108A (BLACK BOX)
Pentium III 1 GHz higher recommended MA-45 (Westermo)
Main memory: The necessary amount of main Cable for connection between Master and Slave
memory is shown below. (4 or less):
Not required (connectable on
Number of FCSes Recommended Memory Size BPHM64)
1 to 16 100 + 80 x (number of FCSes) Cable for connection between Master and Slave
17 to 48 1380 + 10 x (number of FCSes16) (5 or more):
Connector type:10 way DIN41651 bump polar-
Disk capacity: 4 GB or greater total disk space ized
(at least 200 MB must be free.) Cable: 0.05 inch pitch standard ribbon
Other requirements: VF701 (Vnet) or VI701 (Vnet/IP) Maximum length: 4m
card, Ethernet card Cable for connection between Master and Master:
When connecting FF-H1 Fieldbus directly: Not specially specied (normal RS-485
The following cards of National Instru- cable is used)
ments Corporation are used. Cable for connection between BPHM64 and
AT-FBUS ISA bus connection HCU16:
PCMCIA-FBUS PCMCIA Card Connector type: 20 way DIN41651 bump polar-
NI PCI-FBUS/2 PCI bus connection ized
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

All Rights Reserved. Copyright 2001, Yokogawa Electric Corporation GS 33Y05Q10-31E Nov. 7, 2005-00
<<Contents>> <<Index>> 22
When using R. STAHL HART Multiplexer IS pac: When installing PRM Server, Field Communication
Multiplexer: 9192/32-10-10 Server, and PRM Client in one PC:
IS pac Carrier: 9195/08H-***-*** or 9195/16H- IBM PC/AT-compatible: Pentium 300 MHz or higher
***-*** or HART Connection Board: (Pentium III 1 GHz or higher recom-
9196/**H-XX0-*** mended)
Cable (connecting multiplexer to IS pac carrier or Main memory: 1 GB (*1) or greater, 2 GB or greater
connection board): with carrier or board recommended
included *1: 2 GB minimum, if an advanced diagnostic ap-
Cable (connecting HART Multiplexer to converter): plication coexists.
shielded twisted pair; plug = Sub-D 9, Disk capacity: 12 GB or greater total disk space (at
female; max length = 1200 m least 5 GB must be free)
Recommended RS-232C / RS-485 converter, Other requirements: VF701 (Vnet) or VI701 (Vnet/IP)
suitable for zone 2 / div 2 installation: card, Ethernet card
9185/12-45-10* OPC Server (for STARDOM system)
Cable (connecting converter to PC): Type F inter- IBM PC/AT-compatible: Pentium 300 MHz or 400
face cable; max length = 15 m MHz or faster recommended
When using R. STAHL Remote I/O I.S. 1 with Ser- Main memory: 256 MB or 512 MB or greater recom-
viceBus: mended
Analog Input or Analog Output Modules HART: Disk capacity: There must be at least 1 GB of free
9461/12-08-** or 9466/12-08-11; CPU & space.
Power Module 9440/** Ethernet card: 100BASE-TX, 10BASE-T, 10BASE-5
Cable (connecting CPU and power module to
converter): shielded twisted pair; plug = Two communications devices are needed to separate
Sub-D 9, female; max length = 1200 m the STARDOM information network from its control
Recommended RS-232C / RS-485 converter: network.
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 inter-
face cable; max length = 15 m
When using simplied system for HART:
The following hardware is used VIATOR
RS232 HART Interface Model 010001
(MACTek)

All Rights Reserved. Copyright 2001, Yokogawa Electric Corporation GS 33Y05Q10-31E Nov. 7, 2005-00
<<Contents>> <<Index>> 23
Software Requirements
PRM Server
OS:
Windows Server 2003 Service Pack 1
Windows XP Service Pack 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 R10.1.0
Note: Oracle 8i cannot run on Windows XP and Windows Server 2003.
PRM Client
OS:
Windows Server 2003 Service Pack 1
Windows XP Service Pack 2
Windows 2000 (Server/Professional) Service Pack 4
Oracle Client 8.1.6/8.1.7 Net8i
Oracle Client 9.2.0
Oracle 10g: Oracle Database R10.1.0
Note: Oracle 8i cannot run on Windows XP and Windows Server 2003.
Software for document: Adobe Reader 6.0, Adobe Reader 7.0.0

The corresponding Oracle versions and Windows are shown below.

Oracle Version
Windows Oracle 8i Oracle 9i Oracle 10g
8.1.6 8.1.7 9.2.0 10.1.0
Windows 2000 Yes Yes Yes Yes
Windows XP No No Yes Yes
Windows Server 2003 No No Yes Yes

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 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 Multi-
plexer.
(without connecting CENTUM system.)
Types of Oracle Database Server Supported for PRM
Standard Edition
Enterprise Edition
(Personal Edition is not supported)
OPC Server (for STARDOM system)
OS:
Windows XP Professional Service Pack 1 or 2
Windows 2000 Professional Service Pack 4

All Rights Reserved. Copyright 2001, Yokogawa Electric Corporation GS 33Y05Q10-31E Jan. 1, 2006-00
<<Contents>> <<Index>> 24
MODELS AND SUFFIX CODES
PRM Basic Set (for new installation)
Description
Model PRMSET Plant Resource Management Basic Set
-S Basic Software License and Media fee
Sufx Codes 1 Always 1
1 English version
/N0025 Maximum number of connected devices: 25
/N0100 Maximum number of connected devices: 300
Option Codes
/N1000 Maximum number of connected devices: 1000
/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
Communications Server, Software Media for Plant Resource Manager and Electronic Instruction Manual Media for Plant
Resource Manager.
PRM Server (for new installation)
Description
Model SSS7700 Plant Resource Management Server [Media model: SSSSM02-C11]
-S Basic software license
-C Multiple software licenses (for 2 or more)
Sufx Codes
1 Always 1
1 English version
/N0100 Maximum Number of connected devices: 300
Option Codes /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 PC. Prepare a PC separate from HIS PC.
Note: This package uses Oracle 8i/Oracle 9i/Oracle 10g for the database. Prepare Oracle 8i/Oracle 9i separately from this pack-
age.
Note: Exaopc OPC Interface Package for HIS (LHS2411) is required to acquire device events.
PRM Server (for expansion)
Description
Model SSS7700 Plant ResourceManagement Server [Media model: SSSSM02-C11]
-A Software license for additional devices
Sufx Codes 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
Option Codes
/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 PC. Prepare a separate PC from HIS PC.
Note: This package uses Oracle 8i/Oracle 9i/Oracle 10g for the database. Prepare Oracle 8i/Oracle 9i separately from this pack-
age.
Note: Exaopc OPC Interface Package for HIS (LHS2411) is required to acquire device events.

All Rights Reserved. Copyright 2001, Yokogawa Electric Corporation GS 33Y05Q10-31E Nov. 7, 2005-00
<<Contents>> <<Index>> 25
PRM Client
Description
Model SSS7710 Plant ResourceManagement Client [Media model: SSSSM02-C11]
-S Basic software license
-C Multiple software licenses (for 2 or more)
Sufx Codes
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)
Sufx Codes
1 Always 1
1 English version
Option Code /HART For HART devices (*1)

Note: The function for connecting with FOUNDATION eldbus devices is included in the basic specication.
Note: This package cannot be installed in HIS PC. Prepare a PC separate from HIS PC.
*1: R2.02 or later version of Plant Resource Manager supports this option code.
When connecting HART devices, specify the option code /HART.

Any or all Plant Resource Manager (Field Communications Server, Database Server, and Client) can be installed on a
single PC.
Intelligent Calibrator Interface for PRM Client
Description
Model SSS7711 Documenting Calibrator Interface [Media model: SSSSM02-C11]
-S Basic software license
Sufx 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
Description
Model SSSSM02 Software Media for Plant Resource Manager
Sufx Codes -C Supplied media: CD-ROM
1 Always 1
1 English version

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

All Rights Reserved. Copyright 2001, Yokogawa Electric Corporation GS 33Y05Q10-31E Nov. 7, 2005-00
<<Contents>> <<Index>> 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
Sufx 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
Description
Model SSS7750 PLUG-IN ValveNavi [Media model: SSSAM02-C11]
-S Basic software license
-C Multiple software license (for 2 or more)
Sufx Codes
1 Always 1
1 English version
Option Code /FF-H1 For FOUNDATIONeldbus 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 eldbus devices, specify the option code /FF-H1.
PLUG-IN Application Media for Plant Resource Manager
Description
Model SSSAM02 PLUG-IN Application Media for Plant Resource Manager
-C Supplied media: CD-ROM
Sufx Codes 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 OPC Server for Windows
Please see GS 34P02Q61-01E for detail.

ORDERING INFORMATION
Specify model and sufx 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 eldbus 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.

All Rights Reserved. Copyright 2001, Yokogawa Electric Corporation GS 33Y05Q10-31E Nov. 7, 2005-00
Subject to change without notice.