Advanced Alarm Management Specification. AAM310-ST Release 310 April 2008, Version 1.1

Transcription

1 Advanced Alarm Management Specification AAM310-ST Release 310 April 2008, Version 1.1

2 Advanced Alarm Management Specification, AAM310-ST ii Revision History Revision Date Description 1.0 March 2008 Release publication 1.1 April 2008 Add BMA release support details.

3 Advanced Alarm Management Specification, AAM310-ST iii Table of Contents 1. Product Introduction Advanced Alarm Management Suite Architecture Specifications Control Systems Historians Security Localisation Sizing Hardware and Software Requirements Client Software Client Hardware Server Software Server Hardware Model Numbers AAM Suite, (includes ACM, UA, AEA) Alarm Configuration Manager Alarm and Event Analysis UserAlert Glossary... 16

4 Advanced Alarm Management Specification, AAM310-ST 4 1. Product Introduction 1.1. Advanced Alarm Management Suite The Advanced Alarm Management (AAM) suite of products are Advanced Applications on the Experion Process Knowledge System (PKS) platform and a part of the OM Pro suite of operations management applications. AAM solutions optimize a key asset in a production facility the operation team s performance. Using technologies from Abnormal Situation Management (ASM) Consortium research, AAM solutions assist operations personnel to be as efficient and effective as possible. The products and services combined deliver the following benefits: Protect plant uptime and safety by reducing losses caused by ineffective alarming. Increase operator effectiveness by reducing the number of alarms that require operator intervention. Reduce time and effort to develop, deploy and maintain an alarm system that is consistent with ASM Consortium best practices. The AAM applications include: Alarm Configuration Manager (ACM) Alarm and Event Analysis (AEA) UserAlert (UA) Alarm Configuration Manager Alarm Configuration Manager is software for engineering an alarm system to meet a site s alarm management policies and to ensure that the engineered configuration remains in effect over the life cycle of the plant. ACM provides the capability to create and maintain a master boundary database (MBD) for the alarm system configuration. It allows for comparison of the control system alarm configuration to this master database and enforcement of the engineered alarm configuration in the control system. It also supports enforcing lists of exceptions to the typical alarm configuration to handle various operating modes and states of the plant Alarm and Event Analysis Alarm and Event Analysis evaluates performance indicators for a site s alarm and event system with benchmarking capabilities against EEMUA guidelines. This includes measures of alarm and event occurrences (such as rates, total occurrences, repeating, standing, stale), operator changes and, if ACM is deployed at the site, analysis of the configuration of the alarm system as well as the number of exceptions, overrides and such during enforcement actions UserAlert UserAlert delivers automatic notification capabilities that complement the traditional control system alarm system. With user-configurable notifications, it automates the normal monitoring actions of a skilled operator whose scope of responsibility has become increasingly larger and more complex. It allows engineers to monitor select events such as euipment degradation. UserAlert consists of a server that accesses data from one or more OPC DA servers such as Experion, an Application Processing Platform (APP) or Uniformance PHD Architecture There are a number of ways to install the various AAM suite components to suit numerous customer requirements ranging from a single server with all components to multiple servers straddling the control and business networks. Two examples are given below.

5 Advanced Alarm Management Specification, AAM310-ST 5 Figure 1 Level 3 AAM Architecture Figure 2 Level 3/Level 4 Architecture

