00 — Overview

Queensland Audit Office (QAO) reference application. This is a demonstration prototype modelled on the Queensland Audit Office's public-facing documentation, reports, guidance and activities. It is not an official QAO system and holds no real audit information — every entity, programme, requirement, defect and decision in the demo data is fictional and illustrates the data model and workflow only.

What ERPAM is

The ERP Replacement Assurance Manager turns independent assurance over an ERP replacement into a structured, evidence-backed register. A programme isn't "ready" because the plan says so — it is ready when its requirements are tested, its data has migrated and reconciled within tolerance, its interfaces are proven, its go-live-blocking defects are resolved and evidenced, every readiness area is assessed READY, and an authorised board records a go-live decision. ERPAM holds every one of those links so the state of assurance is always demonstrable — and closure only follows once the go-live conditions are met.

The domain

Replacing a core ERP (finance, HR/payroll) is high-risk: data must migrate completely and reconcile to control totals, payroll must be proven by a parallel run, interfaces to banks and downstream systems must work, and a defect in the wrong place can block go-live. The hard parts are reconciliation (does the migrated data balance?), independent test evidence, and readiness discipline (a conditional go-live is not a blank cheque). ERPAM models all three.

The 22 models by area

Project & Scope (5) - Entity — the audited organisation. · ERPProject — the replacement programme. - LegacySystem — a system being replaced. · BusinessProcess — an in-scope process. - Requirement — a scoped requirement (business/functional/control/data/…).

Design & Data Migration (6) - SolutionDesign — a design/configuration meeting a requirement. - DataObject — a data set to migrate (reconciliation-required flag). - MigrationRule — a source→target transformation/validation rule. - MigrationBatch — an extract/transform/load run with control totals. - Reconciliation — a source-vs-target metric check against a tolerance. - Interface — an integration to/from the ERP.

Testing & Defects (4) - TestCycle — a testing cycle (SIT/UAT/…). · TestCase — a test with expected/actual result. - Defect — a defect (severity, go-live-blocking). · RemediationAction — a fix for a defect.

Evidence & Readiness (4) - EvidenceRequirement — what evidence is needed. · EvidenceSubmission — the evidence provided. - ReadinessArea — a go-live readiness area with a status. · GoLiveDecision — the authorised decision.

Closure (3) - ClosureRequest — a request to close the programme. · ClosureApproval — the authorised outcome. - StatusHistory — the project's lifecycle trail.

(The source pack's DomainEvent outbox is Phase 2 — see page 03.)

The demo scenario

A QAO-style assurance engagement over the Department of Energy & Public Works' Finance & HR ERP replacement (legacy → Oracle Fusion Cloud), programme ERP-2026, at READY_FOR_GO_LIVE:

  • Data migration: vendor master reconciled (5000 → 4998, within tolerance); GL opening balances reconciling (control totals match, sign-off pending).
  • Testing: GL posting PASSED; the payroll parallel run FAILED → blocking DEF-001 (payroll tax over-calculated) → remediated, re-run and evidenced → RESOLVED; a residual DEF-002 (duplicate vendors) remains OPEN.
  • Readiness: cutover & training READY; data & business readiness partially / conditionally ready (DEF-002 + GL sign-off outstanding).
  • Decision: a CONDITIONAL go-live, with programme closure DEFERRED pending the conditions.

45 rows across all 22 models — the whole spine in a realistic "cleared the blocker, conditional go-live, not yet closed" state.