FDM R430 spec EP03-480-430_V1_FDM

Experion PKS Field Devic Device e Mana Manager ger Specifi catio ns

EP03-480-430 Release 430 V0.8, V0.8, Jul Ju l y, 2012

Specifications subject to change without notice.

EP03-480-430, Field Device Manager Specifications

pg. ii

Table of Contents Introduction .............................................................................................................................................................................. 1 Product Overview .................................................................................................................................................................... 1 Key FDM Functions and Features .......................................................................................................................................... 3 Detailed Functions in FDM ...................................................................................................................................................... 4 Specifications and Sizing ........................................................................................................................................................ 8 FDM Capabilities Summary .................................................................................................................................................. 11 Configuration Guidelines ....................................................................................................................................................... 12 FDM Sizing and Capacity ...................................................................................................................................................... 13 Model Numbers ..................................................................................................................................................................... 19

Revision History Revisio Revisio n

Date Date

Descrip Descrip tion

0.1

29 January 2012

Initial draft (new HART 7 & SM Universal Safety I/O)

0.2

2 February 2012

Fine tuning of specification

0.3

9 February 2012

Corrected figs 4 & 5

0.4

19 March 2012

Added RocketPort RS-485 COM port extender

0.5

4 May 2012

Clarified FDM Gateway spec

0.6

22 May 2012

Corrected SM I/O naming

0.7

8 June 2012

SM specification correction

0.8

18 July 2012

Correct Win 7 specs


Introduction

pg. 1

Honeywell Field Device Manager Manager

features described in the DD/EDDL file or DTM are supported.

Field Device Manager (FDM) provides instrument technicians, engineers and maintenance personnel with an environment that simplifies tasks associated with smart instrument management, such as:

FDM fully supports the EDDL enhancements to the DD language specifications. These include advanced graphical features, data storage and manipulation features, and advanced parameter organization.

•

Configuration Diagnostics

•

Maintenance

•

FDM provides an open architecture that enables use of smart diagnostic data in any device from any vendor.

Product Ove Overview rview FDM is an asset management system for configuration and maintenance of smart field devices based on HART, Profibus and Foundation Fieldbus protocols. protocols. It provides support for: • •

•

•

•

•

HART devices via Experion-connected HART I/O, HART devices via non-Experion-connected HART multiplexers and modems, HART devices via Safety Manager Universal Safety Safety I/O I/O and Universal Safety Logic Solver, Profibus networks and PA PA (Process Automation) or DP (Decentralized Peripherals) devices using Profibus communication and Device Type Managers (DTMs), HART devices connected to Profibus networks via HART-over -Profibus gateway devices, and Foundation Fieldbus devices via Experion-connected Fieldbus I/O.

FDM allows the user to manage configuration of a large number of devices via FDM clients connected to m ultiple, distributed FDM servers. FDM users can remotely access and change HART, Fieldbus and Profibus device configuration settings.

Open Standards Support FDM supports industry open standards, thereby enabling its use as a single tool for managing plant-wide smart instrumentation, irrespective of the device type or manufacturer. FDM uses unmodified vendor Device Description (DD) files and Electronic Device Description Language (EDDL) files (HART only), as well as Device Type Managers for performing device configuration, management and diagnostics tasks. Functions and

FDM does not require additional files or programming to add support for new devices or to access device specific features.

HART Protocol The Highway Addressable Remote Transducer protocol, ® commonly known as HART , has existed as an open protocol since 1993 and provides a method to access information resident in smart field devices, such as transmitters, analyzers, analyzers, and valve positioners. HART is administered and maintained by the HART Communication Foundation (HCF), and is owned by HCF member companies. A complete list of available registered devices and member companies can be obtained from the HCF http://www.hartcomm2.org/.. web site at http://www.hartcomm2.org/

Device Device Descripti on Files Device Description (DD) files contain electronic descriptions of device parameters and functions needed by a host application to communicate with the devices. They are written written according to the DD DD language specification. DD files are devicespecific and are developed and made available by device vendors. EDDL, or Electronic Device Description Language, represents a significant extension to the DD language specification and includes such enhancements as: • •

•

graphical elements and waveforms, standardized access to historic measurements and device performance information, vendor-specified organization of device parameters, and

EP03-480-430, Field Device Manager Specifications •

enhanced tools for high-level information display and control system use.

EDDL enhancements provide for an improved user interface compared with the DD specification, with support for menus (windows, tabs and groups), graphs, charts and dial indicators. EDDL further further standardizes the user interface for managing intelligent devices and el iminates the need for Windows resource files, supplemental files, and other modifications. FDM provides full support of HART devices by interpreting both DD and EDDL EDDL files. It utilizes all the features of any HART device, irrespective of the vendor or manufacturer, the device version, and the release date. Support for DD and EDDL files includes device-specific commands, device-specific configuration, plus diagnostics and status information. The use of DD files enables FDM to make use of the HART protocol to provide asset management functions like device diagnostics, which help reduce fault isolation effort and enable higher plant uptime.

Field Device Tool (FDT) Techno Techno log y Increasingly complex and sophisticated field devices have led to device-specific software applications that access and analyze information about the field device and its condition. FDT provides an open open standard for integration of such software software applications. FDM supports that standard. FDT standardizes communication between field devices and systems. The key feature is its independence from the communication protocol and the software environment of either the device or the host s ystem. The device supplier develops a Device Type Manager (DTM) for each of its devices or group of devices. The DTM can alternately be developed directly from the DD file if available. The DTM encapsulates device-specific data, functions and rules, such as the device structure, its communication capabilities, internal dependencies, and the human machine interface (HMI) structure. structure. The DTM provides functions for accessing device parameters, configuring and operating the device, and diagnosing problems. DTMs can range from a simple graphical user interface (GUI) for setting device parameters to a highly

pg. 2 sophisticated application capable of performing real-time diagnosis and maintenance calculations. The DTM is installed as a Windows application and loaded and launched in an FDT container or "frame" application. In the case of FDM, FDM, this “frame” is the the FDM Client. It provides the FDT container that defines the interface between FDM and the DTMs. Frame applications can be device configuration tools, control system-engineering tools, operator consoles or asset management tools. The frame application also contains communication components to interface the host system with the specific communication protocol (e.g., HART, PROFIBUS, PROFIBUS, Fieldbus, etc.). For FDM, the Client initiates initiates the DTM and enables the device to interoperate with the s ystem engineering and operating environment.

