Knowledge Base for Prediction App
1. Manage your allocations from the new cockpit view [Project managers]
1.1 See all the allocations by use date in one view
A newAllocation listcockpithas been added to theproject scenarios. This means there are now a total of 4 different available cockpits, accessible through a new dropdown menu in place of the previously existing carousel button.
From this cockpit (see screenshot below), you see the complete list of all frozen and forecasted allocations, from manufacturing lots to manufacturing lots, packaging lots, as well as any demands. The content of the list is similar to the content in theAllocation listsheet from theExcel report, but directly accessible from the cockpit.
The additional information displayed is the following:
- Frozen allocations appear in blue while forecasted allocations appear in grey.
- Allocations pushed to the project master are identified by a specific icon (see the below icon).
- Reusable information is part of the table. This checkbox is by default unselected, meaning any surplus quantity allocated can’t be reused for other allocations and is considered as waste. When selected, any surplus quantity allocated can be reallocated to other lots. The reusable option is not accounted for anymore if Ignore recipe is selected on the child lot.
- Double-clicking on a Consumer applies a filter to display only the allocations going from and to it. Double-click again on the same Consumer removes the applied filter (see second screenshot below). Note that the Consumer on which the filter is applied is added to the column title.
1.2 See the allocation list the way that suits you best
TheAllocation list cockpitoffers two distinct modes, toggleable via the top-left button:
- Default View: an ungrouped list ordered by Use date.
- Grouped View: data is ordered and grouped by Parent lot.
1.3 Interact with allocations directly from the cockpit
When inEditmode, you canmanage allocationsdirectlyfrom the cockpit:
Freeze allocations:you can freeze an allocation provided that both the parent and child lots are already frozen. In the following example, DP03 and BL005 are both frozen, meaning the corresponding allocation can be frozen from the cockpit, while this isn’t the case for DP04 and BL006.
- Unfreeze allocations: unfreeze allocations directly, with a built-in warning if the allocation has already been pushed to theProject master.
- Create new allocations: a new modal has been designed to help you manage allocations more easily.
The allocation modal includes:
- some fields making it possible to refine the allocation that you want to perform:
- Parent lot: by default set to the parent from which you launched the action.
- Allocation type: to manufacturing lot, to packaging lot, to demand.
- Product: used to filter out the available lots or demands in the Consumer field.
- Consumer: lists manufacturing lots, packaging lots or demands based on your selection.
some read-only insights helping you to determine the right quantity to enter in the editable Frozen allocation size.
Two helper actionshave been designed to streamline this process:
the left arrow: allocates the total available quantity from the parent lot.
- the right arrow: allocates the minimum between the Parent lot remainder, and the Need not yet covered by frozen allocations.
- Update an existing allocation: the same modal as described above opens.
2. Various enhancements
2.1 Visually get what is not used in the forecast [Trial & Project managers]
We offer the possibility to define if a row should be used or not in the forecast. For example, not using a certain row, such as a specific study, leads to not considering anything referencing this study in the forecast, such as the associatedPackaginglots. This feature is helpful to run what-if scenarios, but was sometimes making it difficult to identify which rows are effectively accounted for or not.
With this new version, you now directly see for each row if it is used in the forecast or not! For example, ifStudy 17is unused, then it is highlighted with a light grey hatched pattern.
On top of that, all the referenced items, here the packaging lots from this study also appear in a light grey hatched pattern in their own table.
2.2 Directly identify if a field is mandatory or not [Trial & Project managers]
To improve data entry speed, and accuracy, when fields are mandatory, they are now identified by an asterisk. See an example below with theManufacturing lotstable. Note that this is not the case for boolean fields which carry a default value (true or false).
2.3 Set your recurrent filters quicker [Project managers]
Some recurrent filters have been defined as default filters to streamline the user workflow to apply them. Those have been added in the following tables:
- Study: Code
- Packaging lots: Study, Package type (see example screenshot below)
- Guidelines: Product
- Allocations to manufacturing lots: Parent lot, Child lot
- Allocations to packaging lots: Parent lot, Child lot
2.4 Get an even more complete assumption extract [Admin]
The assumption extract has been enriched with additional data:
- Trial scenarios:
- Trial description: displays the description of the scenario in the Prediction app.
- External result name: displays the name of the result imported from Supply app or Lighthouse.
- Project scenarios:
- Project description: displays the description of the scenario in the Prediction app.
2.5 Enhancements & Fixes
- [Change] The Included field available in the project master cockpit has been renamed Finalized.
It is also now visible in the Manufacturing lots table directly. - [Change] A warning now appears in case “Ignore recipe” is selected for a lot which has no allocation defined where this lot is the parent lot. In this situation, either some allocations should be defined, or the lot should be set as Fed.
- [Change] The following warning is now simpler.
- [Change] Download time of the extract assumptions has been slightly reduced.
- [Change] The algorithm has been improved to reduce the likelihood of (not yet fully eliminate) situations where missed demand at a given point in time for a specific product leads to continued missed demand for the remainder of the planning horizon.
- [Fix] Risk was sometimes appearing in the cockpit due to extremely small values related to rounding. This has been fixed and risk now only appears for significant values.
- [Fix] The following message was sometimes wrongly appearing “Data (lots and/or demands) have been truncated after dd-mm-yyyy to avoid a planning horizon exceeding 30 years”. We now prevent ending up in this problematic situation explained below, and inform you how to solve it.
- Multiple products defined in a trial scenario that belong to the same package design can no longer be mapped to the same product defined in a project scenario when the scenario is imported. A banner indicates the reason why the scenario cannot be imported.
If a scenario already contains duplicate packaging lot recipes (i.e. if multiple product belonging to the same package design were previously mapped to the same product of the project), then a validation error asks the user to re-import the faulty studies (i.e. those containing package lots with duplicated recipes).
