Agentic Resource Planning (ARP): The Next Letter After ERP
The P in ERP has been quietly broken for thirty years. ERP systems record orders, inventory, and history beautifully. But the actual production plan, the one that decides what runs tomorrow, still gets built by one person in a spreadsheet at 5am. Agentic Resource Planning (ARP) closes that gap: software that reads the data and writes the plan itself.
This post defines ARP cleanly, traces how we got here, and explains why most food and beverage plants are not ready for it yet.
What is Agentic Resource Planning (ARP)?
Agentic Resource Planning is software that reads orders, inventory, machine status, and constraints, then builds the production plan itself and brings the judgment calls to a named human for sign-off. ERP is the system that remembers. ARP is the system that works. The E records what happened. The A decides what happens next.
Semia is the AI employee for food and beverage production planning. It reads orders, stock, ingredients, attendance, machine status and shelf-life risk, writes tomorrow's plan, and asks a named human to sign off.
That last clause is the whole point. ARP does not replace the planner. It does the assembly work the planner has been doing by hand, then hands back the decisions only a person should own.
Why has the "P" in ERP been a lie for 30 years?
ERP promised "planning" but delivered record-keeping. The system stores every order, every stock level, every past run. Then a human exports it to Excel and builds the real plan by hand. The P was always a person, not the software. Most plants just stopped noticing.
Walk into almost any food or beverage plant and you find the same scene. A planner arrives early, pulls numbers out of the ERP, and rebuilds tomorrow's schedule in a spreadsheet they have maintained for years.
The ERP knows that 4,000 units are due Thursday. It does not know that you never run Product B right after Product A because the allergen washdown costs you ninety minutes. It does not know that one supplier slips every time it rains.
So the planner carries that logic. The ERP holds the data. The plan lives in someone's head and a spreadsheet that only they understand. That is the lie: the most expensive letter in the acronym was never automated at all.
How did we get here? MRP to MRP II to ERP
The acronym kept growing while the planning kept staying manual. MRP arrived in the 1960s to calculate material requirements from a bill of materials. MRP II added capacity and scheduling logic in the 1980s. ERP wrapped finance, HR, and the supply chain into one system in the 1990s. Each step recorded more. None of them made the daily decision.
Here is the short history, and why it matters for what comes next.
MRP (1960s). Material Requirements Planning answered one question: given a forecast and a bill of materials, what do we need to buy and make? It was a calculator for materials. Useful, but blind to the shop floor.
MRP II (1980s). Manufacturing Resource Planning added machines, labor, and capacity. It could tell you whether a plan was feasible in theory. It still could not write the plan that survived contact with a broken line or a late truck.
ERP (1990s). Enterprise Resource Planning connected planning to accounting, procurement, and inventory across the whole business. It became the system of record. And the system of record is exactly what it stayed.
Every era added memory. None added judgment. The planner kept doing the one thing the software never learned to do: look at today's mess and decide.
What makes ARP different from ERP?
ERP answers "what do we have and what happened." ARP answers "what should we do tomorrow." The difference is not a better report or a smarter dashboard. It is a system that produces a finished plan, flags the exceptions, and routes the hard calls to a human instead of waiting for a human to do all of it.
| ERP (the system that remembers) | ARP (the system that works) | |
|---|---|---|
| Core job | Records orders, stock, history | Builds tomorrow's production plan |
| Output | Reports and data | A finished, runnable plan plus flagged exceptions |
| Who makes the plan | A human in Excel | The system, with a human sign-off |
| Handles tribal rules | No, lives in the planner's head | Yes, once captured and confirmed |
| Role of the person | Does the work | Owns the judgment calls |
ERP and ARP are not rivals. ARP sits on top of the ERP, reads from it, and does the job the P always implied. Think of ARP as the next letter, not a replacement for the last one.
Why are most plants not ready for ARP yet?
Two things block ARP: messy data and undocumented tribal knowledge. The ERP is full of stale records, duplicate items, and fields nobody trusts. And the rules that actually run the plant were never written down. They live in one planner's memory. You cannot automate logic you have not captured first.
This is the part people skip, and it is the part that decides whether ARP works or just produces a faster wrong answer.
Most plants run on invisible logic. Why you never sequence Product B after Product A. Which supplier slips when it rains. Which line runs hot on humid days. None of that is in the ERP. It is in one person's head, and that person is usually the one you can least afford to lose.
If you automate before you capture that logic, you get a confident, fast version of the same guess. The plan looks polished and is quietly wrong, because the system never learned the rules the planner knew by heart.
So the first move toward ARP is not installing software. It is capturing the real operating logic and letting the people who own it confirm it. Capture before automation. That sequence is not optional, it is the difference between a useful AI employee and an expensive one.
Where does the named human fit in ARP?
The human moves from doing the work to owning the decisions. ARP builds the plan and surfaces the exceptions: a shelf-life risk, a capacity clash, a supplier flag. A named person reviews those calls and signs off before anything reaches the floor. Authority stays human. The grind does not.
This matters for more than comfort. When a plan goes to the floor, someone is accountable for it. ARP keeps that accountability explicit by requiring a named sign-off, not a silent auto-publish. It is one piece of the larger discipline of production planning for food and beverage manufacturers.
It also protects against the failure mode of "automated and wrong." A person who knows the plant catches the exception the model misjudged. The system gets faster every day. The judgment stays where it belongs.
That is why named-human sign-off is built into the definition of ARP, not bolted on after. Agentic does not mean unsupervised. It means the system does the assembly and the person makes the call.
What does ARP look like in practice?
In practice, ARP turns a three-hour morning into a fifteen-minute review. The system reads overnight orders, current stock, ingredient availability, who showed up, which machines are running, and what is about to expire. It writes the plan. The planner reviews the flagged exceptions and signs off.
With one design partner, that shift has been roughly 12x faster, from about three hours a day of manual planning to around fifteen minutes of review.
The planner does not disappear. Their day changes shape. Instead of rebuilding a spreadsheet from scratch every morning, they spend their attention on the handful of decisions that genuinely need a human: the allergen sequencing call, the shelf-life tradeoff, the late supplier.
This is the same engine behind modern AI production scheduling for food and beverage, applied to the whole resource plan rather than a single line.
Common questions about ARP
Is ARP just ERP with AI bolted on? No. ERP records data. ARP produces the daily plan and routes decisions to a human. You can run ARP on top of your existing ERP. It reads from the system of record and does the job the record was never built to do.
Does ARP replace the planner? No. It removes the manual assembly and keeps the planner in charge of the judgment calls. The named-human sign-off is part of the definition, not an optional setting.
What do we need before adopting ARP? Captured operating logic. The rules that run your plant have to be written down and confirmed by the people who own them before you automate. Capture before automation.
Why does this matter now? Because most corporate AI initiatives still deliver no measurable return, according to the MIT study. The projects that fail usually automate before they capture. ARP works only when the invisible logic is captured and a human stays accountable.
The next letter after ERP
ERP gave us a system that remembers. For thirty years we called it planning while a human did the planning by hand. ARP is the next letter: a system that reads the data, writes the plan, flags the exceptions, and brings the real decisions to a named person.
It is not magic and it is not unsupervised. It is the planner's morning grind, captured and automated, with authority left exactly where it belongs.
If you want to see what Agentic Resource Planning looks like for your plant, book a demo: https://calendly.com/nick-semia/30min