1. Adapted from Presentations by:
Overview of the
OAIS Reference Model
The Lingua Franca of Digital Archives
Kenneth S. Casey
Acting Technical Director
NOAA National Oceanographic Data Center
CLASS - Comprehensive Large Array-data Stewardship System
Adapted from Presentations by:
D.M. Sawyer/NASA/GSFC
C. Huc/CNES
D. Boucon/CNES-SILOGIC
J.G. Garrett/NASA-Raytheon

2. Context
NOAA Archives are evolving to a new paradigm, where CLASS will serve as the common IT infrastructure supporting all three NNDCs
CLASS won’t be the only IT infrastructure (we’ll still have our individual legacy systems) but it will be the only enterprise IT solution
When possible, legacy systems will be “retired” and holdings transferred into CLASS (e.g., GOES Active Archive and Satellite Active Archive)
CLASS, until now, has been entirely within OSD but the operational part is now moving to NNDC management
ISO - International Standards Organization
CCSDS - Consultative Committee for Space Data Systems
The OAIS RM is available from:
NNDC = NOAA National Data Centers
CLASS = Comprehensive Large Array Data Stewardship System
OSD = NESDIS Office of System Development

3. Context DAARWG and the Science Advisory Board
Archival Appraisal Process
NOAA Administrative Order
Submission Agreements
NOAA IOOS Data Integration Framework
GEO-IDE
Archive Architecture Team’s Archive ConOps
…. ENOUGH TO MAKE YOUR HEAD SPIN!
ISO - International Standards Organization
The OAIS RM is available from:
DAARWG = Data Archiving and Access Requirements Working Group
DIF = Data Integration Framework
GEO-IDE = Global Earth Observing Integrated Data Environment
IOOS = Integrated Ocean Observing System

4. What is a Reference Model?
A framework for understanding significant relationships between the entities of a system and to the external environment
A lingua franca for discussion, development, implementation, management, and use of that system
ISO - International Standards Organization
CCSDS - Consultative Committee for Space Data Systems
The OAIS RM is available from:
A reference model is NOT an implementation!!

5. Why the OAIS Matters to NOAA
Provides a framework for consideration of roles and responsibilities of NNCDs and CLASS to ensure fundamental archive responsibilities are accomplished
Facilitates strategic planning of archive evolution
Assists with the education of our customers and stakeholders on essential information preservation activities

6. Why the OAIS Matters to NODC
It gives a common language for us to use as we discuss both our internal archive process and our cross-NOAA archive activities
It serves as a useful tool for “gap analysis”, by providing a comprehensive suite of functions we should perform and responsibilities we must meet to be called a “capital A” Archive

7. The OAIS Reference Model
The Open Archival Information System Reference Model (OAIS RM) is the CCSDS and ISO Standard (14721) for Digital Archives
It applies to all organizations that need to preserve digital information for the long-term
It does NOT specify any particular implementation
An organization conforms to the OAIS RM by discharging a minimal set of responsibilities and supporting basic information concepts
CCSDS = Consultative Committee for Space Data Systems
RM = Reference Model
ISO = International Standards Organization

8. OAIS Responsibilities
Negotiates and accepts information from Producers
Obtains sufficient control to ensure long-term preservation
Ensures the information to be preserved is independently understandable to identified Designated Communities
Follows documented policies and procedures to insure information is preserved
Provides information to the Designated Communities in understandable forms

9. The OAIS Environment Producer provides information to be preserved
Management sets overall policy
Consumer seeks and acquires preserved information
OAIS
(Archive)
Producer
Consumer
Management
The OAIS Environment from 30,000 ft

10. OAIS Functional Entities Preservation Planning
PRODUCER
CONSUMER P R O D U C E
Data
Management C O N S U M E R
Descriptive Info
queries
result sets
SIP
Ingest
Access
Archival
Storage
orders
DIP
AIP
From Sawyer: Conceptually, a Submission Information Package is provided by a Producer to the Ingest entity. An AIP is created and delivered to Archival Storage. Related Descriptive Information is provided to Data Management. A Consumer searches for, and requests, information using appropriate Descriptive Information and access aids. The appropriate AIP is retrieved from Archival Storage and transformed by the Access entity into the appropriate Dissemination Information Package for delivery to the Consumer. This is all under the guidance of the Administration entity. Preservation strategies and techniques are recommended by Preservation Planning and put in place by the Administration entity.
Administration
Policy, budget
MANAGEMENT
MANAGEMENT
The OAIS Environment from 10,000 ft
SIP = Submission Information Package
AIP = Archival Information Package
DIP = Dissemination Information Package

