Added tabs to see the manufacturing orders for a specific item, location or operation.

Update of the “in progress” fields of the inventory report. Are considered in progress for a given bucket
all orders startting before the end date of that bucket and ending after the end date of that bucket.

Forecasting (Enterprise & Cloud Editions)

Improved algorithm to detect seasonal patterns.

Performance optimization when reading forecast data in memory.

Inventory planning (Enterprise & Cloud Editions)

Fix the distribution used to calculate the service level all along the horizon.

4.4.2 (2018/10/20)

A new solver is introduced, specifically designed and tuned for distribution models.

The default solver loops over all demands in order of priority and due date, and reserves material
inventory and capacity along the supply path of that demand.

The distribution solver first generates a unconstrained plan, and then solves all
infeasibilities together and propagates the impact along the supply path. This solver distributes
the shortage proportionally across all impacted demands. In distribution models the solver
is also much faster than the default solver.

So far, only a worksheet called ‘sales order’ was recognized as containing sales order data.
Now “sales-order”, “sales_order” and “salesorder” will also be recognized.

Openbravo connectors

Addition of the importDistributionOrders that read the distribution orders issue from Openbravo.

Export of approved distribution orders issue from frePPLe to OB.

Use of Fpp_InventoryByProduct entity that aggregates the onhand by warehouse (frePPLe connectors are not looking at the storage bins anymore).
The Fpp_InventoryByProduct entity handles the onhand date change meaning that it can now be used in delta mode.

Use of the Fpp_ConsumptionHistoryDetail entity that aggregates the demand for a given item-location at bucket level. That makes the connectors
read much less records. The time bucket (week, month…) is configurable in OB.

Handling of product name change. FrePPLe connectors rely now on the object id rather than on the product name.

Third party components

The Ubuntu binaries will be compiled on Ubuntu 18 LTS from now onwards.

4.4.1 (2018/09/10)

Production planning

Bug fix in the calculation of the lateness/earliness of a manufacturing
order, purchase order or distribution order. The calculation was incorrectly
based on the start date rather the end date of the operation in question.

Ability to make the data anonymous and obfuscated when
exporting an Excel workbook.
The names of all entities are obfuscated in the resulting spreadsheet. You will still
need to carefully review the output to clean out any remaining sensitive data.

Ability to customize the names for the time buckets used in the reports.
The time bucket generation command
now has extra attributes for setting the name of the daily, weekly, monthly, quarterly
and yearly buckets.

Third party components

Support for Ubuntu 18 LTS.

Ubuntu 16 LTS remains fully supported.

Windows installer now uses Python 3.6.

Python 3.5 remains fully supported.

4.4.0 (2018/08/02)

The Windows installer of this version isn’t working correctly due to some packaging mistakes.

Production planning

Resources can now have an efficiency percentage. This allows
the resource to perform an operation faster or slower than the standard operation time.

The resource report now displays the
available capacity as a line, replacing the green bar in previous releases to show the free capacity.

Performance optimization of the solver algorithm. The solver now passes down the minimum shipment
information from the demand to all upstream entities, which allows the algorithm to perform a more
efficient search.

In complex models, the resulting plan may be slightly different - for the better.

Resource build-ahead penalty calculation now also working for 0-cost resources.

New rows to the inventory report
to show 1) days of cover of the starting inventory, 2) the safety stock and 3) more details
on the supply and consumption type.

The minimum field on the buffer defines a safety stock. In previous releases this safety stock was
effective from the horizon start in 1971. Now this safety stock is effective from the current
date of the plan onwards.

This change will give a different result for safety stock replenishments in an unconstrained plan.
In a lead time constrained plan the results will be identical.

Remove buffers of type procurement from the planning engine code. This buffer type was already long
deprecated and hasn’t been accessible to users for quite some time now.

Simpler and more generic modeling of fixed material consumption and production by operations.
The types ‘fixed_end’ and ‘fixed_start’ on operation material
records are replaced with a field ‘fixed_quantity’.

When expanding a confirmed manufacturing order on a routing operation, the automatic creation of the
child manufacturing orders for each routing step now also considers the post-operation time.

Note that such child manufacturing orders are only generated if they aren’t provided in the input
data yet.

Inventory planning

The safety stock and ROQ minimum/maximum period of cover are now expressed in days. It was before entered
as the number of period buckets, the period bucket being the value of the inventoryplanning.calendar parameter.

Forecasting (Enterprise & Cloud Editions)

Forecast parameters forecast.Net_NetEarly and forecast.Net_NetLate are now expressed in days (previously
they were expressed in seconds).

User interface

Bug fix when copying a what-if scenario into another what-if scenario.

Bug fix when uploading data files using the Microsoft Edge browser.

Deprecation

Operations of types alternate, routing and split should not load any resources,
or consume or produce materials. The suboperations should model all material and capacity
usage instead.

Note that in the majority of models, the explicit modeling of alternate operations is no
longer needed. The planning engine detects situations where an item-location can be replenished
in multiple ways and automatically generates an alternate operation.

4.3.4 (2018/06/08)

Forecasting (Enterprise & Cloud Editions)

The forecast error used in frePPLe is SMAPE. This has a counter intuitive property that
provides values in the range from 0% to 200%.