For Data Governance & Compliance Officers

Conformance as a by-product, not a documentation project.

You've seen what happens when "ISO 55000 alignment" means a binder written after the decisions were made. AIPP generates the evidence as the planning happens — measurable data quality, reproducible decision runs, and a provenance registry that makes over-claiming structurally impossible.

Governance walkthrough →Conformance map ↓

"My problem isn't producing documents. It's that the capital program and the documents describing it are built in different tools, by different people, at different times — so under audit, the numbers never quite reconcile, and I'm the one explaining the gap."

— The reconciliation problem every governance officer inherits. AIPP removes the gap by construction: one dataset, one run, every output.

The conformance map

iso 55000Line-of-sight evidence generated in-flight: every prioritisation run is recorded with engine version, configuration version, executor and timestamp; every score decomposes into its contributing factors. Decision-making criteria are explicit, versioned and reproducible — the clause-level asks, answered by the data model itself.

iso 8000-8Data quality is measured, not asserted. Per-record scoring against configurable, critical-weighted rules across DAMA dimensions (completeness, validity, consistency) — the syntactic/semantic/pragmatic measurement structure ISO 8000-8 formalises. Rules are per asset class and per business vertical, and every rule change is logged.

provenanceA machine-readable standards provenance registry declares the status of every content pack — REAL, REPRESENTATIVE, TEMPLATE or SCAFFOLD. The product cannot claim TfNSW "compliance" when the honest status is "aligned, pending validation against your published standard". That guardrail is code, not policy.

audit trailField-level change logs on every write — who, what, when, old value → new value — including configuration changes. Weight changes, rule edits and industry-pack applications are all first-class audit events.

sealed packsEvidence packs seal with SHA-256 over a canonical payload: the portfolio snapshot, the active configuration, the decision-run lineage. Any party can independently re-hash the payload and verify integrity. Tamper-evidence you can demonstrate in the meeting.

honest uncertaintyFigures backed by weak data are visibly hedged — data-quality badges on the numbers themselves, not a footnote. Your auditors will trust a system that admits what it doesn't know far faster than one that's always precise.

⚖

Scope honesty: AIPP evidences the capital planning decision chain. It is not a records-management system, not a full ISO 55001 management system, and its regulator packs are validated against your published standards during onboarding — the provenance registry will show you exactly which content is representative versus template or scaffold on day one — and nothing is labelled "compliant" until it is validated against your published standard.

In the demo

The three artefacts to inspect

artefact 1

A decision, decomposed

Pick any ranked asset. Open its factor breakdown, the weights used, the data-quality score and the run ID. Ask "why this number?" of anything on screen.

artefact 2

The change log

We'll change a prioritisation weight live, re-rank the portfolio, and show you the recorded event — then diff the plan against its frozen baseline.

artefact 3

A sealed pack, verified

Export an evidence pack, then independently re-hash the payload and match the SHA-256. Bring your own hashing tool if you like.

Bring your audit findings from last year

A working session mapping each finding to where AIPP would have evidenced it — or where it honestly wouldn't. You'll leave knowing the difference.

Book the walkthrough →Read: what IPART actually wants