New Solver parameter heuristic_2

[udayv1389]

Hello,

First of all for the great software ! And thanks for the community version !

Recently, I was started working with the Frepple Community Edition, and there i noticed a new solver parameter called heuristic_2.
If it possible to know what is the actual difference between default solver and the new solver and how is the planning works with the new solver.

Thanks !
Uday

[jdetaeye]

The new heuristic_2 solver is an evolution of the current heuristic solver.
Material and capacity unconstrained plans are already using the new solver algorithm.
The new solver isn't ready yet for any constrained planning yet.

The key goal of the new algorithm is to take planning decisions on a more global/aggregated level, rather than the very strict demand-per-demand view the current solver takes. It's a major change in the solver algorithm, and we're developing this step by step.

For the time being, just stay with the current solver... We'll announce when the new algorithm is ready for broader review and testing.

[udayv1389]

Hello Johan,

Thank you very much for the prompt reply and sharing a valuable information. Eager to see the complete version of the new solver.

I do the have other question out of curiosity, when we say planning decisions are more on global/aggregated level, does the planning system use some kind of aggregate or batching window to club demands which user can define somewhere in the system or is it something completely managed by solver internally, how to club or group demands.

Secondly , is this also applicable for items which are of type make to order or only applicable to make to stock items, meaning when we have common sub-assembly or WIP items which is shared among multiple parent demand items, does the new solver try to aggregate the demand of the common WIP item even if they are make to order type?

Thanks,
Uday

[jdetaeye]

I do the have other question out of curiosity, when we say planning decisions are more on global/aggregated level, does the planning system use some kind of aggregate or batching window to club demands which user can define somewhere in the system or is it something completely managed by solver internally, how to club or group demands.

The "batching window" field defines this aggregation/grouping. If we see multiple requirements that are closer together than this window, we will propose a single replenishment for the combined requirements.

This field is available in the "item supplier" table for purchasing.
It's also available in the "item distribution" table for distribution orders.
It's also available in the "operation" table for production orders. But it's only the new solver heuristic_2 that will be able to use it from the operation table.

Secondly , is this also applicable for items which are of type make to order or only applicable to make to stock items, meaning when we have common sub-assembly or WIP items which is shared among multiple parent demand items, does the new solver try to aggregate the demand of the common WIP item even if they are make to order type?

The grouping applies to any level in the supply chain - can be components, subassemblies or end items.

It works for both make-to-order and make-to-stock items. For make-to-order requirements we can only group requirements with the same "batch" field.
Eg if we have a sales order with batch "SO1" and another sales order with batch "SO2", then we cannot replenish them with a single manufacturing order, even if there due date is the same.
Eg if we have a sales order with batch "green" and another sales order with batch "green", then we can replenish them with a single "green" manufacturing order (assuming the due dates are closer together than the "batching window").
So, you can flexibly control what can be combined and what not.

[udayv1389]

Thanks again for the reply. That's good to know that its based on batching window and works for both make-to-order and make-to-stock items.

It's also available in the "operation" table for production orders. But it's only the new solver heuristic_2 that will be able to use it from the operation table.

Probably in the future release we get to see the "batching window" field in the operation table, at the moment i can't see this field edit view in community edition, only if added via grid.

The grouping applies to any level in the supply chain - can be components, subassemblies or end items.
It works for both make-to-order and make-to-stock items. For make-to-order requirements we can only group requirements with the same "batch" field.
Eg if we have a sales order with batch "SO1" and another sales order with batch "SO2", then we cannot replenish them with a single manufacturing order, even if there due date is the same.
Eg if we have a sales order with batch "green" and another sales order with batch "green", then we can replenish them with a single "green" manufacturing order (assuming the due dates are closer together than the "batching window").So, you can flexibly control what can be combined and what not.

What if the batch field is left empty on the sales order, today frepple generates a batch id and uses that batch information for the sub-assembly. My example situtation is like we have 2 items lets call it FG1 and FG2 both have respective demands say demand 1 and demand 2 with batch field not filled and due date are close enough and are within the batching window. These 2 FG items shares the same sub-assembly let's call it WIP1 as one of the components. Now with the new solver, does it create one combined manufacturing order for both FG1 and FG2 together, if yes then what information do we see in the batch field or will it work the same way as today, where it will generate a dedicated MO for WIP1 which goes to FG1 where the batchid is the generated by frepple and a dedicated MO for WIP1 which goes to FG2 with its own batch id.

Looking forward with the full version of the new solver in the near future.

Thanks,