honeywell field device manager specification · honeywell field device manager specification,...

Honeywell Field Device Manager Specification

Technical Information

EP03-480-500 Release 501.1 April 2018, [Comments]

Honeywell Field Device Manager Specification, EP03-480-500 2

[Title] Honeywell Proprietary April 2018

Revision History

Revision Date Description

1.0 April 6, 2018 Released with comments



Table of Contents

Revision History ..................................................................................................................................................................... 2 Table of Contents.................................................................................................................................................................... 3 1. Introduction ..................................................................................................................................................................... 5

1.1. Honeywell Field Device Manager – Enabling the Industrial Internet of Things IIoT .................................................. 5 1.2. Product Overview ...................................................................................................................................................... 5

2. Key FDM Functions and Features ................................................................................................................................. 6 2.1. Device Configuration and Diagnostics ...................................................................................................................... 6 2.2. Device Parameter History and Comparison .............................................................................................................. 6 2.3. Export/Import Capability ............................................................................................................................................ 6 2.4. Audit Trail .................................................................................................................................................................. 7 2.5. Offline Configuration ................................................................................................................................................. 7 2.6. Security and Access Control ..................................................................................................................................... 7 2.7. Device Documentation Support ................................................................................................................................ 8 2.8. Plant Area View ........................................................................................................................................................ 8 2.9. Multiplexer (MUX) Monitoring .................................................................................................................................... 8 2.10. FDM HART Multiplexer (FHM) ……………………………………………………………………………………………….9 2.11. PVST Planner ........................................................................................................................................................... 9 2.12. Dashboard and QuickView displays ........................................................................................................................ 10 2.13. Device Vendor Testing ............................................................................................................................................ 11 2.14. Migration and Upgrades .......................................................................................................................................... 11

3. Standards and Protocols ............................................................................................................................................ 12 3.1. Open Standards Support ........................................................................................................................................ 12 3.2. HART Protocol ........................................................................................................................................................ 12 3.3. Foundation Fieldbus ............................................................................................................................................... 13 3.4. ISA100 Wireless ..................................................................................................................................................... 13 3.5. PROFIBUS .............................................................................................................................................................. 13 3.6. Honeywell DE (Digitally Enhanced) Protocol .......................................................................................................... 14 3.7. Device Description Files.......................................................................................................................................... 14 3.8. Field Device Tool/Device Type Manager (FDT/DTM) Technology .......................................................................... 15 3.9. Field Device Integration (FDI) ............................................................................................................................ 15

3.10. Standards Versions………………………………………………………………………………………………………… 15 4. Tight Integration with Experion PKS and Safety Manager…………………………………………………………………16 5. Flexible Integration with a Variety of Networks…………………………………………………………………………… 17 6. FDM Capabilities Summary .......................................................................................................................................... 20 7. Specifications and Sizing ............................................................................................................................................. 21

7.1. FDM Server PC (Standard) ..................................................................................................................................... 21 7.2. FDM Server PC (Windows 7/10) ............................................................................................................................. 21 7.3. FDM Client and FDM RCI PC ................................................................................................................................. 22 7.4. FDM Gateway PC ................................................................................................................................................... 22 7.5. Virtualization Support .............................................................................................................................................. 22 7.6. Virtualization Client Access Licenses ...................................................................................................................... 23

8. Configuration Guidelines ............................................................................................................................................. 24 8.1. FDM Components ................................................................................................................................................... 21

9. FDM Sizing and Capacity...……………………………………………………………………………………………… . 26 9.1. General Capacities ................................................................................................................................................. 26 9.2. Fieldbus Capacities ................................................................................................................................................. 28 9.3. MUX Capacities ...................................................................................................................................................... 29



9.4. Safety Manager Network Capacities ....................................................................................................................... 29 9.5. PGM (Profibus Gateway Module) Capacity and Topology ...................................................................................... 29 9.6. FDT/DTM Capacity and Topology………………………………………………………………………………………… 29 9.7. ISA100 Wireless Capacities .................................................................................................................................... 31 9.8. ControlEdge RTU Capacities .................................................................................................................................. 31 9.9. Per-RCI Limits by Network Type ............................................................................................................................. 31 9.10. TPS DE Protocol Capacities ................................................................................................................................... 32 9.11. PVST (Partial Valve Stroke Test) Planner Capacities ............................................................................................. 32 9.12. FDM Compatibility and Connectivity ....................................................................................................................... 33 9.13. Supported Networks ............................................................................................................................................... 35 9.14. Supported Peripherals/Accessories ........................................................................................................................ 36

10. Model Numbers ............................................................................................................................................................. 37 10.1. FDM Server Licenses ............................................................................................................................................. 37 10.2. FDM Remote Communication Interface (RCI) Licenses ......................................................................................... 39 10.3. FDM Client Licenses ............................................................................................................................................... 39 10.4. FDM Upgrade Licenses .......................................................................................................................................... 39 10.5. FDM Virtualization Client Access Licenses ............................................................................................................. 39 10.6. PVST Planner Licenses .......................................................................................................................................... 40


1. Introduction

1.1 Honeywell Field Device Manager - Enabling the Industrial Internet of Things (IIoT) The emergence of the Industrial Internet of Things (IIoT) - sometimes used interchangeably with other terms such as Smart Manufacturing, Industrie 4.0, Digitization, and Connected Enterprise - represents a digital transformation of manufacturing that shifts the source of competitive advantage away from physical machinery and towards information. By delivering meaningful information where and when it is needed most across the enterprise, IIoT opens up new possibilities for safety, productivity, organizational responsiveness and ultimately, profitability. One of the key elements of this digital transformation is extensive access to the wealth of information available in field devices. These field devices and equipment with supporting digital technologies have become widely adopted in the process industries and have proven to provide significant benefits to customers. Digital devices and equipment provide a great deal of data about the health of the device and its operating environment. This data can lead to several useful applications that prevent losses or disruptions, enhance quality and reliability, and reduce maintenance costs. Field Device Manager (FDM) provides plant instrument engineers, technicians and maintenance personnel with an optimized environment that simplifies tasks and enables remote management of smart instruments. FDM provides an open architecture that enables use of smart diagnostic data in any device from any vendor.

1.2. Product Overview

FDM is an instrument asset management system (IAMS) for configuration and maintenance of a broad range of smart field devices. Key features include:

• Rich functionality yet secure and easy to use

• Supports open standards and protocols o HART, Foundation Fieldbus, Profibus, ISA100 wireless protocols o DD, EDDL DTM and FDI device file formats

• Tightly integrated with o Experion PKS and TPS networks o Uniformance Asset Sentinel o ControlEdge UOC, PLC and RTU controllers o Experion LX and Plant Cruise controllers o Safety Manager and Safety Manager SC controllers o One Wireless and Wireless HART networks

• Flexible network support to match any architecture requirement



2. Key FDM Features and Functions

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.

2.1. Configuration and Diagnostics

• With FDM, fully configure, maintain, diagnose and troubleshoot any HART, Foundation Fieldbus (FF), Profibus or ISA100 Wireless device from any vendor. In addition, Honeywell DE Protocol devices connected to TPS systems are supported. FDM uses unmodified vendor-created DD files (HART, Foundation Fieldbus and ISA100 Wireless) or DTM based software plug-ins for performing all these functions with the device. DE Protocol devices do not require any special files.

• Health Status: FDM provides health monitoring for all HART, Foundation Fieldbus, Profibus, ISA100 Wireless, and DE Protocol devices. This even extends to HART-over-Profibus.

2.2. Device Parameter History and Comparison

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, Profibus, ISA100 Wireless and DE Protocol devices. History records of devices can be saved, using user friendly names for convenience. History can be managed with features such as the ability to delete a specific history record or a set of history records.

