Idle Optimizer API

You can use the Idle Optimizer API to determine how you would benefit from using IBM Sterling Fulfillment Optimizer with Watson prior to integrating it with your order management system.

The Idle Optimizer API enables asynchronous order optimization. The request to this must include the IBM® Sterling Order Management System Suggested Option to indicate the sourcing choice made by your order management system. The API uses the request and sends it to an internal queue for asynchronous processing. The baseline KPIs are computed after a certain latency period. During the asynchronous optimization process, IBM Sterling Fulfillment Optimizer with Watson takes the last message that's received within a pre-defined period. The Idle Optimizer API performs the following validations:
  • Determining whether the input is a valid JSON document
  • Determining whether orderNo is included in the input

The Idle Optimizer API performs Shadow optimization in addition to regular optimization. KPIs are always computed for the standard optimization and alternate optimization settings. If the sourcing choice of your order management system is passed in the request to the Idle Optimizer API or Optimizer API, the KPIs are computed for the sourcing choice of your order management system.

For more information about the Idle Optimizer API request and response, see the Idle API topic in IBM Developer.

Accessing the Idle Optimizer API

You can access the Idle Optimizer API from the following URL: https://<BaseURL>/<tenantID>/otmz/services/idle/V1/promiseOrder

Limitations of the Idle Optimizer API

  • The OrderDate that is provided to the Idle Optimizer API as input is used for logging purposes. The order is processed with respect to the current time when the order is received by IBM Sterling Fulfillment Optimizer with Watson. A re-sourced order is considered as a new order by Fulfillment Optimizer.
  • Fulfillment Optimizer can process only one ship to address. It uses the address that is provided at order level. If an address is not available at order level, then it uses the address from the first order line.
  • Fulfillment Optimizer cannot process the same SKU if it is part of multiple order lines in the same order.
  • Fulfillment Optimizer can process only one SLA. It uses the value of the attribute CarrierServiceCode provided at first order line.
  • Fulfillment Optimizer does not provided the Cost to Serve information back to the application that is calling the Idle API.

For more information about how to install and configure the runtime adapter for the Idle Optimizer API, refer to the Idle Optimizer API set up in the Using the IBM Sterling Fulfillment Optimizer with Watson runtime adapter topic.