Stage 1 of 7
Discover
Start with your hardest JD Edwards workflow.
A conversation and a live demonstration
Who is involved
- Project owner
- IT
- JD Edwards lead
- Fusion5 Digital Workforce team
You bring
- A candidate workflow, the harder the better
- Someone who owns it
We do
- Show the platform working on a demonstration estate
- Map who the workflow runs as, what it reads and writes, and how it is proven
Outcome: A use case with an owner, a value case and a first view of risk.
Stage 2 of 7
Prove
A proof of concept in a non-production environment.
Agreed with you at the start
Who is involved
- Project owner
- JD Edwards administrator
- Fusion5 onboarding engineer and builders
You bring
- A non-production JD Edwards environment
- Two simple use cases to try
We do
- Install the platform and set up the environment
- Deliver the two use cases in non-production
- Follow with a three-month subscription trial if you want one
Outcome: Value shown on real work before any production commitment.
Stage 3 of 7
Decide and plan
Agree the decisions and return the information pack.
Kick-off on day one, information pack back by day three
Who is involved
- Project owner
- IT administrator
- Fusion5 onboarding engineer
You bring
- Your choice of AI route, with Anthropic directly or AWS Bedrock as options
- Your organisation details, region and target go-live
- Your JD Edwards version and tools release
We do
- Run the kick-off and issue the onboarding guide
- Record each decision against your information pack
Outcome: Decisions recorded and the information pack returned.
Stage 4 of 7
Connect
Single sign-on, connectivity and JD Edwards set-up.
About days three to seven, with approvals the main variable
Who is involved
- Entra ID administrator
- Network team
- JD Edwards administrator
- Fusion5 onboarding engineer
You bring
- Single sign-on approval in your own identity system
- Network agreement for the connection
- A JD Edwards administrator session, booked on day one
We do
- Provision your dedicated environment in its own Azure subscription
- Test the connection and verify it end to end
Outcome: People sign in with their corporate accounts, and questions reach JD Edwards as the person asking.
Stage 5 of 7
Your AI account, knowledge and JDE-IQ on a pilot module.
From about day six, with knowledge loading continuing after
Who is involved
- Project owner
- IT
- JD Edwards administrator
- Fusion5 onboarding engineer
You bring
- Your AI account connected to the platform
- Optionally your own documents
- A pilot module and pilot users
We do
- Load the knowledge base and run discovery so JDE-IQ learns your estate
- Switch JDE-IQ on for one pilot module
- Set up branding, access and first assistants, with Academy training
Outcome: Answers use your own tables and codes, and the pilot module is ready.
Stage 6 of 7
Go live
A validation walkthrough with every line seen by you.
A validation walkthrough on a call, around day seven
Who is involved
- Project owner
- JD Edwards administrator
- IT
- Security and compliance reviewers
- Fusion5 onboarding engineer
You bring
- A named operational owner and escalation path
- A spending limit set with your AI provider
We do
- Walk through every validation line with you
- Prove that two people with different JD Edwards security get different results
- Hand over to your pilot users, with admin surfaces and support contacts
Outcome: A signed-off go-live.
Stage 7 of 7
Grow and operate
Your people build more, we run the platform.
Ongoing
Who is involved
- Your builders and administrators
- Fusion5 operations
You bring
- People to build assistants, agents and skills
- A weekly check on each agent, by its owner
We do
- Host, monitor and update the platform on a published cadence
- Give notice before anything changes behaviour
- Support to the contracted level
Outcome: Your team builds more without code, and Fusion5 runs the platform.