• FDM, upon demand, stores all device description parameters for a connected device when requested by the user, creating a history record or snapshot. A time-saving bulk history feature allows the user to create history records for several devices at the same time. The historical device record is accessible through the device tag and can be used for comparison purposes. The comparison feature is extremely versatile. For any given device, you can compare the live device against any historical record or compare any two historical records. For two different devices of the same type, you can compare any combination of live and/or historical data. Additionally, for Fieldbus and ISA 100 Wireless devices with multiple blocks of the same type, different combinations of identical blocks can be compared.

• Backup and Restore Capability: The FDM database can be backed up and restored using a dedicated utility for that purpose. In addition, functions like the merge of two databases can be achieved by using the export/import feature.

2.3. Export/Import Capability

FDM can export live and historical device data, the list of devices, etc., into a common file format for use with other applications. Another standard FDM feature is the ability to export the following information into a HTML, XML, or CSV (for use with Excel) files:

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



2.4. Audit Trail

FDM can 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. Audit Trail is an optionally licensed 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 • Device health changes

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 audit trail into a XML file and use for printing or reporting purposes. This feature helps plant operations and maintenance comply with standards for change management and automate documentation generation for audits. The audit trail functionality helps users to meet the 21 CFR Part 11 regulations. It is also possible to manually add an event to the audit trail which is useful for tracking inspections, tracking checks, and closing a work order ticket.

2.5. 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 HART DD files as well as for DTM driven device configurations when supported by the DTM.

Offline Configuration is an optionally licensed DD-based feature that allows users to configure HART 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 one or more matching devices when they are physically connected. Configurations can be captured and stored in the database from live devices or 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. Offline Configuration presently works only with HART devices.

2.6. Security and Access Control

Security: Access to FDM is secured via a user ID and password. FDM provides a role-based security system that allows administrators to define site-specific roles and assign allowed 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. Device Access Control: 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. FDM provides a secure environment protected by user ID and password. FDM supports role-based security, which allows administrators to define site-specific roles and assign allowable tasks by role. User authentication



can be based on an FDM specific application level security or on the user’s Windows login ID. FDM supports single sign-on when Windows based security is 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 configuration and prevent users of lower access levels from making changes to the device setup.

2.7. Device Documentation Support

FDM allows you to add device documentation, such as user manuals and P&ID diagrams, to the FDM database. Documents associated with a device are easily invoked from FDM Client. A standard feature of FDM is the ability to link user and device documentation to points or classes of points in the FDM database. Users can attach and associate documentation with devices or device types 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 be of any format (Word, Excel, PDF, etc.). The documents can be added at various levels:

• 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 ST3000) 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.

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

2.8. Plant Area View

Plant Area View enables you to view and monitor smart devices based on any logical grouping category, such as geographical location. It is versatile and time-saving, with up to four hierarchical levels, and can represent virtual grouping within a plant, instrument types, or individual technician job assignment preferences. You can create as many customized, personalized views as you want.

Plant Area View (PAV) is a very valuable FDM feature that enables you to organize and view devices by any desired category, such as geographical location, process function, device type, etc. It would typically be used to represent the virtual grouping of devices as they are arranged in the plant. This feature allows users to easily identify a device location and to view and monitor the device directly by its location. The device grouping strategy followed in Plant Area View is with reference to ANSI/ISA–88.01–1995 standards.

• Display Filters: FDM provides the ability to configure custom views of the plant network and then view a subset of associated devices with a user friendly name such as “UNIT 1” or “ALL HON STT25H.” Plant Area View, another FDM feature, can alternately be used as a filter for viewing devices.

2.9. Multiplexer (MUX) Monitoring

Multiplexer Monitoring, also called MUX Monitoring, is an optional feature that allows Experion to view and manage HART devices connected to hardware multiplexers, Safety Manager Universal Safety I/O and



OneWireless Adaptors. Hardware multiplexers are typically used with systems that do not support HART enabled I/O.

With this feature, Experion can continuously monitor HART devices on the above mentioned networks. It raises alerts for devices reporting problems and provides on-line data for displays. It is not recommended this data be used in Experion control strategies. The alerts from these HART devices are available as normal alarms and events as though the devices were native to Experion. TPS sites with many HART devices may consider this feature along with an HMI upgrade. With Safety Manager HART I/O, this feature helps provide uniform presentation of HART data.

MUX Monitoring requires a node, known as the FDM Gateway, to be running the ACE component (unlicensed) along with some specific FDM components. This node acts as the bridge between the FDM Server and the Experion Server. Experion process I/O point licenses are consumed for HART devices connected to use this 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 license count.

MUX Monitoring supports MTL, P+F, Elcon and Stahl multiplexer networks in addition to Safety Manager Universal Safety I/O, Universal Safety Logic Solver and OneWireless Adaptors.

2.10. FDM HART Multiplexer (FHM)

This option allows vendor-specific third-party software tools to access any HART devices that are connected through FDM. This way, device-specific software applications can integrate with FDM. Applications must be capable of supporting the P+F KFD HART multiplexer system communication protocol. 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 devices in the FDM system. The FDM HART multiplexer runs on a separate FDM Client PC on which the third-party application also runs. The FDM Client component is needed to configure the link between a HART device and its special third-party application. Note that separate user-provided virtual COM port software is generally required for this feature to work properly.

2.11. PVST Planner

Partial Valve Stroke Testing, or PVST, is a concept to increase confidence in safety instrumented systems by periodically testing safety shutdown valves, also known as emergency shutdown (ESD) valves. The valves are automatically tested to detect failure modes related to valve sticking and valve response time, thus insuring that safety and control valves will operate properly when needed. FDM’s optionally licensed PVST Planner feature allows the user to schedule testing to be done automatically, semi-automatically, or manually, with test results stored for documentation purposes. Only HART devices are supported.

Partial Valve Stroke Testing (PVST) is a technique for detecting some of the failure modes of a shut-down valve without completely closing the valve. It is characterized by partly stroking a valve online while causing little or no disturbance to the process. It provides a high degree of confidence that a valve is not stuck in one position and it will function properly if required. Scheduling such tests is an important component in meeting regulatory requirements, lowering plant failure incident rates, lowering plant insurance costs, and increasing plant profits. Honeywell Field Device Manager (FDM) provides an optional, fully-automated PVST scheduler solution for



different ESD (Emergency Shutdown) valves. With PVST Planner, the user can create logical groups of devices, configure/assign schedules to these groups, view the execution status for any set of valves, view/print/export the PVST status for selected devices, and provide alerts/notifications based on various conditions during scheduling. PVST is a powerful tool where safety is a concern!

2.12. Dashboard and QuickView Displays

The FDM Server maintains various types of information related to the FDM Client, devices, RCIs, gateways, networks and operations. The FDM Client does not display all types of information that FDM Server maintains. Using Dashboard feature, you can view all these types of information at a single place and provides quick and easy access to it. You can view the following information. • Tags Information

• Devices Information

• Clients Information

• Loaded Devices Information

• Network Information

• Gateways Information

• Operations Information

• License Usage Information

• You can refresh the information displayed in the dashboard by fetching the latest data from the FDM Server and save the dashboard report in HTML format.



Using the QuickView feature, you can view the information related to device status, device information, network information, device state information, lock state, and attached documents for all connected and disconnected devices. The information is available at a single place to access easily.

2.13. Device Vendor Testing

Honeywell maintains a test program for qualification of device DTMs with FDM. Although most integrate easily, in some cases device manufacturers’ interpretations of the FDT/DTM specifications may vary. This test program is essential to identifying and addressing 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 charge. It is our practice not to issue qualification certificates or any other guarantees of performance for third party devices

2.14. Migration and Upgrades

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 are made to the existing ones to comply with the new format. As a general rule, Honeywell does not maintain a formal test program for HART devices. We do maintain a program for testing of Foundation Fieldbus devices. Experience with a large number of devices in the past has validated this approach.



3. Standards and Protocols

3.1. Open Standards Support

