Who is this for ?
Anyone who rebuilds the same view every morning and wants to save it instead.
What you will learn :
What a Routine saves, how to create and manage one, and why your Routine takes priority over the defaults set for your organization.
1. What a Routine is
A Routine is a saved view configuration. You set a view up the way you want it once, give it a name, and apply it again later instead of rebuilding it.
A Routine saves the way you are looking at your data :
The filters you applied
Your table settings, such as which columns are shown, how they are sorted, and how many rows are displayed
Other display options of the view
A Routine does not change any data. It changes what you see and how it is arranged.
⚠️ A Routine does not save your plant scope. Scope is a separate configuration level with its own action, Save Filters as User Scope. A Routine deliberately leaves scope out and applies on top of whichever scope is active. This means the same Routine gives you different figures if you change plants — which is usually what you want.
Creating and managing a Routine
Every control lives in the view-controls toolbar, at the top of the tab you are working in. Create one
Set up the view the way you want it: filters, columns, sorting, view settings.
Open the Save dropdown and choose Save as New.
Name it in the dialog, then select Save.
Apply one
Select the Routine chip on the left of the toolbar, then pick a Routine from the list. To stop using it, choose Exit routine at the bottom of the same list.
Update one
With a Routine applied, make your changes and select Save, or choose Update routine from the dropdown, then confirm. This is only available on Routines you are allowed to edit.
Rename or delete one
Open the Routine chip dropdown. Each row carries a pencil icon to rename and a trash icon to delete.
💡 The Save button is a split button: the main action updates the Routine you have applied, and the dropdown holds Save as New and the scope action. If you meant to create a second Routine and instead overwrote the first, this is why.
2. Routines belong to one application
Each application keeps its own separate set of Routines. A Routine you create in Production Control does not appear in MRO, Supply or Planning.
The mechanism is identical everywhere. What differs is only which filters and columns each application offers, so a Routine can only capture what its own application exposes.
💡 If you work across several applications, expect to build your Routines separately in each one. There is no way to copy a Routine from one application to another.
3. Why your Routine takes priority
Pelico views are configured in layers, from the most general to the most specific.
Layer | Set by |
Organization | Your organization's Pelico configuration |
Site | Configuration for your industrial site |
Team | Configuration for your team |
You | Your own preferences |
Routine | You, saved under a name |
A Routine is the most specific layer, so it wins over everything above it. This is why applying a Routine can change a view that looked like it was fixed : you are not overriding a rule, you are applying a more specific configuration on top of it.
💡This also means a Routine only changes your own view. Nobody else is affected when you apply one.
4. Sharing a Routine with your team
In Escalation Room, a Routine can be shared with your team, along with instructions explaining how it should be used.
This is not yet available in Production Control, MRO, Supply or Planning. In those applications, Routines are personal saved views only.