Platform
In Memory Caching
In-memory caching is enabled with the application in the following areas, which helps improve performance.
Planning view creation: The application creates a planning view with 2000 plus items in a few seconds.
Planning view loading: The planning view screen loads quickly, even for the larger items.
Override jobs: Multiple override jobs can be performed, and data refreshes quickly.
Business rules computation
Cycle roll jobs
Roles and permissions
To streamline access management, unnecessary permission objects have been removed from the Roles & Permissions screen. This allows administrators to assign precise permissions, granting users specific access to screens and actions required for their roles, thereby improving security and usability.
Removed the following areas from the Roles and permissions screen
Personalization
Planning admin
Supply Plan > Supplier commits
Other > Statistical forecast
Renamed the following
Firstshift AI → S & OP Copilot
Default → Home dashboards
Analytics → Insights
Event triggers → event management.
Demand planning
1. Planning view enhancements
Drilldown pop enhancement: When the user clicks on a particular cell to drill down into order details, the application opens the order details of the transition measures in a pop-up without navigating back to the inspection data.
Lockout issues that occurred when running multiple planning views have been resolved.
All the planning views will refresh automatically with new relations after the data loads and cycle rolls.
2. Usability enhancements
The application automatically displays descriptions for cross-hierarchy entities, such as the Product Location master, product sourcing network, and sourcing network, based on descriptions available in the Product, Customer, Location, and Source.
No additional configuration is required.
The descriptions will appear after the next dataload.
Replenishment planning
The application generates the proposed orders' order line cost(Order amount), considering Suggested Order Quantity (SOQ) and Unit Price.
The application shows the last run details for replenishment and demand fulfillment planning engines.
Introduced ‘Frozen Horizon’ for the Make items. During this period, the application doesn’t generate SOQs. Instead, the application creates a Backlog and considers it the SOQ generation after the Frozen period.
For example, If the planning starts in future buckets, and the frozen period spans from the current period through the next three weeks, any unmet demand during this frozen period should be accounted for as backlog.
The frozen period is a computation parameter in the admin app.
The frozen period doesn’t apply to Raw materials(Is Finished Goods = No) and Buy items (i.e., Make_vs_Buy = Buy items)
Frozen horizon applies only to MAKE items.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article