gs33y05q10-32e

GeneralSpecifications

<<Contents>> <<Index>>

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

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

GS 33Y05Q10-32E

GS 33Y05Q10-32E©Copyright Jul. 26, 2006(YK)12th Edition Mar. 5, 2012(YK)

GENERALPlant Resource Manager (PRM®) is an asset management software tool for the digital network era. The PRM software manages field devices and maintenance work efficiently, and help reduce total cost of ownership (TCO) in an industrial plant.These packages support intelligent devices such as FOUNDATION™ fieldbus, HART, PROFIBUS, and field wireless (conforms to ISA100.11a) devices as well as conventional analog devices.

PRODUCT OVERVIEWPlant Resource Manager (PRM) consists of the following components:

PRM Server• Collects and stores maintenance related data such as device parameters, device alarms, and inspection memo in

the field.• Generates and manages centralized device information such as device lists, inspection schedules and records,

user-created electronic documents, and parts lists.• Generates maintenance alarms for field device maintenance with action guidance information (problem, cause, and

action) and notifies these alarms to the people who need them.

PRM Client• Provides device navigator windows in hierarchy tree view for monitoring and managing devices in a user-friendly

Windows-based operating environment.• Performs automatic device recognition and registration (plug & play) by using field digital networks such as

FOUNDATION fieldbus, HART, PROFIBUS, and ISA100.11a. Monitors device health status with maintenance alarms and communication errors. Also monitors errors of advanced device diagnosis, process interface diagnosis, unit diagnosis, and so on, which allows device parameter setting and performs device diagnosis, with PRM advanced diagnostics application.

• Displays status icons reflecting the communication and device status to let operators grasp the device status intuitively. A confirmation status icon appears for the devices with unacknowledged maintenance alarms (of the device health status).

• Device icons to be displayed on the device navigator can freely be defined by a user. The user can customize those fonts and icons depending on the user requirements and the screen size.

• Maintenance marks are a kind of flags to be assigned to devices for setting and checking maintenance status. The maintenance mark icon is displayed upon setting, and enables to temporarily change device access level. The maintenance marks can also be linked with CENTUM’s operation marks so that the maintenance engineers and operators can share the same information and coordinate their work.

• Performs online device adjustment/setting on screen using the same user interface with FieldMate versatile device management tool which is an on-site device adjustment/setting tool.

• Possible to exchange parameters and maintenance information between PRM and FieldMate.• Provides PRM advanced diagnosis application, device diagnosis data historian, and general-purpose diagnosis

tool for PRM advanced diagnosis function, in addition to the maintenance alarm function and device diagnostics function.

• Allows registering conventional analog field devices as well as field digital devices such as FOUNDATION fieldbus, HART, PROFIBUS, and ISA100.11a, for a true, centralized device management.

• Implements third-party calibration and diagnostic software tools as PLUG-IN applications. DeviceViewer (*1) and PLUG-IN ValveNavi are available from Yokogawa brand.

• Supports FDT/DTM (Field Device Tool/Device Type Manager) and EDDL (Electronic Device Description Language) technologies that enables PRM interfacing with field devices.

*1: DeviceViewer is a PLUG-IN application of the PRM client for self-diagnosis of field digital devices such as FOUNDATION fieldbus and HART. Download device definition files from each device vendor to run on the DeviceViewer prior to its use. DeviceViewer can be displayed on CENTUM VP/CS 3000 HIS with operation and monitoring functions. Use CENTUM CS 3000 R3.07 or later.

../submenu.htm

../../index.htm

2

All Rights Reserved. Copyright © 2006, Yokogawa Electric Corporation


GS 33Y05Q10-32E July 1, 2011-00

Field Communications ServerThis is a server to set and acquire field device data online. It implements data exchange between the field devices and the PRM client or the PRM server. Those data are distributed among maintenance support applications such as device status monitoring, device parameter tuning, and device diagnostics. PRM supports various types of field communication protocols (FONDATION fieldbus, HART, PROFIBUS, and ISA100.11a) and the following system configuration types are available.

Supported hardware• FOUNDATION fieldbus communication modules for CENTUM VP/CS 3000• AI/AO modules with HART communication for CENTUM VP/CS 3000• FOUNDATION fieldbus communication modules for STARDOM• AI/AO modules with HART communication for STARDOM• AI/AO modules with HART communication for ProSafe-RS• NI-FBUS card• 3rd party HART multiplexers (Pepper and Fuchs, MTL, ELCON, and STAHL)• 3rd party PROFIBUS communication devices (CommunicationDTM/GatewayDTM communications)• Field wireless integrated gateway (CommunicationDTM/GatewayDTM communications)

Multiple Server SwitchoverPRM manages CENTUM VP/CS 3000, ProSafe-RS, or STARDOM projects. It also provides an integrated monitoring for a large-scale project which is geographically distributed in remote locations. In case for the large-scale project where tens of thousands of field devices are installed, it is necessary to divide them into multiple numbers of PRM servers. PRM’s multiple server function enables to select which PRM server the PRM client refers to. In this way, a single PRM client is able to monitor several PRM servers.