FDM supports open industry 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, as well as Device Type Managers (DTMs) for performing device configuration, management and diagnostics tasks. Functions and features described in the DD/EDDL file or DTM are supported.

EDDL enhancements to the DD language specifications include advanced graphical features, data storage and manipulation features, and advanced parameter organization. FDM supports them and does not require additional files or programming for new devices or for access to device specific features.

3.2. HART Protocol

The Highway Addressable Remote Transducer protocol, commonly known as HART®, has existed as an open protocol since 1993 and provides a means to access information resident in smart field devices, such as transmitters and valve positioners. HART is administered and maintained by the FieldCommGroup (FCG) and is owned by FCG member companies. A complete list of available registered devices and member companies can be obtained from the FCG web site at https://www.fieldcommgroup.org/ It is estimated that over 80% of process instruments worldwide are HART.

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, RTUs, OneWireless Adaptors (OWAs) and HART modems using both DDs and DTMs (see Sec. 0 and 0). FDM also supports HART devices connected via HART over Internet Protocol, or HART-IP.

• 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 I/O and Universal Safety Logic Solver. • HART devices via Honeywell RTU2020 HART I/O.

HART Host Registration. FDM is the first Host System to be registered by the HART Communication Foundation. As a result of this compliance, significant changes have been made including:

- User Interface enhancements Help icon for each parameter Indications for read-write, read-only, and edited parameters for variable controls Tooltips to indicate overflowing label or field text 5 column layouts versus 3 column layouts in a row of control Improved/new chart and graph controls that are 100% compliant Button support to launch image, grid, graph and chart controls in Table view

- Data modeling requirements Full support for data precision as defined by the standard (e.g. float, double, hexadecimal, etc) Complex reference handling (e.g. nested collections, arrays, etc)

- Methods and actions Pre/post read, write and refresh actions Compliance for method built-ins (such as menu_display, etc)

https://www.fieldcommgroup.org/



3.3. Foundation Fieldbus

FOUNDATION™ Fieldbus (FF) is a technology for integrating bus-powered field devices with digitally-based process control 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 function blocks in devices, and the technology offers the potential for significant wiring savings over point-to-point wired devices. FF is administered and maintained by the FieldCommGroup (FCG) and is owned by FCG member companies. A complete list of available registered devices and member companies can be obtained from the FCG web

site at https://www.fieldcommgroup.org/

FDM communicates with Fieldbus devices connected to Experion FIMs using DD files or vendor-supplied DTMs where available. Features provided by the DD or DTM are supported. FDM supports FF devices connected to Experion Fieldbus Interface Modules (FIMs) using both DDs and DTMs. All FIM versions – FIM2, FIM4, FIM8 – are supported. See Specification EP03-360-500 for more details about the available Experion FIMs.

3.4. ISA100 Wireless

ISA100 Wireless is the commercial branding for ISA100.11a, a wireless networking technology standard developed by the International Society of Automation (ISA). The ISA100 Wireless Compliance Institute, also known

as the WCI, owns the 'ISA100 COMPLIANT' certification scheme and provides independent testing of ISA100 based products to ensure that they conform to the ISA100 standard (www.isa100wci.org).

Honeywell’s OneWireless network offers wireless coverage for both ISA100 Wireless field instruments and XYR devices. FDM communicates with Honeywell XYR and ISA100 Wireless devices through the Wireless Device Manager (WDM) and offers the same features as other protocols supported by FDM.

FDM supports ISA100 Wireless devices and WirelessHART devices connected to Honeywell Wireless Device Manager (WDM) networks. WDMs can be standalone or connected to Experion PKS.

3.5. PROFIBUS

PROFIBUS (Process Field Bus) is a standard for bit-serial field bus communication in automation technology. It is used in both process and factory automation, and it is estimated that about 15% of all installed PROFIBUS nodes are in the process industries. There are two variations of PROFIBUS in use today. The most

commonly used is PROFIBUS DP (Decentralized Peripherals), and the lesser used is application-specific PROFIBUS PA (Process Automation). PROFIBUS PA is electrically identical to Foundation Fieldbus.

FDM supports Profibus DP networks connected via the Experion Series C Profibus Gateway Module (PGM) as well as via third party Profibus gateway devices. PA devices are supported via DP-to-PA network gateways.

• Profibus PA (Process Automation) or DP (Decentralized Peripherals) devices connected through the Profibus Gateway Module (PGM).

https://www.fieldcommgroup.org/

http://www.isa100wci.org/



• Profibus networks and devices through Profibus communication and Device Type Managers (DTMs). • HART devices connected to Profibus networks via HART-over-Profibus gateway devices.

3.6. Honeywell DE (Digitally Enhanced) Protocol

Honeywell Digitally Enhanced (DE) Protocol is a smart device protocol for communication between DE smart field devices and DE host interfaces, namely the TPS Process Manager Smart Transmitter Interface Module (STIM) and the Honeywell MCToolKit handheld communicator. DE, introduced in 1989, makes diagnostics and transmitter status information continuously available to the TPS system.

• Honeywell DE (Digitally Enhanced) Protocol devices via TPS (TotalPlant™ Solutions) through HPM (High-Performance Process Manager) STIM (Smart Transmitter Interface Module) and STIMV (Smart Transmitter Interface Module Multi-Variable) IOPs (Input/Output Processors).

• FDM R500 supports DE devices connected to TPS networks through HPMs with STIM and STIMV (multivariable STIM) IOPs (Input/Output Processors).FDM communicates with Digitally Enhanced (DE) Protocol devices connected to TotalPlant Solutions networks through HPMs with STIM and STIMV (multivariable STIM) IOPs (Input/Output Processors). FDM network connection is via ESVT to each LCN or TPS network. DocTools running in an EST is required for network discovery of devices.

3.7. Device Description 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 according to the DD language specification. DD files are device-specific and are developed and made available by device vendors.

EDDL, or Electronic Device Description Language, represents an 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 • enhanced tools for high-level information display and control system use.

EDDL enhancements provide for an improved user interface compared with the DD specification. EDDL further standardizes the user interface for managing intelligent devices and eliminates the need for Windows resource files, supplemental files, and other modifications.

FDM provides full support of HART, Foundation Fieldbus and ISA100 Wireless devices by interpreting DD and EDDL files. It supports all device features irrespective of the vendor or manufacturer, the device version, or the release date. Support for DD and EDDL files includes device-specific commands, device-specific configuration, diagnostics, status information and methods.



3.8. Field Device Tool/Device Type Manager (FDT/DTM) Technology

Increasingly complex and sophisticated field devices have led to very specific software applications that access and analyze device information and provide powerful diagnostic and maintenance tools. FDT/DTM provides an open standard for integration of such software applications. The key is independence from the communication protocol and the software environment of either the device or the host system.

The device supplier provides a DTM (Device Type Manager) for each device or group of devices. It encapsulates device-specific data, functions and rules. This includes device structure, communication capabilities, internal dependencies, and human machine interface (HMI) 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 sophisticated application capable of performing real-time diagnosis and maintenance calculations.

The DTM is installed as a Windows application, and it is loaded and launched in an FDT container or "frame." In the case of FDM, this “frame” is 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, or Fieldbus). For FDM, the Client initiates the DTM and enables the device to interoperate with the system engineering and operating environment.

3.9. Field Device Integration (FDI)

FDM R500 represents the introduction of FDI technology support for Profibus PA devices. FDI stands for Field Device Integration, an emerging single approach to device integration. FDI technology has been developed and is supported by the automation industry’s leading technology foundations and suppliers. With FDI, the advantages of FDT/DTM and EDDL are combined into a single, scalable solution. Profibus PA devices can

be configured via FDI packages in alternate to FDT DTMs. The current FDI solution is limited to usage of EDD portion of the FDI package and doesn’t use UIPs. Starting in FDM R500, Profibus PA devices connected under PGM (Profibus Gateway Module) or under any other Profibus Master (connected as an FDT network in FDM) can be configured via FDI packages. The FDM R500 FDI offering is limited to consuming the EDDL portion of the FDI package for Profibus PA devices. Plans are in place to add UIP (User Interface Plugin) support as well as full FDI support for other protocols such as HART and Fieldbus in the future. See www.fdi-cooperation.com for more information.

