Honeywell Experion LX User manual

Experion LX
Station Planning Guide
EXDOC-X128-en-500A
April 2017
Release 500

Disclaimer
This document contains Honeywell proprietary information. 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 Sàrl.
While this information is presented in good faith and believed to be accurate, Honeywell
disclaims the implied warranties of merchantability and fitness for a 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 direct, special, or consequential damages.
The information and specifications in this document are subject to change without notice.
Copyright 2017 - Honeywell International Sàrl

Contents
Contents 3
About this guide 8
Enterprise models 9
About enterprise models 9
About asset models 9
About assignable assets and scope of responsibility 10
About system models 11
About generic displays 12
Guidelines for designing enterprise models 13
Guidelines for designing asset models 13
Guidelines for defining scope of responsibility 14
Naming rules for assets 17
Guidelines for determining the optimal topology for your plant 18
Example enterprise models and topologies 19
An asset model for a simple system 19
Implementing an enterprise model 20
Servers 22
Server redundancy 22
Distributed System Architecture 25
Inter-release support 25
DSA and firewalls 26
About point data in a DSA system 26
eServer 27
PHD 28
Remote Engineering and Station Server 29
Server scripts 30
Naming rules for computers 31
Servers and the Enterprise Model Database 33
ESM Server 33
Networks 34
Network redundancy 35
Contents
Honeywell 2017 3

Fault Tolerant Ethernet (FTE) 35
Process controllers 35
Time synchronization 36
Experion time requirements 36
About time protocols 39
Planning your time hierarchy 40
Planning considerations for time synchronization 43
Stations 45
Identifying user types and assessing their needs 45
Connection options for Flex Stations 46
About Console Stations 46
Mobility 47
Station update rates 48
Specialized Station hardware 49
Determining your Station requirements (an example) 49
Printers 51
Controllers 52
Interface references 52
Monitoring and control strategies 52
Connection options 53
Network connections 53
Direct serial connections 53
Indirect serial (terminal server) connections 54
Modems 56
Specialized links 56
Points 57
Point naming conventions 57
Point IDs and Distributed System Architecture (DSA) 60
Standard point types 60
Container points 62
System interfaces 62
Algorithms 63
History collection 63
Periodic history 64
Contents
Honeywell 2017 4

Exception history 64
Offset groups 65
Storage requirements for history samples 65
Archiving history samples 66
Groups 67
Trends 67
Scanning strategy 68
Basic principles of scanning 69
Scanning techniques 69
Scan optimization 70
Estimating the number of points required 71
System Status Network tree 72
About the System Status Network tree 72
About System Event Server and System Performance Server 73
Identifying a network topology 74
Workgroup topology 74
Domain with no Organizational Units (OUs) 75
Domain with Organizational Units (OUs) 77
Multiple domains or multiple workgroups 78
SES event notification behavior 79
Network tree planning summary 79
Alarms and events 82
Planning and designing your alarm system 83
Honeywell products that support effective alarm strategies 84
Factors that contribute to excessive alarms 85
Dealing with excessive alarms 85
Dynamic Alarm Suppression 88
Planning and application guidelines for Dynamic Alarm Suppression 89
Alarm and alert shelving 90
What happens when a shelved alarm is suppressed? 91
Alarm prioritization 92
Alarm annunciation 94
Station-based buzzer or speaker 94
External horn or siren 95
Contents
Honeywell 2017 5

Alarm groups 95
Alarm trackers 95
Alerts 96
Messages 97
Events 98
Displays 99
System displays 99
Tabbed displays 99
Custom displays 100
Custom display features and considerations 101
Custom faceplates 101
Display scripts 102
Display design 103
Display security 103
Acronyms 103
Web pages and other documents 104
Displays with linked documents 104
Reports 105
Standard report types 105
Integrated Microsoft Excel reports 107
Free Format reports 107
Output options 108
Specialized features 109
Recipes 109
Point requirements in recipes 109
Point control schedules 110
Honeywell Digital Video Manager 110
Exchanging data with other applications 112
Microsoft Excel Data Exchange 112
ODBC Data Exchange 113
OPC 113
Experion OPC Client Interface 113
Experion OPC Advanced Client 113
Experion OPC Display Data Client 115
Contents
Honeywell 2017 6

Experion OPC Server 115
Experion OPC Historical Data Access Server 116
Experion OPC Alarm and Event Server 116
Experion OPC Integrator 117
Creating custom applications 121
Installation and commissioning tasks 122
Installation and configuration tasks 122
Configuration tools 124
Configuration Studio 124
Enterprise Model Builder 124
Alarm Suppression display 124
Quick Builder 125
Control Builder 125
System displays 125
HMIWeb Display Builder 125
Experion server utilities 126
Station 127
Special-purpose utilities 127
Notices 128
Contents
Honeywell 2017 7

About this guide
This guide contains high-level planning and design topics for Experion servers and clients, as
well as for controllers other than Process Controllers.
Revision history
Revision Date Description
A April 2017 Initial release of document.
Related documents
The following documents complement this guide. You should read them before you start
detailed planning and design tasks.
Document Description
Network and
Security
Planning Guide
Contains networking, security, and systems integration information applicable
to Experion.
Control
Hardware
Planning Guide
Contains planning and design topics applicable to Process Controllers.
Overview Provides a comprehensive overview of Experion, including basic concepts and
terminology.
Software
Change Notice
(SCN)
Contains last-minute information that was not able to be included in the
standard documents. It may include important details that could affect your
planning or design decisions.
About this guide
Honeywell 2017 8

Enterprise models
The section provides an introduction to enterprise models. Enterprise models provide
structure to support:
nOrganizing your system.
nStructuring your view of alarms.
nDefining the scope of user views and control rights.
This section also includes guidelines for designing enterprise models, as well as examples that
illustrate 'best practice' design principles.
About enterprise models
An enterprise model provides a means of organizing your system around key entities in your
enterprise, such as plant equipment.
An enterprise model provides:
nA hierarchical structure that makes it easier for users to navigate their way through your
system.
nA simple and intuitive means of implementing scope of responsibility—that is,
systematically managing the access rights of operators (or Stations) to various parts of
your system.
nThe mechanism to enable and disable alarming for selected equipment.
An enterprise model is a framework that includes a set of specialized models, such as the asset
and system models, each of which represents one aspect of your system.
About asset models
An asset model forms the core of an enterprise model: it is a hierarchical representation of
your assets, similar to the one shown in the figure below.
An asset represents a particular physical item, such as a piece of plant equipment, a
production line or a building.
Enterprise models
Honeywell 2017 9

A typical asset model
Raw Materials *
Ball Mill
Rod Mill
Digestion *
Train 1
Digestor
Flash Vessel 1
Flash Vessel 2
Train 2
Precipitation *
Thickeners *
Thickener 1
Thickener 2
Train 1
Precipitator 1
Agitator
Cyclone
Train 2
Precipitator 2
About assignable assets and scope of responsibility
An asset model is not just a logical representation of your physical assets and how they relate
to each other. It also provides a framework for defining scope of responsibility (SOR)—that
is, assigning specific assets to specific operators (or Stations).
An asset that you can assign to an operator (or Station) is called an assignableasset. By
default, all top level assets in your asset model are assignable assets. If appropriate, you can
also define assets at other levels as assignable assets.
When you give an operator (or Station) access to an assignable asset, you also give access to
its child assets (except those which have been defined as assignable assets).
If an asset is changed from non-assignable to assignable, any scope of responsibility that was
previously inherited is cleared. As a result, control of this asset is temporarily lost until the
asset is included in the operator's or Station's scope of responsibility.
Enterprise models
Honeywell 2017 10