_______________________________________________________________________________________
New “Firm status” column
In ERP systems, the firm status indicates that an order’s key parameters (dates, quantities) are frozen and excluded from automatic MRP rescheduling, even though planners can still modify them manually when needed.
To ensure consistency with ERP behavior, and enable future rescheduling algorithms to distinguish between firm and non-firm orders, we've added a new “Firm Status” field for all Pelico Books with orders that increment stock (i.e. supply orders and work orders). This will make it possible to reschedule only what’s flexible while preserving what has been validated by operations.
Some more details about the “Firm Status” field:
The field, shown in Pelico, is sourced from the ERP via the ETL.
At this stage, Pelico does not automatically set or modify the firm status: it strictly reflects the ERP value.
Orders marked as “firm” can be excluded from future automatic rescheduling algorithms, while users remain free to simulate changes manually during what-if scenarios.
--------------------------------
Lot Size and MOQ improvements
Manufacturing and procurement constraints often require that orders respect a minimum quantity (MOQ) or be placed in fixed multiples (lot size). By making these parameters visible and integrated into Pelico’s data model, we ensure that any rescheduling adjustment remains realistic and executable in operations - if the user wishes to enforce these constraints.
This is the reason why the Pelico data model is now supporting Lot Size (this was already the case for MOQ). When these two rules are set:
Both MOQ and Lot Size can be displayed in the Plant Part 360 view, making quantity constraints transparent to planners.
A tooltip appears when hovering over simulated quantity fields, giving instant visibility into MOQ and Lot Size rules for the selected part.
*Note: These parameters will soon be leveraged by MRP-like algorithms that propose rescheduling or quantity adjustments, ensuring that all recommended actions respect operational constraints.
.
_______________________________________________________________________________________
Work Order and Service Order Books - Graph view improvements
We're introducing two improvements for the Graph view of Work Order and Service Order Books:
The y-axis can now be based on any numeric tenant-specific data field. Previously, this was limited to Work Order/Service Order counts, revenue, or quantities. This improvement gives users flexibility, allowing them to visualize workload and performance metrics that best reflect their processes.
Orders are displayed based on predicted dates using the prediction logic defined as Propagation of Delays, in addition to the existing planned dates. Because these predicted dates are derived from pegging links, they provide a more realistic view of when orders are expected to occur, therefore helping users quickly detect workload imbalances.
______________________________________________________________________________________
Please don't hesitate to share your comments or suggestions.
The Pelico team
ps.- please note that this email outlines all of the new Pelico features available, some of which may not be deployed for your plant. If you are interested in activating them, please contact Pelico Support or your Account Manager.
--------------------------------
Release v108 - © Pelico 2025