3.10. Standards Versions

Support for open standards is an important aspect of FDM. FDM fully supports HART protocol versions 5.X, 6.X and 7.X, and it recognizes all three versions of HART DD files (.FMS, .FM6 and .FM8). It supports currently available Device, Gateway and Communication DTM types with version 1.2.1. FDM supports up to ITK 6.0 and can interpret the latest revision DD/EDDL files for Foundation Fieldbus and ISA100 Wireless devices.

http://www.fdi-cooperation.com/



4. Tight Integration with Experion PKS and Safety Manager

FDM interfaces with Experion Server over a Fault-Tolerant Ethernet (FTE) network and provides access to HART, Fieldbus and Profibus 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. Universal IO modules are supported by Experion Series C, HART I/O modules are supported for Experion Series C, Experion Chassis I/O – Series A, and PMIO (Process Manager I/O). For Fieldbus, the 2-Link Series A FIM, 4-Link Series C FIM and 8-Link Series C FIM are supported. For Profibus, the Profibus Gateway Module (PGM) is supported.

FDM R500 Server works with Experion PKS R500, R432, R410.7, and R400.7. Earlier versions of FDM are compatible with earlier versions of Experion.

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

• Integration with Experion: FDM connects to all live Experion HART and Fieldbus enabled I/O devices, automatically building its database from the Experion database. FDM also connects to ISA100 Wireless

devices which are integrated with Experion (as well as devices connected to standalone Wireless Device Managers).

• Integration with Safety Manager and Safety Manager SC: 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 safety-connected HART device alerts in Experion.



• Multiplexer (MUX) Monitoring: The FDM MUX Monitoring option monitors HART devices on hardware multiplexer/remote I/O, Safety Manager HART I/O, and OneWireless Adaptors, and it provides alerts to the Experion alarm and event system.

• Integration with Experion Device Detail Displays through Station Maintenance View: HART, Fieldbus and ISA100 Wireless device detail displays in Experion Flex Stations include an optional integrated Station Maintenance View capability to view/configure FDM data via an embedded client. The user can save time by going directly from problem to diagnosis in a couple of mouse clicks!

• Experion Redundancy Support: FDM supports redundant Experion network connectivity. When required Experion services are unavailable, FDM automatically switches over to the redundant partner. No action is required to re-detect devices.



5. Flexible Integration with Variety of Networks

In addition to the tight Experion integration, FDM allows the user to connect to and communicate with field devices through several different networks.

HART Hardware Multiplexers/Remote I/O systems 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 HART analog signal and the digital signal into two distinct pathways. The analog signal is routed directly to the control or logic system while the digital data is routed through a separate (RS-232/RS-485) communication link.

Hardware MUX solutions from P+F, MTL, Elcon and Stahl are supported by FDM. These interfaces can be used with Honeywell TPS, FSC, PMD, and non-Experion controllers and PLCs.

HART Modems and Honeywell HART DE 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. FDM also supports the connection to HART devices through the Honeywell HART DE Modem.

Honeywell OneWireless, ISA100 Wireless and Wireless HART Networks FDM is tightly integrated with Honeywell OneWireless and ISA100 Wireless devices through the Wireless Device Manager (WDM) R220 or later. Connection with the WDM is over Ethernet, with configuration as simple as just the range of IP addresses for the connected WDMs. WDMs can be either standalone or Experion-connected. FDM includes a user-maintainable device library of ISA100 Wireless DD files. In addition, HART devices connected to OneWireless Adaptors (OWAs) are detected and can be configured from FDM.

Safety Manager and Safety Manager SC Universal Safety I/O (USIO) FDM supports configuration and maintenance of HART devices connected to Safety Manager and safety Manager SC through Universal Safe I/O and Logic Solver Modules (USIO/USLS). The Safety network can be configured as a Standalone Safety Network (without Experion integration) to configure HART devices connected to Universal Safe Modules or integrated with Experion. Note that HART channels connected to local SM I/O networks (without USIO/USLS) are supported through multiplexer network configurations in FDM.

ControlEdge RTU, ControlEdge UOC Networks and HART IP The Honeywell ControlEdge RTU Remote Terminal Unit and ControlEdge UOC controller have built-in HART I/O. FDM supports this by connecting to the RTUs and UOCs over Ethernet using HART IP (TCP/IP-based). This is essentially HART protocol over an Ethernet network. The RTUs can be distributed geographically for such applications as wellhead or pipeline monitoring.

TPS Networks and DE Protocol Devices Support is provided for DE Protocol Devices through HPMs connected to TPS Networks via ESVT. Features include network discovery of devices, automatic synchronization of network changes, read/write device parameterization, and monitoring of device health and diagnostics. DocTools running in an EST node is a requirement for this to work properly.



Uniformance Asset Sentinel Integration

Honeywell’s Uniformance© Asset Sentinel (UAS) supports Instrument Asset Management and FDM supports instrument configuration and maintenance. Beginning with FDM R500, this integration enables HART device configuration and real-time health status to be viewed from UAS client without need for an FDM client. This integration is available for Experion connected HART devices only. The view is read-only; however, any configuration change must be performed through the FDM Client. Now, R501 supports asset synchronization, fault model creation and instrument diagnostic synchronization (based on NE107) for all networks and supports HART, Fieldbus and Wireless HART devices. An integrated IAMS (Instrument Asset Management System) can now be tightly integrated and deployed in a single server including FDM and Asset Sentinel.

Honeywell’s Uniformance Asset Sentinel solution continuously monitors equipment and process health, enabling industrial facilities to predict and prevent asset failures and poor operational performance. A key feature of this solution is to fully realize the benefits of digital device diagnostic information. In conjunction with Field Device Manager (FDM), Asset Sentinel delivers an integrated instrument asset management solution to help achieve meaningful organization and prioritization for diagnostic device alerts. Automatic synchronization with Honeywell’s Experion® Process Knowledge System (PKS) makes this task effortless. Asset Sentinel maintains fault history, bad actor and other records so reliability analytics can be employed over time to improve the overall reliability of instrumentation.

Asset Sentinel integration with FDM provides Sentinel users with the required privilege with the Device View to view parameters and diagnostic information for HART devices. This solution provides a read-only view of field instruments connected to the Experion network only. Operators can only view diagnostics and health data for HART devices. The data presented is dynamic and reflects current values in the devices. For configuration tasks, FDM Client is still required. The view provided by Asset Sentinel includes parameters and diagnostics.

Shown here is a screenshot of the parameters for a temperature transmitter device as seen on Asset Sentinel.



6. FDM Capabilities

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

FDM Capability HART

Wireless HART Profibus

DP Profibus PA

Foundation Fieldbus

ISA100 DE

DD DTM DTM DTM FDI DD DTM DD n/a

Device configuration (online) ● ● ● ● ● ● ● ● ●

Offline configuration (template) ● ● ● ● ●

Save history ● ● ● ● ● ● ● ● ●

Audit trail ● ● ● ● ● ● ● ● ●

Compare configuration (history and live) ● ● ● ● ●

Attach documents ● ● ● ● ● ● ● ● ●

Bulk offline operations ●

Bulk history ● ● ● ● ●

Station Maintenance view ● ● ● ● ● ● ● ●

Device health scan ● ● ● ● ● ● ● ●

Display filters ● ● ● ● ● ●

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

● ● ● ● ● ●

Advanced search ● ● ● ● ● ●

Connects to Experion ● ● ● ● ●

Third-party application integration [FHM] ●

Connects to MUXs, modems, Safety Manager, and OneWireless Adaptor

●

Provides MUX monitoring1 ●

Connects to Comm/Gateway DTM ● ● ● ●

