08. CDE Archive: Keeping the Project Record After the Project Closes
A CDE archive is the long term home for a project record once delivery has finished. It holds the files, the folder structure, the version history, the metadata and the audit trail in storage your organisation owns, so the record stays complete and accessible without a live Common Data Environment (CDE) subscription sitting underneath it.
Most asset owners do not have one. The project completes, the team demobilises, and the record stays where it was built, inside a licensed platform that renews every year for as long as someone keeps approving the invoice.
This article covers:
What a CDE archive is and how it differs from a backup
Why retention obligations outlast the platforms holding your records
What an archive has to preserve to remain useful
Where the archive should be stored
How to keep an archived project searchable
How archiving fits the ISO 19650 handover process
What is a CDE archive?
A CDE archive is a copy of a completed project, restructured for long term storage and held outside the delivery platform. It is written once, at project close, and read occasionally over many years.
The distinction that matters is custody. An archive that still depends on a vendor licence is not an archive, it is a dormant project you are still paying for. A true archive sits in storage your organisation controls, and stays readable whether or not any commercial relationship continues.
Archiving is also a separate exercise from moving platforms. Where an organisation is leaving a CDE entirely and taking live projects with it, that is a migration, and CDE Migrate™ handles it.
Why retention obligations outlast the platforms holding your records
Infrastructure records have long lives. Rail, water, energy and defence assets carry statutory retention periods measured in decades, and for many assets the obligation runs for the operational life of the structure.
Software does not last that long. Platforms are acquired, rebranded, re-architected and retired. Licence agreements are renegotiated. Storage formats change. Over a thirty year retention period, the probability that the record is still sitting in the same product it was created in is low.
Leaving a finished record inside a live CDE therefore creates a dependency on a commercial relationship continuing indefinitely. That dependency is the subject of Why CDE Migration Matters: The Platform Is Temporary, The Record Isn't, and it applies just as directly to closed projects as to active ones.
CDE backup and CDE archive are not the same thing
Backup and archive are often treated as one line in an information management plan. They address different risks and are sized for different things.
Running an archive on backup infrastructure is expensive, because you are paying for restoration speed you will use once a decade. Running a backup on archive infrastructure is slow at the moment you need it most. Our companion article, CDE Backup: Holding an Independent Copy of Your Project Record, deals with the live side of the pair.
What a CDE archive has to preserve
The most common approach to archiving is to export every file at its current revision into a folder tree on cheap storage. This produces something that resembles the project but cannot answer questions about it.
A usable archive preserves five things:
Folder structure. A document's position in the work breakdown carries meaning that the filename does not. Flatten the hierarchy and you lose the context that tells a reader what the document belongs to.
Version history. Most of the value in an archive is in what was issued at a given moment, not in the final state. An archive holding only the latest revision cannot support a claim, an audit or an investigation.
Metadata. Classification, discipline, suitability, status and approval attributes need to be normalised into a consistent, documented structure so the record is still queryable by someone who never worked on the project.
Audit trail. Evidence of who issued what, when, and against which revision.
Container relationships. Models should still reference the documents that describe them, and transmittals should still reference their contents.
Metadata is where most archives fall short. Large public sector projects routinely require in excess of a hundred metadata fields per document, and different platforms model those fields differently. Mapping them into a documented structure at archive time is considerably cheaper than reconstructing them years later. Field mapping across platform schemas is covered in ISO 19650 metadata compliance across multiple CDEs.
Where the archive should be stored
Moving a closed record from one vendor's platform into another vendor's archive product reduces the licence cost but keeps the dependency in place.
The archive belongs in storage the owning organisation controls directly. That means the organisation's own cloud subscription, under its own identity management, in a region chosen to meet its residency and sovereignty obligations. The global data region map sets out the available options.
Holding the storage account has three practical effects. Access cannot be withdrawn, the price cannot be raised by a third party, and no permission is required to read the record.
Keeping an archived project searchable
A completed infrastructure project can hold hundreds of thousands of documents. Once the people who knew the folder structure have moved on, browsing is no longer a realistic way to find anything.
Search is what keeps an archive usable. SyncSight™ applies optical character recognition and retrieval augmented search across archived project data, so scanned drawings, marked up PDFs and correspondence become searchable text rather than image files. It runs inside the client's own cloud tenancy, which keeps the index in the same custody as the record it indexes.
CDE archives and ISO 19650 handover
ISO 19650 defines four CDE states, and archive is the last of them. It receives the least attention in practice, because it falls due after the delivery team's contract has ended.
The asset information model has to land somewhere the operator can use. Handing over a set of files with no structure, no version lineage and no metadata schema moves the cost of the record onto the party least equipped to carry it. NIST's 2004 study of inadequate interoperability in the US capital facilities industry put the annual cost at US$15.8 billion, with two thirds of it falling on owners and operators during operations and maintenance. Archiving is one of the points where that cost is either created or avoided.
Challenges organisations face when archiving CDE data
No owner for the task. Archiving falls due after the delivery team has left and before the operations team has taken responsibility.
No budget line. Archiving is rarely priced into the delivery contract, so it competes with operational spending after handover.
Unclear retention requirements. Contract, regulator and internal retention schedules often specify different periods, and nobody reconciles them.
Metadata with no documentation. Custom fields are meaningful during delivery and meaningless later unless the schema is preserved alongside the data.
Archives that cannot be searched. Storage is cheap, and an archive nobody can query is a cost with no corresponding benefit.
How long do we have to keep project records after handover?
Longer than the software will last. Retention periods for infrastructure records are commonly measured in decades, and for many assets the obligation runs for the operational life of the asset. Check the contract, the regulator's requirements and your internal retention schedule, then plan on the assumption that the platform holding the record today will not be the one holding it at the end.
Can a project be archived and still be searchable?
Yes. Normalised metadata and an intact folder structure keep a record queryable, and document intelligence applied over the archive adds optical character recognition and retrieval augmented search so image based content is findable as well.
Is a CDE archive the same as a backup?
No. A backup keeps a live project recoverable and has to be current. An archive preserves a finished project cheaply and durably for the length of the retention obligation. They have different access patterns and different cost profiles.
Closing a project should not mean paying for it indefinitely, and it should not mean losing the record either. CDE Archive™ moves a finished project into long term storage in your own tenancy with structure, version history, metadata and audit trail intact, and pairs with SyncSight so the record stays searchable. Get in touch to discuss archiving a closed project, or see how the underlying synchronisation engine works on the CDE Sync™ page.