• No results found

Honeywell Process Solutions. Experion PKS. Overview. EPDOC-XX81-en-410A R410 March Release 410. Honeywell

N/A
N/A
Protected

Academic year: 2021

Share "Honeywell Process Solutions. Experion PKS. Overview. EPDOC-XX81-en-410A R410 March Release 410. Honeywell"

Copied!
134
0
0

Loading.... (view fulltext now)

Full text

(1)

Honeywell Process Solutions

Experion PKS

Overview

EPDOC-XX81-en-410A R410 March 2012

Release 410

Honeywell

(2)

Notices and Trademarks

Copyright 2012 by Honeywell International Sárl. Release 410 March 2012

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

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. Honeywell, PlantScape, Experion PKS, and TotalPlant are registered trademarks of Honeywell International Inc.

Other brand or product names are trademarks of their respective owners.

Honeywell Process Solutions 1860 W. Rose Garden Lane Phoenix, AZ 85027 USA

(3)

About This Document

Provides brief descriptions of the functions and components that can be combined to personalize your Experion system.

Release Information

Document Name Document ID Release

Number Publication Date

Overview - ovwm

EPDOC- XX81-en-410A

410 March 2012

References

The following list identifies all documents that may be sources of reference for material discussed in this publication.

Document Title Control Building User's Guide

C300 Controller User’s Guide Control Hardware Installation Guide Server and Client Planning Guide Server and Client Configuration Guide Experion Specification document

(4)

Support and Other Contacts

United States and Canada

Contact: Phone:

Fascimile: Mail:

Honeywell Solution Support Center 1-800-822-7673

Calls are answered by dispatcher between 6:00 am and 4:00 pm Mountain Standard Time. Emergency calls outside normal working hours are received by an answering service and returned within one hour. 1-973-455-5000

Honeywell TAC, MS L17 1860 W. Rose Garden Lane Phoenix, AZ, 85027 USA Europe, Middle East, and Africa (EMEA)

Contact: Phone: Fascimile: Mail:

Email:

Honeywell TAC – EMEA +32-2-728-2345 +32-2-728-2696 TAC-BE02 Hermes Plaza Hermeslaan, 1H B-1831 Diegem, Belgium tac-be02@honeywell.com Pacific Contact: Phone: Fascimile: Mail: Email:

Honeywell Global TAC – Pacific 1300-364-822 (toll free within Australia) +61-8-9362-9559 (outside Australia) +61-8-9362-9564

Honeywell Limited Australia 5 Kitchener Way

Burswood, WA, 6100, Australia GTAC@honeywell.com India Contact: Phone: Fascimile: Mail:

Honeywell Global TAC – India +91-20- 6603-2718/19 1800-233-5051 +91-20- 6603-9800

Honeywell Automation India Ltd 56 and 57, Hadapsar Industrial Estate Hadapsar, Pune – 411 013, India

(5)

Email: Global-TAC-India@honeywell.com Korea Contact: Phone: Fascimile: Mail: Email:

Honeywell Global TAC – Korea

+82-80-782-2255 (toll free within Korea) +82-2-792-9015

Honeywell Co., Ltd

4F, Sangam IT Tower B4-4 Block 1590, DMC Sangam-dong, Mapo-gu Seoul, 121-835, Korea

Global-TAC-Korea@honeywell.com People’s Republic of China

Contact: Phone: Mail: Email:

Honeywell Global TAC – China +86- 21-2219-6888

800-820-0237 400-820-0386

Honeywell (China) Co., Ltd

33/F, Tower A, City Center, 100 Zunyi Rd. Shanghai 200051, People’s Republic of China Global-TAC-China@honeywell.com Singapore Contact: Phone: Fascimile: Mail: Email:

Honeywell Global TAC – South East Asia +65-6823-2215

+65-6445-3033

Honeywell Private Limited Honeywell Building

17, Changi Business Park Central 1 Singapore 486073 GTAC-SEA@honeywell.com Japan Contact: Fascimile: Mail: Email:

Honeywell Global TAC – Japan +81-3-6730-7228

Honeywell K.K

New Pier Takeshiba, South Tower Building 20th Floor, 1-16-1 Kaigan, Minato-ku Tokyo 105-0022, Japan

(6)

Elsewhere

Call your nearest Honeywell office. World Wide Web

Honeywell Process Solutions website: https://www.honeywellprocess.com/ Training Classes

Honeywell Automation College: http://www.automationcollege.com

(7)

Symbol Definitions

The following table lists those symbols used in this document to denote certain conditions.

Symbol Definition

ATTENTION: Identifies information that requires special consideration.

TIP: Identifies advice or hints for the user, often in terms of performing a task.

REFERENCE -EXTERNAL: Identifies an additional source of information outside of the bookset.

REFERENCE - INTERNAL: Identifies an additional source of information within the bookset.

CAUTION Indicates a situation which, if not avoided, may result in equipment or work (data) on the system being damaged or lost, or may result in the inability to properly operate the process.

CAUTION: Indicates a potentially hazardous situation which, if not avoided, may result in minor or moderate injury. It may also be used to alert against unsafe practices.

CAUTION symbol on the equipment refers the user to the product manual for additional information. The symbol appears next to required information in the manual.

WARNING: Indicates a potentially hazardous situation, which, if not avoided, could result in serious injury or death.

WARNING symbol on the equipment refers the user to the product manual for additional information. The symbol appears next to required information in the manual.

WARNING, Risk of electrical shock: Potential shock hazard where HAZARDOUS LIVE voltages greater than 30 Vrms, 42.4 Vpeak, or 60 VDC may be accessible.

(8)

Symbol Definition

ESD HAZARD: Danger of an electro-static discharge to which equipment may be sensitive. Observe precautions for handling electrostatic sensitive devices.

Protective Earth (PE) terminal: Provided for connection of the protective earth (green or green/yellow) supply system conductor.

Functional earth terminal: Used for non-safety purposes such as noise immunity improvement. NOTE: This connection shall be bonded to Protective Earth at the source of supply in accordance with national local electrical code requirements.

Earth Ground: Functional earth connection. NOTE: This connection shall be bonded to Protective Earth at the source of supply in accordance with national and local electrical code requirements.

Chassis Ground: Identifies a connection to the chassis or frame of the equipment shall be bonded to Protective Earth at the source of supply in accordance with national and local electrical code requirements.

(9)

Contents

1.

INTRODUCTION ... 19

1.1 Experion® Process Knowledge System (PKS) Offers a Single Solution . 19 Introducing Experion PKS ... 19

Experion PKS basics ... 20

Basic Control System topology ... 22

2.

CONCEPTS AND FUNCTIONS ... 27

2.1 Global Data Ownership ... 27

Global ownership ... 27 Data ownership ... 27 2.2 Composite Data ... 27 2.3 Deterministic Control ... 27 2.4 Redundancy ... 27 2.5 SCADA Support ... 28 2.6 On-Process Migration ... 28

Redundant servers required ... 28

Experion controller migration ... 28

Safety Manager migration ... 29