Dynamically updates devices ● ● ● ● ● ●

Note 1 – Not supported for RTU2020.



7. Specifications and Sizing

7.1. FDM Server PC (Standard)

The standard FDM Server requires a similar PC 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 below.

System Configuration Standard Performance FDM Tag Count <4,000 tags 4,000-16,000 tags Processor Single CPU: 2.33 GHz Four Core

XEON or faster Single CPU: 2.8GHz Four Core XEON or faster

RAM 3 GB1 4 GB Networking 100 Mbps Ethernet or FTE Video Resolution 1024 x 768 or 1280 x 1024 (standard), 65K colors Video RAM 8 MB Minimum Hard Drive 80 GB 160 GB Operating System Windows Server 2008 Standard 64-bit only

Windows Server 2016 Standard 64-bit only Example Hardware2

MZ-PCSV71 Dell T320 Standard Tower MZ-PCSV 72 Dell T320 Standard RAID Tower

MZ-PCSV61 Dell PE R320 Server 1U Rack Mount MZ-PCSV82 HP DL360p G8 Server 2U Rack Mount MZ-PCSV73 Dell PE T320 Server Performance Tower

Note 1 – For better performance, users should upgrade the systems to Performance specification. Note 2 – The systems listed here are for comparison only. The default system configuration of this platform sold by

Honeywell will meet or exceed the recommended components listed. Please contact your Honeywell representative for Honeywell-supplied platform details.

7.2. FDM Server PC (Windows 7/10)

The FDM Server can alternately be installed and run in an OptiPlex 390 economy workstation platform (or later revision) using the Windows 7 operating system. This provides price/performance level below the currently qualified Experion platforms, with reduced capacity specifications (less than 4000 tags). See the FDM Sizing and Capacity tables, Win 7 column, for specific details.

System Configuration 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 Minimum Hard Drive 80 GB Operating System Windows 7 Professional or higher (64-bit)

Windows 10 Professional or higher (64-bit) Hardware Dell OptiPlex 390 Platform or later equivalent revision



7.3. FDM Client and FDM RCI PC

The FDM Client/RCI requires a similar 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 Configuration Standard Performance Processor Single Intel® Core™ i3-2100 (3M

Cache, 3.1 GHz) or greater Intel® Xeon® Processor X5667 (12M Cache, 3.06 GHz) or greater

RAM 2 GB1 4 GB Networking 100 Mbps Ethernet or FTE3 Video Resolution 1024 x 768 or 1280 x 1024 (standard), 65K colors Video RAM 8 MB Minimum Hard Drive 80 GB 80 GB Operating System Windows 7 Professional SP1 64-bit or 32-bit

Windows 10 Professional or higher 64-bit or 32-bit Windows Server 2008 Standard 64-bit or 32-bit Windows Server 2016 Standard 64-bit or 32-bit

Example Hardware2

MZ-PCWS06,07 Dell OptiPlex 3020 Standard Mini-Tower MZ-PCWS73 Dell R7610 Standard Rack 2U

MZ-PCWS91 Dell Precision T3600 Performance Tower MZ-PCWS81 HP Z620 Performance Tower MZ-PCWS74 Dell R7610 Performance Rack 2U

Note 1 – For better performance, users should upgrade the systems to Performance specification. Note 2 – The systems listed here are for comparison only. The default system configuration of this platform sold by

Honeywell will meet or exceed the recommended components listed. Please contact your Honeywell representative for Honeywell-supplied platform details.

Note 3 – 10 Mbps Ethernet Network between Servers and Stations is no longer officially supported, although it may still work on very small systems.

7.4. FDM Gateway PC

The FDM Gateway PC runs the ACE component (i.e., ACE is installed from Experion media but no license is required), and therefore FDM Gateway is recommended to be installed in a PC which meets ACE platform requirements. FDM Server performance grade PCs are supported and qualified for FDM Gateway nodes. Note that this node may not be used as a licensed Experion ACE node.

7.5. Virtualization Support

All FDM components – Server, Gateway, Client, and RCI – have been 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, HPS Virtualization Specifications, Ver.1.3 or later. The performance requirements for running FDM nodes in a virtualization environment are captured in the HPS Virtualization Spec and will not be listed in this document.



7.6. Virtualization Client Access Licenses

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

• VMware Certified TAC professionals located in each region around the world • Extensive certification and approval for our applications to ensure that they work correctly virtualized • Testing and guidance around VMware patches • Development of solutions such as the Backup Control Center solution that solves new industry problems

leveraging virtualization. • Implementation and Planning Guide that provides the best practices for installing and configuring your

virtual environment. • Supply, support the complete virtual environment including the Hardware, Hypervisor, OS and Honeywell

Software.

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

• FDM Virtualization Server CAL, HC-FDMVMS, applies to FDM Server and FDM Gateway. • FDM Virtualization Client CAL, 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

node. • A CAL is 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” 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.”



8. Configuration Guidelines

8.1. FDM Components

The architecture diagram in Figure 1 depicts an example FDM system combined with Experion and non-Experion I/O. Figure 2 shows the optional additional DE Protocol support architecture. Other concepts are given in illustrations in the Sizing and Capacity section. There are several major components of FDM:

. Fig. 1, Field Device Manager Basic Architecture Example

• FDM Server: This is the core component which holds the system database and provides configuration and management functionality. Server maintains the database for all connected HART, Fieldbus, ISA 100 Wireless, DE Protocol and Profibus devices. FDM Server can run in either a server or, with reduced capacity and performance, workstation grade machine

• FDM Client: The FDM Client connects locally or remotely to any available FDM Server and provides the user interface. FDM Clients can be distributed throughout the plant, providing access to device data from remote PCs. Client is an essential component of the Experion Station Maintenance View feature. The FDM Client is also needed to run FDM HART Multiplexer. Client licensing is based on the number of simultaneous active connections, not on the number of installed Clients.

• FDM RCI: The FDM Remote Communication Interface allows devices connected to remote or local PCs to communicate with the Server over a local or wide area network. This greatly expands the distance limits of

PMIO AI/AOSeries-A (1756) AI/AOSeries C I/O AI/AOSeries C Universal I/O

Series-A FIMSeries C FIM

RS232orUSB

RS232

Wireless Devices

IPIP

Wireless Device Manager RTU2020

Universal Safety I/O Universal Safety Logic Solver

Safety Manager

ExperionServer

FDM Server

Gateway PCMUX Monitoring

ProfibusGatewayModule

RS485

MUX

Remote PCwith RCI

MODEM

Remote PCwith RCI

Experion Stationwith FDM ClientFDM Client

One Wireless Adaptor



local serial (RS-485) communication networks used with MUXs, modems and remote I/O systems. The RCI component is also a key part of Comm DTM networks used in communicating with Profibus devices.

• FDM Gateway: The FDM Gateway is the key component of the MUX Monitoring solution, which provides MUX-connected device information to Experion. It allows the user to view MUX-connected HART devices as though they were native to Experion.

• Station Maintenance View: This unique feature is installed with the FDM Client on an Experion Flex Station. It provides the operator or maintenance technician instant access to FDM detail information from an Experion device point detail display.

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

The FDM Server connects to popular hardware multiplexers, remote I/O systems and to RS232 HART modems either directly or through the FDM RCI. FDM configuration rules are provided below:

• The following table describes FDM Client software component compatibility:

FDM Client software is supported on any node running the following software components:

• Operating System only • FDM Server • RCI component • Experion Station – Flex (ES-F) software • Experion Station – Console (ES-C) • Experion Station – Console Extension (ES-CE) software • Experion Station – TPS (ES-T) software • Experion Server – TPS software (ESV-T) • Experion Backup & Restore software Note 1: Not recommended to use FDM Client on Experion Server.

• The following table defines what components are considered licensable tags by FDM:

The following items are treated as individual, licensed tags by FDM:

The following items are NOT treated as individual, licensed tags by FDM:

