Experion ACE Specification

EP03-310-310
Release 310
January 2009, Version 2
Experion ACE Specification, EP03-310-310, V. 2, January 09 2

Table of Contents
1. Product Introduction..................................................................................................... 3
1.1. Experion System.............................................................................................................. 3
1.2. Architecture Overview...................................................................................................... 3
1.3. Experion Controller Overview .......................................................................................... 3
2. ACE Specifications ...................................................................................................... 4
2.1. R310 Sizing ..................................................................................................................... 4
2.2. Supported Function Blocks .............................................................................................. 4
2.3. ACE Configuration Options.............................................................................................. 5
2.4. ACE Communication Performance .................................................................................. 5
2.5. ACE Control Processing Performance............................................................................. 6
2.6. ACE Memory Resources ................................................................................................. 6
2.7. ACE CEE Processing and Memory Models ..................................................................... 7
2.8. ACE Notifications............................................................................................................. 8
2.9. OPC Gateway Communication Performance................................................................... 8
2.10. Inter-Cluster Gateway...................................................................................................... 9
3. ACE-T Specifications................................................................................................. 11
3.1. ACE-T Configuration Options ........................................................................................ 11
3.2. ACE-T Control Processing............................................................................................. 11
3.3. ACE-T TPN Server Group Writes .................................................................................. 12
4. Topologies ................................................................................................................. 13
4.1. ACE OPC Gateway Topologies ..................................................................................... 13
4.2. Inter-Cluster Gateway.................................................................................................... 14
5. ACE Software Model Numbers.................................................................................. 15
6. Glossary..................................................................................................................... 16

Revision History

Revision Date Description

1 January 2008 Release publication

2 January 2009 Updated for R310.3

Honeywell Confidential
Experion ACE Specification, EP03-310-310, V. 2, January 09 3

1. Product Introduction

1.1. Experion System

The Experion Process Knowledge System (PKS) is Honeywell’s unified control system for process, business, and asset
management that helps industrial manufacturers increase their profitability and productivity. Experion takes customers
well beyond distributed control system (DCS) functionality with an advanced automation platform solution and innovative
application integration to improve business performance and peace of mind.

Refer to the “Experion CEE-based Controllers and I/O Overview” (document number EP03-290-310) for prerequisite
information. This document is written with the expectation that the reader understands the information and concepts
covered in the overview document.

1.2. Architecture Overview

The Experion platform comprises many different integrated hardware and software solutions depending upon the needs
of the application. This pictured architecture is a representation of many of the possible nodes that can be utilized in the
Experion architecture. Note that the architecture is highly scalable and not all nodes are necessary or required.

1.3. Experion Controller Overview

Honeywell offers multiple Experion controllers, ranging from embedded controller platforms with dedicated IO hardware
to PC based control environments for supervisory control tasks or simulation. They all support one or more different
network types to integrate the controllers with the Experion Server. They share a common Control Execution
Environment (CEE) software infrastructure and a common builder tool. Together with the different station types, they
form the Experion system. This specifications document provides details specifically related to the Application Control
Environment (ACE).

Figure 1. Sample Experion Architecture

Honeywell Confidential
Experion ACE Specification, EP03-310-310, V. 2, January 09 4

2. ACE Specifications

2.1. R310 Sizing

Functional Area Capacity Description R310 Capacity
ACE Number of ACEs/Server Cluster 7 (FTE)
2 (ControlNet)

2.2. Supported Function Blocks

Function Block (FB) Types Supported in all CEE-based Controllers.