2.7 Off-Process Migration ... 29

2.8 Upgrade Tool ... 29

2.9 Custom installation path ... 30

2.10 Configuration Studio ... 30

2.11 Building an Enterprise Model ... 32

About the Experion Enterprise Model ... 32

System model ... 32

Asset model ... 32

Alarm group model ... 33

Network tree ... 33

2.12 Control Building... 34

Control Builder ... 34

Navigation improvements in the Control Builder ... 35

Search enhancements in the Control Builder ... 35

(10)

Control Builder enhancements in R410 ... 36

Function blocks ... 39

Control Modules ... 39

Continuous control functions ... 39

Logic control functions ... 40

Sequential control functions ... 40

Batch control functions ... 40

Procedural operations ... 40

Layered recipe functions ... 41

Unit Control Function (UCF) ... 41

Support for Class-based recipes ... 41

Template and hierarchical build functions ... 42

Qualification and Version Control System ... 42

Peer Control Data Interface functions ... 42

2.13 Identical Build/Operate Environments ... 42

Build environment ... 42

Independent build capability ... 43

Multiple user access ... 43

Operate environment ... 43

2.14 Safety Builder ... 44

2.15 OneWireless integration ... 45

2.16 Functional Logic Diagrams (FLDs) ... 47

2.17 Custom Display Building ... 50

HMIWeb Display Builder ... 50

Display scripts ... 51 2.18 Online Documentation ... 51 Knowledge Builder ... 51 KB mode ... 52 Internet-awareness ... 52 2.19 Internationalization ... 52

3.

SERVERS AND STATIONS ... 53

3.1 Supervisory Infrastructure ... 53

Components ... 53

Functions and features ... 53

3.2 Server ... 54

Capability ... 54

Alarm and event management ... 54

Alarm aggregation ... 55

(11)

Trending ... 55

Reporting ... 56

Redundancy ... 57

Distributed System Architecture ... 57

Server scripts ... 59

Specialized server software options ... 59

3.3 Stations ... 59

Flexibility ... 59

Flex Stations ... 60

Console Stations, Console Extension Stations, and Consoles... 60

Multiple-window Station configurations ... 60

Mobile Station ... 61

eServer and casual Web access ... 61

Specialized Station hardware ... 61

Station security ... 63

Integrated Security ... 63

Signon Manager ... 63

Electronic signatures ... 64

High Security Policy ... 64

3.4 Data Exchange ... 65

TPS Integration ... 65

Open Database Connectivity (ODBC) Driver ... 66

Open Database Connectivity (ODBC) Data Exchange ... 66

Microsoft Excel Data Exchange (MEDE) ... 67

OLE for Process Control (OPC) ... 67

Experion Application Programming Interface (API) ... 68

Network API ... 68

4.

PROCESS CONTROL HARDWARE ... 69

4.1 Control Hardware Infrastructure ... 69

Basic Components ... 69

Extension Component ... 71

4.2 Process Controller ... 73

About the controller ... 73

Chassis ... 74

Control Processor ... 74

Controller redundancy ... 76

Bumpless failure ... 80

Chassis I/O ... 80

Chassis I/O terminal connectors ... 81

Series C I/O ... 81

(12)

Safety Manager basic architectures ... 84

Controller chassis ... 84

Control Processor ... 85

Quad Processor Pack (QPP) ... 86

Universal Safety Interface (USI)... 87

IO bus ... 87

I/O modules ... 88

IO FTA ... 90

4.4 Wireless Device Manager ... 92

5.

SUPPORTED EXPERION HARDWARE ... 93

5.1 Supported Platforms ... 93

Supported server platforms ... 93

Supported workstation platforms... 93

5.2 Support for new Matrox Extio2 Remote Peripheral Solution (RPS) ... 94

6.

PROCESS COMMUNICATIONS ... 95

6.1 Communications Topology ... 95

Plantwide communications ... 95

Scalable security inhibits unauthorized data access ... 96

Control level communications ... 96

Application and user interface communications for the Experion server ... 97

Foundation Fieldbus communications ... 97

Redundant Fieldbus integrated architecture ... 99

6.2 Network Platforms ... 102

Ethernet ... 102

Fault Tolerant Ethernet ... 102

Supervisory Fault Tolerant Ethernet (FTE), ControlNet or Ethernet ... 103

Time Synchronization ... 103

6.3 ControlNet ... 103

Open technology ... 103

Devices ... 103

Control network redundancy ... 104

6.4 ControlNet Interoperability ... 104

6.5 Connectivity ... 106

Background ... 106

Third-party networks ... 106

6.6 Communications Model for the Control Processor ... 107

(13)

Publish/subscribe transport layer ... 107

Publish/subscribe application layer ... 108

Request/response application layer ... 108

Report-by-exception ... 108

6.7 Safety Manager SafeNet ... 108

7.

MONITORING PLANT PROCESSES ... 111

7.1 Understanding Points ... 111

Process points ... 111

Flexible points ... 111

Standard (Inbuilt) point types ... 111

Scanning ... 112

Point algorithms ... 112

Scripts ... 112

User-defined parameters... 112

7.2 Process Monitoring and Data Display ... 113

System displays for configuring your system ... 113

System displays for managing alarms and events ... 114

System displays for monitoring your processes ... 114

Custom displays ... 117

7.3 Operator Notification of Alarms and Events ... 118

Alarm and event generation ... 118

Alarms ... 119

Filters and views ... 119

Alarm suppression ... 119

Alarm shelving ... 120

Operator response ... 120

7.4 Safety Manager Sequence of Events (SOE) support ... 122

SOE generation ... 122

SOE reporting ... 122

8.

CONTROLLING THE PROCESS ... 123

8.1 Understanding Supervisory Control ... 123

Supervisory control ... 123

8.2 Examples of Process Control ... 124

Background ... 124

Process control using status points ... 124

(14)

9.

ANALYZING PROCESS DATA ... 127

9.1 Understanding Reports ... 127

Background ... 127

9.2 Process History Analysis and Archiving ... 127

History ... 127

PHD integration ... 128

Analyzing process history ... 128

Archiving process history ... 129

Event archiving and storage ... 129

10.

STANDARD COMPLIANCE ... 131

10.1 Safety Manager compliance ... 131

(15)

Tables

Table 1 Safety Manager System Configurations ... 83 Table 2 System Manager Architectures ... 84

(16)

Figures

Figure 1 - Experion Platform Architecture ... 20

Figure 2 - Basic Experion System Topology with C200 Process Controllers ... 24

Figure 3 - Basic Experion System Topology with C300 Process Controllers ... 25

Figure 4 - Example SafeNet Topology ... 26

Figure 5 - Configuration Studio ... 31

Figure 6 - Typical Control Builder view with open Control Module. ... 34

Figure 7 - Sample Safety Builder Function: Network Configurator ... 44

Figure 8 Experion OneWireless integration topology ... 46

Figure 9 - Sample Functional Logic Diagram (FLD) ... 47

Figure 10 - Typical custom display ... 51

