The following tables contain the fixed and recommended capacities of the DeltaV Batch subsystem.
The values in the Fixed Limit column are limits imposed by the system that the user cannot exceed. The values in the Maximum Recommended Limit column are values that are recommended that the user not exceed and are to be used as a guideline when determining your system's performance.
It is important to note that the combination of items and the configuration of those items in a system and other variables (such as available memory in the controller and recipe or phase logic size) can effect whether or not a fixed or maximum recommended limit can be reached on a system; and, may also have an effect on the performance of a particular configuration. For example, a system may exceed the maximum recommended limit for one item without noticing any change in performance. However, if a particular configuration nears the maximum recommended limit of several items in combination, the potential for a change in performance is increased.
|
Controller Capacities |
Fixed Limit |
Maximum Recommended Limit |
|---|---|---|
|
PLMs per controller: non-redundant |
Limited by available memory in the controller. |
SQ, SD Plus, MQ, MD Plus controllers - 300 SX, MX controller - 600 PK controller - 1200 |
|
PLMs per controller: redundant |
Limited by the minimum available memory between the redundant controllers. |
SQ, SD Plus, MQ, MD Plus controllers - 300 SX, MX controller - 600 PK controller - 1200 |
|
Unit Phases running simultaneously per unit module: redundant and non-redundant controller |
10 Unit phases can be marked as Always in Memory. This means that the phase is always able to be loaded so that it never fails to run because of over-commitment of controller memory resources. |
10 |
|
Number of active phases in a controller |
None |
SQ, SD Plus, MQ, MD Plus controllers - 50 SX, MX controller - 150 PK controller - 300 |
|
Number of unit modules per controller |
None |
SQ, SD Plus, MQ, MD Plus controllers - 5 SX, MX controller - 24 PK controller - 48 |
|
Common phase logic algorithms in a single controller |
None |
SQ, SD Plus, MQ, MD Plus controllers - 200 SX, MX controller - 600 PK controller - 1200 |
Batch Executive System Capacities
A DeltaV system can include up to four enabled Batch Executives, four enabled Batch Historians, and four enabled Campaign Managers.
On Redundant Batch systems, a pair of Application Stations running the Batch Executive counts as one Batch Executive. Similarly, a pair of Application Stations running the Campaign Manager counts as one Campaign Manager.
|
Batch Capacities |
Fixed Limit |
Maximum Recommended Limit |
|---|---|---|
|
Maximum active batches, excluding manual phases |
100 |
100 |
|
Maximum total batches (including active, complete and ready) |
200 |
200 |
|
Maximum total campaigns per system |
None |
100 |
|
Recipes assigned to the Batch Executive |
None |
500 |
|
Phases per system (combination of unit phases and PLMs) |
None |
5000 |
|
Unit modules per system |
None |
400 |
|
Downstream unit modules per unit module |
None |
300 |
|
Equipment Train Classes per system |
None |
100 |
|
Equipment Trains per system |
None |
200 |
|
Unit Aliases per Equipment Train Class |
None |
250 |
|
Unit selection policies per system |
None |
100 |
|
Characters per unit selection policy |
2000 |
2000 |
|
Phase Step actions in step (Run Logic) |
None |
50 |
|
Phase step assignments per action |
None |
50 |
|
SFC Parallel Steps (phase run logic) |
None |
50 |
|
PLMs assigned to a single unit |
None |
200 |
|
Unit phases configured per unit |
None |
100 |
|
Sequential steps in an operation |
None |
200 |
|
Parallel steps in an operation (using PLMs) |
None |
30 |
|
Parameters (input) per phase |
99 |
99 |
|
Parameters (report) per phase |
99 |
99 |
|
Recipe parameters (input) per recipe |
None |
1,000 |
|
Recipe parameters (report) per operation |
99 |
99 |
|
Recipe parameters (report) per unit procedure |
99 |
99 |
|
Recipe parameters (report) per procedure |
None |
500 |
|
Active phase-to-phase messages (per Batch Executive) |
None |
50 |
|
Active, unacknowledged operator prompts-messages |
None |
100 |
|
Number of formulas per recipe |
None |
600 |
|
Number of authorizers for a recipe |
5 |
5 |
|
Recipe Exchange connections |
4 |
4 |
|
Remote soft phase workstations |
None |
3 |
|
Remote soft phases in parallel on max remote soft phase workstations |
None |
65 |
|
Remote soft phases in parallel on one remote soft phase workstation |
50 |
50 |
|
Nodes connected to the Batch Executive 1 |
50 |
50 |
|
Process cells |
None |
150 |
|
Concurrent # of connections for a Campaign Manager |
None |
15 |
|
Unit parameters per unit class |
None |
1000 |
|
Aliases per unit class |
None |
500 |
|
Number of phase algorithm parameters per phase class |
None |
200 |
|
Dynamic reference parameters on a unit class as unit parameter definitions |
None |
500 |
|
Dynamic reference parameters on a phase class as algorithm parameters |
None |
200 |
1 Nodes are counted as follows:
Multiple Remote Desktop Service sessions to the same workstation count as one node.
A workstation running both the Batch Operator Interface and a DeltaV Operate picture with the Batch controls on it counts as one node.
Batch Historian System Capacities
A DeltaV system can include up to four enabled Batch Historians.