Capacity conversion
You can define capacity in releases or units. By default, the capacity unit of measure (UOM) is defined in units.
Deprecation of the legacy capacity conversion capability begins on September 30, 2026.
To define capacity in RELEASES, contact IBM® 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 more
information, see Managing capacity conversion.
- Example
- The node capacity at the ship node is 1000. The Optimization service converts the
capacity by multiplying it with the
RELEASES to Unitsconversion ratio. For example, if the conversion factor is 2, during node-balancing optimization, the converted capacity becomes 2000 at the ship node.Similarly, in the input of the Optimizer API, the capacityConsumed parameter is converted by multiplying it with the ship node conversion ratio.
Recommended actions
Capacity is directly computed from the configured capacity workflows supporting the Unit and Release UOMs that provides more accurate fulfillment and delivery‑date estimates. If a node has a valid capacity workflow, UOM conversion is automatically bypassed, otherwise, the legacy conversion continues until the sunset date.
If you currently rely on Release‑to‑Unit conversion to estimate node capacity, you should configure capacity workflows at the node, node type, or the delivery‑method level to ensure consistent behavior across the Promising service, Inventory service and the Optimization service. For more information, see Configuring capacity workflows.
When you ingest capacity via file upload by using CSV or XML files, nodes that include release capacity must not apply the Release-to-Unit conversion factor process to estimate the unit capacity. Instead, the capacity workflow must be configured to define capacity. For more information, see Monitoring data for file ingestion.