Figure 11 - Typical trend display ... 56

Figure 12 - A geographically distributed system ... 58

Figure 13 - A plant-wide distributed system ... 58

Figure 14 - Honeywell's Icon Console ... 62

Figure 15 - Sample Upgraded System with Experion Controller Expansion ... 65

Figure 16 - C200 Control Processor ... 75

Figure 17 - C300 Control Processor ... 76

Figure 18 - Redundancy Module For C200 Controller Redundancy ... 77

Figure 19 - Module redundancy for C200 Controller in redundant supervisory ControlNet networks ... 78

Figure 20 - C300 Controller redundancy in supervisory Fault Tolerant Ethernet network79 Figure 21 - Chassis I/O Module Basic Layout ... 80

Figure 22 - Typical non-redundant Series C I/O configuration ... 82

Figure 23 - Front and Rear View of the CP chassis ... 85

Figure 24 - Safety manager Control Processor Modules ... 86

Figure 25 - Back View of Typical Safety Manager with Redundant Controller and I/O Chassis ... 88

Figure 26 - Example of the High Density SAi 1620m Module... 89

Figure 27 - Some Terminal Type FTA's ... 91

Figure 28 - Scalable Architecture for Plantwide Communications. ... 95

Figure 29 - Control Level Communications Network for C200 Controllers using ControlNet media ... 96

Figure 30 - Supervisory Level Communications Network ... 97

Figure 31 - Foundation Fieldbus Level Communications Network using a Chassis I/O - Series A Fieldbus Interface Module ... 98

Figure 32 - Foundation Fieldbus Level Communications Network using a Series C Fieldbus Interface Module ... 99

Figure 33 - Sample system architecture for redundant Fieldbus integration using a Chassis I/O - Series A Fieldbus Interface Module ... 100

(17)

Figure 34 - Sample system architecture for redundant Fieldbus integration using a

Series C Fieldbus Interface Module ... 101

Figure 35 - Control Network Redundancy ... 104

Figure 36 - Connectivity System ... 106

Figure 37 - Experion versus ISO-OSI Communications Model ... 107

Figure 38 - Example Safety Manager Topology ... 109

Figure 39 - Typical configuration display ... 113

Figure 40 - An alarm summary display ... 114

Figure 41 - A typical point detail display ... 115

Figure 42- A Typical Faceplate ... 115

Figure 43 - A typical trend display ... 116

Figure 44 - A typical group display ... 116

Figure 45 - Safety Manager System Information Display ... 117

Figure 46 - An event summary display ... 118

Figure 47 - Supervisory Control Process ... 123

Figure 48 - Process Control Example ... 124

Figure 49 - Process Control Using Status Points ... 125

(18)
(19)

1. Introduction

1.1 Experion

®

Process Knowledge System (PKS) Offers

a Single Solution

Introducing Experion PKS

Experion PKS is a cost-effective open control and safety system that expands the role of distributed control. It addresses critical manufacturing objectives to facilitate sharing knowledge and managing workflow. Experion provides a safe, robust, scalable, plant-wide system with unprecedented connectivity through all levels of the plant as illustrated in the following high-level view of the architecture. The Experion unified architecture combines DCS functionality and a plant-wide infrastructure that unifies business, process, and asset management to:

Facilitate knowledge capture Promote knowledge sharing Optimize work processes

(20)

Figure 1 - Experion Platform Architecture Experion PKS basics

The Experion platform is well suited for both small and large systems. It provides the power and flexibility required to handle the full spectrum of process control and safety applications.

Experion offers state-of-the-art DCS capabilities that include Abnormal Situation Management® (ASM®), Safety Management, and Information Management technologies. Experion interfaces with FOUNDATION Fieldbus, Profibus, DeviceNet,

HART, LON, ControlNet and Interbus. Robustness, security, compliance, control, safety, and reliability are plant-wide. Its distributed control features include a complete continuous, logic, sequential, and drive object-oriented control environment hosted on fully redundant controllers.

Experion features include:

(21)

Operational integration of control and safety applications.

Open, deterministic, high-speed control network communications system for predictable and repeatable control linking servers, controllers, and remote I/O. A configurable Control Execution Environment (CEE) provides deterministic, consistent, and reliable control application execution.

A single builder tool, Configuration Studio, allows integrated application configuration.

Four CEE-based controllers:

The C200 Process Controller is a compact and cost-effective solution located close to the process with direct IO connections. It is ideal for integrated regulatory, fast logic, sequential, and batch control applications.

The C200E Process Controller an enhanced C200 Controller with additional user memory and an enhanced function block set.

The C300 Process Controller is the next generation controller that builds on the reliability and robustness of the C200 controller to provide even more versatile control integration through innovative mounting and connecting techniques.

The Process, Machinery and Drives (PMD) Controller provides the traditional control process functions and manages smart motor center controls, hydraulic and pneumatic controls of machinery and coordinated line drive control solutions. Fast functions, such as machine element controls and coordinated line drives, can be executed at a 20 millisecond cycle. For more information about PMD Controllers, refer to Experion PKS with PMD

Controller Field Controller User's Guide and Experion PKS with PMD Controller Field Controller Express User's Guide.

The Application Control Environment (ACE) is ideally suited for

supervisory control solutions and integration with third party control systems. It is hosted on a server grade computer platform.

Safety Instrumented Systems (SIS)

Safety Manager topology with scalable safety solution through Safety Manager local I/O and SafeNet plant-wide network capabilities. Safety Manager will meet the most stringent safety requirements with Safety Integrity Levels (SIL) 3 compliancy.

The Simulation Control Environment (SCE) supports system simulation on computers without requiring dedicated controller hardware or process connections. Redundancy support for servers, networks, and controllers.

(22)

Support for internationalization/localization.

Interfaces for wide variety of third-party controllers and protocols. A cost-effective architecture that -

Makes extensive use of open technologies and commonality of hardware, and Is scaleable from just a few points, to thousands of points.

Basic Control System topology

In a basic Experion system topology, the server and C200/C200E and/or C300 Process Controllers share a global database, so you only need to enter data once. This one-step configuration eliminates errors and dramatically reduces configuration time. When you define a control or safety strategy, point detail displays, trends, alarms, and group displays are automatically created, so you instantly have access to the information you need to operate your control or safety strategy. The following figure illustrates the high-level view of a basic Experion system topology. Experion can be segmented into basic sets of hardware component platforms:

Supervisory Platform, which includes non-proprietary computing platforms running Windows operating systems and serving as both Experion servers and Experion Stations. Experion Stations are able to serve as both engineering and operating interfaces, depending on the software loaded on each node.

C200/C200E, C300, using a small hardware form-factor supporting a scaleable and modular architecture. Commonality and flexibility of hardware components, and their placement within the system, reduce initial cost-to-purchase, and minimize cost-of-ownership while plant safety is guaranteed.

