1. Where your Pelico data comes from
Pelico does not replace your ERP. It reads from it.
Your orders, parts, stock levels and dates are extracted from your own systems, loaded into Pelico, then processed. Pelico is a layer on top of your existing data, not a second place where that data is entered.
This has one practical consequence worth remembering. If a part number, a description or a quantity is wrong in your ERP, it will be wrong in Pelico too. Correcting it in your source system is what fixes it.
2. Data Pelico receives, and numbers Pelico calculates
This is the single most useful distinction to understand.
| Received from your systems | Calculated by Pelico |
Examples | Part numbers and descriptions, order quantities, planned dates, stock on hand, supplier confirmations | Coverage statuses, projected stock, suggested dates, pegging links, suggested actions |
If it looks wrong | Check your source system | Check which calculation produced it |
Most of what makes Pelico useful is in the second column. A coverage status, a projected stock level, a suggested start date : none of these exist in your ERP. Pelico calculates them from the data it received.
💡This is why a surprising number is rarely a data error. The more useful question is which calculation produced it, and what that calculation used. See Pelico’s Algorithms.
Why a Pelico number can differ from your ERP
A difference between Pelico and your ERP is not automatically a problem. The two do not always answer the same question.
Pelico may be calculating something your ERP does not calculate at all.
Pelico may be applying a different assumption, for example ignoring the output of orders whose own components are short.
Your data may have been extracted before a recent change in your ERP.
You and your colleague may be looking at different time horizons or different plant scopes.
3. Checking when your data was last updated
Before acting on any figure, check Last data update in the lower area of the platform.
This shows when Pelico’s latest data processing finished. It is not necessarily the exact moment your data was extracted from your ERP, so treat it as the age of the calculations you are looking at.
When the data is outdated
If the last update is more than 24 hours old, Pelico can display an outdated data warning across Home and the main applications. Some organizations have this warning switched off.
⚠️ If you see an outdated data warning, avoid making important decisions on the figures displayed until you have confirmed the situation. Contact your Pelico administrator or your organization’s Pelico support contact first.
How often your data is refreshed
There is no single Pelico refresh rhythm. Your schedule is defined for your whole organization when Pelico is set up.
Most organizations refresh once a day, early in the morning. Refreshing twice a day or every hour is also common. Some organizations refresh as soon as new data arrives from their systems, rather than on a fixed schedule.
Refreshes run in the background. Pelico keeps serving the data already loaded while the new one is being prepared, so a refresh does not interrupt your work.
💡Ask your Pelico administrator for your own schedule. Whatever it is, Last data update always tells you the age of the figures in front of you.
When the calculations are refreshed
Pelico recalculates when its inputs change. This happens when :
Your data is refreshed from your source systems.
Planned dates or quantities change.
A simulation is created or modified.
Upstream availability changes.
Allocation rules or priorities change.
This is why changing one date can update a large part of your screen. You did not change one number. You changed an input that several calculations depend on.
4. Why some data may be missing
An object that exists in your ERP may still not appear in Pelico, or may not appear where you expect.
Reason | What to check |
Outside your time horizon | Your time horizon in Settings. A Part with no event inside the period may not be found. |
Outside your plant scope | Your scope in the application you are using. Scope is set separately per application. |
Outside your permissions | Your teams and industrial site, with your Pelico administrator. |
Not yet processed | Last data update. A recent change may not be included yet. |
Object type not supported | Not every object type is searchable. See Getting started with Pelico. |
No longer in the current dataset | Closed or archived records may no longer be part of the operational data. |
💡 When a colleague sees something you cannot, compare your time horizon and your plant scope first. These two settings explain most of these differences.
Data that stays in its original language
Changing your interface language translates Pelico’s own labels. It does not translate data that came from your systems, such as Part descriptions, custom field values, ERP values or comments written by other users.
5. Sending decisions back to your systems
Pelico is not only a place to read your data. Two paths can send your decisions back towards your execution plan and your ERP.
Committing a simulation
When you commit a simulation, its changes can be applied to your plan and pushed towards your ERP. See Simulations for what each commit action does.
Push to ERP
You can also edit fields directly in a table, then select Push to ERP. A Batch Modification option applies the same change to many rows at once.
The fields you can edit this way typically include Work Order dates, quantities and statuses, Customer Order and Purchase Order line schedules, Service Orders, Stock Transfer Orders and Purchase Requests.