Deutsch (Deutschland) 
Polski (PL) 
Independent IFS Cloud practice · Supply Chain
Your ERP already knows - closing the distance between a record and a person
Key takeaways
- Stock under minimum, a receipt past due, an order stuck in a state it should have left days ago - IFS Cloud is holding all of it right now, correct and current, sitting in a projection.
- The failure is rarely the system. It is the distance between a record changing and a human noticing it changed.
- Reporting tells you what happened last month. By then the decision window has closed and you are managing a consequence instead of a choice.
- What a supply chain actually needs is smaller: the short list of things that need a decision today, in front of the person who can make it, before the delivery date turns choice into cleanup.
Ask most operations leaders what is wrong with their reporting and they will describe wanting more of it: another dashboard, another KPI, a deeper cut of the same numbers. That is usually the wrong instinct, because the data behind the decisions that actually matter is not missing. Stock under minimum, a purchase order sitting unconfirmed, a receipt that never matched an invoice, an order stuck in a state it should have left days ago: IFS Cloud is holding every one of those facts right now, correct and current, the moment they become true. The exception is not hidden. It is sitting in a projection, waiting. What is actually missing is the last mile: the short distance between that record changing state and a specific person finding out it changed, in time to still have a choice. This article is the overview of that idea: where the gap comes from, what it costs, and the shape of the fix, with pointers to the deeper articles on specific exceptions.
1.Why does the gap between data and attention exist at all?
ERPs are built to record state accurately, not to decide who should care that the state changed. That division of labour made sense when the alternative was manual pull-based reporting, where someone runs a query and someone reads a printout. It stops making sense the moment the exception is time-sensitive, because a system that only answers when asked is structurally always one step behind the person who did not think to ask yet.
Reporting compounds the problem instead of solving it. A monthly or weekly report is, by design, a summary of what already happened, aggregated after the window to act on any single instance has usually already closed. It is genuinely useful for trend and pattern (is this getting better or worse over a quarter) and genuinely useless for the specific stuck order sitting in front of you today. Teams keep building more reports because reporting is what the tools make easy, not because it addresses the actual gap.
2.What does the attention gap actually cost?
The cost shows up as a series of moments where a decision that was available got replaced by a cleanup that was not:
- A closed decision window. Stock trending toward a shortage is a choice on day one and an emergency purchase on day ten, yet the data was identical the whole time and only the options changed.
- Consequence management instead of choice management. Once the delivery date passes, the team is no longer deciding whether to act but absorbing the impact of not having acted sooner.
- Duplicated watching. In the absence of a system that surfaces the exception, multiple people end up independently checking the same reports, each assuming someone else has it covered.
- Reactive culture. Teams that only ever hear about problems after they land stop expecting to be told in advance, and stop asking for it, which quietly lowers the bar for what “on top of it” means.
The data is not the problem. The last mile between the record and the person is.
3.How do you find where the gap sits in your own IFS Cloud?
Walk your last three genuine surprises (the stock-out nobody saw coming, the order that quietly slipped, the invoice mismatch that surfaced at month-end) and ask one question of each: was the fact that this was going to happen sitting in IFS Cloud before it happened? In almost every case it was. Stock position, order state and age, confirmation status: the projections held the truth well before the surprise landed.
That exercise reliably produces a short list of two or three exception types that keep costing you, and each one becomes a candidate for the same pattern: a Custom Event that watches the relevant state, checks it against a sensible threshold, and tells one named person before the window closes. Two of the most common starting points already have their own detailed treatment: unconfirmed purchase orders and the broader set covered in SCM automations for IFS Cloud.
4.Waiting for a report versus surfacing the exception
Reporting and exception surfacing are not competing solutions to the same problem, because they answer different questions. Reporting answers “how are we doing.” Surfaced exceptions answer “what needs a decision from me today,” and only one of those questions has a closing window.
| Reporting | Surfaced exceptions | |
|---|---|---|
| Answers | How are we doing overall | What needs a decision now |
| Timing | After the fact, on a cadence | As the state changes |
| Who has to look | Someone who remembers to pull it | The specific owner, automatically |
| Best for | Trend, pattern, board packs | The stuck order in front of you today |
| Decision window | Usually already closed | Still open |
Neither replaces the other. A supply chain needs both: the trend view to know if things are improving, and the surfaced exception to act while there is still a choice to make.
5.How do you start closing the gap without a big-bang project?
This is not a platform decision or a transformation programme. It is a small, repeatable pattern you apply to one exception type at a time.
- Pick the exception costing you the most. Use the “last three surprises” exercise above to find it rather than guessing.
- Define the threshold. Agree exactly what state and age should trigger a notice, in terms specific enough to encode.
- Run it in dry-run. Log what would have fired over a real period and check it against what actually happened.
- Route it to one owner. A surfaced exception with no clear recipient is just a new report nobody reads, so name the person.
- Prove it, then take the next exception on the list. Once the first pattern is trusted, the second and third are faster, because the mechanics repeat.
Every one of these rules is built inside the IFS Extensibility Framework (standard Custom Events, Workflows and PL/SQL), so the last mile you close today stays closed after every future upgrade, with no core modification at risk.
6.Frequently asked questions
What is the data-attention gap in a supply chain system?
It is the distance between the moment a record in IFS Cloud changes to a state that needs attention and the moment a specific person actually notices it changed. The data is correct and available the entire time; the gap is purely about whether and when a human sees it.
Isn’t better reporting the answer to this?
Reporting answers a different question (how things are trending), and it is genuinely valuable for that. It rarely closes the attention gap because it is built on a cadence, and most exceptions have a decision window shorter than the reporting cycle.
Which exception type should we close the gap on first?
Whichever one produced your most recent genuine surprise. Walking back through the last three surprises and checking whether the data existed beforehand almost always points directly at the highest-value starting point, rather than requiring a guess.
Is this a big IT project?
No. Each exception type is closed with a single Custom Event scoped to one threshold and one recipient, proven in dry-run before it goes live. It is deliberately small and repeatable rather than a platform change, so it can start with the single highest-cost exception and expand from there.
7.About the author
Dariusz Myśliwiec: 18 years of hands-on IFS practice (Apps 7.5–10 and IFS Cloud). IFS Certified Associate Consultant. PRINCE2® 7. Independent practice based in Kraków, delivered remotely across Europe and globally, so you talk to the consultant who builds it, not a sales layer.
Selected clients: Fugro · LGC · BVI Medical · Betafence (PRÆSIDIAD) · Barlinek · NGK Ceramics · Newag · Oleofarm.
IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.
Close the last mile between your data and your team
Your ERP is not short on data but on a mechanism that gets the right fact to the right person while there is still a decision to make. A 30-minute call is enough to name your highest-cost exception and sketch the fix (fixed price, dry-run before anything goes live).