Safety Manager Controller is the SIL 3 safety controller that executes safety strategies independently from the process control layer. It communicates with dedicated Input/Output (I/O) modules that are directly connected to the Safety Manager controller. Safety manager is a fully redundant controller that seamlessly integrates in the Experion topology. Safety Manager Controllers can connect to each other through a dedicated network or through the FTE network. The "SafeNet" connection is a SIL 4 certified safety protocol.

Process, Machinery and Drives (PMD) Controller is a controller unit that contains an integrated application execution environment, two independent fieldbus interfaces, an Upline interface, an FTE system interface.

Integrated Controllers, the server integrates to a number of Honeywell loop controllers and recorders. This integration effectively reduces engineering time by integrating the device configuration tools and/or diagnostic features with the Experion platform.

(23)

Third -party Controllers, the server can interface to a number of third party controllers including the Allen Bradley PLC5 and SLC range, Modicon, GE Fanuc and Siemens plus many more.

Communications Platform, which utilizes open network standards, including: Ethernet-or Honeywell's Fault Tolerant Ethernet (FTE) based plant information network (PIN) linking servers and clients together for the purpose of

supervisory level communications.

Fault Tolerant Ethernet (FTE) network providing the communications link between the C300 Controllers and the supervisory level as well as peer-to-peer communication between Controllers and remote I/O.

SafeNet providing the safe communication link between the Safety Manager Controllers on a separate network or by using Fault Tolerant Ethernet (FTE). ControlNet, Ethernet, or Fault Tolerant Ethernet (FTE) network providing the communications link between the C200/C200E Controllers and the supervisory level, as well as peertopeer communications between Controllers, with -ControlNet network providing the communications link between the C200/C200E Controllers and remote I/O.

ATTENTION

With R410, you can configure native peer-to-peer communication between the CEE points and non-CEE points such as SCADA, TPS, PMD, and Safety Manager points.

(24)

Figure 2 - Basic Experion System Topology with C200 Process Controllers

Supervisory Fault Tolerant Ethernet, ControlNet, or Ethernet

Non-Redundant Controller Redundant Controller Other connectivity Honeywell S9000 Honeywell 620 LC TDC 3000 Data Hiway Honeywell UDC Modicon PLC Allen-Bradley

LAN (TCP/IP, Ethernet, Fault Tolerant Ethernet, etc.)

Server Station Station Controller Controller Controller I/O ControlNet I/O ControlNet

(25)

Figure 3 - Basic Experion System Topology with C300 Process Controllers

(26)
(27)

2. Concepts and Functions

2.1 Global Data Ownership

Global ownership

The global ownership part of the Global Data Ownership concept means that there is one-and-only-one owner of any particular object across the entire automation system. This has advantages primarily in the area of engineering efficiency. Global data allows the Experion system to provide a unified build environment.

Data ownership

In the Experion system, the controller owns some data while other data is owned by a server-based database known as the System Repository. Each data element is owned by one-and-only-one of these entities. This provides robustness because all users

throughout the Experion system are dealing with the same value for that data at any given point in time. Since the data is owned by one-and-only-one entity yet is usable throughout the entire system, each data entity needs to be built only once in Control Builder.

Data is also acted upon in a unified fashion, best typified by unified event

management. For example, the C200/C200E or C300 Process Controller originates alarms and events and notifies all relevant parties throughout the system of their occurrence. This is known as the "event notification subsystem" and it is an important part of the system's architecture. Data in the Experion environment is global in nature, and as such, can be used by any relevant entity throughout the system.

2.2 Composite Data

Composite data (using a Control Module, point, parameter model) provides engineering efficiency by establishing predefined data structures. It also permits precise control by supporting consistent exception and failure mode handling.

2.3 Deterministic Control

Deterministic control simply means quality through repeatable control. Users are informed when they approach the limits of the control processing cycle. If a user has overloaded a controller processing cycle, control is still performed.

2.4 Redundancy

Redundancy provides critical system components with the software to transfer from a primary to a secondary device should a problem develop in the primary device. The Experion system has been designed to accommodate the most complete redundancy protection ever developed for an industrial automation system, and fully implement redundancy in terms of servers, networks, controllers, and selected I/O.

(28)

For Experion Safety Manager, redundancy is applied by running the two single legs simultaneously. This allows for uninterrupted process safety in case of any anomaly detected in controller, I/O or field instrumentation. Even the single Safety Manager leg is SIL 3 certified without restrictions.

2.5 SCADA Support

By definition, an Experion process system includes C200/C200E, C300, and/or ACE controllers. It can also include SCADA devices that may consist of serial devices (RS232 or RS485), ControlNet connections, and/or Ethernet Interfaces (for example, MODBUS TCP) or combinations of these. In addition, SCADA points and connections may coexist with C200/C200E s and TPS within given capacity constraints. The Quick Builder application provides the tools for building a SCADA network interface. A SCADA only system does not include C200/C200E, C300 or ACE controllers.

2.6 On-Process Migration

Experion on-process migration is a licensed option for upgrading software on redundant servers, Stations, and Process Controllers to a new release. It does not include the migration of SCADA connected controllers.

Redundant servers required

If you have a redundant system, you can use on -process migration to upgrade to the next release of Experion while maintaining view and control of your processes. On-process migration involves upgrading one of the servers, switching the upgraded server to primary mode and then upgrading the other server.

Once you upgrade the redundant servers and their associated Stations, you can use the Controller Migration Wizard to upgrade the redundant Controllers and their associated I/O modules.

Experion controller migration

Redundant C200/C200E Controllers migration includes the firmware upgrade of chassis-resident modules such as the Control Processor Module, Redundancy Module, Fieldbus Interface Module and I/O Link Interface Module. The same is true for Redundant Series C hardware such as the C300 Controller and Series C Fieldbus Interface Module.

You must upgrade ACE and SCE nodes off process, but you can use the Controller Migration Wizard to start the migration.

ATTENTION

You must perform freeze and switchover operation of redundant C200, C200E, and C300 from server B only.

(29)

Safety Manager migration

Safety Manager on-process migration is an option for upgrading software on redundant Safety Manager Controllers to a new release.

If you have a redundant system, you can upgrade to the next release of Experion Safety Manager while maintaining view and safety of your processes.

On-process migration involves upgrading one of the Safety Manager Control Processors, switching the upgraded server to primary mode and then upgrading the other Control Processor. This all is done by using the 4-step wizard that guides you through the OPM process

The Safety Manager migration allows for upgrades of application, and firmware. The migration is TUV approved and Safety Manager will continue safeguarding the Process during all steps of the migration process. No external measures (such as external overrides or secondary means of process stops) are needed.

The flexible migration of Safety Manager allows even adding and removing of hardware modules, chassis or even complete Safety Manager Controllers while continuously monitoring the plant safety.

2.7 Off-Process Migration

The off-process migration does not require a license and you can use it to upgrade redundant as well as any non-redundant system components including servers.

2.8 Upgrade Tool

