BrainStorm
The ultimate complete AI solution for JD Edwards® — conversation, search and orchestration over your own data, under your own identity, in your own language, on your terms. No extra components to install or manage.
BrainStorm is the whole stack from the user's screen to the JDE record: a web-based chat application with its own built-in webserver, a retrieval system over your own documents - also built-in, an extensible set of MCP servers including one for JDE Orchestrations. Just add the LLM of your choice — including local ones. Every conversation runs under the user's JDE identity. No parallel API. No shadow integration. No surprises.
Ask questions about your data and get answers that cite their sources. Trigger Orchestrations conversationally and have the same audit trail JDE would have produced if the user had clicked through all the screens in JDE. Drop vendor manuals, internal policy docs, media objects, or engineering specifications into a folder — minutes later it's all part of the conversation, literally at your fingertips and the user can open and see the exact page the answer came from - instantly.
- Web app, mobile install — one URL, one tap.
- Nine languages, auto-detected.
- Local LLM (Ollama) or hosted frontier (OpenAI, Claude, Gemini).
- Every answer cites its sources, with the source pages in view.
- Runs under the user's JDE identity. No shadow integration.
- Extensible via standard MCP servers.
Don’t ask for an application. Ask for the outcome.
JD Edwards® Orchestrations already changed what enterprise functionality can be: powerful read/write services, built through AIS, without the weight of traditional custom development. BrainStorm turns that capability into a new way to work. Instead of asking for a new application, a new batch job, or a new set of custom objects, the user simply asks for the business outcome they need — and the LLM searches, understands and invokes the right Orchestrations to get it done. A completely new paradigm. The LLM can also search any supporting documentation, perfecting its answer on the fly.
This moves JDE enhancement, customization and development from the legacy development-heavy model to a lighter modern orchestration-first approach. Requirements become smaller, clearer and faster to deliver. Solutions become easier to maintain, easier to secure and easier to evolve — with less reliance on invasive customisations, fewer long delivery cycles, and a much faster way to turn business needs into working enterprise processes.
It is not just another user interface for JD Edwards. It is a revolutionary new way to work with JDE — the single all-encompassing chat interface your users will ever need for any task, and it also doubles-up as a mobile app.
- Development-heavy → much lighter orchestration-first
- New custom objects → existing, approved services
- Long delivery cycles → small, clear, readily achievable requirements
- ‘Yet another application’ → the only interface they need
What it does
- Conversation, not click-paths. Ask in natural language. Get a detailed written answer with citations, grounded in fact. Follow up. Switch topic. The chat remembers the conversation; the user doesn't have to.
- JDE orchestration, conversationally. Through an MCP server that exposes your existing Orchestrations as typed tools, the user can trigger any orchestration they are already permitted to call — from chat. Same authentication. Same audit.
- Provide your own documentation. Vendor manuals, internal policy documents, engineering specifications, training material, change logs — whatever your team needs to consult. The built-in retrieval engine ingests it and the chat can quote from it.
- Source-anchored answers. Every claim links to the page it came from. The user sees what the AI saw — not just the model's summary of it.
- Bring your own LLM. Local models via Ollama for cost and privacy. Hosted frontier models (OpenAI, Claude, Gemini) when the question warrants it. The choice is configuration, not architecture.
Sources & citations
The retrieval engine automatically digests any documents dropped into a configured folder. PDFs — including scanned ones.
When the chat draws on a document to answer a question, the response includes inline links to the relevant document pages. Not a paraphrase, not a snippet, not a reformulation. The actual page.
This matters in two directions. The user trusts an answer that comes with its receipts. And the auditor can confirm, after the fact, exactly what evidence the model was working from.
Per-corpus access control means a user only sees citations from corpora they are entitled to see. A field engineer sees vendor manuals; a payroll clerk does not. The same identity that governs JDE access governs corpus access.
For CNC & security
- The user's JDE identity, end to end. The user signs in once. From that point on, every Orchestration call — whether triggered conversationally or directly — runs under their real JDE user. Not a service account. Not a pool. Not a proxy.
- No parallel API. BrainStorm reaches JDE only through the same AIS surface every other AIS client uses. Whatever Orchestrations your CNC team has already approved is the entire menu.
- No shadow integration. Nothing reaches into the JDE database directly. Nothing bypasses orchestration security. Nothing escalates privilege.
- Audit is JDE's own. Because the calls are real AIS calls, JDE's audit captures exactly what would have been captured if the user had clicked through the screens. No separate audit log to reconcile.
- Corpus access scoped per user. Document corpora are tagged with the personas or groups permitted to consult them. The chat never quotes from a corpus the current user cannot see.
- Local LLM option for sensitive content. Configure BrainStorm against a locally hosted model and no part of the conversation, retrieval, or response leaves your LAN.
Languages & mobile
The UI runs in nine languages and detects the user's preference automatically — English, German, French, Spanish, Italian, Portuguese, Polish, Czech and Hungarian. The conversation itself is in whatever language the user types in.
BrainStorm is also a Progressive Web App. On a phone it installs to the home screen with one tap and runs full-screen, like any native app. No App Store. No Play Store. No code-signing. No corporate MDM hoop-jumping. The URL is the install.
The result is the JDE mobile app every other JDE mobile app wishes it were — and once your team has it, they stop wanting any other.
Licensing
Annual subscription, sized by named users and production / non-production servers per edition. A fixed-price Pilot / Proof-of-Value is available to remove buyer risk. Contact us for a demo or quote, or see the pricing page for editions and indicative figures.
Common JD Edwards AI questions
These pages explain the specific problems BrainStorm solves for JDE teams: conversational work, document-grounded answers, orchestration execution, local models and mobile use.