General Purpose (Utility)
Flag Numeric Text array
Type Convert Block Numeric array Timer
Push Flag array Operator message
PV Algorithms (Auxiliary)
General Linearization Totalizer PV Calculator
Flow compensation Dead Time Lead / Lag
Signal Selector Enhanced PV Calculator Summer
PV handling
Data Acquisition
Regulatory Control Algorithms
Profit Loop Fanout Block (1 input/up to 8 Ratio Bias
Proportional, Integral, Derivative (PID) outputs) Ramp / Soak
PID with Feed forward Inter cluster cascade support Positional Proportional
PID with External reset Regulatory Calculator Pulse Length
Override Selector (4 inputs) Enhanced Regulatory Pulse Count
Auto Manual Calculator Regulatory Control Summer
Switch (8 input single pole) Ratio Control Remote Cascade support
Device Control Custom Block T^ypes
DEVCTL (multi input, multi output, multi state) Custom Data Block
Discrete Logic (per IEC 1131 standard)
2oo3 (2-out-of-3 Voting) MIN (Minimum) QOR (Qualified OR)
AND MINPULSE (Minimum Time ROL (Rotate Left)
CHECKBAD Limit Pulse) ROR (Rotate Right)
CHECKBOOL MUX (8-Input Multiplexer) RS (Reset-Dominant Flip-Flop)
DELAY MUXREAL (8-Input RTRIG (Rising-Edged Trigger)
EQ (Compare Equal) Multiplexer, Real Number) SEL (Selector Function)
FTRIG (Falling-Edged Trigger) MVOTE (Majority Vote) SELREAL (Selector Function, Real
GE (Compare Greater Than or Equal) NAND Number)
GT (Compare Greater Than) NE (Compare Not Equal) SHL (Shift Left)
LE (Less Than or Equal) nOON (n-out-of-N Voting) SHR (Shift Right)
LIMIT NOR SR (Set-Dominant Flip-Flop)
LT (Compare Less Than) NOT STARTSIGNAL
MAX (Maximum) OFFDELAY TRIG (Change Detect Trigger)
MAXPULSE (Maximum Time Limit ONDELAY WATCHDOG
Pulse) OR XOR (Exclusive OR)
PULSE (Fixed Pulse Output)
Sequential Control Functions (in line with the ISA S88.01 standard)
Step Synchronize
Transition Handler: Main, Interrupt, Check, Restart, Hold, Stop,
Abort
Container Block Types
Control Module Unit Control Module
Sequential Control Module Recipe Control Module

Function BlockTypes Only Supported by the ACE CEE

Gateways
OPC Gateway through the optional OPC Extension Inter Cluster Gateway
library
Interface Block Types
HIWAY output (optional) UCN output (optional)
Custom Block Types
Custom Algorithm Block Phase block

Honeywell Confidential
Experion ACE Specification, EP03-310-310, V. 2, January 09 5

2.3. ACE Configuration Options

ACE Configuration Options

Base Execution Periods Supported 500 ms
Configurable Values for CM/SCM Execution Periods 500 ms. & 1, 2, 5, 10, 20 sec.
Additional options for CMs only:
30, 40 sec.
1, 2, 5, 10, 20, 30 min.
1, 2, 4, 8, 12, 24 hr.
NOPERIOD
Configurable Values of Peer Update Rates (period). 500 ms. & 1, 2, 5, 10 sec.
Defines the period at which data is updated for all ‘pull/get’
requests for peer data required by all blocks within a CEE.

2.4. ACE Communication Performance

ACE Communications Performance
Definitions: ACE
PPS = Average Parameters Per Second
PPM = Average Parameters Per Minute
EPS = Average Array Elements Per Second
Overall Data Access Performance 500 ms CEE
Maximum Total Parameter Access Response Rate 3000 PPS
(Includes all Server Data Requests, Console Station Data Requests, and peer
communications including other ACEs, C200s, C300s, SIM-C200s, SIM-ACEs,
and FIMs)
Display Data Access Capacity 500 ms CEE
Maximum Total Subscribed Parameters per ACE 6000
(Includes all Server Data Requests + Console Station Data Requests)

Request/Response Data Access Performance 500 ms CEE

