CC-PCNT01 Honeywell Controller module Brand new

Control requirements of a C300 are estimated in PUs, using a PU estimation spreadsheet similar to those used 

for C200 and ACE. The definition of a PU (see Section 1.4) does not change with the introduction of C300, 

because the PU definition is platform independent. C300 PU specifications are provided for the same set of 

typical module types (e.g. Small Analog Data Acquisition CM, Regulatory Control CM, Device Control CM, 

etc.) as already documented for C200 and ACE.

PU specifications are not provided for Series C IO Modules and PM IO Modules, because the IO Module 

execution for these IO types is not part of CEE. Processing load attributed to the execution of Series C IO 

Modules and PM IO Modules is accounted for in the IO component of C300 CPU usage.

2.3.4.3 C300 IO

Performance testing has determined that the following factors have the greatest influence on the amount of CPU 

used to support and communicate with IO.

• IO Link 1 Type – PM IO, Series C IO, or None

• IO Link 2 Type – PM IO, Series C IO, or None

• IO Link 1 LUs – estimated from LU estimation sheet

• IO Link 2 LUs – estimated from LU estimation sheet

• Number of FTEB supported IO modules

CPU Usage

0%

100%

Free

Comm

Control

IO

Base

XUs for user

ExperionPKS C300 Controller Capacity, EP03-300-511 16

Version 1 Honeywell Proprietary July 2019

Honeywell Internal

The C300 performance model estimates the XUs required to support IO, when provided with estimates for the 

above factors.

The LU estimation worksheet contains all the details needed to estimate the LUs associated with a given IO 

Link and its complement of PM IOPs or Series C IOMs. To summarize, the number of LUs is dependent on the 

following items.

• Link Type - PM IO or Series C IO

• Number of IO Modules, and for each its type (AI, AO, DI, DO, etc.), scan rate, and redundancy 

configuration

• Number of AO connections – quantity and rate

• Number of DO connections – quantity and rate

• Number of SCM reads and writes per second of IO Link data

2.3.4.4 C300 Communication

Performance testing has determined that the following factors have the greatest influence on the amount of CPU 

used to communicate with peer nodes and displays. A conscious effort has been made to keep the number of 

input factors to a minimum to keep the C300 performance model as simple as possible while maintaining its 

usefulness and accuracy. The model has been refined to the point that only these major factors need be input to 

the spreadsheet. The XUs required to support the specified communications are calculated automatically from 

these inputs.

• # of Peer Connections (node type is not critical) – nodes considered as peers include C300, C200, ACE, FIM4

• # of Console Stations associated with Experion Server/cluster

• # of Parameters per second for display throughput

• # of Messages per second

o # Messages/second is calculated from the number of Exchange blocks, Push block stores, and SCM block

stores that initiate and respond to requests

The number of Notifications per second generated by a C300 is an example of a factor not included in the model 

because it is not significant when compared to the other factors listed above.