So the deadline behind the question does not exist. That changes what a JD Edwards owner can do about AI, because the decision can be made on evidence from the plant and the ledger, with no end-of-support date forcing it.
Note one: the doorway was built before the agents arrived
Oracle describes the Orchestrator as the way customers "collect, filter, analyze, and act on real-time data" from connected devices, turning outside data into business processes inside EnterpriseOne. An orchestration is a named, tested routine. It enters a work order or a goods receipt through the same applications a person would use.
An AI agent should be limited to exactly that. Give the agent no path to the database. Give it a short list of orchestrations it may call, each with an owner in the business, and read the log.
We directed East Africa's largest JD Edwards programme, bringing ten sugar factories onto one integrated platform. What stays with me from that work is how much of a mill's truth arrives from outside the ERP: the weighbridge ticket, the laboratory reading, the bearing temperature. A governed doorway for those signals is worth more to a plant manager than any assistant on a screen.
Note two: the upgrade became a habit
EnterpriseOne 9.2 became available in October 2015 and has never been replaced. Oracle delivers new functionality as numbered updates to that one code line. Release 26 arrived in October 2025 and added an Enterprise Automation Dashboard, a single view of process models and their measures.
Oracle recommends taking those releases regularly. Treat them like planned maintenance: a fixed window, a regression pack, a finance controller who signs off before month-end. An owner who skips years of updates rebuilds the big upgrade they thought they had escaped.
Note three: reasoning sits outside, the record stays inside
Oracle's Release 25 announcement shows the pattern: an orchestration sends an image to Oracle Cloud Infrastructure's Vision service and returns the result to the Quality Management application. Document Understanding and Language services are called the same way.
The division of labour is simple. The ERP holds the record and the rule: who may approve, what a work order costs, which period is open. The cloud layer does the reading and the reasoning. Nothing learned in the cloud becomes a transaction until an orchestration posts it.
Stay, move or leave: decide with evidence
Stay and extend. Right when the processes that make the business distinctive, such as cane procurement or grower payments, already run well in JD Edwards. The cost is discipline: a release cadence, retired customisations and people who know the Orchestrator.
Move to Oracle Cloud. Oracle states that the same EnterpriseOne application runs on-premises or on its cloud infrastructure, which changes the hosting and little else. Moving to Oracle's Fusion cloud applications is a new implementation. It suits a group that wants standard finance processes more than it wants its own plant processes.
Leave. Right when the parent has standardised on another platform, or when the business has changed shape so far that the original design no longer fits.
The evidence that separates these paths is ordinary. Count the customisations still in use. Count the months since the last release was applied. Price one process, end to end, on each path.
Where the pressure is coming from
Policy is pushing processors and manufacturers towards connected plants. Kenya's Sugar Act, 2024 directs 15% of a new sugar levy to factory development and rehabilitation, money that can modernise old mills. In India, ethanol blending in petrol rose from 10% in the 2021-22 supply year to 20% in the 2025-26 supply year to June 2026, and a mill supplying that programme now runs a distillery schedule beside the crushing schedule.
A maintenance planner's morning in 2029
Picture the maintenance planner at an agro-processor with several factories. At six, a vibration sensor on a mill turbine gearbox crosses its limit. An orchestration reads the signal, checks the asset's history and raises a draft work order with the evidence attached.
By the time she arrives there are four drafts in her queue, ranked by the crushing hours at risk. She approves two, defers one to the weekend stop and rejects the fourth because she knows that sensor was moved last week. The software prepared the work. The approval is still hers, and the ERP shows it.
Ninety days, one orchestration
This quarter, choose one signal your plant already produces and one transaction it should trigger, and build that orchestration with a named approver. It will show how current your estate is.
An Dependable Core readiness review will then set the three paths side by side for your own JD Edwards estate, with the evidence for each.