Max Request/Response Parameter Access Rate 3000 PPM Read
(Includes all Slow Server Data Requests, e.g. Greater than 10 sec OPC data, 1500 PPM Write
Slow History, Data Writes, etc.)
Peer-to-Peer Performance 500 ms CEE
Maximum Initiator Pull/Get Request Rate to all target nodes. (incoming data) 1000 PPS
Maximum Target Response Rate to Pull/Get Requests from all initiator nodes. 1000 PPS
(outgoing data)
Peer-to-Peer Subscription Capacity / Update Rate ControlNet or FTE1
Maximum ACE peer capacity per update rate choices: 500 @ 500 ms
1000 @ 1 sec
2000 @ 2 sec
5000 @ 5 sec
10000 @ 10 sec
Push/Store Request Performance 500 ms CEE
Maximum Push/Store Request Rate to all target nodes 3 50 PPS
Maximum Response Rate to Push/Store Requests from all initiator nodes 50 PPS
ACE to OPC Gateway Peer Performance 500 ms CEE
Maximum Initiator OPC Pull/Get Request Rate (to all target OPC Gateways) 2000 PPS
Maximum Initiator OPC Push/Store Request Rate (to all target OPC Gateways) 500 PPS
Peer-to-Peer Capacity 500 ms CEE
Peer Connection Units (PCUs) 30
(Remote CEEs that this ACE can initiate a peer connection with, includes total of
remote ACEs, SIM-ACEs, C200s, C300s, SIM-C200s, and/or Primary FIMs)
Whole Array Capacity 500 ms CEE
Max Array Size for Whole Array Transfer 8K bytes
(1000 float64s)
Initiator’s Max Whole Array Connection References 25
Responder’s Max Whole Array Connections (from all peers using pub-sub) 25
Initiator’s Max Whole Array Connection References (to all peers using 5
request/response)

Honeywell Confidential
Experion ACE Specification, EP03-310-310, V. 2, January 09 6

Responder’s Max Whole Array Connections (to all peers using 5

request/response)
Overall Array Transfer Response Performance 500 ms CEE
Whole Array Response Rate (EPS) 4000 EPS
(Includes all Peers and Displays – when supported) This is in addition to the
Parameters Per Second specification.
Note 1: ACE is not supported on CIP Ethernet based cluster.
Note 2: See Section OPC Servers that can be accessed by the ACE.
Note 3: Currently the SCM Step and the PUSH Block are the only block types that can initiate peer
push/store requests for CEE-to-CEE peer communications.

2.5. ACE Control Processing Performance

ACE Processing Resources

Minimum Reserved CPU to be Maintained During Runtime 40%1
CEE Configuration PU Maximum Maximum Cycle Loading2
500 ms CEE – Non-Redundant Configuration 100,000 PU/sec 60%
Definitions:
PU = Processing Unit. The PU represents a platform independent amount of processing resources (time) required
to complete a predefined amount of computational (control) work.

Note 1 – CPUFREEAVG is not supported on ACE; CPU Usage from Windows Task Manager provides the %CPU
used
Note 2 – Maximum Cycle Loading: Over a cycle (0-39), the “Average CPU Used” (CPUCYCLEAVG1) statistic is
not to exceed the stated maximums.

2.6. ACE Memory Resources

ACE Memory Resources and Block Configuration

Maximum Available ACE CEE Memory Resources 128,000 MU
Maximum Total Number of CMs, SCMs, RCMs Configurable per ACE CEE 4095
Maximum Number of Component Blocks per CM 100
Maximum Total Number of Steps and Transitions 400
(in all handlers) per SCM
Maximum number of parallel paths executing in SCM simultaneously 10
Definition: MU = Memory Unit = 1 Kbytes = 1024 bytes

Honeywell Confidential
Experion ACE Specification, EP03-310-310, V. 2, January 09 7

2.7. ACE CEE Processing and Memory Models

Typical Processing and Memory Resource Capacities

