_______________________________________________________________________________________
🔥🔥FEATURE SPOTLIGHT 🔥🔥
360 views - Redesigned UI
We've redesigned the User Interface for Tickets and other objects 360 Views, which are among the most-used features of the Pelico platform. These ongoing enhancements—validated through thorough user testing—are designed to deliver a meaningful impact on the overall user experience, including smoother onboarding:
Redesigned Show/Hide buttons for 360 View panels, now repositioned for better user discovery to better align with navigation paths
Editable properties are more visually prominent, making them easier to identify
Collapsible sections (General Information, etc.) have been redesigned to improve space optimization and overall usability
--------------------------------
Customer-specific data fields - New filter operators: “Does not contain", “Is empty", and “Is not empty”
Users frequently need to define their routine scopes by excluding certain values rather than including them. For example, they might want to review purchase orders for all suppliers, except their main one; or find escalation tickets that haven't been tagged yet. Without proper exclusion and empty/non-empty filter operators, users are forced into complicated workarounds or have to fall back to Excel processes.
For this reason, we're introducing new filter operators when working with customer-specific data fields:
Does not contain: Exclude specific values from your results
Is empty: Find records where a customer-specific data field has no value
Is not empty: Find records where a customer-specific data field has a value
These filter operators work with String, List, Single-select, and Multi-select customer-specific field types, giving users more flexibility when defining routine scopes and filters.
--------------------------------
Sharing views with filters - all filters are now correctly shared and loaded
When users shared configured views (including filters, columns, and other settings), some reported that in cases with multiple filters the generated URL was truncated. As a result, recipients opened the view with missing or incomplete filters.
For this reason, we're no longer encoding filters in the URL. Instead, filters are now persistent in the database, which means shared views are always loaded with the complete and correct filter configuration.
--------------------------------
Last Upstream Event - more reliable identification of the most critical upstream event
To assess execution risk, planners need to clearly understand which upstream event creates the biggest threat to a given consuming order (e.g. work order or customer order).
In scenarios where a single order consumes multiple parts at different dates, each pegged to different upstream events, identifying risk based only on the “latest” upstream event can be misleading. What matters is not which upstream event arrives last in absolute terms, but which one creates the largest delay relative to the consumption it is meant to cover.
This is the reason why we're implementing a more reliable identification of the most critical “Last Upstream Event”, for all Pelico books (except the Purchase Order Book). This change improves the accuracy and consistency of upstream risk visualization across all planning and simulation views. Here are some details on this improvement:
The displayed event is the one with the worst pegging delta, defined as: The largest delay between an upstream event’s projected availability date and the planned consumption date it is pegged to.
Pegging deltas are now computed using the planned consumption date (instead of the consuming order’s planned start date), ensuring accurate risk evaluation when multiple consumption dates exist.
*Note: Important behavior change!
When a consuming order is only partially covered by its pegged upstream events, no upstream event will be displayed in the Last Upstream Event group.
This prevents giving a false impression that the situation is fully under control when coverage is partial.
_______________________________________________________________________________________
New View Setting - By Part and SLK in a single plant
We are introducing a new View Settings, “By Part and SLK in a single plant”, currently available only in the Planning app. By giving users this level of granularity, we are enabling them to see the finest level at which stock is projected, and therefore allowing planners to analyze and simulate scenarios for specific stock segments or programs. With this view, users will be able to:
Apply SLK filters at equipment level or consumed part level to narrow down their scope.
Distinguish stock, supply, and demand flows that share the same part but belong to different stock link keys.
Analyze shortages, excess stock, and allocation issues with finer granularity.
*Note: this view is only available in the Planning app (not in the Supply Planning page, of the Supply app). Support in Supply Planning will be added in a future release.
_______________________________________________________________________________________
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 v110 - © Pelico 2026