GIAMA-style planning — user plans, custodian plans, annual updates — only works when the register underneath is trustworthy. Claimpal reads the documents your municipality already holds into a fixed asset register that is CIDMS-structured and mSCOA-ready, so every figure in your municipal asset management plan traces to a source record.
An asset management plan is only as strong as the register it cites. Claimpal is an asset intelligence platform that builds that register from the documents your municipality already holds — manuals, inspection reports, finance files, insurance schedules — and exports it CIDMS-structured and mSCOA-ready, with per-asset identification, a condition grade that carries its basis, and GPS-ready fields that match physical asset verification scopes. From there, the condition profile, remaining-useful-life work and renewal budgets in the AMP trace back to audit-ready source records instead of estimates.
Honest scope: Claimpal builds the register and the evidence trail — mSCOA-ready, not mSCOA-certified. It does not write or certify the AMP, it does not replace the professional judgement of your engineers, finance team or auditors, and field verification remains the work of the municipality or its service provider. What it removes is the blank spreadsheet.
Under GIAMA, every user of government immovable assets sets out what it holds, what condition it is in and what it needs — a user asset management plan, revisited every year.
Custodians plan the full life cycle of the portfolio — acquisition, operation, maintenance and disposal — in a custodian asset management plan that has to reconcile with what users report.
These are not one-off documents. GIAMA expects annual updates, and municipal asset management plans are expected to move with the budget cycle rather than gather dust between reviews.
Every plan rests on an immovable asset register that is complete, current and verifiable. This is where most plans quietly fail — the document is written, but the register under it cannot carry the weight.
GIAMA formally binds national and provincial government. Municipalities plan under the MFMA, with National Treasury's CIDMS framework setting the asset hierarchy, condition grading and life-cycle logic an infrastructure asset management plan is built on. The names differ; the discipline — an annually updated, evidence-backed plan on a reliable register — is the same.
Assets that exist on the ground but not in the fixed asset register, and lines in the register carried at a single globular amount nobody can unpack. An AMP built on that inherits every gap on page one.
Finance holds one version, engineering another, the consultant a third. None carries provenance, so useful-life and renewal figures get copied from last year's plan because nobody can defend a change.
An incomplete or unverifiable asset register is a recurring Auditor-General finding against municipalities. A plan that cites that register inherits the same audit risk, however well the document reads.
A physical asset verification fixes the register for a season. Without a structured home for the data, it drifts the day the field teams leave — until the next expensive exercise starts from scratch again.
Manuals, nameplate photographs, condition assessments, job cards, finance files, insurance schedules — scans and handwritten notes included. No sensors to install, no format preparation, and the data stays POPIA-safe.
Make, model, serial, rating, acquisition date and value, outstanding maintenance and insurance status are read out of those documents and attached to the asset they belong to — one identified row per asset instead of one unexplained figure per site.
Each asset is placed in the CIDMS hierarchy with the basis for its classification recorded, and the export follows the same conventions as our mSCOA and CIDMS asset register work: municipality-supplied fields such as the mSCOA item code and useful life are left as clearly-headed blank columns, never guessed.
Per-asset identification, a condition grade on the CIDMS 1 to 5 convention with its basis, and GPS-ready location fields — the columns a physical asset verification scope typically specifies. Export the portfolio as CSV and hand it to finance, engineering or the verification team.
Portfolio condition on the CIDMS 1 to 5 convention, per asset, with every grade carrying the basis it was derived on. Assets whose documents say nothing about condition are left ungraded with the reason stated — never given a flattering default.
The determination belongs to your engineers and finance team. What Claimpal supplies is the evidence it rests on, per asset — age, condition and maintenance history — so the useful-life column starts from records rather than a blank cell.
Open and critical issues, overdue maintenance and insurance status per asset feed the risk section of the plan — which assets carry which service, and where the next failure is likely to land.
A renewal budget built from a graded register can be defended line by line in front of council and the auditors. One copied forward from last year's plan cannot.
Related reading: mSCOA and CIDMS asset register software, municipal infrastructure asset management, and reducing water loss with predictive maintenance.
A municipal asset management plan typically describes the asset portfolio — what the municipality owns, where it is and what condition it is in — then sets out levels of service, remaining useful life, criticality, life-cycle strategies for maintenance, renewal, upgrade and disposal, and the budgets those strategies require. Every one of those sections leans on the asset register. If the register is incomplete or unverifiable, the plan inherits that weakness on page one.
GIAMA is the Government Immovable Asset Management Act of 2007. It requires every user of government immovable assets to produce a user asset management plan (U-AMP) stating what it holds, how it uses it and what it needs, and every custodian to produce a custodian asset management plan (C-AMP) covering the full life cycle — acquisition, operation, maintenance and disposal. Both plans are updated annually and both rest on an immovable asset register. GIAMA formally binds national and provincial government; municipalities plan under the MFMA and National Treasury's CIDMS framework, but the same discipline — an annually updated, evidence-backed plan built on a reliable register — applies.
In municipal practice the terms overlap. The fixed asset register (FAR) is the finance-side record — assets at cost, with depreciation and carrying value — audited under GRAP standards. 'Asset register' is often used more broadly to include the technical view: asset hierarchy, location, condition and maintenance status. An asset management plan needs both views joined, which is why registers split across separate finance and engineering spreadsheets cause so much trouble. Claimpal exports one register carrying financial and technical fields side by side, with municipality-supplied fields left as clearly-headed blank columns.
Claimpal structures and stores the data a verification exercise needs and produces: per-asset identification — description, make, model and serial — condition grading on the CIDMS 1 to 5 convention, and GPS-ready location fields that match what physical asset verification scopes typically specify. The field verification itself — walking sites, tagging assets, confirming existence and condition — remains the work of the municipality or its appointed service provider. What changes is the starting point: the team goes out with a populated register to confirm and correct rather than capturing every asset from scratch, and the results come back into a structured record instead of another spreadsheet.
Annually. GIAMA requires U-AMPs and C-AMPs to be updated every year, and municipal asset management plans are expected to be reviewed each budget cycle so that condition, useful-life and renewal figures stay current. The update is only painful when the underlying register has drifted — which is most of the argument for keeping the register alive year-round instead of rebuilding it every time the plan is due.
No. Claimpal builds the data foundation the plan stands on: the fixed asset register, per-asset condition grades with the basis recorded, and exports structured for CIDMS and ready for mSCOA reporting. The plan document itself — levels of service, life-cycle strategies, budget decisions — is drafted by the municipality's engineers and finance team or its asset-management advisers, and professional judgement stays theirs. What changes is that every figure they put in the plan traces to a source record instead of an estimate nobody can defend.
Upload a handful of files for one site and watch the register build itself. Most teams are live in 2-4 weeks — no sensors, no clipboards, no data-capture project.