11. OAIS Functional Entities Preservation Planning
Data Management
Ingest
Access
Archival Storage
PRODUCER
CONSUMER
Administration
Preservation Planning
The OAIS Environment from Sea Level
Adapted from
MANAGEMENT

12. OAIS Common Services Operating System Services Network Services
Security Services
These pervasive functions link together the other 6 OAIS Functional Entities…

13. OAIS Functional Entities
Ingest: This entity provides the services and functions to accept Submission Information Packages (SIPs) from Producers and prepare the contents for storage and management within the OAIS
Receive Submission
Quality Assurance
Generate AIP
Generate Descriptive Information
Coordinate Updates

14. OAIS Functional Entities
Archival Storage: This entity provides the services and functions for the storage, maintenance and retrieval of Archival Information Packages (AIPs)
Receive Data
Manage Storage Hierarchy
Replace Media
Error Checking
Disaster recovery
Provide Data

15. OAIS Functional Entities
Data Management: This entity provides the services and functions for populating, maintaining, and accessing both descriptive information that identifies and documents OAIS holdings and internal OAIS administrative data
Administer Database
Perform Queries
Generate Report
Receive Database Updates

16. OAIS Functional Entities
Access: This entity supports Consumers in determining the existence, description, location and availability of information stored in the OAIS and allows Consumers to request and receive Dissemination Information Packages (DIPs)
Coordinate Access Activities
Generate DIP
Deliver Response

17. OAIS Functional Entities
Preservation Planning: This entity monitors the environment of the OAIS and provides recommendations to ensure that the information stored in the OAIS remain accessible to the Designated Community over the long term
Monitor Designated Community
Monitor Technology
Develop Preservation Strategies and Standards
Develop Packaging Designs and Migration Plans

18. OAIS Functional Entities
Administration: This entity manages the overall operation of the OAIS
Negotiate Submission Agreement
Manage System Configuration
Archival Information Update
Physical Access Control
Establish Standards and Policies
Audit Submission
Activate Requests
Customer Service

19. Making Sense of the Seascape Preservation Planning
Conference Booths
IOOS DIF
QA and Products
(WOD, GTSPP)
Preservation Planning
PRODUCER
CONSUMER P R O D U C E
ATDB, OAS
Data
Management C O N S U M E R
Descriptive Info
queries
result sets
SIP
Ingest
Access
Archival
Storage
orders
DIP
AIP
CLASS
From Sawyer: Conceptually, a Submission Information Package is provided by a Producer to the Ingest entity. An AIP is created and delivered to Archival Storage. Related Descriptive Information is provided to Data Management. A Consumer searches for, and requests, information using appropriate Descriptive Information and access aids. The appropriate AIP is retrieved from Archival Storage and transformed by the Access entity into the appropriate Dissemination Information Package for delivery to the Consumer. This is all under the guidance of the Administration entity. Preservation strategies and techniques are recommended by Preservation Planning and put in place by the Administration entity.
Administration
Policy, budget
Submission Agreements
MANAGEMENT
MANAGEMENT
Implementation of the OAIS:
GEO-IDE, Archive ConOps and Architecture
Archive Appraisal, NAO

20. CLASS, NNDCs, and the OAIS
Broad agreement to use the OAIS language and framework for CLASS - NNDC relationships and operations transition planning
Not always easy to do - very easy to slip back into using “local dialects”
The Data Management Committee (DMC), subset of the NOAA Observing System Council (NOSC) has directed we perform a “mapping” to the OAIS RM

21. CLASS, NNDCs, and the OAIS
Mapping of Current and Desired End States to the OAIS RM:
Refine the roles and responsibilities of the: NNDCs, CLASS operations, and CLASS development
Increase understanding of OAIS functional gaps (i.e., a baseline assessment or “gap analysis”)

22. NODC OAIS Mapping Process
Commence with overview of the OAIS RM
Hold follow-on meetings to discuss each of the Functional Entities
Start each discussion with detailed description of that Functional Entity and its constituent functions
Populate the OAIS Traceability Matrix for that Functional Entity, describing how our current activities map to the OAIS functions now and how we envision the CLASS-NNDC partnership should accomplish those functions in the future

23. Traceability Matrix

24. Evolution of NOAA’s Archives
OAIS RM provides a basis for delineating archive roles and responsibilities among NNDCs and CLASS
Provides a basis for identifying required archive functions and ensuring CLASS development to NNDC operations handoff can occur smoothly
Provides a way forward for strategic planning of archive evolution

25. “For the eye sees not itself, but by reflection, by some other things
Brutus, in William Shakespeare’s
The Life and Death of Julius Caesar