ERP Migration Data Validation demo
Each migrated object is sampled by stratum and traced to its source document, not the old ERP; each stratum gets a 95% error bound, failures are swept in full, and owners sign object by object. 1:29
What the demo shows
ERP data migration validation for device makers: migrated records sampled and traced to source
The Bound Plot shows every stratum as a point: records traced to source across, the 95% upper bound on its error rate up, the go-live line across the middle. Points fall as records trace clean. The hospital system's consignment locations stay above it, 7 of 60 wrong, so the agents sweep all 2,140 and find 214 still pointing at a storage room closed on Sep 1 while the old ERP was frozen. The steward corrects them from the agreement, a re-check finds none left, and the process owner signs after opening corrections he did not make.
Transcript
- ERP Migration Data Validation checks Tarnbrook's migrated records against their source documents.
- Since February 2026, FDA expects that software to be validated; a perfect copy can still be wrong.
- Larkmoor's locations stay above the line: seven of sixty point to a room closed in September.
- The agent sweeps all 2,140 Larkmoor locations and finds 214 wrong.
- Cressida, the steward, reads the amendment and accepts the corrections rack by rack.
- The re-check finds none left.
- She opens the two clean records drawn for her, each against its agreement, then signs as verifier with her own password.
- Obiora, the process owner, opens two corrections drawn for him, work he did not do,
- and approves consignment locations for go-live.
- 214 locations fixed from the agreement, and three lost holds stopped before cutover.
- Built on Botminds: agents, data, screens and governance on one platform.
The narration as written for the film. Captions are on the player.