PRM Advanced Diagnosis Server Function (optional)This sever function provides an environment for executing diagnostic algorithms by utilizing field device parameters.The diagnostic algorithm application can be configured by using the PRM advanced diagnostic software development kit (PAA-development kit) without any additional software program. By monitoring parameters and process data transmitted from field devices, the PRM advanced diagnostic function configures and executes diagnosis of the devices and assets.For details of the PRM advanced diagnosis, refer to general specifications of SSS7740 PRM Advanced Diagnosis Server (GS 33Y05Q21-32E).

PST Scheduler Package (optional)PST(*1) stands for a partial stroke test. The PST Scheduler schedules PST, automatically executes PST in accordance with the schedule, and manages the results in unified manners. It is possible to modify the planned schedules and switch PST execution from automatic to manual.For details of the PST Scheduler package, refer to general specifications of SSS7780 PST Scheduler Package (GS 33Y05Q23-32E).

*1: By slightly operating emergency shutdown (ESD) valves online which are not activated under normal conditions, PST is to check if ESD valves function correctly in case of emergency. By using PST, the interval period between full stroke tests can be prolonged without disturbing the safety of the ESD valves, thus the maintenance cost for those ESD valves can be reduced.

Interface for Computerized Maintenance Management System (optional)PRM has an interface with Maximo, a computerized maintenance management system (CMMS), from IBM Software, Inc. It enables PRM to provide maintenance information to the maintenance management system online. For details of the CMMS interface, refer to general specifications of SSS7730 Interface for CMMS (GS 33Y05Q20-32E).

Interface for GE Energy’s System 1® (optional)PRM is able to provide a single monitoring window for diagnosis of turbines, rotating equipment and reciprocating equipment under management by GE Energy’s System 1 Optimization and Diagnostics Software Platform in addition to field devices such as pressure transmitters and flowmeters.For details of System 1 integration, refer to general specifications of SSS7770 Interface for GE Energy System 1 (GS 33Y05Q22-32E).

../submenu.htm

../../index.htm

3<<Contents>> <<Index>>

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

SYSTEM CONFIGURATIONPRM manages a PRM server as one unit. The PRM system can be configurable in scalable ways – a minimum system consists of a PRM server, field communications server and a PRM client all resided in a single PC, and a large system with multiple clients. Examples of PRM system configurations are shown in this section.

System configurationCENTUM VP/CS 3000

HISExaopcOPC Interface for HIS

Field Communications ServerFOUNDATION fieldbus H1 Host Interface

PRM Client

PRM Server

Ethernet

Ethernet

bus 2

bus 1

FOUNDATION fieldbus H1 (for device adjustment)

HART devices

HART I/O Module ALP111PROFIBUS-DP

Field devices

FieldMate

ALF111

EthernetPROFIBUS-DPConverter

FCS

Terminator

Coupler

F01E.ai

FOUNDATION fieldbus H1

Terminator

Field WirelessIntegratedGateway

Field WirelessIntegrated

Gateway

Firewall

L3 Swittch

Wide-area Field NetworkField Wireless devices

HIS: Human Interface StationFCS: Field Control StationALF111: FOUNDATION fieldbus Communication Module

Field devices

Field Wireless devices

(*1)

ALE111

ALE111: Ethernet Communication ModuleALP111: PROFIBUS-DP Communication Module

Control Network

Figure: System Configuration (CENTUM VP/CS 3000 systems)

Note: A PRM server, a PRM client and a field communications server can run on a single PC. PRM client can run on the same PC where HIS/ENG is already installed.*1: Process data and diagnosis status can be displayed on HIS. As for configuration of ISA100.11a field wireless, see GS 01W01A01-01EN “Field Wireless System Overview.”

../submenu.htm

../../index.htm

4



GS 33Y05Q10-32E Mar. 1, 2011-00

STARDOMMessages from STARDOM controllers are transmitted to a PRM server via an OPC server. FCN/FCJ OPC Server for Windows (a software package) is required.

HMI Client

FCN/FCJ

HMI ServerData Server

OPC Server

Control Network

Ethernet

FCN

PCPRM Client

PCPRM ServerField Communication Server

Logic designer Resource Configurator

Controller

VDS/HMI PRM

CPU NFLF111PSU FCJ

(with FOUNDATION fieldbus H1 port)

F10E.ai

FOUNDATION fieldbus H1 Fieldbus

FOUNDATION fieldbus H1 Fieldbus

Terminator

Coupler

Terminator

Coupler

Field WirelessIntegratedGateway

Field Wireless devices

HART I/O module

HART device

FCNController

PSU NFAI141

CPU NFAI841

NFAI835

NFAI135

FieldMate

VDS: STARDOM versatile data serverHMI: Human machine interfaceFCN: STARDOM autonomous controller (field control node)FCJ: STARDOM autonomous controller (field control junction)NFLF111: FOUNDATION fieldbus communication moduleNFAI***: Analog I/O modules (with HART communication function)

Figure: STARDOM System Configuration

Note: A PRM server, a PRM client and a field communications server can run on a single PC. A PRM client and an HMI client can run on the same PC. A PRM server or a field communication server cannot run on the same PC where VDS is already installed.

../submenu.htm

../../index.htm