Typical Module Types Processing Resource Memory
1
(FB Content in Parenthesis) Consumption Resource
(Per Module) Usage
500 ms. ACE CEE 500 ms. ACE
(PU/Module Execution) (MU/Mod)
Analog Digital Acquisition Module 3.4 7.3
(10 Numerics, 10 DataAcq FBs)
Small Analog Data Acquisition Module 0.6 1.0
(1 Numeric, 1 DataAcq FB)
Regulatory Control Module 3.2 3.9
4
(1 Numeric, 1 DataAcq, 1 PID , 6 Logic FBs)
Auxiliary Function Module 0.7 6.4
(10 Aux. FBs, such as AuxCalc, Totalizer)
Digital Data Acquisition Module N/A for ACE 2.0
(10 DI, 10 Flag FBs)
Small Digital Data Acquisition Module N/A for ACE 0.5
(1 DI, 1 Flag FBs)
Device Control Module 0.8 2.5
(4 Flags, 1 DevCtl, 5 Logic FBs)
Logic Control Module 1.3 3.9
(20 Logic FBs)
Sequence Control Module A 2.5 27.9
(1 each of Main, Hold, Stop and Abort Handlers, 10 Steps with 8 Outputs
each, 10 Transitions with 5 Conditions each, 10 Recipe items, 5 History
items)
SCM has total of 10 Steps and 10 Transitions among the 4 Handlers
Sequence Control Module B 3.0 35.7
(1 Main Handler, no other Handlers, 20 Steps with 4 Outputs each, 20
Transitions with 3 Conditions each, 10 Recipe items, 5 History items) ;
SCM has total of 20 Steps and 20 Transitions
Sequence Control Module with an alias table of size 45 rows by 100 3.0 128.5
columns
(1 each of Main, Hold, Stop and Abort Handlers, 10 Steps with 8 Outputs
each, 10 Transitions with 5 Conditions each interspersed in all the
handlers, 10 Recipe items, 5 History items)
SCM has total of 10 Steps and 10 Transitions among the 4 Handlers
Sequence Control Module with an alias table of size 500 rows by 9 3.0 124.5
columns
(1 each of Main, Hold, Stop and Abort Handlers, 10 Steps with 8 Outputs
each, 10 Transitions with 5 Conditions each interspersed in all the
handlers, 10 Recipe items, 5 History items)
SCM has total of 10 Steps and 10 Transitions among the 4 Handlers
Recipe Control Module A 0.7 10.5
(1 each of Main, Hold, Stop and Abort Handlers; each handler has 1
Invoke transition with 5 Conditions. Main Handler contains 1 Step with 8
outputs, 4 Synch blocks, and 2 Transition blocks with 1 Condition each,
and 10 Phase blocks with 25 Formula parameters and 25 Report
parameters each.) ; The RCM executes 5 Phases in parallel.
Recipe Control Module B 2.7 19.3
(1 each of Main, Hold, Stop and Abort Handlers; each handler has 1
Invoke transition with 5 Conditions. Main Handler contains 1 Step with 8
outputs, 4 Synch blocks, and 2 Transition blocks with 1 Condition each,
and 10 Phase blocks with 25 Formula parameters and 50 Report
parameters each.) The RCM executes 5 Phases in parallel.
2
Medium sized CDB Module 0 1.5
(CM with 1 medium sized CDB instance). 1.0 3
CDB instance has a total of 15 Custom Data Parameters of which 2 are
arrays: 5 32 char. STRING; 4 scalar FLOAT64; 4 scalar BOOLEAN; 1
20 element FLOAT64 array; 1 20 element BOOLEAN array.
Note 1 – Total Processing Resources (PU/sec) per module are computed as = Processing Resource Consumption
(PU/module execution) / Execution Period (sec/module execution).
Note 2 – Memory usage for first module instance.
Note 3 – Memory usage for every subsequent module instance.
Note 4 – For PID-PL use 1.4 X the PU and values listed here.

Honeywell Confidential
Experion ACE Specification, EP03-310-310, V. 2, January 09 8

2.8. ACE Notifications

ACE Notifications Performance

Maximum number of events (burst condition)1 10 events/sec

2
Maximum number of events/second (sustained) 2/sec
Note 1 – This is the rate per second that is throttled at the Controllers.
Note 2 – This is the “tested” sustained rate from controllers. This rate X 16-20 event
producers will be just under the limit for overloading the notification subsystem
in the Server.

2.9. OPC Gateway Communication Performance

OPCG Communications Performance