Foundation Fieldbus FOUNDATION™ Fieldbus (FF) is a technology for integrating buspowered field devices with digitallybased process control systems. systems. It defines how "smart" field devices communicate and operate with other devices in a control network. A unique feature of FF technology is control in the devices. FDM supports FF devices connected to Experion for which vendor-specific DTMs DTMs are available. These devices are connected to the Fieldbus Interface Module, or FIM. Because Experion provides full DD and EDDL support for FF, DTM support in FDM is considered to be supplemental, primarily for the purpose of running diagnostics and other asset management functions. functions. Note that DD and EDDL files for Fieldbus devices are m anaged in Experion, not in FDM.

Standards Versions FDM fully supports HART devices with HART protocol versions 5.X, 6.X 6.X and 7.X. FDM supports Device, Device, Gateway and Communication DTM types with version 1.2.1.


Tight Integration with Experion & Safety Manager

pg. 3 •

FDM is tightly integrated with Experion and Safety Manager. The various aspects of of this integration include: •

•

•

•

Connectivity with Experion : FDM connects to all Experion HART and Fieldbus enabled I/O devices, automatically building its database from the Experion database. Multipl exer exer (MUX) (MUX) Monitori ng : The FDM MUX Monitoring option monitors HART devices on hardware multiplexer/remote I/O networks and provides alerts to the Experion alarm and event system.

•

•

Integration wit h Experion Device Detail Detail Displays: HART and Fieldbus device detail displays in Experion Flex Stations include an optional integrated capability to view/configure FDM data via an embedded client. Note this is limited to Flex Station only. Integration w ith Safety Safety Manager Manager : FDM supports Safety Manager Universal Safety I/O and Universal Safety Logic Solver in two network configurations – Experion with Safety Manager integrated and standalone Safety Manager. When connected to Experion, the user has the option to view safetyconnected HART device alerts in Experion.

•

•

•

Key FDM Functions and Features The summary below describes important FDM features. Note that many features and functions are optional, as indicated in the Model Number section of this document. •

•

•

•

Instrument Configuration and Diagnostics : With FDM, fully configure, calibrate and diagnose any HART, Fieldbus or Profibus device from any vendor. FDM uses unmodified vendor-created DD files (for HART only) or DTM based software plug-ins for performing all these functions with the device. Instrument Database Database: FDM includes a centralized instrument database that is capable of storing the current and historical configurations and details of a large number of HART, Fieldbus and Profibus devices. HART Device Device Communicati ons : FDM communicates with HART 5, 6, and 7 devices connected to Experion HART enabled I/O as well as HART devices connected to hardware multiplexers, remote I/O systems and HART modems. Fieldbus Device Device Communicatio ns : FDM communicates with Fieldbus devices connected to Experion FIMs via vendor-supplied DTMs. All features provided by the DTM are supported.

•

•

•

•

Au di t Trai T rai l : FDM can maintain maintain an audit log of user actions performed on the device, describing the action made, the user and the timestamp for each event. The audit log is designed to support users (such as the pharmaceutical industry) that must meet the requirements of 21 CFR Part 11. MUX Monitori ng : The MUX Monitoring option continuously monitors HART devices on hardware multiplexer/remote I/O networks and provides alerts from these devices as standard Experion alarms and events as well as device on-line data for displays. Offline Configuration : FDM can provide the ability to configure devices offline and store the configuration into a database or file. The configuration can then be downloaded to a device once the device is online. This is supported for DD as well as for DTM driven device configurations. Export/Import : FDM can export live and historical device data, the list of devic es, etc., into a common file format for use with other applications. Display Filters : FDM provides the ability to to configure custom views of the plant network and then vie w a subset of associated devices with a user friendl y name such as “UNIT 1” or “ALL HON STT25H.” Enhanced History Functions : History records of devices can be saved, using user friendly names for convenience. History can be be managed with features such as the ability to delete a specific history record or a set of history records. Device Device Documentation Suppo rt : FDM allows you to add device documentation, such as user manuals a nd P&ID diagrams, diagrams, to the FDM database. Documents associated with a device are easily invoked from FDM Client. Experion Redundancy Redundancy Suppo rt : FDM supports automatic Experion Redundancy switchover such that there is no loss of network view. No action is required to re-detect devices. Backup and Restore Capabilit Capabilit y : The FDM database can be backed up and restored usi ng a dedicated utility for that that purpose. In addition, functions like the merge of two databases can be achieved b y using the export/import feature. Security : Access to FDM is secured secured via a user ID and and password. FDM provides a role-based security system that allows administrators to define sitespecific roles and assign allo wed tasks for these roles. The user authentication system can be based on FDM specific application level security or the Windows login. FDM supports single sign-on when Windows based security is used.

EP03-480-430, Field Device Manager Specifications •

•

•

FDM HART HART Multi plexer : This option allows vendorvendorspecific third-party software tools to access HART devices connected through Experion HART-enabled I/O or multiplexer-connected multiplexer-connected I/O. This way, devicespecific software applications can integrate with FDM. Applications must be capable of supporting supporting the P+F KFD HART multiplexer system communication protocol. Device Device Access Contro l : FDM provides a unique Device Access Control feature whereby write access to any device, set of devices, or entire network can be managed under password protection. This is especially critical for safety-connected devices. Health Status : FDM provides health monitoring for all HART, Fieldbus Fieldbus and Profibus Profibus devices. This even extends to HART-over-Profibus. HART-over-Profibus.

Detailed Functions in FDM Devic Devic e Parameter Parameter His tor y Database The FDM database stores all parameters for each connected device when when requested by the the user. The historical device parameter data is accessible through the device tag and is available for comparison purposes. The comparisons can be made with historical data or current data.

Audi Au di t Tr ail Audit Trail is an optionally licensed feature feature of FDM. When available, FDM records all actions performed by the user. Examples of the recorded actions include: • • • •

Device parameter changes Device method executions and results Discovery of devices on the network Malfunctions reported by devices or the networks connected

Each audit log item is stored with the timestamp, user name and the action performed along with all applicable details (device tag, etc.). It is possible to export the the audit trail into a XML file and use for printing or reporting purposes. This feature helps plant operations operations and maintenance comply with standards for change management and automate documentation generation for audits. The audit trail functionality functionality allows users to to meet the 21 CFR Part Part 11 regulations. It is also possible to manually add an event to the audit trail which is useful for

pg. 4 tracking inspections, tracking checks, and closing a work order ticket.

Multiplexer Monitoring Multiplexer Monitoring, also called MUX Monitoring, is an optionally licensed feature used when hardware multiplexers or remote I/O systems are used to connect to HART devices. Hardware multiplexers are used, for example, with Honeywell Fail Safe Controller (FSC), Safety Manager, PMD Controller, TPS or third party PLCs and DCS systems that do not support HART enabled I/O. Remote I/O systems are used when third party I/O is integrated with Experion via open protocols like Profibus/Modbus. With this feature, FDM continuously monitors the HART devices on the hardware multiplexer/remote I/O network. It raises alerts for all devices reporting problems and provide on-line data for displays. The alerts from these HART devices are available as normal alarm s and events in Experion. Additional features include: •