Notes for STARDOM configuration:PRM packages cannot be installed on a PC where STARDOM versatile data server (VDS) is already installed.It is recommended to install FCN/FCJ OPC server for Windows package on a different PC separately from PRM packages.Refer to the below table for combination of the software revision numbers when installing FCN/FCJ OPC server for Windows package on the same PC with PRM. Those combinations other than shown here, FCN/FCJ OPC server for Windows must be installed on a different PC separately from PRM packages.

FCN/FCJ OPC Server for Windows PRM

Revision R1.90 R3.02

R2.20 R3.03, R3.04

R3.01 to R3.10 R3.05

– R3.10

Up to 100 units of FCN/FCJ controllers can be connected to a field communications server. As for a large-scale system, use multi-server function to divide the number of controllers connected to a PRM server by the group of 100 units or less.

ProSafe-RS

HISExaopc OPCInterface package for HIS

PRM ClientPRM ServerField Communication Server

Control Networkbus 2bus 1

F15E.ai

HART device

ProSafe-RS

HART I/OModule

SCS

SENG

SENG: Safety engineering PCSCS: Safety control station

Figure ProSafe-RS System ConfigurationNote: A PRM server, a PRM client and a field communications server can run on a single PC. A PRM client and SENG can run on the same PC.

../submenu.htm

../../index.htm

6



GS 33Y05Q10-32E July 1, 2011-00

Communication with HART devices via MultiplexerPRM can communicate with HART devices via HART multiplexer connected to the serial ports of the field communications server.

Ethernet

Field Communications Server

PRM Client

HART Devices

HART Devices

HART Devices

PRM Server

Control Network

RIO bus

F05E.ai

FCS

AAM11AAM11

HIS/ENG

HART Multiplexer(3rd party)

RS CommunicationRS-485

(*1)

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

4-20 mA HART Digital Signals

HART DevicesAdapter board

AAM11: Current/Voltage Input Module

Figure Serial Port Connection via HART Multiplexer (Parallel Connection and Two-way Data Flow)Note: A PRM server, a PRM client and a field communications server can run on a single PC.

../submenu.htm

../../index.htm



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

Device Navigator

PRM

Maintenance Information Management

Audit Trail Management

Adjustment and Diagnosis

Other Functions

Plant ViewNetwork ViewClass ViewCustom View

Device MasterInspection MemoInspection ScheduleParts ListLink to Document

Parameter setting and tuning - DTMWorks - Parameter mangerFF DD menu windowDeviceViewerCalibration management (Optional)

Operation LogEvent Log of DeviceInspection LogRecord filtering

PRM Advanced Diagnosis (Optional)

BrowserSecurityExportSelf-documentationPLUG-IN ApplicationDevice TemplateDatabase Maintenance ToolPRM System BackupOnline ManualFieldMate Synchronization

Diagnostic NavigatorPRM Advanced Diagnosis Application (PAA)Device Diagnosis Data HistorianGeneral-purpose Diagnosis Tool

Maintenance Alarm

Message AcquisitionDevice PatrolFiltering

Maintenance Mark

PST Sheduler (Optional)

Interface for GE Energy System 1 (Optional)

PRM Advanced Diagnostic Application SoftwareDevelopment Kit (Optional)

Interface to Computerized Maintenance Management System (Optional)

F03E.ai

Figure: Organization of Functions

../submenu.htm

../../index.htm

8



GS 33Y05Q10-32E

Device NavigatorProvides four different views - plant view, network view, class view, and custom view.Each view displays devices in a plant in the form of a plant hierarchy tree view, in the Windows explorer-like format. In these views, device status is shown with icons utilizing the maintenance alarm function so that operators are able to judge the status of the devices at a glance. Where there are devices with unacknowledged maintenance alarms, unacknowledged alarm icons are displayed.User access can be restricted based on the device navigator hierarchy, which prevents unauthorized personnel from operating devices by mistake.

Plant viewDisplays devices and equipment modules in the plant in hierarchy tree view according to the actual structure of the plant, or plant layer. Not-in-use devices can be allocated either to the “Spare” folder for spares and failed or in-service devices to the “Out Of Service” folder.

Network viewDisplays the network hierarchy of devices connected to the field network in the tree view form.

Class viewArranges devices in a tree view by vendors, models, and revisions. Users can identify the status of how spare devices are used while devices-in-use are failed or under maintenance. Device templates can be created using this function.

Custom viewUser-created views can be created and displayed in the hierarchical structure. Devices can be categorized by the persons in charge of maintenance, by inspection or replacement schedule, operation or failure status, and so on.

Maintenance Mark Assign maintenance mark to each device electronically to let maintenance engineers identify the status of a device. Enabled to link it with CENTUM’s operation marks so that maintenance engineers and operators can share the same information and coordinate their work.

Maintenance Alarm FunctionThis is a message system to notify maintenance information and guidance messages. It broadcasts information necessary for device maintenance to all the maintenance engineers. The information contains not only messages generated by the devices, but also attributes such as message information, phenomenon, causes, and actions. Alarms generated by diagnostic functions can also be delivered to the users.