OPCG
Configurable Values for OPC Subscription (Read) Rate (period) per OPCG 1, 2, 5, 10, 15, 30 sec
Number of OPC Gateways resident/loaded per ACE Computer Platform 151
Number of OPC Gateways per Cluster 30
Number of CDA Peer Connections per OPCG 302
Maximum connected OPC Servers per OPCG 1
OPC Gateway Client Performance
OPCG Client Read Rate in items/second Limited by:
Publish rate of the OPC
Server that this OPCG is
connected to.
CDA publish rate per OPC Gateway to all subscribing ACEs in Parameters Per 2000
Second (PPS)
OPCG Client Write/Store Rate (items/second) Limited by:
The OPC Server that this
OPCG is connected to.
CDA store rate per CDA connection to this OPC Gateway in Parameters per 503
Second (PPS)

Definition: PPS = Average Parameters Per Second

Note 1 – TPS connected ACE (ACE-T) is further constrained for number of OPCGs supported. See ACE-T
Configuration Options for details.
Note 2 – Since only ACEs can connect to the OPC Gateway, and there can only be 7 ACEs/Cluster, only 7
connections can be used.
Note 3 – Limited by the per ACE store rate limit

Honeywell Confidential
Experion ACE Specification, EP03-310-310, V. 2, January 09 9

2.10. Inter-Cluster Gateway

ICG Communications Performance

Inter-Cluster Gateway Performance ICG

Number of ICGs supported on a single ACE Computer Platform 1
Number of ICGs allowed per Cluster 71
ICG OPC Server support
Number of Peer CDA connections per ICG Server2 30
Maximum number of OPC connections allowed from all OPCG clients + ICG 14
clients per ICG Server
Maximum number of CDA parameters per ICG Server that can be subscribed to 12000
from all peer CEEs3
Maximum CDA receive rate from all CEEs subscribed to by an ICG Server in PPS 2500
OPC groups and items
Maximum number of OPC groups supported Only limited by CPU &
Memory
Maximum number of items per group supported Only limited by
ACE/CDA peer
subscription size limits
Total number of items supported across all groups Only limited by
ACE/CDA peer
subscription size limits
Group update rates supported Same as ACE supported
CDA subscription rates:
250 @ 500 ms
500 @ 1 sec
1000 @ 2 sec
2500 @ 5 sec
5000 @ 10 sec
ICG OPC Client support
Number of peer CDA connections per ICG Client4 30
5
Number of ICG Servers per ICG Client 1
ICG Client Read Rate (items/second) Limited by the Publish
rate of the ICG Server
that this ICG Client is
connected to
Maximum CDA publish rate from an ICG Client to all subscribing ACE in PPS 2000
ICG Client Write/Store Rate (items/second) Limited by the ICG
Server that this ICG
Client is connected to
CDA store rate per CDA connection to this ICG Client in PPS 506
Definition: PPS = Average Parameters Per Second
Note 1 – Only limited by the number of ACEs supported per Server
Note 2 – The total number of CEEs (C200s, C300s, ACEs, FIMs, etc.) that this ICG can collect parameters from to
send to other Clusters.
Note 3 – This is the total number of parameters that a single ICG Server can collect from this Cluster and publish to
all OPCGs and ICG Clients connected to it from other Clusters
Note 4 – Since only ACEs can connect to the ICG Client, and with the 7 ACEs/Cluster limit, only 7 connections have
been tested
Note 5 – This means that the ICG can only connect as a client to one other ICG Server

Honeywell Confidential
Experion ACE Specification, EP03-310-310, V. 2, January 09 10

ICG Communications Performance

Note 6 – Limited by the ACE store rate limit.

Honeywell Confidential
Experion ACE Specification, EP03-310-310, V. 2, January 09 11

3. ACE-T Specifications

The specifications in this section are specific to ACE-T, an ACE with an LCNP4 providing a direct LCN connection.

3.1. ACE-T Configuration Options

ACE-T Configuration Options

Maximum Number of OPC Gateways 3
Recommended Number of OPC Gateways 1 2
Note 1 – Two OPC Gateways are recommended to minimize the number of clients to the local TPN
Server, which will reduce the number of data access transactions through TPN Server as
compared to having three OPC Gateways. This way two different OPC Gateway Subscription
Periods can be selected, which establish the rates at which data is fetched from TPS
components.

3.2. ACE-T Control Processing