6 Advanced Alarm Management Specification, AAM310-ST 6 2. Specifications 2.1. Control Systems ACM provides native support for some control systems, and generic support for others. A control system with native support has a dedicated ACM interface that is aware of alarm types and parameters for that control system, while generic support requires the site to supply some configuration for alarm types and parameters, alarm limit validation rules and secondary support. Limited alarm configuration management is possible with generic support using tag templates and variable entitles with offline source tags. The interface between ACM and the control system is via OPC DA or files. When OPC is used, ACM requires one OPC DA server for each control system and this server must support the OPC DA 1.0a or 2.0 specification. Some interfaces support write access, where ACM is able to enforce alarm settings, while others provide only read-only access, so that ACM can report on differences but cannot enforce alarm settings. When OPC cannot be used, ACM can access alarm configuration data from a properly formatted text file rather than accessing the control system directly. This allows ACM to document and report on control systems that do not have OPC DA access or that are otherwise not supported fully by ACM. AEA provides native support for some control systems, and generic support for others. Many of the interfaces are files using a defined file format. Other control systems can be supported if events can be written to this file format. The table below summarises the control systems supported by ACM and AEA. UserAlert can access data from any OPC DA server, (see UserAlert specifications section for details), including noncontrol system sources such as laboratory systems. Therefore UserAlert is not specifically mentioned in the supported control systems table below. ACM AEA Control System Type Interface Read/Write Type Honeywell Experion R30x, R31x including CEE, SCADA, EHG, TPS & BMA R320 tags Honeywell Experion R21x including CEE, SCADA & EHG tags Honeywell TPS R533 through R670 via APP node with APP Base & optionally CL Server, (to request ACM enforcement from TPN) Native OPC DA Read/Write Native (each Experion server requires 1 x EP-NTAUNS) Native OPC DA Read/Write Native (each Experion server requires 1 x EP-NTAUNS) Native OPC DA Read/Write Native: HM or EJC Honeywell TDC3000 R400 through R532 Generic File Read only File: generic Honeywell PMX Native OPC DA Read/Write n/a Honeywell BMA R320 via Experion as listed above See Experion See Experion Emerson DeltaV (7.3) Native OPC DA Read only n/a Foxboro I/A 6.5 via Matrikon s OPC server, Matrikon.OPC.Foxboro Version GenCS: foxomsrvr Generic OPC DA Read only File: specific to Foxboro IBM Advanced Control System (ACS) Native OPC DA Read/Write n/a Siemens PCS 7 (5.1) Generic OPC DA Read only File: specific to Siemens

7 Advanced Alarm Management Specification, AAM310-ST 7 ACM AEA Control System Type Interface Read/Write Type Yokogawa Centum CS3000, 2.10 and above Native OPC DA Read/Write except for alarm priorities Yokogawa Centum CS, 2.09 and above Native OPC DA Read/Write except for alarm priorities File: specific to Yokogawa File: specific to Yokogawa Yokogawa CS1000 Generic OPC DA Read only File: specific to Yokogawa Yokogawa Centum XL (24) Generic OPC DA Read only File: specific to Yokogawa Yokogawa Centum μxl Generic File Read only File: specific to Yokogawa Yokogawa COPS V (22.5) Generic File Read only File: specific to Yokogawa Generic unknown Generic File Read only File: generic Ronan EHAS N/A N/A Documentation only n/a Offline Components It is possible to deploy ACM without a control system connection, and the components can be networked or installed on a single computer (e.g., a laptop). This is known as an offline or disconnected ACM installation, and it supports almost all aspects of ACM configuration. This could be useful during the design stage of a project where the control system is not yet available but you wish to capture and analyse the alarm configuration decisions being made or as part of an alarm rationalisation project Historians ACM variables support a connection to a historian tag. Two options are supported: Honeywell Uniformance PHD and generic historians via Business FLEX. Business FLEX connects to generic historians such as PI using OPC HAD. See the Business FLEX Specification and Technical data document for further details Security AAM uses a role-based security model with Windows authentication. User accounts are required to access the system. Entitlement to perform actions in the AAM suite is controlled by the roles assigned to the user account. Each Windows user is granted one or more roles by an administrator using the administration consoles in each AAM product. Roles are independent of one another, not hierarchical. Roles can be assigned to groups, including to Windows groups, so that users can obtain role privileges based on group membership. ACM and UserAlert use Windows local groups on the computer where the Manager servers run. AEA and ACM Web can use Windows local groups and domain groups on the computer where the web server runs Localisation The AAM products can be localised, which includes support for local conventions such as dates, running client software components on international versions of Windows operating systems and the ability to translate the user interface.

