Node capacity
The node capacity data type, formerly known as processing plan data type, defines the capacity that is available for nodes over a specified time span.
Your node capacity can be created in advance for as many days as your business has the available
information. 30 days
is recommended. This data is required only when you are
balancing node capacity.
For more information, see Create capacity API.
Node capacity example over a time period
Node | 09/19/2016 | 09/20/2016 | 09/21/2016 | 09/22/2016 | 09/23/2016 |
873 | 80000 | 80000 | 80000 | 80000 | 80000 |
809 | 70000 | 70000 | 70000 | 70000 | 70000 |
819 | 95000 | 95000 | 95000 | 95000 | 95000 |
829 | 60000 | 60000 | 60000 | 60000 | 60000 |
Setting the capacity unit of measure
Capacity can be defined in releases or units. By default, the capacity unit of measure (UOM) is
defined in units. To define capacity in RELEASES, contact IBM® Software Support to switch the
configuration for your tenant from UNITS
to RELEASES
. Then, define
the conversion factor from RELEASES
to UNITS
. You can also define
the conversion factor for each node type.
For example, the node capacity at the ship node is 1000. The capacity is converted with the help
of the Optimization service by multiplying it with the conversion ratio for RELEASES to
Units. If the conversion factor is 2, the converted capacity becomes 2000 at the ship node during
node-balancing optimization. Similarly, the capacityConsumed
parameter in the input
of the Optimizer API is converted by multiplying its value with the conversion ratio for the ship
node.