• •

The ability to have simultaneous configuration and monitoring of devices on the same multiplexer/remote I/O network Supports commonly used HART multiplexers Provides tools that that makes engineering of the solutions easier

The Multiplexer Monitoring functionality requires an Experion Server and a node running the ACE component. With TPS systems, an Experion Server TPS (ESVT) will provide the required support. TPS sites with many HART devices may consider this feature along with an HMI upgrade. With FSC or Safety Manager, this feature helps provide the uniform presentation of HART data in a s ystem where FSC or Safety Manager does not use HART enabled I/O. The Multiplexer Monitoring functionality is available with MTL, P+F, Elcon and R. Stahl multiplexer networks. Experion process I/O point licenses must be considered for HART devices devices connected to use this feature. feature. For all devices being monitored through multiplexers/remote I/O systems, it is necessary to purchase process I/O point licenses as part of the Experion Server point l icense count.


Offline Configuration Offline Configuration is an optionally licensed f eature and allows users to configure devices without them being physically present. Such configurations are stored using user friendly names in the database or in separate files, and they can be downloaded to devices when they are physically connected. Configurations can also be captured captured and stored in the database from live devices, from device history or be created completely from scratch. This feature greatly reduces configuration effort during plant startup. Maintenance can use this function during production to easily replace a faulty device with a new one by simply taking the historical configuration of the faulty device and downloading it to the new device.

FDM HART Multiplexer (FHM) In addition to support by DD files and DTM standards, some vendors provide device-specific software tools that interact with their specific HART devices to perform special tests or configuration actions. In this case, the FDM software emulated HART Multiplexer can be used as the bridge between the vendor’s third-party application and any matching HART HART devices in the the FDM system. The FDM HART multiplexer runs on a separate FDM Client PC on which the third-party application also runs. T he FDM Client component is needed to configure the link between a HART device and its special t hird-party application.

pg. 5 •

Securit Securit y and access access contr ol FDM provides a secure environment protected by user ID and password. FDM supports role role based security, which which allows administrators to define site-specific roles and assign tasks to be allowed for these roles. The user authentication system can be based on an FDM specific application level security or on the users’ Windows login ID. FDM supports single sign-on when Windows based security is used. used. This can be used in both Windows domain and Windows workgroup environments. FDM also provides a unique application level security, whereby a user can “lock” a particular device c onfiguration and prevent users of lower access levels from m aking changes to the device setup.

Export/Import Export/Import Capability Capability FDM provides the ability to export the f ollowing information into a HTML, XML, or CSV (for use with Excel) files: • • •

Device Device Documentation Documentation Support This feature is available as part of the base FDM license. It allows users to attach and associate documentation with devices stored in the FDM database. Such documents are made available to users whenever the device is being viewed in the FDM display. The documentation can can be of any format (Word, (Word, Excel, PDF, etc.). etc.). The documents can be added at various levels:

•

•

The architecture diagram in Figure 1 depicts an example FDM system combined with Experion and non-Experion I/O. Other concepts are given in illustrations on page 12. There are three major components of FDM. They are:

Plant Level : Documents added at this level are available from the context menus of all devices opened in FDM. The documents ideal for this level include plant standard procedures, safety manuals, etc. Device Type Level : Documents added at this level are associated with a device type (such as a STT25H or DVC 6000) and are available from the context menus of all devices of this type opened in FDM. The documents ideal for this level include device manuals.

Current device configuration with parameter values Device history with parameter values Device parameter and methods audit trail trail information information System audit trail info

FDM Compon ents

• •

Device Level : Documents added at this level are associated with an individual device and are available from the context menus of only this device. T he documents ideal for this level include instrument maintenance records, special instructions etc.

•

FDM Server : FDM Server is the core component and provides configuration and management functionality. Server maintains the database for all connected HART, Fieldbus and and Profibus devices. FDM Server can run in either a server or workstation grade machines FDM Client : FDM Client, which can connect remotely to any available FDM Server, provides the user interface. FDM Clients can be distributed throughout throughout the plant, providing access to device data from remote


pg. 6

Experion

PCs. The FDM Client is also needed to to run FDM HART Multiplexer. •

FDM interfaces with Experion Server over an Ethernet network and provides access to the HART and Fieldbus devices connected to the respective I/O. HART I/O makes use of both analog and digital data, but only the digital HART information is passed onto FDM. HART I/O modules exist for Experion Series C, Experion Chassis I/O – Series A, and PMIO. PMIO. For Fieldbus, the 2-Link Series A FIM, 4-Link Series C FIM and 8-Link Series C FIM are supported.

FDM RCI: The FDM Remote Communication Communication Interface allows devices connected to remote or local PCs to communicate with the Server over a local or wide area network. network. This network greatly greatly expands the distance limits of local serial (RS-485) communication networks used with MUXs, modems and remote I/O systems.

FDM RCI can be installed in PCs in remote relay rooms where RS-485 RS-485 cables terminate. Connection between the the FDM RCI to the FDM Server is accomplished via Ethernet. FDM RCI will also allow for a connection to a HART modem or a Honeywell Smart HART DE modem through an RS-232 port for local bench top configuration.

FDM R410 requires Experion R400 R400 or greater. Earlier versions of FDM are compatible with earlier versions of Experion.

HART Hardw Hardw are Multipl exers/Remot exers/Remot e I/O I/O systems The FDM Server also connects to popular hardware multiplexers, remote I/O systems and to RS232 HART modems either directly or through the FDM RCI.

HART Hardware Multiplexer systems have existed for many years and are useful where HART enabled I/O are not available. Terminal panels are used to split the the HART analog signal and the digital signal into two distinct pathways. The analog signal is routed d irectly to the control or logic system while the digital data is routed through a separate (RS-232/RS-485) communication link.

Supported HART Networks FDM allows the user to connect to and communicate with HART field devices through four different networks. The user can monitor or change device co nfiguration through the following architectures or HART networks.

MODEM

Hardware MUX solutions from P+F, MTL, Arcom, Elcon and R. Stahl are are supported by FDM. These interfaces can

t FDM Clien

FDM Client

FDM Client

FDM Client

Experion

Experion

Station

Station

Honeywell H ART-DE ART-DE Modem

Experion Server

Experion ERDB

FDM Server

Remote Node

Gateway PC (ACENode) FDM/ Instrument Database

FDM FDM Gateway Gateway

RS232

MUX Monitoring