8 Advanced Alarm Management Specification, AAM310-ST 8 Client software components can be translated to languages other than English using the Localisation Guides and translation toolkits that are included with the AAM product media. Translations are not provided with the AAM product media. AAM products have been tested and are supported with French, German and Spanish and the client versions of Windows for those same languages, Note that AAM client components are supported on international versions of Windows operating systems, but server components are supported only on English versions of Windows, Oracle and SQL Server Sizing System Items Specifications Comments Users No limit No limit to number of named users. Number of simultaneous or concurrent users for most components is limited by server capacity. Number of simultaneous or concurrent users for AEA reporting is limited by the Business Objects licenses, (se AEA section). User account names Maximum 20 characters Maximum 20 characters combined length of a Windows user account name plus domain name. Maximum 20 characters length for Oracle account names. Asset Models 1 per control system For each control system configured in ACM, a connection to one asset model can be defined. AEA and UserAlert access the asset models via ACM. The asset model represents the plant hierarchy. For example, process units, individual pieces of equipment or facilities. The primary relationship in the asset model is that of asset containment, where one asset contains another. Asset Models can be shared with Experion or can be stand alone for non-experion control systems. Assets 4,000 Assets are used to organise views and metrics and in mode based alarming. Akin to TPS Units or Experion Assets. Assignable assets 1,000 Alerts in UserAlert can only be members of assignable assets. They cannot be members of un-assignable assets. The number of assignable assets is a subset of the total number of assets. In Experion, assignable assets provide a way to assign assets to an operator s scope of responsibility. Nesting depth for asset hierarchies 10 Maximum of 255 characters in the fully qualified name, (an assets name concatenated with its parent s name and subsequent parents names). Children per asset Shift rotation No limit (up to the 4,000 total assets) Shift length must split evenly into 24 hr. E.g.: 1 x 24hr; 2 x 12 hr; 3 x 8hr etc; An asset contained in another asset is known as a child of that asset. No limit on the number of teams or the length of the rotation cycle. Multiple shift rotations can be configured per site, with different shift lengths. OPC DA versions supported 1.0a, 2.05

9 Advanced Alarm Management Specification, AAM310-ST ACM Items Specifications Comments Control Systems No limit Limited by server capacity. Maximum of one generic control system. Historians 1 One per ACM system, either PHD r210, R215 or others via Business FLEX and OPC HDA. Variables, (tags) 65,000 Testing limit Consoles 99 per control system Alarm settings Trip point, priority and alarm enable state Audit and Enforce Yes Audit control system settings against the ACM MBD. Enforcement schedules Alarm enforcement action Shift based or time based Must enforce; Report only; Ignore; Conditional (trip point only) By console Individually available for alarm Trip point, priority and alarm enable state Mode based alarm settings Yes Also known as state based alarm settings. Modes are configured on assets. Modes per asset 20 Testing limit Constraints per asset No limit Alarm documentation fields 5 Names of fields can be edited and are used site wide. Defaults are Reason for value, Potential impact etc. Other Alarm documentation Yes Shutdown pre-alarm indicator; Consequence and time to respond, (to apply alarm priority matrix) Variable (tag) documentation fields 10 Across two tabs in Manager Client. Names of fields and tabs can be edited and are used site wide. Other variable documentation Yes Alarm category, (type of alarm, eg quality); Alarm determination, (group to determined the need for alarm); Hyperlink to a relevant cross reference document; Hyperlink to a relevant drawing file, (eg, P&ID); Data export Text file All variable entity, constraint and drawing data. Data import Text file, as per export All variable entity, constraint and drawing data. Either only add new, or only update existing or add new and update existing. Load control Yes Specify the amount of data read or written with each ACM request as well as the delay between requests Configuration workflow (MOC) In Progress state Proposed state Approved state Released state Deleted state Is being modified Has been validated and is awaiting approval. Has been approved and the changes documented. Has propagated to the console base file and is in use for enforcement. Has been removed from enforcement and is unavailable for editing. Note: ACM stores multiple versions of a variable such that enforcement still occurs on last approved state while currently editing. Audit path Yes All changes made to the MBD are logged as are enforcement sessions

