ERP Replacement Assurance Manager (ERPAM)
Make ERP-replacement assurance a live, connected model — from the programme and its scope, through requirements and design, data migration and reconciliation, interfaces, testing and defects, to the evidence, readiness and the authorised go-live decision and programme closure.
Its central question:
For an ERP replacement, is the scope covered by tested requirements, has the data migrated and reconciled, are the interfaces proven, are the go-live-blocking defects resolved, and is every readiness area evidenced — so the go-live decision rests on assurance rather than assertion?
It sits beside the programme's delivery tooling (requirements, test management, migration, defect trackers) — it owns the independent assurance view: the scope → migration → test → defect → evidence → readiness → go-live → closure spine.
The assurance spine
Entity / ERP Project → Legacy System / Business Process / Requirement → Solution Design → Data Object → Migration Rule / Batch → Reconciliation → Interface → Test Cycle → Test Case → Defect → Remediation Action → Evidence → Readiness Area → Go-Live Decision → Closure Request → Closure Approval, with a Status History trail on the project.
The documents
| Page | What's in it |
|---|---|
| 00 — Overview | What the app is, the domain, the 22 models by area, the demo scenario |
| 01 — Quick Reference | Menu map, every model, key status vocabularies, the demo data set |
| 02 — System Diagram | The replacement-assurance data model as a diagram (+ interactive viewer) |
| 03 — Phase 2 Scope | The runtime not yet built: the project/defect state machines, go-live readiness guards, reconciliation checks and the DomainEvents outbox |
Status
Phase 1 (built): all 22 models render as an AI-Safe CRUD register with a dashboard, seeded with one coherent QAO-style ERP-replacement assurance engagement (45 rows) — a blocking payroll defect resolved and evidenced, a residual data defect still open, and a conditional go-live with closure deferred pending conditions.
Phase 2 (scoped, not built): the project/defect lifecycle state machines, the go-live
readiness guard rules (all mandatory readiness READY, no go-live-blocking defects,
mandatory reconciliations passed), evidence/plan versioning, and the DomainEvent
outbox — see page 03.
Prototype system; draft. All entities, systems, requirements, migrations, defects, evidence and decisions in the demo data are fictional; values demonstrate structure only and are not real audit findings.