O A / I A O A / ) I 6 A 5 7 O 1 O / ( I A / I A A - C s s O e e I i r i r M e e P S S

RS485 M M I I F F A - C s s e e i r i r e e S S

Safety Manager Profibus Gateway

SM I/O

HART DEVICES FIELDBUS DEVICES

MUX

PROFIBUS DEVICES

HART DEVICES

Fig. 1, Field Device Manager Basic Architecture Example

HART DEVICES

EP03-480-430, Field Device Manager Specifications be used with Honeywell TPS, FSC, PMD, and nonExperion controllers and PLCs.

pg. 7 number of HART devices to date combined with the maturity of the HART specifications has proven this to be a valid assumption.

HART Modem The HART modem allows the user to configure HART devices in the maintenance shop and on the bench top. Connection is made using one of the PC serial COM or USB ports. The port connects to a HART modem, and the modem connects to the HART device. HART modems are available from multiple third party suppliers.

Honeywell Smart (HART + DE) Modem FDM also supports the connection to HART devices through the Honeywell Honeywell HART DE Modem. Note that only the HART mode is supported.

HCF, FDT/DTM, and Device Vendor Testing The HART Communication Foundation (HCF) developed standard application program source code for DD-enabled hosts, like FDM, and handhelds, to use as the core online configuration tool. This program is known known as SDC-625 (Smart Device Configurator), and its source code is used in FDM as the basis for DD interpretation and device configuration. It is also the the basis of Honeywell’s Honeywell’s MC Toolkit Configurator, a Pocket PC-based engineering and maintenance tool. SDC-625 is used by the HCF as the basis f or all HART device registration testing. testing. It is also used by most device device vendors as the basis for their device d evelopment and testing. Because FDM uses the same code as the HCF testing program, Honeywell does not maintain a test program for HART HART devices. Experience with a large

Honeywell maintains a test program for the qualification of device DTMs with with Field Device Manager. Manager. Although most devices integrate easily, in some cases device manufacturers’ interpretations of the FDT/DTM specifications may vary. vary. This test program is essential to identifying and addressing any such issues. It is not a requirement to test devices to insure they will work correctly with FDM, but we are happy to test any HART, Fieldbus or Profibus device DTM at no ch arge

Migration FDM supports migration from the previous two releases to the current release. During migration, the database contents and any user created resources/templates are retained. Any changes to the database database are made to the existing ones to comply with the new f ormat.

Safety Safety Manager Integration The Safety Network interface enables you to communicate with HART devices associated with Universal Safety I/O Modules connected to Safety Manager (SM) systems. Universal Safety I/O and Universal Safety Logic Solver modules with HART capabilities are connected to the network via the SM Controllers, and FDM accesses HART devices through the SM Controllers. Two network configuration options are available, Experion with integrated Safety Manager and standalone Safety Manager.


pg. 8

Specifi Spe cifi cations and Sizing FDM Server PC (Standard) The standard FDM Server supports a similar PC hardware hardware configuration as the Experion Server. A PC must meet the following specifications to be used as an FDM Server. Honeywell supplied platforms will meet these specifications but may not necessarily be the example platforms listed be low. System Configuratio n

Minimum

Typical

Perfor Perfor mance

Processor

Intel® Xeon® 2.80 GHZ or Faster

Single CPU: 2.33 GHz Dual Core XEON or faster

Dual core AMD Opteron 2.80 GHZ or faster

RAM

2 GB

Networking

100 Mbps Ethernet or FTE

Video Resolution

1024 x 768 or 1280 x 1024 (standard) 65K colors

Hard Drive

60 GB

Operating System

Windows Server 2008 Standard

Example Hardware

MZ-PCSV02

MZ-PCSV10

MZ-PCSV22

PE T105-based Server Platform, 1GB, tower

Dell Power Edge SC1430, 2CPU (non-RAID)

PE T610-based Server RAID5 tower, or MZ-PCSV52 PE R710-based Server RAID5 2U rack

1

Please contact your Honeywell representative for Honeywell-supplied platform details. Note 1 – Note 2 – Note 3 –

1

2 GB

80 GB

4 GB

80 GB

For better performance, performance, users users should upgrade the systems systems to Performance specification. The systems listed here are for for comparison only. only. The default system system configuration configuration of this platform platform sold by Honeywell Honeywell will meet or exceed the recommended components listed. 10 Mbps Ethernet Ethernet Network between between Servers and Stations Stations is no longer longer officially supported, supported, although it may may still work on very small systems.

FDM Server PC (Windows 7) The FDM Server can alternately be installed and run in an OptiPlex 3 90 economy workstation platform (or later revision) using the Windows 7 operating operating system. This provides price/performance level below the the currently qualified Experion Dell Precision platforms, with reduced capacity specifications. specifications. See the FDM Sizing and Capacity tables for details. System Configuratio n

Minimum

Processor

Single Intel® Core™ 2 Duo E7500 (2.93 GHz or greater)

RAM

3 GB minimum

Networking

100 Mbps Ethernet or FTE

Video Resolution

1024 x 768 or 1280 x 1024 (standard) 65K colors

Hard Drive

160 GB SATA 3.5”, 7200 RPM drive minimum

Operating System

Windows 7 Professional or higher (32-bit and 64-bit)

Hardware

Dell OptiPlex 390 Platform or later equivalent revision


pg. 9

FDM Client and FDM RCI RCI PC The FDM Client/RCI supports a similar PC PC hardware configuration as the Experion Station. A PC must meet the following specifications to be used as an FDM Client/RCI. Honeywell supplied platforms will meet these specifications but may not necessarily be the example platforms listed below.

System Configuratio n

Minimum

Typical

Perfor Perfor mance

Processor

3.0 GHz Pentium IV or faster

Single 2.33GHz QuadCore XEON or faster

RAM 2 Networking

1GB 100 Mbps Ethernet or FTE

Single 2.83GHz QuadCore, RAID1 XEON or faster 4 GB

Video Resolution

1024 x 768 or 1280 x 1024 (standard) 65K colors 40 GB 40 GB Windows 7 or Windows Server 2008 Standard

Hard Drive Operating System Example Hardware Please contact your Honeywell representative for Honeywell-supplied platform details.

1

MZ-NTPC31, MZ-NTPC32 (based on Dell Precision WS360, WS370)

2GB

MZ-PCWS32 T5500-based 2GB Workstation tower

80 GB MZ-PCWS42 T5500-based 2GB Workstation RAID1 tower

Note 1 –

For better performance, performance, users users should upgrade the systems systems to Performance specification.

Note 2 –

10 Mb Ethernet Network Network between Servers and Stations Stations is not officially officially supported, although although it may perform perform acceptably on small systems.

Note 3 –

The FDM RCI PC should have enough slots to add COM Port extenders extenders if they plan to be used

FDM Gateway PC The FDM Gateway PC runs the ACE component, and therefore FDM Gateway is recommended to be installed i n a PC which meets ACE platform requirements. requirements. The PE T610 and PE R710, suitable for the FDM Server performance performance grade PC, are supported and qualified for FDM R430 Gateway Gateway nodes. Note that this node may not be used as a licensed Experion ACE node.

Virtualization Virtualization Support All FDM components – Server, Server, Gateway, Client, and RCI – have been tested tested with VMware and are fully supported. For more general information about virtualization, please refer to PN-11-16-ENG, Honeywell Process Solutions Virtualization Overview. For relevant VMware specifications, refer to EP03-700-100, EP03-700-100, HPS Virtualization Specifications, Specifications, Ver.1.3 or later. The performance requirements for running FDM nodes in a v irtualization environment are captured in the HPS Virtualization Spec and will not be listed in this document.


pg. 10

Virtualization Virtualization Client Access Li censes Honeywell provides value add additions to the virtualization layer. For this additional value, a Client Access License (CAL) is required for the use of FDM Software Software in a virtualized environment when used at Level 2. This is not required for Level 3 and above. Some of the things things that Honeywell provides with these CALs include: • • • •

•

•

VMware Certified TAC professionals located in each region region around the the world Extensive certification certification and approval approval for our our applications to ensure that they work correctly virtualized Testing and guidance around VMware patches Development of solutions solutions such as the Backup Control Center Center solution that solves new industry problems leveraging virtualization. Implementation and Planning Guide that provides the best practices for installing and configuring configuring your virtual virtual environment. Supply, support the complete virtual environment including the Hardware, Hypervisor, Hypervisor, OS and Honeywell Software.

FDM Virtualization Client Access License models can be found in the the Model Number section of this specification. The following rules apply to FDM Virtualization CALs: • • • •

•

FDM Virtualization Virtualization Server CAL, CAL, HC-FDMVMS, HC-FDMVMS, applies to FDM Server and FDM Gateway. Gateway. FDM Virtualization Virtualization Client CAL, HC-FDMVMC, HC-FDMVMC, applies to FDM Client and FDM RCI. A CAL must be purchased for each running, on-process Level 2 virtual machine that contains the referenced referenced node. A CAL is NOT NOT required for (a) Level 3 and above, (b) a node which is already covered by a CAL license, such as Experion Station, or (c) an off-process virtualized node used for backup or training. The term “on-process” “on-process” in this case means “FDM is connected to any external system, Honeywell or third party, where where that connection is used to access real-time or historical data. Data in the system is live process or instrument information.”


pg. 11

FDM Capabilities Summary The table below summarizes the capabilities of FDM with respect to each of the three supported dev ice open protocols, HART, Profibus and Foundation Fieldbus. It also presents a comparison of capabilities as applied to DD/EDDL versus FDT/DTM technologies.

HART HART FDM Capability Device configuration (online)

Profibus

DD

DTM

●

●

●

●

Offline configuration (template)

●

●

●

●

Save history

●

●

●

●

●

●

●

●

Audit trail Compare history to live device Attach documents to to device types (Library)

DD

DTM

Fieldbus

DD

DTM

● ●

Bulk operations (history and offline templates)

●

Station Maintenance view

●

●

●

Third-party application integration

●

Device health scan (non-FDT networks)

●

●

●

Display filters

●

●

●

●

●

●

Advanced search

●

●

●

Attach documents to to devices

●

●

●

Import / export (tags, audit trail, history, and offline configuration)

Connects to Experion

●

Connects to MUXs & provides MUX monitoring

●

Connects to Comm/Gateway DTM

●

Dynamically updates devices (non-FDT networks)

●

●

●

●

● ●


pg. 12

Configuration Guidelines FDM configuration rules are provided below: •

The following table describes FDM Client software software component compatibility: FDM FDM Client softw are is support ed on any node running the follow ing softw are components: • • • • • •

Operating System only FDM Server software RCI software Experion Station - Flex (ES-F) software Control Builder Client software Experion Backup & Restore software

FDM FDM Client Client sof tware is not sup ported on any node running the follow ing software components: • •

•

• •

•

The following table defines what what components are considered licensable, process points points by FDM: The followi ng items are treated as as indiv idual, licensed process points by FDM: •

•

•

• •

• •

•

•

•

• •

• •

• •

• •

•

•

Experion Station - TPS (ES-T) software Experion Station - Console (ES-C) software Experion Station - Console Extension (ESCE) software Experion Server software Experion Server TPS software

HART, Profibus PA or DP, or Fieldbus devices I/O Modules (Series C, Series A and PMIO) C300 or C200 Controllers MUXs Safety Managers, Universal Safety I/O and Universal Safety Logic Solver modules COMM DTM or Gateway DTM Fieldbus FIM and each Fieldbus Link

The follow ing items are NOT treated treated as individual, licensed process points by FDM: • •

• •

FDM Server itself Communication Servers RCIs Network Interfaces

The FDM Client and FDM RCI can be installed installed on the same PC as Experion Flex Station. The FDM Client and FDM RCI cannot be installed on the same PC as Experion Console Station (ES-C) and TPS Station (ES-T). An FDM Client can connect to one FDM Server at a time. The Server Server connection is established established when launching Client and can be changed from within the client without closing FDM. No other server-based server-based application or any application using SQL Server may be installed in the same PC as the FDM Server. Experion Server Server may not be installed installed in the same node as as FDM Server. When used with a redundant Experion Experion Server configuration, configuration, under normal conditions FDM should be configured to communicate with the backup server. One FDM RCI can connect to one FDM Server Server only. If an RCI in the the same PC as FDM Server is used for large MUX networks, the the RCI can have a negative impact on Server performance. When MUX Monitoring feature is used, the FDM FDM Server can talk to to and raise alerts to up to 6 Experion Servers. Each HART device connected to to Experion via FDM Multiplexer Monitoring counts counts as 1 process process point license to the Experion system. For Fieldbus devices, devices, FDM supports only the DTM view. DDL/EDDL view is seen from Experion Experion only. An FDM Gateway PC can connect to only one Experion Server. Server. Even if two FDM Gateways Gateways reside in the Gateway PC, they must both connect to the same Experion Server. No MUX hardware license is required required for standalone Safety Safety Manager (SM) and Universal Safety I/O to connect to FDM. Connection is via Ethernet. Ethernet. For Experion-connected SM and I/O, I/O, no other license beyond the Experion Experion interface license is required. For Experion-connected SM and Universal Universal Safety I/O, I/O, MUX Monitoring is required if HART device device alarms are needed in Experion. One MUX Monitoring Monitoring license is required per Experion Server.


pg. 13

FDM FD M Sizing and Capacit y Descri Descri ption Maximum number of network connections per FDM Server

Standard Standard

Win 7

25

10

6

2

25

5

(1 network connection is one of the following: 1 HART Modem, 1 RS 485 HART hardware MUX network, 1 Profibus network, 1 Safety Manager network, or 1 Experion Server or Redundant Server pair.)

Maximum number of Experion network interfaces per FDM Server (1 Experion network interface will consume 1 RCI connection. If an RCI is configured for an Experion interface, it cannot be used for any other type of network connection like MUX or HART modem.)

Maximum number of FDM RCIs configurable per FDM Server (total of RCI PCs including Experion Servers)

Maximum number of RCIs per PC

1

Maximum number of FDM Servers per RCI

1

For Non-Experion networks, maximum number of network connections per FDM RCI

6

(where 1 network connection is defined as 1 HART Modem or 1 RS 485 HART hardware MUX network)

Maximum number of concurrent FDM Clients or Station maintenance views per FDM Server

25

5

(Total connections per FDM server = Maximum concurrent FDM clients + Maximum concurrent Experion stations with maintenance view open. open. Station maintenance display consumes one client license.)

FDM Client-to-Server Relationship

1-to-1

(One Server connected at a time. User can select server during login or change after log-in.)

Maximum number of FDM Client instances per node Maximum number of device configuration screens simultaneously opened per Client Maximum number of device configuration screens simultaneously opened per FDM Server

1 5 per Client 50

15

6

2

4,000

1,000

12,000

2,000

(Subject to Server memory limitations. limitations. This limit applies across multiple FDM Clients and Experion Stations. See other limits below per connection types.)

MUX Monitoring Solution -- FDM Gateway (HART only) Maximum number of FDM Gateways connected per FDM Server Maximum number of devices monitored per FDM Gateway Maximum number of devices that one FDM Server can monitor via the MUX Monitoring option (the devices can be connected to one or more HART Hardware multiplexer networks)

Maximum number of FDM Gateways that can be connected per Experion cluster

2

Maximum number of Experion Servers connected per FDM Gateway PC

1

(All FDM Gateways residing within an FDM Gateway PC must connect to the same Experion PKS Server.)

Maximum number of HART hardware MUX networks configured for MUX Monitoring

25

6

(using Server management tool )

Maximum number of FDM Gateways per Gateway PC node

2

(FDM Gateway is a component of MUX Monitoring Solution. Each Gateway PC requires installation of the Experion ACE component and can run either 1 or 2 FDM Gateways. Gateways. No ACE license purchase is required. required. Note that the ACE component in the Gateway PC PC node cannot be used used as an Experion Experion ACE node.)

Maximum number of network nodes that one FDM Server can recognize

18,000

5,000

Maximum number of devices that one FDM Server can communicate with (all device types)

16,000

4,000

Maximum number of devices connected to one Experion cluster that one FDM Server can support (HART and Fieldbus only)

10,000

1500

160,000

100,000

(A node here is defined as one of the following: Device, I/O, controller, Hardware MUX, COMM DTM, or Gateway DTM)

(subject to Experion Server point license limitations)

Maximum number of history records per FDM server (all devices) (subject to availability availability of disk space )


Descri Descri ption Maximum number of devices that can be selected for Bulk History operation at a time

pg. 14

Standard Standard

Win 7

150

50

150

50

16,000

10,000

150

50

(Note that Bulk History operations can take a very long time.)

Maximum number of devices that can be selected for Bulk offline creation at a time (using Bulk save online as offline feature) Maximum number of Offline templates that can be created per FDM server Maximum number of devices to which Offline Configuration can be downloaded at a time using Bulk offline download feature Number of FDM HART Multiplexers per FDM Client PC

1

Number of FDM HART Multiplexers simultaneously connected to one FDM Server

1

Maximum number of devices connected per FDM HART Multiplexer

2,048

Number of third party packages that can be integrated per FDM HART multiplexer

1

Maximum number of users configured

50

Maximum number of windows groups that can be configured Maximum number of audit trail records for the entire FDM database

20

10

3,200,000

100,000

(subject to availability availability of disk space )

Maximum number of audit trail records for a single device

2,000

For HART modem, maximum number of devices that can be connected

1

Recommended number of device configuration screens or MUX Monitored block forms in Control Builder simultaneously opened in FDM per Hardware MUX network

2

Recommended number of device configuration screens simultaneously opened in FDM per Experion Series A I/O

2

Recommended number of device configuration screens simultaneously opened in FDM per Experion Series C IO or PM I/O

4

Recommended number of device configuration screens simultaneously opened in FDM per HART modem

1

Fieldbus Capacities

Descri Descri ption Maximum number of FF devices per Experion cluster that FDM Server can support Maximum number of FF devices exposed through the ValveLink DTM application

Standard Standard

Win 7

8000

640

5 per Client

Maximum number of ValveLink applications active per FDM Client

1

Maximum number of ValveLink application per FDM Server Maximum number of FF device configuration screens simultaneously opened in FDM

TBD 50

15

Recommended maximum number of device configuration screens open in FDM for one link

2

2

Recommended maximum number of device configuration screens open in FDM per FIM2

4

4

Recommended maximum number of device configuration screens open in FDM per FIM4/FIM8

8

8

(includes HART + Profibus + FF)


pg. 15

MUX Capacities

Description

Value

For RS-485 MUX networks, maximum number of HART devices per network

992

For MUX monitoring with P+F or MTL MUX MUX network, maximum recommended number of HART devices per MUX master Baud rates of P+F, MTL or STAHL hardware multiplexer networks that FDM can connect to

32 9600 and 19.2K

Safety Safety Manager Networ Networ k Capaciti es

Descri Descri ption

Standard Standard

Maximum number of SMs allowed across various Safety Networks per RCI

50

Maximum number of SMs per Experion Network

20

Maximum number of Safety networks per RCI

5

Maximum number of HART devices shown per SM network

16,000

Win 7

4,000

Maximum number of HART device configurations concurrently opened per SM at any po int of time

4

Max number of HART device configurations concurrently opened per Universal Safety Module at any point of time

4

FDT/DT FDT/DTM M Capacit Capacit y and Topolo gy

Descri Descri ption Maximum number of concurrent FDT Communication Consoles per FDM Server

Standard Standard

Win 7

25

3

(One RCI can have one FDT Communication Console configured.)

Maximum number of concurrent FDT Communication Consoles per RCI

1

(If an RCI is configured for FDT Communication Console, it cannot be used for any other type of network connection like Hardware MUX, HART modem or Experion.)

Number of Communication DTMs per FDT Communication Console (per RCI)

12

5

Number of Gateway DTMs per FDT Communication Console (per RCI)

38

10

1200

500

Number of total devices per FDT Communication Console (per RCI) Concurrent Network scans per Communication Console

1

(Scanning devices from Gateway DTM and Communication DTM)

Number of device configuration screens opened in FDM at any time per Communication DTM (varies per Comm DTM)

PGM Lite Softing T&H PMD

2 4 4 2

The FDT Communication Tool resides in RCI nodes. Its full name is “FDT Communication Configuration Tool,” and it is used to configure Comm DTM networks using the Comm and Gateway DTMs on the RCI machine. DTM load times can vary considerably, depending on following parameters: 1) Complexity of the device; 2) Number of Gateways connected to the Communication DTM; and 3) Number of concurrent DTMs loaded from a given Communication DTM. Profibus device configuration is supported supported only through DTMs. Qualified Comm DTMs current include PMD, T&H xEpi, Softing FG100 and Brad USB. Qualified Gateway DTMs currently currently include Siemens ET200M, Siemens DP Link/DP-PA Link/DP-PA Coupler, P&F SK3, SK3, and Phoenix Contact. Contact. Unqualified Comm, Gateway and Device DTMs need to be qualified with FDM. Versions of Qualified PMD tools and qualified device DTMs will be documented in the software change notice. A Gateway DTM DTM is a software communication component representing representing the Gateway Gateway device in the field. For example, HART over over Profibus Gateway Gateway DTM represents a Gateway connecting HART devices to a Profibus network.


