Building it is half the job.
A team needs more than a login and a demonstration. People need to know which work belongs in the system, which sources they can trust, and who will help when a result is wrong.
Start with an existing piece of work
Choose a task the team already understands. Establish the current process, the person who owns it, and a concrete definition of a usable result. Use those same criteria to judge the new workflow.
Train on the real workflow
Have the person who will operate the system run the request, inspect the output, and handle a missing fact. A useful handoff includes the procedure, the sources, the failure path, and the owner of the next update.
Measure use as well as output
The existing manufacturing-network system is used daily by 100+ people. I personally onboarded and trained 20+ employees. Those are separate measures: a useful system has to be adopted as well as built.
Watch for repeat use, time spent correcting work, and places people return to the old process. Those observations should change the workflow and training.