10 Advanced Alarm Management Specification, AAM310-ST 10 Items Specifications Comments Web Access Yes Via ACM Web, a read only interface to ACM variable entity data. Can be hosted on same web server as AEA. Can be made available to the business network (LAN) as well as the process network, (that is, either side of a network firewall) Alarm and Event Analysis Items Specifications Comments Events and alarm metric storage No limit Limited by server capacity due to control system configuration, event data rate, types of reports used. Control Systems No Limit Limited by server capacity Data Sources per Control System No Limit For example, for one Experion control system there could be multiple Experion servers. AEA connects individually to each Experion server. Configuration Data Source ACM AEAs alarm configuration reports use the configuration information already stored in ACM. Standard Reports 38 different reports Some reports are provided as both a RPT report and a CAR report. Others are RPT only. Only publish the reports a site needs. CARs are typically used dynamically. RPTs are typically scheduled but can be called at any time. Custom Reports No limit Design your own or modify the standard reports. Report Schedules Time based or Shift based Some reports can be scheduled based on time, (say weekly), while others can be based on shift, (say afternoon shift). Scheduled Report Notifications Contains hyperlink to report. Optionally the report can be attached to the in PDF, DOC and XLS formats. Report Formats Users viewing scheduled reports HTML, PDF, DOC, XLS No limit Web, PDF, Microsoft Word and Microsoft Excel Limited by server capacity. No additional licenses required to view results of scheduled reports. These are the normal consumers of reports. Business Objects Enterprise Premium licenses included Business Objects OLAP Intelligence licenses included Business Objects Crystal Reports Developer licenses included 5 named users Additional licenses can be purchased. Used to view/analyse published reports and to create report schedules. These are the super users of reports. 1 named user Additional licenses can be purchased. Used to create/modify/publish CAR (OLAP) type reports 1 named user Additional licenses can be purchased. Used to create/modify/publish RPT type reports Disk Space, (estimated): Scheduled report Disk Space, (estimated): HM (TPS) Data Collector event file disk space 20 KB (on AEA Web Server) 4 KB (on AEA Application Server) Disk space for scheduled reports, which must be deleted manually, is calculated as follows: Reports per day X days kept X 20 KB When an HM Data Collector is used, each event collection cycle generates an event file (4KB, assuming the block size on the disk is 4KB). Disk space for event files, which must be deleted manually, can be calculated as follows: Collections per day X days kept X 4 KB

11 Advanced Alarm Management Specification, AAM310-ST 11 Items Specifications Comments Disk Space, (estimated): 1000 alarm events 0.5 MB (on AEA Database Server) Alarm, acknowledge and return are each one event. Disk space used by SQL Server to store alarm data is calculated as follows: (Alarm events per day/1000) X 0.5 MB Note Assumes 200 operator changes per 1000 alarm events. Web Access Yes All AEA reports are web based UserAlert Items Specifications Comments Configured conditions 10,000 Up to 10,000 conditions evaluated every one minute per UserAlert Server. 10,000 is the tested limit. Monitoring resolution 10 seconds Conditions can be evaluated as often as every 10 seconds. Server memory usage 700 MB RAM for 10,000 conditions Demand on memory is approximately linear based on number of conditions. Condition types, (algorithms) 9 Bit Pattern, Boundary, Combination, Digital, Frozen, Group, Range, Rate of Change, Timer OPC Server OPC DA 1.0a, 2.0 One or more required to provide data. Tested with Experion R21x, R30x, APP R240, PHD R210, R215 and OSIsoft OPC Server for PI 3.3 and 3.4. OPC data sources No limit UserAlert can access data from many OPC sources. OPC Quality checks Yes Optional OPC quality alerts can be configured, meaning that an alert will be generated when an associated tag s data is unreliable, hence making the monitoring of the conditions that depend upon that data unreliable. Alert Disable Yes Alert sources, (possibly with multiple alert conditions), can be enabled and disabled. Private Alerts Yes Alert sources can be private or public. Public alerts are normally for many users based on asset assignment, while private alerts are for individuals to set up their own notifications. Condition configuration import/export Some Available for Range, Rate of Change and Digital conditions. Uses a Microsoft Excel spreadsheet. Experion Integration Yes UserAlert s operator interface is the Experion Alert Summary. If a site has Experion, alerts can be delivered to the existing Experion Station, (DSA license required by the Experion server that Station is connected to). For non-experion control systems, Experion Station is installed to provide the Alert Summary. 40 Station licenses provided with UserAlert for this stand alone purpose. Maximum number of active alarms and alerts (Experion server) 2,000 Alarms and alerts occupy the same storage space so there can be a maximum of 2,000 active alarms and alerts in the Alarm and Alert summaries.

12 Advanced Alarm Management Specification, AAM310-ST 12 Items Specifications Comments Alarm pager protocols Paging Entry Terminal (PET) Telocator Alphanumeric Protocol (TAP) UCP protocols UCP 01 UCP 30 UCP 51 Service providers in North America generally use the PET or TAP protocols where as the UCP protocols are mainly used in Europe. The two-digit suffixes refer to the EMI command numbers used by the provider. Number of pagers 100 Each pager and address can be configured with an individual schedule of operation so that users are only paged when they are on call. Number of addresses 100 Alarm pager configurable notification delays 0-60 minutes