pg. 16

Note on HART devic e data load ti mes A common question asked asked is, “What is the time taken taken by FDM to completely completely load a device?” Generally, this refers to reading of essential parameters in the device. There is no one answer, and this note explores factors affecting HART device load times. There are no “typical” HART devices. Each HART device is unique, and the HART standard allows vendors to customize devices by adding parameters and functions. More parameters do not necessarily result in higher load times, as each HART message can have up to 255 b ytes of data, and vendors can pack several parameters into a single HART message. HART DD files also may have parameter “attributes “attributes with conditionals.” The host will have to resolve the the conditionals by fetching data from from the device. “Conditional” constructs in DD DD files increase the device load times. Similarly, DTM’s send their requests serially, even though FDM is capable of processing several HART message requests simultaneously. A DTM waits until the the response for the first request is received before the the second one is sent. This considerably slows down the data call u p times for that device within FDM. The above factors can affect the time taken by FDM to load a device. These factors can only be altered by the device manufacturer or vendor. There is no fixed limit on the number of Communication DTM, Gateway DTMs and Devices that can be added in FDT Comm Console. The number of Communication DTMs, Gateway DTMs and Devices depend on the type of the DTMs and the resource and memory consumption of the DTMs being used.

Note on FDT network loading Since DTMs have varied resource and memory consumption, the number of Communication and Gateway DTMs that can be added to an FDT Network must be calculated based on the resource and m emory load they add to the s ystem (through the FDT Comm Console). An FDT Spec Calculator has been created for the purpose of determining this load based on the number of Communication DTMs, Gateway Gateway DTMs, devices and RCIs used. This is available from the OnLine Support (OLS) web site at http://hpsweb.honeywell.com/Cultures/en-US/default.htm http://hpsweb.honeywell.com/Cultures/en-US/default.htm.. The tool provides loading for DTMs that have been been qualified and will be updated periodically. To ensure optimized performance, the the recommended percentage load on a given FDT Comm Console is 50%.