The term “LCN Control Cascade” refers to a Regulatory Control (RegCtl) strategy that utilizes a HiwayOut or UcnOut
function block in the ACE-T for interfacing an Experion RegCtl block to a TPS RegCtl point. The Level 1 controller
RegCtl block is normally in a Data Hiway controller or UCN controller.

ACE-T Control Processing

Maximum values per second from LCN 1600
Fastest LCN Control Cascade (Execution Period of CM) 5 sec 1
Maximum Number of Fast LCN Control Cascades 120
(CM Execution Periods of 5, 10, and 20 sec)
Maximum Number of Slow LCN Control Cascades 120
(CM Execution Periods of 30 sec and slower)
Minimum Shedtime for Level 1 controller RegCtl point (in Hiway or UCN ACE-T CM Execution Period + 5 sec
controller) of LCN Control Cascade
Maximum non-Control Cascade Push/Store Request Rate to the LCN 20 PPS
(from CAB, Push, and SCM blocks)
Note 1 – An LCN Control Cascade between ACE-T and a Hiway/UCN controller executing any faster than a 5
sec period in ACE-T is not realistic for reliable control, given the multiple communication layers in
existence between the ACE-T and the ultimate IO connections to the process.

The following configurations and control capacities have been qualified for ACE-T.

Qualified Configuration, 2 OPC Gateways

OPC Gateways Quantity 2
Subscription Periods 1 and 15 sec
Control Cascades Quantity Execution Shed Time OPC Gateway
Period Assignment
(Seconds)
120 1 sec 10 sec 1 sec
60 30 sec 35 sec 15 sec
60 60 sec 65 sec 15 sec
Non-control (push blocks) 20 per second

Honeywell Confidential
Experion ACE Specification, EP03-310-310, V. 2, January 09 12

Qualified Configuration, 3 OPC Gateways

OPC Gateways Quantity 3
Subscription Periods 1, 5 and 15 sec
Control Cascades Quantity Execution Shed Time OPC Gateway
Period Assignment
120 5 sec 10 sec 1 sec
60 30 sec 35 sec 15 sec
60 60 sec 65 sec 30 sec
Non-control (push blocks) 20 per second

3.3. ACE-T TPN Server Group Writes

The ACE-T LCNP card has a limited number of LCN data access servers available for the TPN Server to use, which
limits the number of group writes to LCN transactions that the TPN Server can perform.

Users can minimize and optimize the number of TPN Server group writes by phasing the ACE-T strategies (CMs/SCMs)
that store data to the LCN and/or lower level TPS components. ACE-T strategies can be phased across 0…119 half-
second execution cycles using the CM/SCM PHASE configuration parameter. The guideline for ACE-T phasing includes
consolidating the stores to LCN (through the local OPC Gateways) as much as practically possible. At a minimum, the
default value of PHASE (-1) should be overridden with a specific phase number to avoid the automatic load balancing of
CMs/SCMs, which may result in writes executed every half-second, potentially overloading the TPN server. A major
consideration for how many stores to group together is the subsequent impact on the underlying LCN, HG, NIM, and
ultimate data owners. The ACE-T phasing should be set up to achieve an agreeable compromise between TPN Server
capability and the capabilities of the TPS system components.

Honeywell Confidential
Experion ACE Specification, EP03-310-310, V. 2, January 09 13

4. Topologies

4.1. ACE OPC Gateway Topologies

4.1.1. OPC Gateway Block

The OPC Gateway Block is capable of communicating with any ACE node, which is part of the same Experion cluster,
on one side and with an OPC server on the other side. This creates a gateway interface between the Experion control
systems and any OPC Data Access compliant servers.

The following diagrams (network not shown), describe a couple of configurations, the data paths, and what protocols
that are used for OPC Gateway usage by the ACE.

ACE

CEE

CDA

OPC DCOM
Gateway OPCS
Client

Resident OPC Gateway Client

ACE_2 ACE_1

CEE CEE

CDA CDA

OPC DCOM
Gateway OPCS
Client

Non-resident OPC Gateway Client