The Upgrade tool checks the upgrade readiness of the nodes and its subsystems in an Experion system. The Upgrade tool is installed as a part of the Engineering tools installation. If you have redundant servers, Upgrade tool is installed on Server B. In case of non-redundant server, Upgrade tool is installed on the only server. The Upgrade tool does not depend on any specific Experion topology. In case of a redundant Experion configuration, the Upgrade tool is run only on the Server B. In case of a non-redundant Experion server configuration, the Upgrade tool is run on the single Experion server node. The Upgrade tool ensures that it does not overload the Experion server. Before starting an Experion upgrade, you have to verify the upgrade readiness of the Experion system and prepare it for the upgrade. The Upgrade tool automates the manual process of preparing the Experion system for the upgrade. After the upgrade is complete, you can run the Upgrade tool to perform a post-upgrade analysis. Upgrade tool makes the upgrade readiness process effortless, easy, and error-free. It reduces the manual information gathering time and minimizes the possibility of errors.

(30)

2.9 Custom installation path

Starting R410.1, Experion installation, and migration is supported on custom installation paths. This feature allows control on the path where Experion is installed/migrated and the location where the runtime files and SQL logs are stored. You can select the custom installation path for the following components.

Experion software: This consists of deliverable that are part of Experion installer and third party software.

Experion runtime data: This consists of the all the files and folders available at “C:\ProgramData\Honeywell\” path for the Experion release and the Experion SQL databases. Following files comes under this category.

Runtime data

Experion created SQL data files

Experion SQL logs: This consists of SQL database log files generated during installation/migration

2.10 Configuration Studio

Configuration Studio provides a central location from which you can configure your Experion system. The individual tools required to configure parts of your system are launched from Configuration Studio.

(31)

Figure 5 - Configuration Studio

In Configuration Studio, you are provided with a customized list of tasks that you are required to complete to configure your system. When you click a task, the appropriate tool is launched so that you can complete the task.

(32)

These tools include:

Enterprise Model Builder: a graphical tool for building your asset model. (See

Asset model.)

Quick Builder: a graphical tool for building hardware items such as Flex Stations, printers, controllers, and standard (non-C200/C200E) points in your system. After building hardware and points with Quick Builder, you download these items from Configuration Studio to the server database.

System Displays: displays that are used to configure items such as reports, group display, trends, Station settings, and Console Stations.

Control Builder: a graphical tool for building your control strategy for Process Controllers.

HMIWeb Display Builder: a graphical tool for creating your own (custom) displays using Web-based features. Displays are saved in HTML format. For more information on custom displays and HMIWeb Display Builder, see the Safety Builder section.

2.11 Building an Enterprise Model

About the Experion Enterprise Model

The Experion Enterprise Model is a framework that can be used by engineers, operators, and applications to model and view their plant or process. The Enterprise Model replaces the flat, area-based structure that was used prior to Release 210. You use Configuration Studio (see Configuration Studio) to define the various components of your Enterprise Model, which comprises:

A system model An asset model An alarm group model Network tree

System model

The system model represents the boundaries of your system. You build your system model by defining the servers that are part of your Experion system. You can also use your system model, to define those servers that are connected to, but outside of, your system.

Asset model

An asset model forms the core of the Experion Enterprise Model and is used to: Define scope of responsibility for operators and other users

(33)

Resolve data references Manage alarms

Organize points, displays and reports.

About assets in an asset model

An Experion asset is a database entity that represents a particular physical item in your enterprise, for example, fixed plant equipment, facilities and buildings.

The benefits of a hierarchical asset-based structure in your Experion database include: A simple and intuitive means of implementing scope of responsibility (SOR), that is, of allowing or restricting access to parts of the plant, process, or equipment. Instead of having to nominate each and every item for which a given Station or operator has scope of responsibility, you can often assign the scope of

responsibility with a single click, depending on how you have defined your asset structure. By assigning a given asset to a Station or operator, you assign that Station or operator the ability to control all the points that belong to that asset (and any of its subsidiary or "child" assets) and to view the alarms and custom displays for that asset.

A structure that can be used to logically replicate your physical assets and to engineer your Experion system around your key entities.

A user-friendly asset-naming system that helps operators and other users to more easily navigate through displays and identify particular parts of the plant or specific pieces of equipment without having to remember obscure tag names.

A ready-made form of alarm aggregation. Once you have defined your assets and the points that belong to those assets, alarms for those points are automatically aggregated under each asset.

Alarm group model

The alarm group model is used to: Define alarm groups

View aggregated alarms for those alarm groups Network tree

The Network tree is a graphical view of the nodes on your network, which can be viewed on the System Status display. This provides you with a single display that can be used to view the status of all the parts that comprise your control system.

The Network tree works in conjunction with the System Event Server and the System Performance Server to display system errors, which can be used to troubleshoot faults within the system.

(34)

2.12 Control Building

Control Builder

Control Builder is an engineering tool offering the latest in control strategy building going well beyond looking "pretty" on screen. Its graphical, object-oriented design dramatically reduces the effort required to design, implement and document control applications.

Figure 6 - Typical Control Builder view with open Control Module. Prior to R400, you could search or a tag by expanding the function block tree view in Project or Monitoring mode.

With R400, you can search, sort, and filter the tags. The Control Builder search window can be resized to view the complete tag name and other fields.

(35)

Navigation improvements in the Control Builder

Navigating to the function block/parameter in the Control Builder is based on the Closed Match concept.

For more information on navigation enhancements, see Control Building User's Guide. Search enhancements in the Control Builder

Prior to R400, you could search for a tag by expanding the function block tree view in Project or Monitoring mode.

With R400, you can search for tags in the following ways. Using File > Open > Open Object

Using Find Options toolbar in the tree view Typing the prefix of a tag in the tree view

Using New List View, which also provides sorting and filtering functionality For more information on search enhancements, see Control Building User's Guide. Resize Control Builder Search windows

Prior to R400, you could not resize the search window to view the complete tag name and other fields.

With R400, following are the enhancements with Control Builder Search windows. Resizing of the Control Builder Search window to view the complete tag name A tooltip is available for the controls in the dialog box.

Column sorting and resizing based on the column values

The following are the search windows considered for the enhancements: Point Selection popup window

Create / Read Bulk Build List Create / Read Bulk Edit List Substitute Name List

Execution Environment Assignment

For more information on resizing the Control Builder Search windows, see Control

(36)

Control Builder enhancements in R410

The following are the Control Builder enhancements in Experion R410.

Configuring on-delay and off-delay for individual alarms

With R410, on the Alarms tab, you can configure on-delay time, off-delay time, deadband value, and deadband units for the individual alarms. This is applicable only for few function blocks for which alarms are supported.

For more information about the on-delay and off-delay functionality, refer to Control

Builder Components Theory. Configuring alerts

With R410, the FLAG block is enhanced such that you can configure the FLAG block to generate alerts. To accomplish this, a new parameter ALTENBOPT is introduced in the Main tab of the FLAG block configuration form.

For more information about configuring the alerts, refer to Control Building User's

Guide.

Control Builder print feature

Prior to R410, you could not print multiple pages in a single sheet. This resulted in wastage of paper. In addition, you could not view the complete chart configuration in a single page. In addition, before printing, you could not predict the number of pages that might be required to print the selected chart.