Supported Experion Releases and Connectivity Experion PKS Releases Releases

Connectivity

FDM R430 Server connection with Experion PKS R410.1, R400.2, and R311.3

Ethernet or FTE


pg. 17

25 Clients max per FDM Server

FDM Client

FDM Client

…

FDM Client

FDM Client

FDM Client may connect to 1 FDM Server at a time

FDM Server

FDM Server

Experion Server*

FDM Client may run in the same PC as FDM Server or RCI (see Configuration Guidelines)

FDM Server

Experion Server*

…

Experion Server*

6 Experion Servers max per FDM Server or Redundant Server Pair

RCI

25 total RCIs, including Experion Servers, max per FDM Server

Fig. 2, FDM Server, Experion Server, FDM Client and RCI Limits 6 network connections max per RCI 25 network connections max per FDM Server

FDM Server

MUX MUX

RCI

6 total Gateways per FDM Server

MUX 6

MUX MUX MUX

2

RCI




Gateway PC*

Gateway PC*

Gateway PC*

MODEM MUX

2

FDM Server

6 Experion Servers max per FDM Server

Experion Server Experion Server

*Gateway PC requires installation of Experion ACE ACE component. Cannot be used as an Experion ACE node. No ACE license is required.

Fig. 4, MUX Monitoring Illustration Illustration

