Agentic resource planning: what this means
Agentic Resource Planning (ARP) is a planning approach in which decisions about a company’s resources (inventory, capacity, cash and people) are monitored and prepared continuously by AI agents and carried out with human approval. In short: the ERP records what happened; ARP prepares what should happen next.
What an ERP does, and what it does not
An ERP is a system of record. It records orders, invoices, stock movements and production orders accurately and consistently. It is very good at this, and it remains the backbone of the business.
What an ERP does not do is look at those records, work out what they mean and prepare the next step. “This product will run out in three stores within two weeks” is not a conclusion the ERP draws; a planner, a report and usually a spreadsheet draw it. Decision preparation happens outside the ERP, on people’s time.
What ARP changes
ARP moves that preparation to agents that sit on top of the ERP. The loop has four steps:
1. Read. The agent reads inventory, order, production, finance and HR data from the ERP at regular intervals.
2. Notice. When a threshold is crossed or a pattern shifts, it raises a signal: days of cover are shrinking, a supplier has started arriving late, a cash outflow is coming earlier than expected.
3. Prepare. The signal starts a workflow; the agent gathers the relevant data, weighs the options against your rules and prepares a recommendation with its reasoning: a transfer, an order, a shift change, a collection priority.
4. Submit and apply. The recommendation goes to the responsible person for approval. Once approved, the result is written to the ERP; if rejected, the reason is recorded.
Every step is logged: which data was read, which rule applied, who approved.
ERP and ARP side by side
| | ERP | ARP |
|—|—|—|
| Core job | Record what happened | Prepare what should happen |
| Mode | When a transaction arrives | Continuous monitoring |
| Decision | A person, reading a report | A person, reviewing a ready recommendation |
| Output | Records, reports | Reasoned recommendation, approval, write-back to ERP |
| Relationship | System of record | A layer running on top of the ERP |
ARP does not replace the ERP. The agents cannot work without it; what they read and what they write is the ERP.
Why “agentic” matters
Classic planning software runs a rule or a model and returns a result. An agent takes several steps towards a goal: it gathers data, fills gaps from another source, compares options and, where needed, consults another agent. That is why it produces a piece of work ready for a decision rather than a single report.
The same flexibility brings a responsibility: an agent’s recommendation is not as predictable as the output of a formula. In a well-designed ARP setup, the reasoning, the evidence and the approval step are not negotiable.
When ARP makes sense
– Resource decisions are frequent and slightly different each time (daily replenishment, weekly capacity, monthly cash).
– Decision preparation depends on a few people’s reports and spreadsheets.
– Problems are usually described with the words “we noticed too late”.
If decisions are rare and one-off, the return on an agent layer is low.
Summary
The ERP is the company’s memory; ARP is the layer that looks at that memory and prepares what to do. They work together: the ERP records, the agent prepares, a person approves, and the result is written back to the ERP.