Dates and Delays

Who is this for ?

What you will learn :

Every date in Pelico is one of two things, and telling them apart saves a lot of time.

💡Pelico never changes a planned date on its own. It calculates what your dates imply, and it suggests better ones. Moving an order is always a decision someone makes.

Three calculated dates answer three different questions. They are easy to mix up because their names are similar, so it helps to remember the question each one answers.

The first is the deadline you are working against. The second is your fallback if you cannot meet it. The third tells you where to start.

⚠️ The next enablement date appears in the Work Order Book as the Suggested Start Date column. Same number, two names. If you compare this documentation with your screen, that is why.

One timeline carrying all three dates, each labelled with the question it answers. Already listed as a visual to add in Stock Projection, so produce it once and use it in both articles.

A delay in Pelico is the gap between when material arrives and when it is needed. The sign is what matters, and it is easy to read backwards.

So a delay of 5 means material lands five days too late. A delay of −3 means it lands three days early.

You can see delays in the Event Explorer, alongside the upstream and downstream links of an event, and in the upstream and downstream event columns of the Books where they are available.

This is the most common confusion about dates in Pelico, and it changes what you should do about it.

The two are independent. An order can be late and fully covered. It can be blocked and not yet late. It can be both.

⚠️ A plant with many late orders and good coverage has a scheduling problem, not a material problem. If you read those two as the same thing, your team ends up chasing suppliers when the real issue is releasing work on time.

See Pelico’s Algorithms for how coverage itself is calculated.

Calculated dates are counted in working days, in the time zone of the plant concerned, not in calendar days.

This is usually why a suggested date lands further out than you expected. Five working days across a weekend is seven calendar days.

⚠️ Pelico excludes weekends, but it does not know your factory calendar. Public holidays, plant shutdowns and shift patterns are not part of these calculations. A suggested date can land on a day your plant is closed.

Calendar strip showing a five working day span crossing a weekend. Already listed as a visual to add in Pelico’s Algorithms, so reuse the same one.

A suggested date sometimes looks wrong to the people who would have to meet it. There are two reasons, and neither is a fault in your data.

The next enablement date tells you when material and upstream work allow a start. It does not ask whether you have the capacity to start. There is no work centre capacity in that calculation.

So if your shop floor says the date is impossible, that is not a contradiction. Pelico was never asked that question.

The calculation assumes every sub-assembly involved is produced in an optimised way. Your real plan for those sub-assemblies may be different.

This is why moving an order to its suggested date does not guarantee it becomes covered. If it stays blocked after the move, this is usually the reason.

Pelico does not quietly reschedule an overdue order. It keeps it at its planned date and applies specific rules.

⚠️ This is why today's stock figure can differ from what is physically on your shelves. Overdue orders that nobody rescheduled are replayed at their old planned date.

Before investigating a date, check Last data update. If your data was loaded this morning, a change made in your ERP this afternoon is not in Pelico yet.

This is worth ruling out first, because it looks exactly like a calculation problem. See the Data article.