Total of 10 connections in this example

Fig. 3, FDM Server RCI Limit Example Device DTM #1 Device DTM #1 Device DTM #2

FDM Cli ent

FDM Cli ent

Device DTM #2 Device DTM #3

FDT Comm Comm Console Console FDM/Instrument Database (HART/Profibus)

FDM Server

RCI Node

Communication DTM

DTMs can be for HART, Fieldbus or Profibus DP or Profibus PA devices.

FDT Comm Console used to to configure the networks using the Comm Comm and Gateway DTMs on the RCI machine.

Gateway DTM #1 Gateway DTM #2

Gateway Device #1 Gateway Device #2

s e c i v e D

Devices

Fig. 5, FDT/DTM Installed Component Illustration Illustration (Clients and RCIs)


pg. 18

Supported Networks Connection Type

Supported Types

Modem

Honeywell IM&C HART DE Modem and any HART compliant RS232 HART Modem

Experion HART Enabled I/O

TC-HAI081, TK-HAI081 TC-HAO081, TK-HAO081 MC/MU- PHAI01 HLAI HART MC/MU- PHAO01 AO_16 HART CC-PAIH01 CC-PAIH01 (AI) & CC-PAOH01 (AO) (Series C HART) CC-PAIH51 CC-PAIH51 (AI) & CC-PAOH51 (AO) (Series C HART Single Modem) (new in R430)

Experion Fieldbus Enabled I/O

FIM2 (Series A), FIM4 (Series C), FIM8 (Series C)

Hardware Multiplexers/Remote I/O systems supported

Elcon, Arcom, MTL, P+F, R. Stahl

Supported Peripherals/Acce Peripherals/Accessori ssori es The table below contains the l ist of peripheral hardware that has been qual ified with FDM. The use of an y other hardware with FDM is NOT necessarily supported. Hardware Type

Make

Model

