Your SOPs, turned into lessons and tests.
Every company does order entry, receiving and month-end a little differently, and the difference is written down in your procedures. Upload an SOP and Simetta drafts a training module from it on your ERP’s screens: guided lessons, scored tests with fresh data, and a final test, with your own procedure beside every step.
From document to module
An admin uploads the SOP and reviews the plan. Writing the lessons runs in the background.
- 1
Upload the procedure
A Word file, a PDF or pasted text, filed by department in your company’s procedure library. If the SOP was written for a different ERP, say which, and the training is still written on the screens your people will use.
- 2
Review the plan
Simetta reads the whole procedure and proposes a module: the skills it teaches, in order, each tied to the part of the SOP it comes from. Steps that happen outside the ERP, like signing a driver’s paperwork, are listed as not practiced rather than invented. You rename, reorder, add or drop skills before anything is written.
- 3
Lessons and tests are written
Each skill becomes a guided lesson and a scored test on your ERP’s screens, using the same engine and checks as the built-in library. Every draft is checked against the procedure it came from, and against the rule that its answer must score 100 and doing nothing must fail.
- 4
Publish
Publishing approves the drafts that pass and adds a learning path with a final test, ready to assign with due dates like any other module.
Training that matches how your company works
Your rules, scored
If your SOP says a rush order needs a required date and a note for the warehouse, the test checks for both.
Measurable, not a signature
A signed SOP acknowledgment proves someone read it. A scored test on the screen shows they can follow it.
Current when the SOP changes
A new version of a procedure flags the training built from the old one, so it gets rebuilt instead of drifting.
Questions about SOP training
What does a trainee see?
The lesson and the test on the ERP screen, with an “Our procedure” panel quoting the part of your SOP that step comes from. They can open the whole procedure at any time. The final test leaves the procedure out, so passing it shows they know the steps.
What happens when we change the SOP?
Editing the text saves a new version, and any training built from the old version is flagged as out of date, so nobody keeps certifying people on a procedure you have retired.
Which ERPs does it write for?
Any screen in your ERP’s pack: Epicor Prophet 21 or Microsoft Dynamics 365 Business Central. A company moving from one ERP to another can upload its current SOPs and train on the new system’s screens.
Who sees our procedures?
Only your company. Each company has its own procedure library, and the lessons written from it are assigned to your people only.
Do we have to review everything?
You approve the plan before lessons are written, and you publish when you are ready. Drafts that fail their checks are not published, so a trainee never gets a test that can’t be passed.
Five minutes on the demo will tell you more than this page can.
Play a real lesson, take the scored test, then see what your manager would see.