13 Advanced Alarm Management Specification, AAM310-ST Hardware and Software Requirements 3.1. Client Software Note that individual client components may require only some of the platforms listed here. Item Operating systems can be used in any combination Other software generally required by most AAM client components Other software required for selected AAM client components, but not required for all end users Requirement Windows XP Professional SP2 Windows 2000 Professional SP4 Windows Server 2003 Standard Edition SP2 Windows Server 2003 Enterprise Edition SP2 Windows Vista Business Edition Windows Vista Enterprise Edition Internet Explorer 6.0 SP2 or 7.0 Microsoft.NET Framework 2.0 and 3.0 MSXML 4.0 SP2 MDAC 2.7 (or higher) Adobe Reader version 5 or later Microsoft SQL Server 2000 Analysis Services SP4, client components (needed only for AEA Reporting Building Workstation) Business Objects Crystal Reports XI Release 2 Professional or Developer (needed only for creating or editing AEA reports). 1 x Developer license provided with AEA license. Business Objects XI Enterprise Premium (needed only for AEA Web client users not required to only view scheduled reports in AEA Web). 5 x named users provided with AEA license. Microsoft Office XP, 2003 or 2007 (used in some cases when importing and exporting data) Exceptions: The Enterprise Model Builder is not supported on Windows Client Hardware A computer must meet the following specifications to be used as an AAM client. These guidelines are intended to provide a minimum baseline but including using Experion Station for UserAlert purposes. If this is not required, lower specification machines might be able to be used. System Configuration Minimum Recommended Processor 3.0 GHz Pentium IV or faster 3.4 GHz Xeon or faster RAM 1 GB 2 GB Video resolution 1024 x 768, 65K colours 1024 x 768, 65K colours Free hard drive space 1 GB 20 GB Network interface (Ethernet) 10 Mbits/sec 100 Mbits/sec

14 Advanced Alarm Management Specification, AAM310-ST Server Software Note that individual server components may require only some of the platforms listed here. Item Operating systems can be used in any combination Database management Requirement Windows Server 2003 Standard Edition SP2 Windows Server 2003 Enterprise Edition SP2 Oracle 9i Release 2 Server with patch or 10g Server : Standard Edition One, Standard Edition or Enterprise Edition option only for ACM MBD Microsoft SQL Server 2005 SP2: Standard Edition or Enterprise Edition Microsoft SQL Server 2000 Analysis Services SP4 needed only for AEA Reporting all listed software is required Business Objects Enterprise Premium XI Release 2 1 Business Objects OLAP Intelligence XI Release 2 Business Objects Crystal Reports Server XI Release 2 Other software required for at least some AAM server components Experion shared components Internet Explorer 6.0 SP2 or 7.0 Microsoft.NET Framework 1.1 SP1, 2.0 and 3.0 MSXML 4.0 SP2 MDAC 2.7 Oracle 9i client or 10g client SMTP and IIS Admin Adobe Reader version 5 or later Internet Explorer WebControls Visual Studio 2005, SP1 Runtime Experion Application Framework (EAF) R310 provided with AAM license Note 1 - Business Objects XI Release 2 (R2) is not the same as Business Objects XI SP2. Release 2 is a later release that has enhanced capabilities and different license keys. AAM R310 requires Business Objects XI Release 2 and does not support XI SP Server Hardware A computer must meet the following specifications to be used as an AAM server. These guidelines are intended to provide a minimum baseline. A single AAM server with all components installed is assumed. If some server components are to be installed on separate server, (e.g. ACM Enforcer server), see relevant installation guide for individual component minimum requirements. System Configuration Minimum Recommended Large System Processor Dual 3 GHz Xeon or faster Quad 3.6 GHz Xeon or faster Dual 2.66 GHz Xeon dual core or faster RAM 2 GB 4 GB 4 GB Video resolution 1024 x 768, 65K colours 1024 x 768, 65K colours 1024 x 768, 65K colours Free hard drive space 100 GB 300 GB 300 GB Network interface (Ethernet) 10 Mbits/sec 100 Mbits/sec 100 Mbits/sec

