The OAIS Reference Model Explained

The Open Archival Information System (OAIS) reference model is the conceptual foundation on which most of modern digital preservation is built. Originally developed under the auspices of the Consultative Committee for Space Data Systems and later adopted as an international standard (ISO 14721), it answers a deceptively simple question: what does it take for an archive to keep digital information understandable and usable not just for years, but for decades, long after the hardware, software, and people that created it are gone? Rather than prescribe a particular technology, OAIS describes a vocabulary and a set of functions that any organization committed to long-term preservation must address.

Because OAIS is a reference model, it does not tell you which software to buy or which file formats to mandate. Instead, it offers a shared mental map. When preservation professionals talk about “ingest,” “the designated community,” or a “SIP,” they are speaking the language of OAIS. That common vocabulary is what makes it possible for repositories around the world—national archives, university libraries, research data centers, and corporate records programs—to compare practices, audit one another, and build interoperable systems.

What “Open Archival Information System” Actually Means

The word “open” in OAIS does not refer to open-source software or open access to content. It means the standard was developed through an open, public process and is freely available for anyone to read and apply. An “archival information system” in this context is the combination of people and systems that accepts responsibility for preserving information and making it available to a designated community. That phrase—designated community—is one of the model’s most important contributions. It forces an archive to define, in advance, who the future users are and what background knowledge they can be assumed to have. Preservation is meaningful only relative to an audience; a file that no future reader can interpret has not truly been preserved.

The Core Idea: Information Packages

OAIS frames everything an archive holds as information packages, each bundling the content itself with the metadata needed to find, understand, and trust it. The model distinguishes three flavors of package that correspond to three moments in an object’s life:

• Submission Information Package (SIP): what a producer hands over to the archive. SIPs often arrive in inconsistent formats with incomplete metadata.
• Archival Information Package (AIP): the canonical, preserved version the archive maintains internally, enriched with the metadata required for long-term care.
• Dissemination Information Package (DIP): what the archive delivers to a user in response to a request, which may be a transformed or simplified version of the AIP.

Underpinning these packages is a layered notion of information. A raw bitstream is meaningless without representation information that explains how to interpret it, and a complete AIP also carries preservation description information—provenance, fixity (integrity checks), context, and reference identifiers—so the archive can prove the object’s authenticity and trace its history.

The Six Functional Entities

OAIS organizes the work of an archive into six functional areas. These are not departments or software modules but groupings of responsibility that any sound preservation operation must cover:

• Ingest: receives SIPs, validates them, generates AIPs, and extracts descriptive metadata.
• Archival Storage: stores AIPs, manages media migration, and performs error checking and fixity verification.
• Data Management: maintains the databases and indexes that describe holdings and support discovery.
• Administration: handles overall operations, negotiates submission agreements with producers, and enforces policy.
• Preservation Planning: monitors the technology environment and the designated community, recommending format migrations or other actions before obsolescence sets in.
• Access: authenticates users, processes requests, and delivers DIPs.

Preservation Planning deserves special emphasis. It is the function that keeps an OAIS from becoming a passive warehouse. By continuously watching for format obsolescence, shifting user expectations, and aging storage media, it triggers the proactive interventions—format migration, normalization, or emulation—that distinguish genuine preservation from mere storage.

Mandatory Responsibilities and Trustworthiness

OAIS also defines a set of mandatory responsibilities an organization must accept before it can legitimately call itself an OAIS-compliant archive. These include negotiating for and accepting appropriate information from producers, obtaining sufficient control to preserve it, determining the designated community, ensuring the information is independently understandable to that community, following documented policies, and making the preserved information available. These responsibilities became the conceptual seed for trustworthy-repository auditing frameworks (such as the later ISO 16363 audit standard), which assess whether a repository can actually be relied upon over time. In practice, this is where preservation intersects with the broader discipline of records management and the principles championed by professional bodies like the Society of American Archivists.

How OAIS Relates to Records Management Standards

OAIS sits alongside, rather than inside, the records management standards many organizations already follow. Where records standards focus on capturing, classifying, and dispositioning records throughout an active business lifecycle, OAIS picks up the long-tail problem of keeping the permanently valuable subset usable indefinitely. The two are complementary: a records program may apply functional requirements for managing records in digital environments to govern day-to-day recordkeeping, then transfer records of enduring value into an OAIS-aligned repository for permanent preservation.

It is worth noting how the standards landscape continues to shift. In the United States, the National Archives revoked its longstanding endorsement of the DoD 5015.2 records management software certification in 2022, steering agencies instead toward the Universal Electronic Records Management (ERM) Requirements developed through the Federal Electronic Records Modernization Initiative (FERMI). That move reflects a broader trend away from rigid product certifications and toward functional, technology-neutral requirements—precisely the philosophy OAIS embodied from the start.

Why the Model Endures

OAIS has proven durable because it is abstract in the right ways. By describing functions and information flows rather than tools, it has survived multiple generations of storage technology and remains the common reference for digital preservation practice today. For anyone building or evaluating a preservation program, it offers a checklist of questions that never go out of date: Who is your designated community? What representation information travels with your content? How will you detect and respond to obsolescence? Engaging seriously with those questions, more than adopting any particular software, is what makes long-term preservation real. Readers exploring the broader discipline can continue with the archives and preservation topic hub.