With R410, Control Builder print and zoom feature is enhanced such that you can print multiple pages of a chart in a single sheet based on the scale factor. In addition, before printing you can preview the charts and can predict the number of pages to be printed using the Print Preview option. You can also zoom-in and zoom-out the charts to the desired zoom values.

For more information about configuring the alerts, refer to Control Building User's

Guide.

Print Preview feature

With R410, Print Preview feature enables you to preview the charts before printing. You can only preview the chart that is currently open before printing. The Print Preview feature enables you to view each page of a chart individually. You can also navigate to the next or the previous page of the chart.

For more information about configuring the alerts, refer to Control Building User's

(37)

Inserting comments into a strategy using Text Comment block

With R410, you can use the Text Comment block to add comments into a template or a strategy. The Text Comment block contents can be added/modified from the Project view. The strategy can then be loaded to the Monitoring view without inactivating the strategy or setting the CEE to IDLE. If you add a Text Comment block into a strategy that is already loaded, the Load while active delta flag appears against the strategy. Similarly, if you modify the existing comments in the Text Comment block, the Load while active delta flag appears against the specific Text Comment block. This indicates that the strategy/block can be loaded while active.

For more information about Text Comment block, refer to Control Builder

Components Theory. Exporting object with contents

With R410, you can export objects with contents. When you select a parent object to be exported, all the childlevel objects are also selected for export, by default. The parent objects can be Controllers, CEEs, IOLINKs, containers CM, or user-defined templates. For example, you can export a controller along with its assigned strategies in a single operation.

For more information about exporting objects, refer to Control Building User's Guide.

Regulatory control (REGCTL) function block detail displays

With R410, standard detail displays are supported for some of the REGCTL function blocks. As a result, the operator need not create a custom display for these REGCTL blocks for monitoring purposes.

For more information about exporting objects, refer to Control Building User's Guide.

Support for validation of blocks with OPC references

Prior to R410, if you entered an incorrect block name, there was no option to verify the OPC references during configuration. If any of the block that contained OPC

references had executed successfully, and if that block was deleted later, there was no indication of the missing block during the subsequent execution.

With R410, a new feature is introduced in the Control Builder/Recipe Builder to validate blocks with OPC references after loading the OPC gateway. This feature can also be used for validating OPC references, if the OPC gateway is configured through the Redirection Manager (RDM).

(38)

Support to edit or load parameters while active

With R410, you can modify and load the SR-resident parameter values without inactivating the control strategy/setting the CEE to IDLE. The parameters that can be modified/loaded while active are referred to as ‘active loadable’ parameters. In addition, you can turn off editing of all parameter values except for active loadable parameters. To accomplish this, Allow only active loadable parameter changes option is introduced in the System Preferences > General tab.

To load parameters while active, a new load option called Load Values while Active is provided. Note that when load while active is performed, the server point build also happens simultaneously. Any errors that occur while loading the active loadable parameter values do not affect the on-process control.

For more information about Load Values While Active functionality, refer to Control

Building User's Guide.

Automatically apply Daylight Savings Time (DST)

Prior to R410, at the start of DST, you had to manually set the DAYLIGHTTIME parameter to ON in all Experion controllers. Similarly, at the end of DST, you had to set this parameter to OFF in all Experion controllers.

With R410, a new feature Automatically apply DST is introduced, which enables you to automatically apply DST settings to all Experion controllers in a cluster. This feature is applicable to all Experion controllers. This feature is optional; however, if you do not select this feature, you still have to manually set the DAYLIGHTTIME parameter. For more information about Automatically apply DST functionality, refer to Control

Building User's Guide.

Identification of unused I/O channels

Prior to R410, identifying unused I/O channels was not easy since I/O channels retained their last modified names even after unassignment or deletion.

With R410, I/O channel names return to their default names after unassignment or deletion; thereby making the identification of unused I/O channels simpler. In R410 and later, in case the channel name conflicts during any of the scenarios mentioned, “_1” is suffixed with the channel name. For example, if

“AICHANNEL_01” already exists in the unassigned list, the channel name is changed to “AICHANNEL_01_1.”

For more information about identification of unused I/O channels functionality, refer to

(39)

Support to rename objects while importing

Prior to R410, you could not rename the objects while importing. As a result, the existing objects would be overwritten with the new objects.

With R410, you can rename objects while importing the objects. You can also rename objects containing Foundation Fieldbus blocks.

For more information about renaming objects while importing functionality, refer to

Control Building User's Guide.

Support to search for dangling/missing connection

A connection is said to be dangling, if a block is missing at one end of the connection. A connection is said to be missing, if the blocks are missing at both ends of the connection.

With R410, you can search for dangling and missing connections in the system using the Search utility in Configuration Studio. You can perform a search for a dangling connection at the system, the server, the controller, and the tagged module level. You can perform a search for a missing connection at the system and the server level. For more information about searching for dangling/missing connection functionality, refer to Control Building User's Guide.

Function blocks

Function blocks represent the basic unit of control functionality that includes Regulatory Control blocks, Device Control blocks, Logic blocks, Sequential blocks and Auxiliary blocks. With Control Builder, function blocks are selected from a Honeywell-supplied "Function Block Library" and placed in a Control Module. These function blocks are then soft wired together to perform the desired control strategy. Control Modules

Experion provides two basic types of control modules: Control Modules - used for continuous control functions, and Sequential Control Modules - used for sequential and batch control functions. Both control module types contain their respective function blocks.

Continuous control functions

The designed-in features of the continuous control functionality reduce your engineering costs and enable intuitive operator interaction with the control strategy. This has been done by designing in features and options that address a wide range of control needs through simple configuration tasks. By offering configuration options to address control needs, Experion provides predefined approaches for the operator interface, and handling how failures are managed by the control strategy. This in turn defines how your control strategies recover when failures are cleared. In Experion, the continuous control automatically handles these functions, supporting control that

(40)

enforces maximum ramp rate of the temperature measurement-adjusting output ramp as necessary. No additional engineering effort is required to implement this on your part.

Logic control functions

The value of logic control functions is focused in the area of improving engineering efficiency by providing a full suite of algorithm options in an approach that can be consistently configured and operated. The built-in device level functions also address:

Common application needs for motors, valves, and pumps Improve operational monitoring by offering

Intuitive interlock tracing, and

Direct access to device maintenance statistics, such as motor run-time. Sequential control functions

Sequential control functions reduce the engineering costs for implementing sequential and batch control applications. The implementation of batch and sequential control is in the implementation of abnormal situation management such as:

"What control action should be taken when a motor trips?"

"What control action should be taken when an interlock shuts a valve?"

"What control action should be taken when an operator has intervened with manual action to adjust a mode or setpoint?"

The Experion sequencing control facility is designed with built-in options to handle abnormal situations. Devices can be configured to enter states, setpoint, outputs etc. based on abnormal status, or you can program a series of steps to safely handle the process. Devices can also be configured to take fail-safe action on abnormal sequence operations. Implementation is simplified and intuitive operator information on