Message acquisitionAcquires messages from field digital devices as well as event messages generated by CENTUM, STARDOM ProSafe-RS, and third-party systems. User-defined information such as event priorities, objective information, phenomenon, causes, and actions are automatically added to the original event messages. These are acknowledged as maintenance alarms, and passed on to the filtering function.

Device patrolAcquires field device status provided by device’s self-diagnostics and generates maintenance alarms with the user-defined attributes such as message priorities, objective information, phenomenon, causes, and actions. These maintenance alarms are handed over to the filtering function. Data acquisition is done periodically or on demand. It also collects information from devices which do not generate alarm messages by themselves.

Filtering functionAll the alarms generated by message acquisition, device patrol, advanced diagnostic application, and manually-entered messages are filtered and the results can be notified by each users.

Mar. 1, 2011-01

../submenu.htm

../../index.htm


All Rights Reserved. Copyright © 2006, Yokogawa Electric Corporation GS 33Y05Q10-32E Mar. 1, 2011-01

Maintenance Information ManagementPRM acts as the central database for device maintenance information.

Device masterGenerates and manages a list of devices with all the relevant information. Users can display the list of all the devices or detailed information of the individual device. As for devices with field communication function, it is added to the device list automatically by plug & play upon recognition of the devices.

Inspection memoIncludes details of inspection, maintenance, or servicing tasks performed on a device or at a plant. Comments and remarks by maintenance engineers during servicing or maintenance can also be included as the service logs.

Inspection scheduleManages schedule information such as inspection, adjustment, and calibrations by each device.

Parts listContains components and attribute information of parts that compose of a device. As for Yokogawa field devices with digital network communication function, dedicated templates are provided.

Document linksManages device related documents such as plant structures (e.g. P & ID and control drawings), component spare parts list, online instruction manuals, and device images and enables users to access them by the device tag name as keys. These documents can be stored in a document server on an Ethernet and accessed by URL addresses.

Audit Trail ManagementManages and displays historical records of PRM operations, inspection records, and event information generated by the maintenance alarm function on the PRM client. These historical records can be shown by chronological orders, device priority, or message priority. With filtering function, the records can be displayed by the device IDs or device tag names.

Adjustment and Diagnostic FunctionsSupports devices’ adjustment and diagnostic functions online.

Parameter tuning and comparisonSets and displays device parameter online. With this function, PRM compares the saved and the actual parameters. The parameter set values are saved as logs. The device data can be uploaded and stored to the database at any time. PRM also supports one-time uploading of all the connected devices.

Tools• For FOUNDATION fieldbus communication Switches to DeviceViewer, DD menu, and diagnosis

navigator.

DD menu: This function is applicable for the devices supporting DD method (DD menu or enhanced DD). Using DD files provided by vendors, PRM implements device diagnostics and parameter tuning and setting, and calibrations. The specifications of the DD files are different by the field devices.

DeviceViewer: A PLUG-IN application to display device self-diagnostic results. Most of the field devices hold self-diagnostic results as the vendor-specific parameters. DeviceViewer reads those self-diagnostic results and displays them in user-friendly ways. It also displays device information that is usually displayed on the LCD of the devices. This function enables users to remotely monitor the devices connected to PRM without viewing the local LCDs.

• For HART communication Switches to DeviceViewer and PRM diagnosis

navigator.

DeviceViewer: Supports HART devices. Displays device status based on the self-diagnosis and setting status of the HART devices.

Calibration data managementPRM database manages and maintains device calibration data.Calibration results, differences, and judgment (pass or fail) are registered to the database and displays them on a PRM client. The approval function of the calibration data is available, and it allows only the authorized person to modify the calibration data once it is approved. Historical operation of the calibration data can also be saved by using the historical operation management function.When a documenting calibrator is used, the calibration data can be upload/download via communication. The calibration results are automatically saved into the database. The documenting calibrator connection is provided as optional.

../submenu.htm

../../index.htm

10



GS 33Y05Q10-32E

Other FunctionsBrowserSearches specific devices by the keywords of device attributes information such as device ID, device tag name, device tag comments, block name, and parameters.

SecurityDuring the maintenance of field devices, this function allows only authorized personnel to access PRM or limiting the scope of work so as to prevent troubles caused by mis-operations to happen or secure system safety.It asks a user to specify its user name so that the user can be traced back. The user names are recorded to the operation records. The user operations and its privileges are restricted by the user groups where they belong.By using the device security function, it is possible to display field devices on the device navigator only for the specified user group.

ExportA device list (device ID, device tag name, device tag comments, etc.) registered to the PRM database can be exported as a text file in CSV file format. With this function, PRM’s device information can be utilized by asset management software or others.

Self-documentationOutputs the data stored in PRM database in a document format. This function enables to let users manage device-related information electronically and print out on demands. The information displayed on each window can also be printed out in a format to make it a maintenance report.The following printing properties can be edited.• Printing range• Table of contents• Header and/or footer• Cover page