• HART, Profibus PA or DP, Fieldbus, DE Protocol, ISA100 and Wireless HART devices

• Experion I/O Modules (Series C, Series A and PMIO)

• Experion C300 or C200 Controllers • HPMs, STIM/STIMV IOPs • HART Multiplexers (MUXs) • Safety Managers, Universal Safety I/O and

Universal Safety Logic Solver modules • COMM DTM, Gateway DTM or I/O DTM • Fieldbus FIM and each Fieldbus Link • RTU2020s • WDMs and OWAs

• FDM Server itself • RCIs (or RCI PCs) • Network Interfaces • FDAP



• The FDM Client and FDM RCI can be installed on the same PC as Experion Flex Station, Experion Console Station (ES-C), TPS Station (ES-T) and Experion Server TPS (ESV-T).

• An FDM Client can connect to one FDM Server at a time. The Server connection is established when launching Client and can be changed from within the client without closing FDM.

• No other server-based application or any application using SQL Server may be installed in the same PC as the FDM Server. Experion Server may not be installed in the same node as FDM Server.

• When used with a redundant Experion Server configuration, under normal conditions FDM should be configured to communicate with the backup server.

• A given FDM RCI can connect to one FDM Server only. • If an RCI in the same PC as FDM Server is used for large MUX networks, the RCI can have a negative

impact on Server performance. Consider relocating to a separate PC. • When MUX Monitoring feature is used, the FDM Server can talk to and raise alerts to up to 6 Experion

Servers. • Each HART device connected to Experion via FDM Multiplexer Monitoring counts as 1 process point

license to the Experion system. See documentation for all MUX Monitoring Experion points. • An FDM Gateway PC can connect to only one Experion Server. Even if two FDM Gateways reside in

the Gateway PC, they must both connect to the same Experion Server. • No MUX hardware license is required for standalone Safety Manager (SM) and Universal Safety I/O to

connect to FDM. Connection is via Ethernet. For Experion-connected SM and I/O, no other license beyond the Experion interface license is required.

• For Experion-connected SM and Universal Safety I/O, MUX Monitoring is required if HART device alarms are needed in Experion. One MUX Monitoring license is required per Experion Server. The same applies to HART devices connected to OneWireless Adaptors (OWAs).

• All components in an FDM network (Server, Clients, RCIs, Gateways) must be of the same release. • An ESVT used as both an Experion Server and a TPS (TPN) Server (for DE Protocol support) requires

two (2) Server Experion/TPS Interface licenses, one for the Experion Server and one for the TPS Server. When an ESVT is used in this capacity, it is not recommended that FDM use the same ESVT for a third network of any type. In this case, the third network such as Safety Manager or OneWireless must be treated as a separate standalone network.

9. FDM Sizing and Capacity

9.1. General Capacities

Description Standard Win 7

Maximum number of network connections per FDM Server (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, 1 Experion Server or Redundant Server pair, 1 HART IP Network, or 1 WDM Network.)

25 10

Maximum number of Experion or TPS network interfaces per FDM Server (1 Experion network or 1 TPS 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. If the user configures both Experion and TPS on same ESVT PC, 2 RCI’s will be consumed.)

10 2

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

25 5

Maximum number of RCIs per PC 1 Maximum number of FDM Servers per RCI 1




Maximum number of network connections per FDM RCI See Table 8.8, Per-RCI Limits by Network Type

Maximum number of concurrently connected FDM Clients or Station maintenance views per FDM Server (Total connections per FDM server = Maximum concurrent FDM clients + Maximum concurrent Experion stations with maintenance view open. Station Maintenance Display consumes one client license.)

10 5

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

1-to-1

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

5 per Client

Maximum number of device configuration screens simultaneously opened per FDM Server (Subject to Server memory limitations. This limit applies across multiple FDM Clients and Experion Stations. See other limits below per connection types.)

50 15

MUX Monitoring Solution -- FDM Gateway (HART only) Maximum number of FDM Gateways connected per FDM Server

6 2

Maximum number of devices monitored per FDM Gateway 4,000 1,000 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, Safety Manager networks or OneWireless Adaptors)

12,000 2,000

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

2

Maximum number of Experion Servers connected per FDM Gateway PC (All FDM Gateways residing within an FDM Gateway PC must connect to the same Experion PKS Server.)

1

Maximum total combination of HART hardware MUX networks, SM networks and One Wireless networks configured for MUX Monitoring (using Server management tool )

25 6

Maximum number of FDM Gateways per Gateway PC node (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. No ACE license purchase is required. Note that the ACE component in the Gateway PC node cannot be used as an Experion ACE node.)

2

Maximum number of network nodes that one FDM Server can recognize (A node here is defined as one of the following: Device, I/O, controller, Hardware MUX, COMM DTM, or Gateway DTM)

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) (subject to Experion Server point license limitations)

10,000 1500

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

160,000 100,000

Maximum number of devices that can be selected for Bulk History operation at a time (Note that Bulk History operations can take a very long time.)

150 50




Maximum number of devices that can be selected for Bulk offline creation at a time (using Bulk save online as offline feature)

150 50

Maximum number of Offline templates that can be created per FDM server 16,000 10,000 Maximum number of devices to which Offline Configuration can be downloaded at a time using Bulk offline download feature

150 50

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 20 10 Maximum number of audit trail records for the entire FDM database (subject to availability of disk space )

3,200,000 100,000

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

9.2. Fieldbus Capacities


Maximum number of FF devices per Experion cluster that FDM Server can support

8000 640

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



9.3. 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 network, maximum recommended number of HART devices per MUX master

32

Baud rates of P+F, MTL or STAHL hardware multiplexer networks that FDM can connect to

9600 and 19.2K

9.4. Safety Manager and safety Manager SC Network Capacities


Maximum number of Safety Builder databases per FDM Server1 1 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 4,000 Maximum number of HART device configurations concurrently opened per SM at any point of time

4

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

4

1FDM Server can only import one Safety Builder Export File.

9.5. PGM (Profibus Gateway Module) Capacity and Topology

Description PGM Comm DTM PGM Native Integration

Number of concurrent device configurations allowed per PGM Link 2 4 Maximum number of concurrent device configurations allowed per Gateway (RIO/NTL)

2 2

Maximum number of concurrent device configurations (all protocols and all networks) per FDM server2

50 50

Number of DSBs supported per PROFIBUS Link1 100 100 Maximum of HART devices supported per PGM Link1 500 500 Maximum number of PGMs per Experion Server1 80 80 1Experion specifications. 2Existing general FDM specification.



Performance

Average time taken to read/write one parameter from HART device connected under PGM 1 & 3

10 sec

Average time taken to read/write one parameter from PROFIBUS device connected under PGM 1 ,2 & 3

10 sec

Average time taken to discover all the devices (Profibus DP, HART, PA) under a single PGM 2 & 3

30 min

Average time taken for health update for a Profibus/HART device 3 10 sec Note 1 - The time taken by PGM to respond to a HART/PROFIBUS DPv1 command depends on various parameters such as (but not limited to) % DPv1 bandwidth allocated, DP baud rate, Experion DPv1, Experion HART Over PROFIBUS traffic, No of slaves configured, number of parallel device configured. Note 2 - If the device is under Non transparent link (DP/PA Link) then it might take more time than 10 sec to read/write a parameter. Hence discovery of PA devices beneath Non Transparent Link will also be slower. Note 3 – FDM can’t function natively with PGM when the %DPv1 bandwidth allocated is made 0 in PGM.

Capacity

FDM RCI uses “EPKS Server’s CDA Server” for all its parameter access communication and also to support Monitoring features of Profibus or HART Devices like “Dynamic Detection”, and “Device Health”. Since “CDA Server” is also responsible for display and other Data access component for Experion, it might have some base load from other Clients. Following attached documents explains amount of CDA load PPS (parameters per second) consumed by FDM as part of PGM integration

