01
Where it fits and where it does not
Use these four checks before committing implementation time.
- Use it when
- Designing or evaluating repositories that accept responsibility for preserving information and keeping it understandable and available to a defined community over technological and organizational change.
- Limits
- OAIS is a conceptual reference model, not software or certification; the term Open refers to standards development rather than unrestricted data access, and local preservation policies remain necessary.
- Best for
- Cross-cutting teams working across Plan → Exchange → Learn + reuse.
- Maturity
- EstablishedSuitable for production assessment. Pin the exact release and any implementation profile.
02
See it in the workflow
This view shows the input, the change the standard introduces, and the resulting output.
- InputWhat starts
Cross-cutting source data, metadata, and local mappings
- OAISWhat changes
Use OAIS as a pinned reference architecture across Plan → Exchange → Learn + reuse
- OutputWhat becomes possible
A handoff the next system or team can validate against the same release
03
A concrete example
Define the designated community and knowledge base, document mandatory archive responsibilities, transform deposits into preservation information packages, monitor fixity and format risk, plan migrations, and produce controlled dissemination packages.
Why it matters: Supports durable access to authentic, interpretable data and context, but preservation architecture does not establish scientific quality, consent, or suitability for training.
04
What it fits with
Provides the preservation architecture beneath CoreTrustSeal assurance; PREMIS can encode preservation metadata, while DataCite, RO-Crate, and domain standards describe deposited research objects.
- FrameworkFAIR
Both support Cross-cutting work and meet around Plan, Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship - FrameworkFDOF
Both support Cross-cutting work and meet around Plan, Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship - FrameworkFAIR DMM
Both support Cross-cutting work and meet around Plan, Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship - Metadata vocabularyDPV
Both support Cross-cutting work and meet around Plan, Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship
05
Implementation starter
Start with one bounded handoff. Pin, test, and review it before scaling.
Define one handoff, its accountable owner, and the decision OAIS must support.
Pin the exact version and companion artifacts: ISO 14721:2025 · Edition 3; CCSDS 650.0-M-3 · Issue 3.
Map one representative input to the required reference architecture artifacts.
Test the result against the canonical source and record every exception.
Preserve the source data, mappings, and review evidence before scaling.
06
Test the main limitation
OAIS is a conceptual reference model, not software or certification; the term Open refers to standards development rather than unrestricted data access, and local preservation policies remain necessary.
Run one representative end-to-end pilot and record exactly where OAIS loses context, needs an extension, or depends on another standard.
Machine-readable output may still be unfit for analysis or ML.
Test the output for missing context, provenance, terminology alignment, time leakage, and the intended downstream decision. Supports durable access to authentic, interpretable data and context, but preservation architecture does not establish scientific quality, consent, or suitability for training.
07
Official resources
Specifications, diagrams, examples, and guides from the organizations that maintain them.
ISO 14721:2025 OAIS reference model
Official publisher or steward guidance for this reference architecture profile.
- Publisher
- ISO/TC 20/SC 13 · Consultative Committee for Space Data Systems