sequence/batch status is directly available. The system also uses smart device drivers to enable the control strategy to easily and quickly return to its normal state when the abnormal condition is cleared.

Batch control functions

Experion batch capabilities enable significantly reduced engineering costs and improved operational security. The built-in coordination and batch, sequence, and device controls eliminate the work required to handle normal housekeeping chores, which in many projects can amount to 20% or more of the engineering effort. Procedural operations

The Sequential Control Module (SCM) and Recipe Control Module (RCM) views and operator interactive functions that collectively work to improve operator effectiveness are referred to as Procedural Operations that are also known as ProcOps or Interactive

(41)

startup, shutdown, grade change, and so on, in an interactive manner patterned after those previously executed from paper documents. A Table View function in Station facilitates operator interaction with SCMs and RCMs. Some of the features and functions of Table View are the ability to:

View transition details associated with the step, View Step associated Instructions when implemented,

Use filters allowing operators to focus on items relating to the steps and outputs currently executing ,

Use filters allowing operators to display only executing steps/phases with key trailing transitions ,

Enable the operator to 'stand' on a step to view leading and trailing transition details, and

Record all operator changes made through the SCM/RCM Table View in the system journal.

Layered recipe functions

Starting in Experion R310, Control Builder supports multiple layers of recipe

configuration. This means you can build and execute multiple level hierarchical recipes as defined in ISA S88.01. In this hierarchy, a higher level recipe can control its underlying recipe(s). Recipes at each layer are implemented as a modular function block. Recipe Control Module (RCM) blocks can represent Procedures, Unit

Procedures, and Operations. Sequential Control Module (SCM) blocks can represent Phases.

Unit Control Function (UCF)

The UCF provides the ability to map a PHASE block to an SCM or an RCM, which allows a "function" defined by a PHASE block to initiate a single simple SCM in one case and a more complex multi-layer RCM/SCM in another. This lets layered recipes map directly to an SCM/RCM at any level rather than constraining initiation of a Phase/SCM to the operation level. For example, a Procedure, Unit Procedure, or Operation can directly initiate a Phase/SCM. The UCF does not constrain to a defined parent/child relationship between the layers. It supports the standard layers while giving users the flexibility to adjust to meet specific process needs.

Support for Class-based recipes

With R410, the Experion Batch Manager (EBM) is enhanced to support Class-based recipes.

Class-based recipes are recipes that are designed for Unit classes and not for a specific Unit. When you need to run an operation on every Unit in a Unit class, you can create Class-based recipes to avoid creating the same operation for every Unit. That is, you

(42)

can design a recipe for a Unit class and during runtime, the recipe can be assigned to run on any selected Unit in the Unit class.

Class-based recipes enable reuse of recipes and reduce engineering effort; there by improving the batch cycle time.

For more information about implementing and using Class-based recipes, refer to the following documents –

Batch Overview and Planning Guide Batch Implementation Guide Operator’s Guide

Template and hierarchical build functions

Control Builder offers optional template and hierarchical build functions so users can create their own templates and arrange control strategy components to reflect their process hierarchy.

Qualification and Version Control System

The optional Qualification and Version Control System (QVCS) lets users easily track and compare changes that are made to control strategies and user templates through Control Builder. It features a Version Control System Manager with a familiar Windows like interface for intuitive interaction with the application.

Peer Control Data Interface functions

Beginning in Experion R310, Control Builder offers a licensed option for a Peer Control Data Interface (PCDI) function to facilitate communications with Safety Manager or third-party devices that support the MODBUS TCP protocol. The PCDI function allows a C300 Controller to communicate directly with Safety Manager without requiring the Experion Server in the communications path. It uses the existing FTE network as the communications medium and has built in redundancy. Other features include:

Bi-directional data transfer,

Operational integration without common cause failures, and Fault reaction configuration per Safety Manager point.

2.13 Identical Build/Operate Environments

Build environment

With Control Builder, you build your control strategy by assembling a collection of related control modules.

(43)

Independent build capability

Control Builder can be run on an engineering Station for independent development, thereby allowing users to configure, load, and test control strategies without an Experion server.

The engineering Station can be used as a development-only node for developing and testing templates and control strategies independent of the target system.

Once developed, individual template strategies, or an entire database, can then be exported and subsequently imported to the ERDB on the target system.

Multiple user access

Control Builder can run simultaneously on up to four Experion Station nodes and other non-Experion server nodes in a ControlNet system or up to twelve in a Fault Tolerant Ethernet system. Use of the Control Builder client allows simultaneous multi-user configuration, monitoring and debugging capabilities thereby improving plant productivity.

Up to four or twelve application engineers may configure control strategies in the same ERDB from multiple computers.

Up to four or twelve operators and maintenance engineers (with appropriate security levels) may access Control Building monitoring charts from separate Experion Stations.

Between two and four users in separate locations, such as an operator at a plant site and an engineer at a remote location, may be allowed simultaneous access of the same control strategy from different computers thereby facilitating debugging and troubleshooting.

Control Builder can run on any workstation connected to the server either by LAN, or WAN connection. In addition to this, an engineer using Control Builder may choose which server to use and switch servers at run time. It also features a secure logon function that lets you integrate Windows user account with Station operator-based account access.

Operate environment

When the process is running, the identical control module configuration forms used in engineering your control strategy can be used by anyone with access to monitor or run the process.

Of course, you may also build custom graphic displays to monitor the process but these displays can be supplemented with the control modules themselves. This is particularly useful for sequential operations where continuation conditions are frequently used by your operators to move the process along.

(44)

2.14 Safety Builder

Safety Builder is a powerful software package that runs on computers with a Microsoft Windows operating system. It provides a user interface with Safety Manager and supports the user in performing a number of design and maintenance tasks as illustrated in the following figure.

Figure 7 - Sample Safety Builder Function: Network Configurator

ATTENTION

Refer to the Experion specifications document for information about the operating systems specification on which the Safety Manager executes.

(45)

Network Configurator, Hardware Configurator, Point Configurator, Application Editor,

Database import and export,

Automatic control program documentation, FLD revision control, and

Easy loading of system software and control program into the Control Processors. Safety Builder's maintenance support features include:

Live viewing of Application execution, Detailed monitoring of process signal behavior,

Collection of diagnostics of Safety Manager, automatically or on user demand, Diagnostic message storage, with user-definable browsing functions, and Forcing of Safety Manager input and output interfaces.

2.15 OneWireless integration

Within Experion PKS, the wireless process I/O is considered identical to wired process I/O in terms of data, event, and alarm information view, access, and configuration. After integrating OneWireless with Experion, the OneWireless components such as Wireless Device Manager (WDM), Field Device Access Point (FDAP), Multinode, and the field devices become a part of the Experion system. The best approach for

deploying OneWireless Network infrastructure is to place it on the dedicated subnet routed to the rest of the PCN.

(46)

Figure 8 Experion OneWireless integration topology For more information about integrating OneWireless with Experion, refer to the