PLUG-IN applicationsA PLUG-IN application is a third-party software program that runs with PRM. It runs on a PRM client PC and accesses to field devices and PRM database via PLUG-IN application library. Among all the PLUG-IN applications, Yokogawa offers two packages - DeviceViewer and PLUG-IN ValveNavi. PLUG-IN ValveNavi is a software program for YVP110 valve positioner complied with FOUNDATION fieldbus to calibrate and execute advanced diagnostics using signature function such as device diagnosis. Its functions are equivalent to YVP205, a stand-alone type ValveNavi. For more details of the ValveNavi functions, please refer to GS 21B04C50-01E YVP205 YVP Management Software.

Supported PLUG-IN applications• DeviceViewer• PLUG-IN ValveNavi for YVP110 (Rev. 2.1 or later)• Other third party PLUG-IN applications approved by

Yokogawa.

Mar. 1, 2011-01

Device template functionProvides templates which a user can define device information of its own. These templates help simplify engineering work of individual device settings.

Database maintenance toolPRM’s database size increases in accordance with the number of connected devices and over long period of operations. This is a tuning tool to archive, retrieve, delete and clean up the database to optimize the PRM database to be used efficiently. The data can also be automatically archived to an external storage media.

Online instruction manualAll the instruction manuals are provided in PDF format on a CD-ROM. Users are able to view and print the electronic instruction manuals on-demand.

PRM system back-up scriptEnables users to back up and restore the conditions of the PRM system appropriate for the user environment such as registry information, PRM database, advanced diagnosis database and so on.

Relevant SolutionField asset KPI reportThis is a solution tool for InsightSuite®AE service solutions aiming for monitoring, diagnosing, and optimizing customer’s plant assets.By using this tool, users are able to have a good understanding of the device conditions and prioritize maintenance activities by using condition-based maintenance approach which allows users to prepare a better maintenance workflow plan. For details, refer to GS 43D02S03-02EN for Field Asset KPI Report, and GS 43D02A03-02EN for InsightSuiteAE AE service & engineering.

../submenu.htm

../../index.htm


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

MULTIPLE SERVER SWITCHOVERWith this function, asset management of multiple plants can be integrated. A “server-set” concept has been introduced and enables a PRM client to switch from a field communications server and a PRM server to other servers. A user has to define the server-set before use. With this function, a PRM client manages all the device management information of the multiple plants at a single location.

PRM can be connected with CENTUM, STARDOM, or ProSafe-RS systems on the same Ethernet.

Ethernet

Ethernet

Router

Control Network

Server Set A

PRMClient

PRM Clientwith multiple serverswitchover function

F07E.ai

PRMServer

Switchover between server sets

Field Communication Server

HIS

FCS

Ethernet

Control Network

Server Set B

PRMClient

PRMServer

Field Communication Server

HIS

FCS

Router

Figure: Multiple Server Switchover

July 1, 2011-00

../submenu.htm

../../index.htm

12



GS 33Y05Q10-32E July 1, 2011-00

Supported FunctionsAll the functions are available for use with FOUNDATION fieldbus devices, and there are several restrictions for HART, PROFIBUS, and wireless devices.

Table Supported Functions

Function Conventional

Devices(*1)

FOUDATION fieldbus

HART (*2)

ISA100.11a(*3)

PROFIBUS(*4)

Device Navigation Function

Plant View XX XX XX XX XXNetwork View — XX XX XX XXClass View XX XX XX XX XXCustum View XX XX XX XX XX

Maintenance Mark XX XX XX XX XX

Maintenance Information Management Functions

Device Master XX XX XX XX XXPlug & Play — XX XX XX XXRegister fromhost file set — XX X — X

Inspection Memo XX XX XX XX XXInspection Schedule XX XX XX XX XXParts List XX XX XX XX XXLink To Document XX XX XX XX XX

Audit Trail Management Function

Parameter History — XX XX XX XXInspection Memo History XX XX XX XX XX

Operation History XX XX XX XX XXDevice Event Message — XX XX — XX (*5)

Adjustment and Diagnosis

Parameter Tuning and Comparison — XX XX XX XX

Status Display — XX XX XX XXTool — XX XX — —Calibration — XX XX — —

MaintennanceAlarm

Plant View — XX XX XX XXNetwork View — XX XX XX XXClass View — XX XX XX XXCustum View — XX XX XX XX

Other Functions

Browser XX XX XX XX XXSecurity XX XX XX XX XXPrinting XX XX XX XX XXPLUG-IN Application (*6) — XX XX — —

FieldMate XX XX XX — —

XX: Supported X: Partly supported —: Not applicable*1: The conventional devices include 4 to 20 mA analog devices and static devices such as motors.*2: HART 5, 6, and 7 are supported, but Wireless HART is not supported.*3: Conforms to ISA 100.11a wireless system for industrial automation. (ISA = International Society of Automation)*4: Condition monitoring with device navigator is available for PROFIBUS PA device which conforms to PA profile. To find out if

the devices conform to PA profile, visit the PROFIBUS International web site or its device vendors.*5: PROFIBUS device event message is acquired via ALP111 PROFIBUS-DP communication module.*6: PLUG-IN ValveNavi and other applications.

../submenu.htm

../../index.htm



OPERATING ENVIRONMENT Hardware RequirementsThe required main memory size and disk capacity depend on the number of registered devices. The minimum hardware requirement is described here when no more than 3000 devices are connected to a PRM server. In case the system requires more than 3000 devices to be connected, please consult Yokogawa.In case the size of the required main memory differs between the Windows OS and the PRM packages (PRM server, PRM client, and field communications server), apply the higher of the two values.The main memory sizes required by the applicable Windows OS are as described as below:

