🔥 🔥 FEATURE SPOTLIGHT 🔥 🔥
Line of Balance comes to Customer Support
Customer Support gains a Line of Balance tab showing part availability dates per customer event.
The tab carries its own filters, saved view settings and column configuration, so a customer-facing team keeps a working view of its own rather than borrowing one built for production.
A stock transfer column is headed by the part delivered at the destination plant, with that part's escalation and comment summary and its line stop date. Component rows, cells, coverage, quantity and date still use the source part, as do the column filters and business-unit scoping, and simulated transfers keep naming the source part.
Two Line of Balance corrections land with it, in Customer Support and in every other view that shows it: required-quantity rows, flat and tree, are now ranked by the column of their first shortage rather than by the rank of that shortage among the component's own needs; and the flat required-quantity view sorts on pegged cells only, which cuts memory and response time on large scopes.
Note: this feature requires specific setup and data integration. Please contact your Customer Operations Manager if you are interested.
Latest conversion date for purchase requisitions, and lead time override per requisition
The Purchase Order Book now shows the latest date by which a purchase requisition must be converted into a purchase order, together with the delivery lead time used to compute it, which can now be set per requisition instead of only per part in a plant.
These changes apply only if you are running on the new projection engine.
A purchase requisition can show a positive date adjustment while its delivery date is still in the future. This is expected: the requisition must first be converted into a purchase order, and that order then needs its full delivery lead time to arrive. The requisition is feasible only if delivery date − delivery lead time is still ahead of today. Until now, this deadline was computed but not displayed, so the adjustment looked unjustified.
Four fields are now available for purchase requisitions in the Purchase Order Book and in Purchase Requisition 360:
Latest Conversion Date — the last date by which the requisition must be converted into a purchase order for its delivery date to remain feasible: delivery date − Applied Delivery Lead Time. Sortable and filterable, so you can prioritize which requisitions to convert first.
Adjusted Latest Conversion Date — the same date after preprocessing. When the latest conversion date is already in the past, it is adjusted forward before the projection runs.
Applied Delivery Lead Time — the delivery lead time actually used for the requisition, in calendar days: the requisition's own value when one is provided, otherwise the default lead time of the part in the plant.
Delivery Lead Time Source — where that value comes from: Plant Part Default or Purchase Requisition Override.
The delivery lead time can now be provided per purchase requisition line through your data integration, for cases where a requisition is already assigned to a supplier whose real lead time differs from the default of the part in the plant. When no value is provided, the default applies, as before. The existing Delivery Lead Time column, which shows the default of the part in the plant, is unchanged; when a requisition has its own lead time, the value in use is the one shown in Applied Delivery Lead Time.
Line stop date is now computed per stock link key
The line stop date now shows the first date a consumption is delayed or blocked for a part in a plant and a given stock link key, instead of the first date the total stock of that part in that plant goes negative.
Until now, the line stop date was computed on the total stock of a part in a plant, all stock link keys combined. When that total was positive but one stock link key was already short, no line stop date appeared. For plants working with stock link keys, the field was unusable.
The line stop date is now the earliest delayed or blocked consumption for a part in a plant and a given stock link key, instead of the first date the combined stock goes negative. For the part in the plant as a whole, the line stop date is the earliest one across all its stock link keys.
The correct value now appears in Planning, escalation tickets, the Purchase Order Book, the Line of Balance and Plant Part 360. For example, in Planning, when you display a part in a plant for a given stock link key, you now see the line stop date specific to that stock link key.
Safety Status view mode is back in Planning, and the Coverage legend is clearer
A new Safety Status view mode colors each part in a plant against its safety stock and safety time, and the Coverage view mode in ERP plan now has a legend that matches what the colors mean.
These changes apply only if you are running on the new projection engine.
Planning showed shortages (projected stock below zero) but not safety breaches (projected stock below safety stock). Parts leaving their stock policy before becoming a missing part were not visible.
A new Safety Status view mode is available in the view settings, alongside Stock Coverage, Inventory, Need Quantity and Resource Quantity. It colors each cell against the part's safety stock, taking safety time into account:
🔴 Negative stock
🟡 Safety threshold not reached
🟢 Within safety thresholds
⚪ No consumption
In this view mode, the Show Realistic Plan toggle is switched off and disabled: the safety status is evaluated on the ERP plan, without propagation of blockers.
Separately, the Coverage view mode in ERP plan (Show Realistic Plan off) has a new legend. In this mode, the values in the main row follow the ERP dates, while the colors show what the projection engine expects to happen once delays propagate. A positive projected stock can therefore appear in a red cell. The legend now describes this:
🔴 Shortage once delays propagate
🟡 Covered only by conditional supply
🟢 Covered, delays included
⚪ No consumption
Usability improvements on book graphs filtering
Hovering a bar in a book graph opens a popover that filters the table beneath it.
In the work order, purchase order, customer order and MRO service order books, the popover lists each series in the bar with its value, plus an All row; picking one filters the embedded table to that series or to the whole bar. A Reset selection button appears next to the X-axis selector while a selection is active, and clicking the empty graph background no longer clears your selection by accident.
MRO: an allocation priority you set yourself
From the MRO service order book you can set a shared allocation priority on a service order, or clear it to fall back to the ERP value.
The Allocation Priority column splits into two sub-columns, ERP and user input. An administrator enables this per tenant in the annotations category of the Config Editor; it is off by default, and the priority is only used when the tenant runs the realistic algorithm strategy.
Note: this feature requires specific setup and data integration. Please contact your Customer Operations Manager if you are interested.
Also in this release
Performance: the heaviest views got materially faster Several of the slowest screens in the platform were rebuilt to stop doing redundant work, and the difference is measured in seconds, not milliseconds.
Event Explorer: upstream and downstream events can be filtered by material coverage, from a new filter or from the column header. The Delayed option is only offered when your plant is not on the legacy algorithm.
Production Control: Part Book improvements the Part Book gains a last upstream event column group for fully covered needs, hidden-by-default custom field columns for work, purchase and service orders, editable work order BOM component custom fields, and comments on the escalation ticket of a consumed part that apply to every row of that part.
Event Navigator: selecting any card, including the central event, highlights the critical path one step upstream and downstream, with the path to the central event faded where it is not critical.
Global search: new options let you narrow your search for faster, more accurate results, and make it easier to access the different objects managed in Pelico.
Reliability Index: KPI #2 (comparison between today and line stop date, in days) and KPI #5 (low safety stock coverage) now display positive values. For visual consistency the “−1 ×” factor is removed from their computation, so the raw values shown in the 360 view are positive, like every other KPI of the Reliability Index.
Filters: autocomplete lists gain a “Select all displayed (N)” checkbox and a “Show selected only” switch that lists your whole selection regardless of the search or the 50-row cap; the truncation note now says how many of the total matches are shown.
Plant Part 360: the Events & projected stock graph offers zoom on every part whose bars are not already full width, and adds a brush strip for picking a time window on parts with very many event days.
Accessibility: side panels, the routine instructions panel, the 360 activity panel and the settings tabs are exposed as named regions for screen readers; the notifications button announces its unread count; and the Notifications, Time Horizon, Language and Date format controls carry proper labels.
For administrators: partial supply rescheduling is now off by default — enable_partial_supply_rescheduling is reset to false on every existing tenant, so re-enable it if you relied on the previous default. The eight single-row Config Editor tables no longer allow adding or deleting rows, which previously could crash the application. The Teams page visibility toggles show their state in a tooltip. Re-run core2algo after the upgrade to refresh results computed on the earlier stock increments, and note that the qualityNotes, qualityNotesOnBlockedProduction and qualityNotesOnResources GraphQL fields are removed — a breaking change for any custom GraphQL client.
*Note: this feature requires specific setup and data integration