Honeywell Confidential
Experion ACE Specification, EP03-310-310, V. 2, January 09 14

4.2. Inter-Cluster Gateway

Experion R300 introduced a new ACE block type called the “Inter-Cluster Gateway Block” (ICG). This ICG block is used
to provide ACE to ACE peer-peer between nodes that reside in different clusters. The following topology diagrams and
configuration rules show how this function may be used.

Experion Cluster #1 Experion Cluster #2

ACE ACE

CEE CEE

CDA CDA

Inter- DCOM Inter-

Cluster Cluster
Gateway Gateway

Simple Inter-Cluster Gateway

Honeywell Confidential
Experion ACE Specification, EP03-310-310, V. 2, January 09 15

5. ACE Software Model Numbers

ACE software and function block libraries are subjected to licensing. The license always applies to the Experion Server
that the ACE Server connects to. Licenses are not transferred between servers. There are two types of licenses:

A – A fixed number of instances can be loaded or used on the system, regardless of controller assignment,
B – The function block library or feature is enabled; the number of instances of a function block does not matter.

Model Number Description License Type

TC-SWSC011,2 ACE Base Software License A
TC-OPCL013 OPC Extension Library (OPC Gateway) B
3
TC-UCNL01 UCN Output Extension Library B
3
TC-HWIL01 Hiway Output Extension Library B
4
TC-CADL01 CAB Developer License A
5
EP-ACETPS ACE TPS Enabler, per ACE Base Software License A
Note 1 – The ACE Base software requires a dedicated Windows 2003 Server PC.
Note 2 – The ACE Base software includes CAB runtime environment
Note 3 – These are additional options for the ACE Node. These require TC-SWSC01
Note 4 – To be able to create CAB types a minimum Experion PKS System needs to be available
consisting of at least an Experion server and engineering client. A SIM-ACE is recommended
for testing the CAB types during the development phase. The Experion server, ACE or SIM-
ACE and CAB developer license requiring each their own PC platform.
Note 5 – ACE-T is only supported on computer platforms provided by Honeywell, requires an LCNP4
processor and that the system be licensed for the OPC Extension Library.

Honeywell Confidential
Experion ACE Specification, EP03-310-310, V. 2, January 09 16

6. Glossary
Term or Acronym Description

ACE Application Control Environment. Experion controller node hosted on a server computer platform.
The ACE node is ideally suited for supervisory control solutions and integration with third party
control systems.
ACE-T Application Control Environment –TPS. This is a normal ACE node with the LCN connectivity
option.
AM Application Module.
C200 A specific type of Honeywell Process Controller
C300 A specific type of Honeywell Process Controller based on the series C form factor
CDA Control Data Access is the Experion system communication infrastructure and data access
interface schema that provides application integration with Experion system objects.
ControlNet Real-time control-layer network.
ES-C Experion Station – Console
ES-CE Experion Station – Console Extension
ES-F Experion Station –Flex

ES-T Experion Station –TPS

ESVT Experion Server – TPS
Experion Server 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.
LCN Local Control Network

OPC Series of standard specification for open connectivity in industrial automation, originally based on
Microsoft’s OLE COM and DCOM technologies.
PPS Parameters per second
TPN Total Plant Network
TPS Total Plant Solution
UCN Universal Control Network

Honeywell Confidential
Experion ACE Specification, EP03-310-310, V. 2, January 09 17

Experion, PlantScape and TotalPlant are registered trademarks of Honeywell International Inc. All other products and brand
names shown are trademarks of their respective owners.

While this information is presented in good faith and believed to be accurate, Honeywell disclaims the implied warranties of
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

This document that is published for the sole usage of Honeywell Process Solutions’ customers and prospective customers

For More Information

Learn more about Honeywell’s products and solutions,
visit our website www.honeywell.com/ps or contact
your Honeywell account manager.

Automation & Control Solutions

Process Solutions
Honeywell
2500 West Union Hills Drive
Phoenix, AZ 85027
Tel: 877.466.3993 or 602.313.6665 EP03-310-310
January 2009
www.honeywell.com/ps © 2009 Honeywell International Inc.

Honeywell Confidential