Table Required Main Memory Size by Windows OS

Memory Size OS

Minimum MemoryRequirement

Recommended(for better performance)

Windows Vista Business Edition 512 MB 1 GB

Windows Server 2008 Standard EditionWindows Server 2008 R2 Standard Edition 512 MB 2 GB

Windows 7 Professional Edition 2 GB 4 GB

PRM ServerPC: IBM PC/AT-compatible machineCPU: Refer to the table below.Main memory: Refer to the table below.Hard disk space: Refer to the table below.Other requirements: DVD-ROM drive Ethernet cardDisplay resolution/colors: 256 colors or more

Table PRM Server Hardware Requirements (without Advanced Diagnosis Server)

Number of Devices 300 units or less 1000 units or less 3000 units or less

CPU Pentium - 1G Hz or higher (required)

Pentium - 1 GHz or higher (required)Pentium 4 - 2.8 GHz or higher (recommended)

Pentium 4 – 2.8 GHz or higher (required)Xeon Dual – 2.8 GHz or higher (recommended)

Main memory

For Windows Server 2008: 2 GB or more (recommended)For other applicable Windows OS: 512 MB or more (required).

For Windows Server 2008: 2 GB or more (recommended)For other applicable Windows OS: 512 MB or more (required), or 1 GB or more (recommended).

For all applicable Windows OS: 1 GB or more (required) 2 GB or more (recommended)

Hard disk space (*1) 3 GB or more (required)

5 GB or more (required)Use of a high-speed disk drive such as SCSI or RAID drive is recommended.

10 GB or more (required)Use of a high-speed disk drive such as SCSI or RAID drive is recommended.

PRM Database capacity (*2) 600 MB 2 GB 6 GB

*1: The minimum free space required is inclusive of the database capacity specified in (*2).*2: Device database size covers the required size for one year. The size is calculated with the assumption that comparing and

saving the parameters of all devices and function blocks with Parameter Manager for 5 times per year.

PRM ClientPC: IBM/AT compatible machineCPU: Pentium 1 GHz or higherMain memory: 256 MB or more (required), 512 MB or more (recommended)Hard disk space: 2 GB or moreCommunication unit: Ethernet cardPeripheral devices: DVD-ROM driveDisplay resolution/colors: 1024 x 768 or higher, 256 colors or more

July 1, 2011-00

../submenu.htm

../../index.htm

14



GS 33Y05Q10-32E July 1, 2011-00

Field Communications ServerPC: IBM/AT compatible machineCPU: Pentium 1 GHz or higher In case of more than 2000 devices are connected, 2.8 GHz or higher is required.Main memory: Refer to the table below.Hard disk space: 1 GB or moreCommunication unit: Refer to the table below.Peripheral devices: DVD-ROM driveDisplay resolution/colors: 256 colors or more

Table Hardware Requirements for Field Communication Server

CENTUM VP/CS 3000 connection

system ProSafe-RS

connection system

STARDOM connection system

Simplified system for FOUNDATION

fieldbus H1 device adjustment

Simplified system for HART device adjustment or

system connected to HART multiplexer

commDTM/gatewayDTM

communication

Main memory (*1) (*2)

• FCS/SCS 1-16 units (100+80 x number of FCS/SCS) MB or more recommended

• FCN/FCJ 1-16 units (100+60 x number of FCN/FCJ) MB or more recommended 256 MB or more

required512 MB or more recommended

256 MB or more required512 MB or more recommended

256 MB or more required{30+(commDTM/gatewayDTM main memory)×(No. of node)}MB or morerecommended

• FCS/SCS 17-44 units (1380+10 x (number of FCS/SCS-16)) MB or more recommended

