Skip to main content
Records Authority
Category: Digital Preservation

Open Archival Information System (OAIS)

Also known as: OAIS, OAIS reference model, ISO 14721, OAIS Reference Model
Simply put

An Open Archival Information System (OAIS) is a conceptual framework that describes how an archive can preserve digital materials and keep them accessible over the long term. It defines an archive as an organized combination of people and systems that has taken on responsibility for preserving information and making it available to those who need it. The framework is widely referenced as a foundational model for building and operating digital repositories.

Formal definition

OAIS is a reference model, published as ISO 14721, that provides a conceptual framework and common vocabulary for archival systems dedicated to the long-term preservation of and continued access to information, with particular emphasis on digital materials. It defines an OAIS as an archive, an organization of people and systems, which may sit within a larger organization, that has accepted responsibility for preserving information and making it available to a designated user community. Sources indicate that an OAIS-type archive is expected to meet a set of minimum responsibilities, though the specific responsibilities and detailed functional entities should be consulted directly in the standard rather than paraphrased here. As a reference model, OAIS describes conceptual roles, functions, and information objects rather than prescribing a specific implementation or technology; the manner in which it is applied depends on organizational context and policy.

Why it matters

The OAIS reference model matters because it provides a shared conceptual vocabulary and framework for organizations grappling with a distinctly modern challenge: preserving digital materials and keeping them accessible over timeframes that outlast specific technologies, file formats, and systems. Before the model gained wide adoption, institutions building digital repositories often lacked a common language for describing what a preservation archive must do and which roles it must fulfill. By defining an archive as an organized combination of people and systems that accepts responsibility for preservation and access, OAIS gives records managers, archivists, and repository designers a foundation on which to reason about long-term digital custody in a consistent way.

The model is widely referenced as a foundational standard for digital preservation, and it underpins how many repository designs and related preservation frameworks are conceived. Its emphasis on defining a designated user community, and on the archive's accepted responsibilities, helps organizations articulate not only how they store digital materials but why, for whom, and under what obligations. This is significant because long-term digital preservation involves risks, such as format obsolescence and loss of context, that differ from the concerns of short-term storage or general information management, and OAIS offers a structured way to frame those concerns.

It is important to be clear about the model's scope. OAIS is a conceptual reference model rather than an implementation specification, so it describes roles, functions, and information objects at an abstract level rather than dictating particular technologies or procedures. Organizations should not treat conformance to the model as equivalent to a guarantee of successful preservation; how the model is applied depends heavily on organizational context, policy, and resourcing. The detailed responsibilities and functional entities are best consulted directly in the published standard rather than inferred from summaries.

Who it's relevant to

Digital preservation specialists and archivists
Those responsible for preserving digital materials over the long term often use OAIS as a foundational reference for designing and describing their repositories. The model gives them a shared vocabulary for articulating preservation responsibilities, roles, and the notion of a designated user community, which supports consistent planning and communication across institutions.
Repository designers and system architects
People building digital repository systems may draw on OAIS to structure how they think about preservation functions and information objects at a conceptual level. Because the model does not prescribe specific technologies, architects can use it to reason about requirements while retaining flexibility in how they implement them within their own organizational context.
Records managers and information governance professionals
For those whose remit extends to the long-term retention of digital records, OAIS offers a way to frame preservation and continued access as a distinct concern from short-term storage. It can help clarify what it means for an organization to accept responsibility for keeping information usable over time, though it should be understood as a preservation-focused model rather than a complete governance framework.
Memory institutions and their governing bodies
Libraries, archives, and similar institutions, along with the organizations they may sit within, can use OAIS to define and communicate the responsibilities their preservation programs undertake and the communities they serve. This supports accountability and planning, while recognizing that alignment with the model depends on organizational policy and resourcing.

Inside OAIS

Reference Model
OAIS is a conceptual reference model that describes the functions, responsibilities, and information flows involved in the long-term preservation of digital information. It provides a common vocabulary and framework rather than a prescriptive implementation, and it originated in the space data community before being widely adopted across archives and digital preservation more broadly.
Information Packages
The model distinguishes among the Submission Information Package (SIP) received from a producer, the Archival Information Package (AIP) stored and preserved within the archive, and the Dissemination Information Package (DIP) delivered to a consumer. These constructs describe how content moves through and is transformed within the preservation environment; the specific packaging technologies used are an implementation matter.
Functional Entities
OAIS typically describes a set of high-level functional areas, often characterized as Ingest, Archival Storage, Data Management, Administration, Preservation Planning, and Access. These represent groupings of responsibilities rather than mandated organizational units or software modules, and how they are realized depends on the implementing organization.
Designated Community
A defining concept in OAIS is the Designated Community, the identified group of users the archive intends to serve and for whom preserved information must remain understandable over time. Preservation decisions, including what representation information to retain, are framed in relation to this community's assumed knowledge base.
Representation Information
OAIS emphasizes preserving not only the content data object but also the information needed to render, interpret, and understand it, so that the object remains usable by the Designated Community. This supports the recordkeeping properties of usability and, in a preservation context, ongoing intelligibility.
Environment Roles
The model situates the archive between Producers, who supply information, and Consumers, who use it, with Management providing overarching direction. These roles describe relationships and responsibilities rather than specific job titles or governance structures.

Common questions

Answers to the questions practitioners most commonly ask about OAIS.