15 Advanced Alarm Management Specification, AAM310-ST Model Numbers 4.1. AAM Suite, (includes ACM, UA, AEA) Model Number AM-AAM001 AM-AAM002 AM-AAM003 AM-AAM004 AM-AAM005 AM-ACPACS Description AAM suite -- Size 1 (1 to 5 operator stations) AAM suite -- Size 2 (6 to 15 operator stations) AAM suite -- Size 3 (16 to 30 operator stations) AAM suite -- Size 4 (31 to 50 operator stations) AAM suite -- Size 5 (51 operator stations or larger) ACM Personality Module for non-honeywell control systems, per control system type, per site 4.2. Alarm Configuration Manager Model Number AM-ACMA01 AM-ACMA02 AM-ACMA03 AM-ACMA04 AM-ACMA05 AM-ACPACS Description ACM -- Size 1 (1 to 5 operator stations) ACM -- Size 2 (6 to 15 operator stations) ACM -- Size 3 (16 to 30 operator stations) ACM -- Size 4 (31 to 50 operator stations) ACM -- Size 5 (51 operator stations or larger) ACM Personality Module for non-honeywell control systems, per control system type, per site 4.3. Alarm and Event Analysis Model Number AM-AEA001 AM-AEA002 AM-AEA003 AM-AEA004 AM-AEA005 Description AEA -- Size 1 (1 to 5 operator stations) AEA -- Size 2 (6 to 15 operator stations) AEA -- Size 3 (16 to 30 operator stations) AEA -- Size 4 (31 to 50 operator stations) AEA -- Size 5 (51 operator stations or larger) 4.4. UserAlert Model Number AM-UAAA01 AM-UAAA02 AM-UAAA03 AM-UAAA04 AM-UAAA05 Description UserAlert -- Size 1 (1 to 5 operator stations) UserAlert -- Size 2 (6 to 15 operator stations) UserAlert -- Size 3 (16 to 30 operator stations) UserAlert -- Size 4 (31 to 50 operator stations) UserAlert -- Size 5 (51 operator stations or larger)

16 Advanced Alarm Management Specification, AAM310-ST Glossary Term or Acronym AAM ACM AEA APP ASM BMA CAR CEE DA DSA EADS EAF EAS EDS EHG Experion server HM LCN MBD MOC OPC PHD RPT SCADA TPN TPS UA Uniformance PHD Description Advanced Alarm Management, a suite of applications including ACM, AEA and UserAlert Alarm Configuration Manager, an AAM application Alarm and Event Analysis, an AAM application Application Processing Platform. Application node for the Honeywell TotalPlant Solution (TPS) system. Abnormal Situation Management Blending Movements Automation Crystal Analysis Report file. Flexible; Fast; more transient reports generally used for ad-hoc investigation via the web The Control Execution Environment supports execution of a set of function blocks for solving control applications. It is a software layer within Experion process controllers such as C200, C300, ACE and EHG. Data Access Distributed System Architecture is an Experion technology providing easy connectivity between servers. Experion Application and Desktop Server A component of EAF. A combined EAS and EDS. Experion Application Framework Experion Application Server - A component of EAF Experion Desktop Server - A component of EAF Experion Hiway Gateway provides an Experion interface to the TDC2000 Hiway and is a CEE device. The node (optionally redundant) at the heart of Experion. The servers encompasses a wide range of subsystems including history collection, SCADA interfaces, alarm/event, etc. History Module: TPN node that journals events among other functions. Local Control Network, the TDC3000 and TPS control network. Master Boundary Database Management of Change Series of standard specification for open connectivity in industrial automation originally based on Microsoft s OLE COM and DCOM technologies. See Uniformance PHD Report file (Crystal Reports): These are static; permanent; and specific analyse. Used for scheduling & distributing. Supervisory Control and Data Acquisition TotalPlant Network, (otherwise known as LCN) TotalPlant Solution UserAlert, an AAM application Flexible environment for the collection, storage and analysis of process data. A Process History Database (PHD) database may be centrally configured and managed, gathering data from many systems including Honeywell Experion PKS and TotalPlant Solution (TPS), OPC Servers, and other third-party sources.

17 Business FLEX, Uniformance and TotalPlant are U.S. registered trademark of Honeywell International Inc.. Experion TM is a 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/solutions visit our website or contact your Honeywell account manager. Automation & Control Solutions Process Solutions Honeywell 2500 West Union Hills Drive Phoenix, AZ Tel: or AAM310-ST March Honeywell International Inc.