• FCN/FCJ 17-100 units (1060+5 x (number of FCN/FCJ-16) MB or more recommended

Communication devices

Ethernet card Control bus interface card Control network interface card (VF702, VI702)

Ethernet card Ethernet cardFOUNDATION fieldbus H1 interface card

Ethernet cardCOM port Ethernet Card

*1: The specified hardware requirements do not include the requirement for third party CommDTM/GatewayDTM. Refer to the respective DTM documentation.

*2: The total memory requirement should be calculated by summing the memory requirement for each required function and connected system.

All-in-One Configuration (when all components – PRM Server, Field Communications Server, and PRM Client reside together in one PC)

PC: IBM/AT compatible machineCPU: The maximum CPU capability among the capabilities required for the respective packages, or higher.Main memory: Total sum of memory size required for the respective packages or the operating system (whichever is

higher), or more.Hard disk capacity: Total sum of available hard disk spaces required for the respective packages, in addition to a

virtual memory area of approximately 1 GB.Connectable number No. of stations: Maximum 24 of FCS/SCS or less. When the number of stations exceeds 24,

install PRM server and field communications server on separate PCs.Display resolution/colors: 1024 x 768, 256 colors or more

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

For STARDOM connection, two communication devices are required to segregate information and control networks.

../submenu.htm

../../index.htm



Software RequirementsPRM ServerOS: Windows Vista Business Edition with Service Pack 2 (32-bit) Windows Server 2008 Standard Edition with Service Pack 2 (32-bit) Windows Server 2008 Standard Edition R2 with Service Pack 1 (64-bit) Windows 7 with Service Pack 1 (64-bit)Others: Microsoft SQL Server 2008 (Runtime) is used as a database software and is included in a software media for Plant Resource Manager. Internet Explorer 8.0 or 9.0PRM ClientOS:

Windows Vista Business Edition with Service Pack 2 (32-bit)Windows Server 2008 Standard Edition with Service Pack 2 (32-bit)Windows Server 2008 R2 Standard Edition with Service Pack 1 (64-bit)Windows 7 with Service Pack 1 (64-bit)

Software for document: Adobe Reader 9.4 or XField Communications ServerOS:

Windows Vista Business Edition with Service Pack 2 (32-bit)Windows Server 2008 Standard Edition with Service Pack 2 (32-bit)Windows Server 2008 R2 Standard Edition with Service Pack 1 (64-bit)Windows 7 with Service Pack 1 (64-bit)

Driver:When PRM is connected with CENTUM VP/CS 3000 and/or ProSafe-RS, a control network driver is required. For simplified system for FF-H1 device adjustment, FF-H1 fieldbus interface card driver is required. And for communicating with devices via third-party gateway devices, third-party CommDTM/GatewayDTM are required.

Software Requirements for Connected SystemCENTUM VP

CENTUM VP: R4.01 or later R4.01 or later to support HART communication R4.02.30 or later to support ISA100 Field Wireless communication R4.03.00 or later to support Fast Device Patrol for HART

Exaopc OPC interface package (for HIS): R3.05 or laterExaopc OPC interface package (NTPF100): R3.01 or later

CENTUM CS 3000CS 3000: R3.01 or later R3.02 or later to support HART devices R3.07 or later to notify HIS of operatior guide message R3.08 or later for Consolidated Alarm Management Software for HIS (CAMS for HIS) consolidationExaopc OPC interface package (for HIS): R3.01 or later R3.02 or later to support HART devicesExaopc OPC interface package (NTPF100): R3.01 or later

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

ProSafe-RSProSafe-RS: R1.02 or later

R2.20 or later to support HART communicationExaopc OPC interface package (for HIS): R3.06 or later R3.07 or later to notify HIS of operatior guide message R3.08 or later for CAMS for HIS consolidationExaopc OPC interface package (NTPF100): R3.01 or later

FieldMatePRM: R3.02 or later to support synchronization with FieldMate.FieldMate: R1.03.01 or later to support synchronization with PRM.

July 1, 2011-00

../submenu.htm

../../index.htm

16



GS 33Y05Q10-32E Mar. 5, 2012-00

YOKOGAWA PRODUCTS AVAILABLE TO RESIDE WITH PRM ON THE SAME PC PRM ClientCENTUM VP HIS CENTUM CS 3000/HIS ProSafe-RS SENG STARDOM HMI Client PC

PRM Server or Field Communications ServerNeither PRM server nor field communications server can be installed on a PC where the products described above are installed.

MODELS AND SUFFIX CODESPRM basic set (for new installation)

Description Model PRMSET Plant resource manager basic set

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

Option Codes

/N0025 Maximum number of connected devices: 25 /N0300 Maximum number of connected devices: 300 /N1000 Maximum number of connected devices: 1000/N3000 Maximum number of connected devices: 3000

Note: The basic set includes licenses of a PRM client, a PRM server, and a field communications server; a software media for PRM; a device files media; and an electronic installation manual media.

PRM server (for new installation)

Description Model SSS7700 Plant resource manager (server) [Media model: SSSSM02-C11]

Suffix Codes

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

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

Note: Every project requires one PRM server.Note: This package cannot be installed with CENTUM VP/CS 3000 HIS, ProSafe-RS SENG, or STARDOM HMI client PC, and

need a separate PC.Note: Exaopc OPC interface package for HIS (LHS2411) is required to acquire device alarms and events.

PRM server (for expansion)

Description Model SSS7700 Plant resource manager (server) [Media model: SSSSM02-C11]

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

Option Codes

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

Note: Option codes of /T01 and /T02 are applicable to the PRM server license for 1,000 devices only and the total number of connected devices should not exceed 3000 devices with this option.

Note: This package cannot be installed with CENTUM VP/CS 3000 HIS, ProSafe-RS SENG, or STARDOM HMI client PC, and need a separate PC.

Note: Exaopc OPC interface package for HIS (LHS2411) is required to acquire device alarms and events.

../submenu.htm

../../index.htm



PRM client

Description Model SSS7710 Plant resource manager (client) [Media model: SSSSM02-C11]

Suffix Codes


Note: This package can be installed with CENTUM VP/CS 3000 HIS, ProSafe-RS SENG, or STARDOM HMI client PC.Field communications server

Description Model SSS7720 Field communications server [Media model: SSSSM02-C11]

Suffix Codes


Note: The functions to communicate with devices for FOUNDATION fieldbus, HART, PROFIBUS, and ISA100.11a are included in the basic specifications.

Note: This package cannot be installed with CENTUM VP/CS 3000 HIS, ProSafe-RS SENG, or STARDOM HMI client PC, and need a separate PC.

All or a part of the PRM functions (PRM server, PRM client, or field communications server) can be installed on a single PC.

Documenting calibrator interface for PRM client

Description Model SSS7711 Documenting calibrator interface [Media model: SSSSM02-C11]

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

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

Note: With the basic license, this software package can be installed in two or more PRM client PC.Software Media for Plant Resource Manager

Description Model SSSSM02 Software media for Plant resource manager

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

Note: The electronic instruction manual for this package is included in the media model SSSSD02.Device Files Media

Description Model SSSSM03 Device files media

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

Note: This media contains DD and DTM for field devices.

July 1, 2011-00

../submenu.htm

../../index.htm

18



GS 33Y05Q10-32E July 1, 2011-00

Electronic Instruction Manual Media for PRM

Description Model SSSSD02 Electronic instruction manual media for plant resource manager

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

Note: The PRM software media (SSSSM02) is required to install this media.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]