Version

Transio A52

-

RS 232 to RS 485 converter

Moxa ICP-CON CMS

i-7520A

-

CS485-AD

-

ICPCON

I-7561 USB to RS232\422\485 converter

-

Moxa

UPORT 1130 USB to serial adaptor

-

Mactek

Viator RS232

-

Viator USB HART Modem (HART modem network only) 4841 & 4842 4850

-

HW Ver. 10, SW Ver. 3 HW Ver. 10, SW Ver. 1

R. Stahl

KFD2-HMM-16 Elcon 2700G IS1

HW Ver. 10, SW Ver. HW Ver. 10, SW Ver. 8 -

Digi International

AccelePort 8r 920

Dell Part# A0012190

RocketPort

RS-485 PCI-E Card COM port extender

Part No. 5002505

USB to RS 485 Converters

Mactek MTL Hardware Multiplexer P+F

COM Port Extender Cards RS232 HART Modem Honeywell Smart DE modem Ethernet to Profibus Gateway

MacTek Honeywell

Viator

-

MC Toolkit Modem

-

Softing

FG-100

Trebing and Himstedt

xEPI

HW Ver. 2 DTM Version- 2.03 (110) HW Ver. 2 DTM Version-3.0.0.0


pg. 19

Model Numbers FDM Server Server Li censes Model Number

Descrip Descrip tion Base Server License

HC-SV0001

Base FDM Server license and configuration database. This includes 1 Client license, 1 MUX license (Hardware Multiplexer network connection), 1 HART Modem connection license for local (bench top) device configuration, 16 devices, and all essential device configuration management functions.

Server Server Device Adder Blo cks (all device t ypes)

HC-SV0016

Add a block of 16 points to Server

HC-SV0032


HC-SV0064


HC-SV0128


HC-SV0256


HC-SV0512


HC-SV1024


HC-SV2048


HC-SV4096


HC-SV8192


HC-SV016K

Add a block of 16000 points to Server Au di t Trai T rai l Ad der Bl oc ks

HC-AT0016

Add a block of 16 devices to Server Audit Trail

HC-AT0032


HC-AT0064


HC-AT0128


HC-AT0256


HC-AT0512


HC-AT1024


HC-AT2048


HC-AT4096


HC-AT8192


HC-AT016K

Add a block of 16000 devices to Server Audit Trail Server Hardware MUX Interface License

HC-HM0000

One interface license is required for each Hardware MUX network connected to the FDM Server. Also required for every Hardware MUX network connected to any FDM RCI. A Hardware MUX Network Network usually consumes one RS-232 (or USB) COM port connection and is implemented on an RS-485 network.


pg. 20

Model Number


HC-HMOMX1 HC-HMOMX1

License that provides ability to connect to maximum number of multiplexers (qty 25) supported. Multiplexer Multiplexer Monitoring

HC-MM0000

One license is required for each Hardware MUX network or Safety Manager network connected to the FDM Server to be enabled for monitoring. The Hardware MUX license is NOT included in t his license and must be purchased separately. If connecting via an RCI, that license must be purchased separately. separately. No connection license is required for Safety Manager networks.

HC-MMOMX1 HC-MMOMX1

License that provides ability to have maximum number of multiplexer monitoring connections (qty 25) supported. FDM HART Multiplexer

HC-FH0016

Add a block of 16 devices to FDM HART Multiplexer

HC-FH0032


HC-FH0064


HC-FH0128


HC-FH0256


HC-FH0512


HC-FH1024

Add a block of 1024 devices to to FDM HART HART Multiplexer Offline Configuration

HC-OC0000

One license is required for each FDM Server. Server Server Experion Interface License

HC-SM0000

Base to add one Experion interface. This includes a connection to one Experion Server (via Ethernet connection).

FDM Remot Remot e Communic ation Interface (RCI) (RCI) Licenses Model Number


HC-RI0000

Base license fee to add one FDM RCI. An RCI license allows the user user to load FDM FDM RCI software software on one remote PC. An interface fee is required for each Hardware MUX network connection. A Hardware MUX Network usually consumes one RS-232 com port connection and is implemented on one RS-485 network. These interface licenses are added as part of the Server pricing. See HC-HM0000, Server Hardware MUX interface license, above. Support for local (bench top) device configuration via HART Modem is included in the base RCI license fee.

HC-RIOMX1 HC-RIOMX1

License that provides ability to have maximum number of RCI connections (qty 25) supported.


pg. 21

FDM Client Li censes Model Number


HC-CLNT00

Base license to add one FDM Client. This provides the HMI for the FDM Server and user access to all functions a nd features. Clients can be loaded on the FDM Server PC or on remote PCs.

FDM SESP SESP Lic ense Model Number


HC-SESP00 HC-SESP00

FDM upgrade/update (for customers with valid SESP contracts).

FDM Virtualization Client Access Licenses Model Number


HC-FDMVMS

FDM Virtualization Server CAL

HC-FDMVMC

FDM Virtualization Client CAL

• • • •

FDM Virtualization Server CAL applies to FDM Server and FDM Gateway. FDM Virtualization Client CAL applies to FDM Client and FDM RCI. A CAL must be purchased for each running, on-process on-process Level Level 2 virtual virtual machine that contains contains the referenced node. node. A Client CAL CAL is NOT required for (a) Level 3 and above, (b) a node which is already already covered covered by a CAL CAL license, such as Experion Experion Station, or (c) an off-process virtualized virtualized node used for backup or training

The term “on-process” in this case means “FDM is connected to any external system, Honeywell or third party, where that connection is used to access real-time or historical data. Data in the system is live process or instrument information.” information.”

Experion, PlantScape, TotalPlant are U.S. registered trademarks of Honeywell International Inc. All other products and brand names shown are trademarks of their respective owners. While this information is presented in good faith and believed to be accurate, Honeywell disclaims the implied warranties of m erchantability and fitness for a particular purpose and makes no express warranties except as may be stated in its written agreement with and for its customer. In no event is Honeywell liable to anyone for any indirect, special or consequential damages. The information and specifications in this document are subject to change without notice

For More Information Learn more about how Honeywell’s Field Device Manager R430 can manage smart devices visit our website www.honeywellprocess.com or contact your Honeywell account manager. Honeywell Process Solutions Honeywell 1250 West Sam Houston Parkway South Houston, TX 77042 Honeywell House, Arlington Business Park Bracknell, Berkshire, England RG12 1EB UK Shanghai City Centre, 100 Junyi Road Shanghai, China 20051 www.honeywellprocess.com

EP03-480-430 July, 2012 © 2012 Honeywell International Inc.

FDM R430 spec EP03-480-430_V1_FDM

Recommend Documents