(47)

2.16 Functional Logic Diagrams (FLDs)

Safety Manager safety-critical control functions (contained in the control program) are determined by the safety instrumented functions assigned to the system for the specific application. Safety Builder supports the design of the control program by the user. The control functions are defined through graphical Functional Logic Diagrams (IEC 61131-3: Continuous Function Charts). The following figure shows an example of a Functional Logic Diagram (FLD).

Figure 9 - Sample Functional Logic Diagram (FLD) An FLD is split into four main areas:

Information area (bottom) (on hardcopy only), Input area (left),

(48)

Output area (right).

The FLD information area, at the bottom of the FLD, is included on printouts, and provides information to identify the Functional Logic Diagram, including revision data. The FLD input area, on the left-hand side of the FLD, contains all the variables that serve as the input to the control function. Input variables may originate from the field equipment or from other computer equipment (Experion server, Safety Manager). Special input functions are provided for:

Diagnostic status of the Safety Manager IO interfaces, Status of field loops, and

System alarm summary, e.g. temperature pre-alarm or device communication failure.

Data can be exchanged between FLDs through sheet transfer functions. This allows a structured design of complex functions across multiple diagrams.

The table below lists the input functions that are available in Safety Manager functional logic diagrams, together with their source.

Input Type Source

Analog Input Field Equipment

Boolean Input Field Equipment, Process Computer, Other Safety Manager.

Numerical Input Field Equipment, Process Computer, Other Safety Manager.

Diagnostic Input Diagnostic status of Safety Manager safe IO interfaces Loop Status Input Field loop status of Safety Manager IO interfaces with

loop monitoring

System Alarm Input Safety Manager controller Sheet Transfer Other FLDs

The FLD control function area, which is the central area of the FLD, contains the actual implementation of the control function. The function is realized by

interconnecting predefined symbols, which provide a variety of functions including logical, numerical and time-related functions.

Apart from these standard functions, user-definable blocks are supported:

(49)

Equation Blocks for tabular definition of complex functions. For example, non-linear equations.

The following table lists the control functions that are available in Safety Manager functional logic diagrams.

Function Description

Data type conversion functions

INT SINT DINT INT, SINT REAL DINT, INT, SINT

Boolean functions Boolean Constant, AND, OR, XOR, NOT, NAND, NOR, XNOR, flip-flop set and reset dominant

Arithmetical functions Numerical Constant, AND filter, ADD, SUB, MUL, DIV, SQR, SQRT, ln(x), ex

Comparison functions EQ, NEQ, GT, GTE, LT, LTE Timer functions (with

constant or variable time value)

Pulse, Pulse-retriggerable, Delayed-ON, Delayed-OFF, Delayed-ON memorize

Count and storage functions

Counter, Register User-definable blocks Equation Block

Function Block

The supported data types are: Boolean, ShortInt 127 .. +128) Integer (-32767...32768), LongInt and Real (-1038...1038).

The FLD output area, on the right-hand side of the FLD, contains the results of the control function. These variables may be used to drive the field equipment or may be transferred to other computer equipment. For example, a process computer or another Safety Manager.

The following table lists the output functions that are available in Safety manager functional logic diagrams, together with their destination.

Output Type Destination

Analog Output Field Equipment

(50)

Output Type Destination Manager.

Numerical Output Field Equipment, Process Computer, Other Safety Manager.

Sheet Transfer Other FLDs Timer functions (with

constant or variable time value)

Pulse, Pulse-retriggerable, Delayed-ON, Delayed-OFF, Delayed-ON memorize

Count and storage

functions Counter, Register

User-definable blocks Equation Block Function Block

2.17 Custom Display Building

HMIWeb Display Builder

You use HMIWeb Display Builder to create your own (custom) displays.

HMIWeb Display Builder is supplied with a set of shape libraries that cover a range of industries.

You can also insert your own graphics, such as photographs and layout diagrams, using any of the following formats.

GIF (*.gif)

Windows Bitmap (*.bmp) JPEG (*.jpg)

Metafile (*.wmf)

Portable Network Graphic (*.png)

The following figure shows a typical custom display created using HMIWeb Display Builder.

(51)

Figure 10 - Typical custom display Display scripts

Experion provides many native functions that minimize the need to write complex scripts to accomplish appropriate visualization of process conditions in custom displays. However, if the standard functionality does not provide the needed animation or capability, then a powerful display scripting subsystem is available to supplement the native functionality.

2.18 Online Documentation

Knowledge Builder

The online user documentation supplied with Experion is called the Knowledge Builder. It is created using the familiar HTML language. This permits the support information to be transmitted and searched over the Internet, Intranet, and yes, even your facility's standard information network. A unique feature of the Knowledge

(52)

Builder is that, while it utilizes common World-Wide-Web based technologies, we have removed the need for a web or Intranet server.

This permits your entire facility the option of accessing one central repository of Experion support information, eliminating or minimizing the need to manage and update multiple book sets.

KB mode

Knowledge Builder (KB) can be installed in the following modes.

Server mode - The KB server only contains booksets and installs the booksets locally. The path where the KB booksets are installed is referenced in the following scenarios.

The path is referenced by the KB installed in client mode.

The path is the default KB server path in case you do not provide the KB server path during KB client installation.

Client mode - The KB client contains tools (KB.exe and KB backup and restore utility) and installed them on the local computer.

Full mode - The KB full mode contains both KB server and client components. The selected booksets and KB tools are installed on the same local computer.

Internet-awareness

Honeywell will be providing documentation and training, including updates, over the Internet to minimize your cost and maximize the expediency of their delivery. We expect you will also find ways to leverage the power of the Internet to build efficiencies into the way that you engineer and operate Experion systems.

2.19 Internationalization

Most major processing companies today operate on a global basis. Everyone involved in the life cycle of a control application (engineers, operators, technicians, electricians, managers, and so on) is more efficient if they are able to carry out their tasks in their native language. Experion provides a built-in capability for Honeywell regional offices to present the system in their local, native language.

References

Related documents

While there is overwhelming in vitro evidence to support the theory that VEGFA and its receptors, FLT1, KDR, and NRP1, are critical for sex-specific vascular development which

If it is the key that is stored in the online, then the systems permit delivery of encrypted data to recipients’ desktops, with a required multi-step recipient

In order to become transmissible, a cancer must acquire adaptations both to support the physical transmission of living cancer cells between hosts, and to escape

Identifying Orion Console components 12 Unpacking the Experion Orion Console 13 Placing the Experion Orion Console into position 18 Attaching the work surface to the Experion

Helpful high school courses are: Math, English, Speech, Computer Science, Accounting, and

Oblique view of the stifle in a foal aged 6 months, showing a wide dip in the bone surface in the proximal third of the lateral Trochlear ridge of the distal femora ( white

(b) The contractor shall not comply with any order, direction or request of government personnel unless it is issued in writing and signed by the Contracting Officer, or is pursuant

Systems”, IEEE Power and Energy Society General Meeting 2010, paper ID:001550,.