Adelaide's Duplicate Image Problem: What Happens Next and the Key Decisions Ahead

South Australian government agencies are sitting on a mounting problem that has been quietly accumulating for years: vast libraries of duplicated digital images embedded in public records, planning documents, and infrastructure databases that are creating storage bloat, complicating archival retrieval, and — in at least some cases — causing version-control failures that affect downstream decision-making. The question is no longer whether to fix it, but how fast, at what cost, and who carries the bill.

The issue has sharpened in 2026 partly because of the scale of digitisation underway across the state. The Lot Fourteen precinct on North Terrace, home to the Australian Space Agency's national headquarters and a cluster of defence and data-focused tenants, has been generating enormous volumes of technical imagery as programs mature. Meanwhile, the Olympic Dam expansion north of Port Augusta and the AUKUS submarine industrial base being built around the Osborne Naval Shipyard in Port Adelaide are each producing engineering documentation at a rate that earlier government records systems were never designed to absorb. Duplicate images — generated when files are re-uploaded, scanned multiple times, or migrated between legacy and modern platforms — are an inevitable byproduct of that pace.

Why the Decision Can't Be Deferred

Storage costs are one pressure. Enterprise cloud storage for government-grade data in Australia has been priced at roughly $80 to $120 per terabyte per month depending on redundancy tier, and agencies carrying duplicate-inflated libraries are paying for capacity they are not meaningfully using. That is money that cannot be redirected to front-line services while the duplication persists.

There is a more serious operational concern underneath the cost issue. When engineers or planners pull an image from a shared repository and cannot quickly determine which version is current — the original scan, the corrected re-upload, or a compressed derivative — they face a version-control risk. In low-stakes environments, that produces administrative friction. In the context of submarine construction documentation at Osborne or site-survey imagery feeding Olympic Dam approvals under the South Australian Resources and Energy Department, the stakes are higher. A wrong image attached to a compliance record is not simply an embarrassment; it can trigger regulatory queries, delay sign-off, or create audit exposure.

The State Records Act 1997 still governs how South Australian public agencies manage and dispose of official records. Any automated deduplication program — regardless of how technically elegant — has to run through an approval process that confirms deleted or consolidated images are not records with ongoing archival value. That legal framework means the fix cannot simply be a technical one. It requires a governance decision, and that decision has to be made at a senior enough level to bind agencies that often operate their own siloed systems.

The Decisions That Will Shape the Outcome

Three choices are sitting in front of SA government planners right now. First: whether to invest in a centralised deduplication platform or let individual agencies handle it internally. A centralised model — potentially run out of the Department for Industry, Science and Resources or through SA Digital, the state's digital transformation office — would allow consistent rules and economies of scale, but requires agencies to cede some control over their own data environments. That is a political negotiation as much as a technical one.

Second: whether the Lot Fourteen digital infrastructure hub, which already hosts some of Australia's most advanced space and defence data operations, could serve as a testbed for a pilot deduplication protocol before any state-wide rollout. Running a pilot in a contained, high-capability environment makes practical sense. It also gives the government a visible example of the approach working before it is mandated elsewhere.

Third: the timeline. The AUKUS submarine program's documentation requirements are intensifying through 2026 and into 2027 as design phases accelerate. If agencies have not implemented workable image-management protocols before that volume peaks, deduplication will become significantly harder and more expensive to retrofit.

The practical next step for agencies is an internal audit — a count of how many image files exist across active repositories, what proportion fail basic hash-comparison uniqueness checks, and what proportion are covered by existing disposal authorities under State Records. That audit does not require new legislation or new funding. It requires someone to assign it, and to set a deadline. Without those two things, the decisions remain theoretical, and the storage bills keep climbing.