Knowledge Base for Prediction App
1. Retrieve the raw size of your lots based on input and output losses [Project managers]
The raw size is the size of the lot before output losses are applied.
When a lot is in Ignore recipe mode, the lot is assumed to be produced based on the allocations entered by the user.
In this case, losses are overridden based on the size of the input allocations. The whole lot is always assumed to be produced. The raw size is then recomputed by minimizing the deviation from the theoretical losses.
When input losses are set to zero, the recomputed losses are always fully transferred to output losses.
In particular, when there is only one input product and no input loss, the raw size is equal to the total allocation size divided by the product conversion rate.
The raw size is only exposed in the XLS report, under the Manufacturing lots sheet, and in the API.
New validation error
To avoid having a raw size that is smaller than the produced size, the interface now checks that all allocations defined by the user are sufficient to produce a lot in Ignore recipe mode, even in the worst case where losses would be zero.
In other words, for each product, the App checks that the sum of all input allocations divided by the rate is at least equal to the manufactured size of the lot.
If this is not the case, an error is displayed in the Manufacturing lot table.
2. Project Cockpit Improvements [Project managers & Trial managers]
You can now execute the same actions in the Overview Cockpit as in the Supply & Demand cockpit. Clicking the lock icon next to a lot no longer directly freezes or unfreezes the lot. Instead, it opens a menu where you can freeze or unfreeze the selected lots, following lots, or previous lots. Only relevant actions are shown in the menu.
3. Import Demand Improvements [Project managers]
When importing demands from a trial, the project scenario must now be in a saved state. This prevents data loss if the action fails and the App needs to revert partially imported data.
4. Get more visibility on synchronization statuses [Project managers]
- By hovering over the global synchronization badge of a scenario, you can now see the list of tables that are not synchronized with the master. This lets you identify unsynchronized tables at a glance, without browsing each table individually.
- The Packaging lot table now displays the synchronization status. Contrary to other tables that can be synchronized with the project master, no action to update from the project master is available from the packaging lots table. The update should be performed by re-importing lots from the trial (from the Studies table)
As in the other tables that can be synchronized with the project master, the button in these tables only shows the statuses Up to date and Outdated.
When the update action is available, clicking the button updates all new items from the master and outdated elements in the scenario. Out-of-sync elements are never updated by this action. Therefore, out-of-sync elements in the scenario do not affect the status or action shown by the button.
In particular, if all elements in a table are either up to date or out of sync, the button indicates Up to date and no action is available. At least one outdated element is required for the update action to be available.
5. Enhancements & Fixes
- [Fix] The offset and multiplicative factor are now correctly applied to all lots, except those synchronized with the master, when importing demands in a project.
- [Fix] The algorithm was improved to better manage lots with variable lot sizes.
- [Fix] The App no longer crashes in some cases when a lot is defined with a date more than 30 years before it is used in an allocation.
- [Fix] An issue related to frozen allocations with multiple input products was fixed.