Suffix Codes

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

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

Note: This package runs on a PC installed with PRM client (SSS7710).Note: This software supports on FOUNDATION fieldbus devices.*1: To connect with FOUNDATION fieldbus devices, specify the option code of “/FF-H1.”

Software media for PLUG-IN ValveNavi

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: Electronic instruction for PLUG-IN ValveNavi is included in this software media.FCN/FCJ OPC Server for WindowsFor more information, refer to GS 34P02Q61-01E.

../submenu.htm

../../index.htm



SOFTWARE LICENSE VERSION UPGRADE FROM R2 TO R3This section is dedicated for the PRM R2 users who wish to upgrade to R3 for the benefit of using new functions that are only available from R3. Purchase every upgrading R3 license that match with the existing R2 (basic and multiple licenses). Specify the same number of connected devices as R2.

PRM server for upgrading from R2 to R3

Description Model SSS7700RU Plant resource manager (server ) upgrade [Media model: SSSSM02-C11]

Suffix Codes


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

Note: The option code of “/N0100” in R2.10 or earlier for maximum number of connected devices 100 units has been expanded to 300 units in R3. Specify “/N0300” in place of “/N0100.”

Note: PRM R3.10 requires Microsoft SQL Server 2008 which does not support Windows 2000. There are two ways to cope with PRM R2 operating on Windows 2000. One is to newly install R3.10. The other is to upgrade to R3.04 first, replace OS to the new one, then install R3.10. In the latter case, the device files and other database can be saved.

PRM client for upgrading from R2 to R3

Description Model SSS7710RU Plant resource manager (client) upgrade [Media model: SSSSM02-C11]

Suffix Codes


Field communications server for upgrading from R2 to R3

Description Model SSS7720RU Field communications server upgrade [Media model: SSSSM02-C11]

Suffix Codes


Note: Communication with HART devices is included as a standard function from R3, and there is no need to specify “/HART” option code which was necessary for R2.

Documenting calibrator interface for upgrading from R2 to R3

Description Model SSS7711RU Documenting calibrator interface upgrade [Media model: SSSSM02-C11]

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

Option Codes FLK01 Calibrator type: FLUKE 743B/744

July 1, 2011-00

../submenu.htm

../../index.htm

20



GS 33Y05Q10-32ESubject to change without notice.

Mar. 1, 2011-00

PRM basic set for upgrading from R2 to R3

Description Model PRMSETRU Plant resource manager basic set upgrade

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

Option Codes

/N0025 Number of connected device: 25 units or less /N0300 Number of connected device: 300 units or less /N1000 Number of connected device: 1000 units or less /N3000 Number of connected device: 3000 units or less

Note: PRM basic set for upgrading can only be purchased when a user has R2 PRMSET. Specify the number of connecting devices as the same as the existing one.

Note: The basic set includes a PRM server, a PRM client, a field communications server, a software media for PRM, and an electronic instruction manual media.

Note: The option code of “/N0100” in R2.10 or earlier for maximum number of connected devices 100 units has been expanded to 300 units in R3. Specify “/N0300” in place of “/N0100.”

ORDERING INFORMATIONSpecify model and suffix codes.

TRADEMARKS• PRM is a registered trademark of Yokogawa Electric Corporation.• CENTUM, Vnet/IP and Prosafe are registered trademark of Yokogawa Electric Corporation.• Pentium is a registered trademark of Intel Corporation.• Ethernet is a registered trademark of XEROX Corporation.• Windows and Windows Vista are registered trademarks of Microsoft Corporation in the United States and/or other

countries.• “FOUNDATION fieldbus” is a registered trademark of Fieldbus Foundation.• Adobe and Acrobat are registered trademarks of Adobe Systems Incorporated.• “HART” is a registered trademark of the HART Communication Foundation.• STARDOM is a trademark.• Other product and company names appearing in this document are trademarks or registered trademarks of their

respective holders.

../submenu.htm

../../index.htm

gs33y05q10-32e

Documents

eld device maintenance

device alarms

device icons

device parameters

device lists

eld device data

device vendor

device denition