Problem Description Example

Here is a sample problem description in YAML. It is complete in terms of the description but the problem is too simple to optimize anything.

There are two hierarchies, one level each: [product] and [customer].

There are two spaces: ByProduct and ByProductAndCustomer. Each of them contains only the standard All scope.

In ByProduct, All scope, there is only one variable, called ListPrice. It means that list prices are defined at a product level. It is a Value Finder: list prices will vary during the optimization, to reach some criteria. List prices have strict bounds list_price_lower_bound and list_price_upper_bound which are provided by the data and may be different for each product. Value Finder parameters are defined in the code, they are the same for all the products.

In ByProductAndCustomer, All scope, there are two variables: Volume and Turnover. Their values are different for each pair of (product x customer). Volumes are fixed, they are read from historical_volume data. Turnovers are computed. They are the product of a list price by volume for each pair of (product x customer), they change because of list prices changes.

There is also a TargetTurnover criterion in ByProductAndCustomer, All scope. It defines that at a level of (product x customer) the turnover value should reach the historical_turnover value.