Is OAIS a software system or product I can purchase and install?
No. OAIS is a reference model, not a software product or a specification for a particular system. It provides a conceptual framework and common vocabulary for understanding the functions and responsibilities involved in long-term digital preservation. Organizations may implement systems that conform to the OAIS model, and various tools describe themselves as OAIS-based, but the model itself does not prescribe any specific technology, architecture, or vendor solution. It describes what a preservation environment must address rather than how it must be built.
Does OAIS apply only to traditional archives, or is it relevant to records management more broadly?
The word 'archival' in OAIS can be misleading. The model is concerned with the long-term preservation of information intended to remain accessible and understandable over time, which extends beyond the concerns of a conventional physical archive. While OAIS originated in a context associated with the preservation of digital information over the long term, its concepts are often applied wherever information must retain its meaning and usability across extended periods and technological change. It is worth noting that OAIS is a preservation-focused model and does not itself cover the full scope of records management or information governance, which encompass creation, classification, retention scheduling, disposition decisions, and broader accountability concerns.
How do the OAIS information package concepts relate to what we actually store?
OAIS distinguishes between packages at different stages: the Submission Information Package (SIP), which is what a producer transfers into the environment; the Archival Information Package (AIP), which is the form preserved for the long term; and the Dissemination Information Package (DIP), which is what is delivered to a consumer. In practice, the content transferred in typically requires transformation and enrichment before it becomes the preserved AIP, and what is delivered to a user may be a different rendering again. Implementations often need to map their ingest, storage, and access workflows onto these package concepts to clarify where responsibilities and transformations occur.
What kinds of metadata does OAIS suggest we need to preserve alongside the content?
OAIS frames the information needed for long-term preservation in terms of supporting the ongoing understandability and usability of content by a designated community. This typically includes information that allows the content to be rendered and interpreted, information that establishes its provenance and context, information that supports fixity and integrity checking, and information that ties the components of a package together. Depending on organizational policy and the nature of the holdings, the specific metadata schemes and elements chosen to satisfy these functions will vary. The model describes the categories of information required rather than mandating particular metadata standards.
How does the concept of a 'designated community' affect preservation planning?
OAIS introduces the idea of a designated community as the intended audience expected to be able to understand the preserved information, along with an assumed level of relevant knowledge that community possesses. This concept has practical consequences because it shapes decisions about how much contextual and interpretive information must be preserved: content that is understandable to specialists today may require additional explanatory information to remain understandable to a broader or future audience. Defining the designated community, and revisiting that definition over time, is therefore often treated as a foundational planning step that influences metadata capture, format decisions, and access provision.
How does OAIS relate to other standards and models we may already use, such as ISO 15489 or ISO 30301?
OAIS occupies a preservation-focused space and is often used alongside records management standards rather than in place of them. Broadly speaking, records management standards such as ISO 15489 and management-system standards such as ISO 30301 address the control of records as evidence of activity across their lifecycle, including capture, classification, retention, and disposition, whereas OAIS concentrates on the functions required to preserve information so it remains accessible and understandable over the long term. In practice, organizations may draw on records management frameworks to govern the lifecycle and on OAIS concepts to structure the preservation environment for records with long or permanent retention. The precise interfaces between these frameworks depend on organizational policy, and readers should consult the source standards directly for authoritative detail.

Common misconceptions

OAIS is a software product or a specification that dictates a particular system architecture.
OAIS is a conceptual reference model providing terminology and functional descriptions. It does not prescribe specific technologies, products, or architectures, and organizations may implement its concepts in many different ways depending on their context and resources.
Following OAIS is equivalent to performing records management, so the two are interchangeable.
OAIS focuses on the long-term preservation and continued usability of digital information for a Designated Community. Records management is broader in one sense, concerning the control of records as evidence of activity across their whole lifecycle including creation, capture, classification, retention, and disposition. The two overlap in the preservation and access phases but are not synonymous, and OAIS does not by itself address matters such as classification schemes, retention scheduling, or disposition decisions.
An OAIS-conformant archive guarantees that preserved digital objects will always remain authentic and understandable.
OAIS provides a framework intended to support ongoing understandability and integrity, but outcomes depend heavily on implementation choices, resourcing, preservation planning, and how well the Designated Community and its knowledge base have been characterized. The model itself makes no absolute guarantee, and continued usability typically requires sustained, active effort.

Best practices

Define and periodically review your Designated Community explicitly, since preservation decisions such as what representation information to retain depend on the assumed knowledge base of the users you intend to serve.
Treat OAIS as a shared vocabulary and functional framework to structure your preservation environment, while recognizing that you must still select the technologies, workflows, and organizational arrangements appropriate to your context.
Distinguish carefully among SIP, AIP, and DIP in your processes, documenting how information is transformed at ingest, in storage, and at access rather than assuming a single unchanging package throughout.
Capture and maintain adequate representation information alongside content so that preserved objects remain interpretable and usable over time, and revisit this as the Designated Community's knowledge base evolves.
Coordinate OAIS-based preservation activities with your broader records management and information governance responsibilities, so that classification, retention, and disposition decisions made elsewhere are reflected in what is ingested, preserved, and eventually transferred or destroyed.
Invest in ongoing preservation planning and administration rather than treating conformance as a one-time state, since continued authenticity, integrity, and usability typically require sustained monitoring and intervention.