9.6. FDT/DTM Capacity and Topology


Maximum number of concurrent FDT Communication Consoles per FDM Server 25 3 Maximum number of concurrent FDT Communication Consoles per RCI 1 Maximum number of FDT/DTM Networks per RCI 1 Concurrent Network scans per Communication Console (Scanning devices from Gateway DTM and Communication DTM)

1

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

PGM Lite 2 Softing 4 T&H 4 PMD 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 the complexity of the device, the number of gateways connected to the Communication DTM, and the number of concurrent DTMs loaded from a given Communication DTM.

Profibus device configuration is supported only through DTMs. Qualified Comm DTMs currently include PMD, T&H xEpi, Softing FG100 and Brad USB. Qualified Gateway DTMs currently include Siemens ET200M, Siemens DP Link/DP-PA Coupler, P&F SK3, and Phoenix 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 is a software communication component representing the Gateway device in the field. For example, HART over Profibus Gateway DTM represents a Gateway connecting HART devices to a Profibus network.



Note on FDT network loading There are no fixed limits on the numbers of Communication DTMs, Gateway DTMs and Devices that can be added using FDT Comm Console. These limits depend on the types of the DTMs and the resource and memory consumption of the DTMs being used.

Since DTMs have varied resource and memory consumptions, the number of Communication and Gateway DTMs that can be added to an FDT Network must be calculated based on the resource and memory load they add to the system (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 DTMs, devices and RCIs used. This is available from the On-Line Support (OLS) web site at https://www.honeywellprocess.com. The tool provides loading for DTMs that have been qualified and will be updated periodically. To ensure uninterrupted performance and allow some headroom, the recommended percentage load on a given FDT Comm Console is no greater than 50%.

9.7. ISA100 Wireless Capacities

Description Value

Maximum number of Wireless Device Managers (WDMs) per Experion Network (This restriction comes from the Experion/OneWireless integration specifications.)

5

Maximum number of standalone WDMs per FDM RCI across various OneWireless networks.

10

Maximum number of Wireless Device Managers (WDMs) per FDM Server 250 Maximum number of OneWireless networks per RCI 2 Maximum number of device configurations simultaneously open per WDM 4 Maximum number of ISA100 Wireless or OneWireless devices per FDM Server 16,000 Maximum number of devices per WDM is 100 as of WDM R220. This may increase in the future.

9.8. ControlEdge RTU Capacities

Description Value

Maximum number of RTUs per RCI spread across various HART-IP network interfaces

1000

Maximum number of HART-IP Networks per RCI 5 Maximum number of simultaneous device configuration for HART devices per RTU

2

Maximum number of RTU HART devices per FDM Server 16,000 RTU2020 uses HART-IP to communicate with FDM. Each RTU has a separately assigned IP address on the network.

9.9. Per-RCI Limits by Network Type The table below summarizes maximum number of networks per RCI for each network type.

Description Value

Experion PKS Networks1 1 Honeywell TPS network² 1

https://www.honeywellprocess.com/



Description Value

Modems and MUX Networks 6 FDT/DTM Communication Networks 1 Safety Manager Networks (with Universal Safety I/O) 5 HART-IP Networks (RTU2020) 5 OneWireless Networks 2 1 If an RCI is configured for Experion Server, it cannot be used for any other type of network connection except TPS Network.

2 If an RCI is configured for a TPS network, it cannot be used for any other type of network connection except Experion PKS Network.

9.10. TPS DE Protocol Capacities

Description Value

Maximum number of DE Devices per FDM Server 6000 Maximum number of DE Devices per FDM RCI 1000 Maximum number of DE Devices supported by FDM RCI per NIM 1000 Maximum number of FDM RCIs (TPS) per FDM Server 6

Maximum number of TPS Network per FDM RCI 1

Maximum number of TPS Networks per FDM Server 6

Maximum number of FDM RCIs per LCN 6

Maximum number of LCNs per FDM Server 6

Maximum number of open DE Device configurations per NIM 4

Maximum number of open DE Device configurations per RCI 4

Maximum number of open DE Device configurations per FDM Server 24 An ESVT used as both an Experion Server and a TPS (TPN) Server requires two (2) Server Experion/TPS Interface licenses, one for the Experion Server and one for the TPS Server.

9.11. PVST (Partial Valve Stroke Test) Planner Capacities


Total number of ESD3 devices support per FDM Server 1024 500 Maximum number of PVST execution at the same time per FDM Server 25 15 Maximum number of PVST execution at the same time per SCIO, PMIO 4 4 Maximum number of PVST execution at the same time per Series A I/O 0 0 Maximum number of PVST execution at the same time per SM or RUSIO 4 4 Maximum number of PVST execution at the same time per MUX 2 2 Maximum number of PVST execution at the same time per S8IO and UIO 2 2 Maximum number of PVST groups that can be created per FDM Server 100 100 Maximum number of ESD devices associated per group 100 100 Maximum number of PVST specific system/node level Audit Trail/Event Logging Unlimited1 Unlimited1 Maximum number of PVST Planner UI that can be loaded at the same time 10 10




Notes: 1Limited by available disk space. Audit Trail/Event Logging would also compete for disk resources. 2PVST Planner is part of the FDM Client. It is not an independent application. 3ESD = Emergency Shutdown. The following devices are supported by PVST Planner:

• Metso Automation VG 9000H • Metso Automation VG 800 • GE Masoneilan SVI 2 ESD • Fisher Controls DVC 6000 SIS • Flowserve LX3200 MD • Samson 373X-3

Additional devices may be added in the future without notice. Note on device parameter load times A common question asked is, “What is the time taken by FDM to completely load parameter data from a device?” Generally, this refers to reading of essential parameters in the device. There is no one answer, and this note explores factors affecting device load times.

There are no “typical” devices, and device response speeds can vary considerably from vendor to vendor. Nominal communication speeds vary considerably from protocol to protocol and can further be affected by a number of loading factors. Each device is unique, and standards allow vendors to customize devices by adding parameters and functions. More parameters can result in higher load times, but that is not necessarily the case. Vendors can use “conditionals” in DD files, which can greatly slow the process of loading parameters from the device.

DTM’s send their requests serially, even though FDM is capable of processing several message requests simultaneously. A DTM waits until the response for the first request is received before the next one is sent. This considerably slows down the data call up 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.

9.12. FDM Compatibility and Connectivity

Compatibility Connectivity

FDM R500 Server connection with Experion PKS R500 Experion PKS R432.1 Experion PKS R431.3 Experion PKS R410.9 Safety Manager 160.2 or higher OneWireless R230 or higher RTU 2020 R101 or higher TPS R685 or higher

Ethernet or FTE



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

FDM Server

FDM Client FDM Client

RCINodeFDM/Instrument

Database (HART/Profibus)

Gateway Device #1

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

Devices

Device DTM #1

Device DTM #2

Device DTM #3

Device DTM #1

Device DTM #2

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

Gateway Device #2

Communication DTM

Gateway DTM #1

Gateway DTM #2

Devi

ces

Fig. 3, FDM Server, Experion Server, FDM Client and RCI Limits

FDM Server

ExperionServer*

FDM Server

ExperionServer*

FDM Server

ExperionServer*

FDM Client

FDM Client

FDM Client

FDM Client

…

RCI

10 Experion Servers max per FDM Server or Redundant Server Pair

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

25 Clients max per FDM Server

FDM Client may connect to 1 FDM Server at a time

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

Fig. 4, FDM Server RCI Limit Example

FDM Server

RCI

RCI

ExperionServer

MUX

MODEM

MUX

MUX

MUX

MUX

MUX

6 network connections max per RCI

25 network connections max per FDM Server

Total of 10 connections in this example

10 Experion Servers max per FDM Server

MUX

6

2

2

ExperionServer

Fig. 5, MUX Monitoring Illustration

FDM Gateway

Gateway PC*

FDM Gateway

FDM Gateway

Gateway PC*

FDM Gateway

FDM Gateway

Gateway PC*

FDM Gateway

FDM Server

6 total Gateways per FDM Server

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



9.13. Supported Networks

Connection Type Supported Types

Modem Honeywell IM&C HART DE Modem and any HART compliant RS232 HART Modem or qualified USB Modem or 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-PAIH02 (AI) & CC-PAOH01 (AO) (Series C HART), CC-PAIH51 (AI) & CC-PAOH51 (AO) (Series C HART Single Modem) CC-PUIO01 Universal I/O (32 point) CC-PUIO31 Universal I/O 2 (32 point)

Experion Fieldbus Enabled I/O FIM2 (Series A), FIM4 (Series C), FIM8 (Series C)

Experion Profibus Gateway PGM (Profibus Gateway Module)

Third-Party Profibus Gateways Siemens SIMATIC ET 200 M (HART over PROFIBUS) Rev 5.0.9 Siemens SIMATIC DP/PA Link-153-2 (DP to PA) Rev 5.0.9 Siemens SIMATIC DP/PA Coupler-FDC 157-0 (DP to PA) P & F SK3 -DP/PA Coupler (DP to PA) Phoenix Contact IL PB BK DI8 DO4 PAC (HART over PROFIBUS) Rev: HW/FW:02/101 Turck Excom (HART Over PROFIBUS) Rev: 2.2.2.0

Hardware Multiplexers/Remote I/O systems supported

Elcon, Arcom, MTL, Pepperl+Fuchs, R. Stahl

OneWireless/ISA100 Wireless Wireless Device Manager (WDM) R220 or later

RTU Honeywell ControlEdge RTU (via HART-IP)

TPS Network DE Protocol through HPM STIM and STIMV IOPs



9.14. Supported Peripherals/Accessories

The table below contains the list of peripheral hardware that has been qualified with FDM. The use of any other hardware with FDM is NOT necessarily supported.

Hardware Type Make Model Version

RS 232 to RS 485 converter Moxa Transio A52 -

ICP-CON i-7520A - CMS CS485-AD -

USB to RS 485 Converters

ICPCON I-7561 USB to RS-232\422\485 converter

-

Moxa UPORT 1130 USB to serial adaptor

-

P&F Mactek Viator RS232 -

P&F Mactek Viator USB HART Modem (HART modem network only)

-

Hardware Multiplexers

MTL 4841 & 4842 4850

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

Pepperl+Fuchs KFD2-HMM-16 Elcon 2700G

HW Ver. 10, SW Ver. 11 HW Ver. 10, SW Ver. 8

R. Stahl IS1 -

COM Port Extender Cards

Digi International AccelePort 8r 920 Dell Part# A0012190

RocketPort RS-485 PCI-E Card COM port extender (no RS232 to RS485

converter required) Part No. 5002505

Terminal Servers

Moxa NPort 5650-16 FW Version 3.5 Advantech EKI-1521-BE, EKI-1521I-BE

EKI-1522-BE, EKI-1522I-BE EKI-1524-BE, EKI-1524I-BE

FW v1.98 FW v1.98 FW v1.97

RS232 HART Modem MacTek Viator - Honeywell Smart DE modem Honeywell MC Toolkit Modem -

Ethernet to Profibus Gateways

Softing FG-100 HW Ver. 2 DTM Version- 2.03 (110)

Trebing and Himstedt xEPI HW Ver. 2

DTM Version-3.0.0.0

http://www.measys.com/Data-Communication/Serial-and-USB-Converters_c25_59/

http://www.moxa.com/product/UPort_1130_1130I.htm

http://www.mactekcorp.com/product1.htm

http://www.mactekcorp.com/product3.htm



10. Model Numbers

10.1. FDM Server Licenses

Model Number Description

Base Server License

HC-SV0001 Base FDM Server license and configuration database. This includes 1 Client license, 1 Server Network Interface License (MUX, OneWireless, Comm DTM/Profibus or HART-IP), 1 HART Modem connection license for local (bench top) device configuration, 16 devices, and all essential device configuration management functions.

Server Device Adder Blocks (all device types)

HC-SV0016 Add a block of 16 points to Server










HC-SV016K Add a block of 16000 points to Server

Audit Trail Adder Blocks (all device types)

HC-AT0016 Add a block of 16 devices to Server Audit Trail










HC-AT016K Add a block of 16000 devices to Server Audit Trail




Server Network Interface*

HC-HM0000 Server Network Interface License One license is required for each Hardware MUX network, OneWireless network or HART-IP network connected to the FDM Server or any FDM RCI. No connection license is required for Safety Manager networks. A Hardware MUX network connection usually consumes one RS-232 (or USB) COM port connection and is implemented on an RS-485 network. OneWireless and HART-IP networks are implemented over Ethernet.

HC-HMOMX1 Server Network Interface Maximum License Provides the ability to connect the maximum number of network interfaces (qty 25) supported.

*formerly known as Server Hardware MUX Interface License

Multiplexer Monitoring

HC-MM0000 Multiplexer Monitoring License One license is required for each Hardware MUX network, Safety Manager network, OneWireless Network or HART-IP connected to the FDM Server to be enabled for monitoring. The Server Network Interface License is NOT included in this license and must be purchased separately. If connecting via an RCI, that license must be purchased separately. No connection license is required for Safety Manager networks.

HC-MMOMX1 Multiplexer Monitoring Maximum License Provides the ability to have the maximum number of multiplexer monitoring connections (qty 25) supported.

FDM HART Multiplexer

HC-FH0016 Add a block of 16 devices to FDM HART Multiplexer







Asset Sentinel Integration

HC-IS0000 Add interface for integration of Asset Sentinel

Offline Configuration

HC-OC0000 One license is required for each FDM Server.

Server Experion/TPS Interface License

HC-SM0000 Add one Experion or TPS interface. This provides a connection to one Experion Server or one TPS (ESVT Node) Server (via Ethernet connection). Note that an ESVT Node configured for both TPS and Experion network connection requires two (2) licenses.



10.2. FDM Remote Communication Interface (RCI) Licenses


HC-RI0000 Base license fee to add one FDM RCI. An RCI license allows the user to load FDM RCI 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 License that provides ability to have maximum number of RCI connections (qty 25) supported.

10.3. FDM Client Licenses


HC-CLNT00

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

10.4. FDM Virtualization Client Access Licenses


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 Level 2 virtual machine that contains the referenced node. • A Client CAL is 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” 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.”

10.5. FDM Upgrade Licenses


HC-UPANR1 FDM UPGRADE UNIT - RELEASE MINUS 1

HC-UPANR2 FDM UPGRADE UNIT - RELEASE MINUS 2

HC-UPANRX FDM UPGRADE UNIT - RELEASE MINUS X

HC-UPGCLN FDM SERVER/CLIENT UPGRADE LICENSE


10.6. PVST Planner Licenses


HC-PV0032 ADD 32 DEVICES TO PVST PLANNER





HC-PV1024 ADD 1024 DEVICES TO PVST PLANNER PVST Planner is an optional licensed feature for automatically, semi-automatically, or manually performing partial valve stroke tests on supported HART ESD devices.

EP03-200-501 April 2018 © 0418 Honeywell International Inc.

Experion® is a registered trademark of Honeywell International Inc.

All other products and brand names shown are trademarks of their respective owners.

This document contains Honeywell proprietary information. It is published for the sole usage of Honeywell Process Solutions’ customers and prospective customers worldwide. Information contained herein is to be used solely for the purpose submitted, and no part of this document or its contents shall be reproduced, published, or disclosed to a third party without the express permission of Honeywell International Inc.

While this information is presented in good faith and believed to be accurate, Honeywell disclaims the implied warranties of merchantability 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 To learn more about Honeywell’s products or solutions visit our website www.honeywellprocess.com or contact your Honeywell account manager. Automation & Control Solutions 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