From Tools Release to agentic AI

Stage 1 — stabilise the traditional upgrade

Move the application and Tools baseline forward, migrate custom Objects deliberately, capture Version configuration and eliminate obsolete technical dependencies. This is where Boomerang, the Commanders, queue tools and attachment conversion belong.

Stage 2 — modernise identity

Give users a modern sign-on path and establish how enterprise identity maps to JDE and other protected resources. This becomes the trust foundation for later automation.

Stage 3 — make business actions explicit

Use Orchestrations for bounded business capabilities. Name them well, describe them well and give them contracts that applications and agents can understand.

Stage 4 — expose deliberate tool surfaces

Add MCP where runtime discovery and structured tool calling are useful. Keep servers focused: JDE execution, metadata, logs and files should not become one giant undifferentiated tool server.

Stage 5 — add the agentic layer

Introduce a conversational interface that can combine retrieval, reasoning and approved tool calls. At this stage, the AI is not being trusted with raw ERP access; it is choosing among capabilities you have already made explicit.

Stage 6 — automate recurring work

Once a workflow is predictable enough, scheduled or event-driven agents can execute it with the same policy and tool boundaries. The distinction between interactive and automated execution should remain visible in audit and governance.

The roadmap at a glance