1. WGISS - 40 30/09/2015 DATA PRESERVATION – CNES APPROACH B. Chausserie-Laprée

2. WGISS - 40 SUMMARY  CONTEXT  METHODOLOGY  DOCUMENTATION AND SOFTWARE PRESERVATION  EXAMPLES 2

3. WGISS - 40 CONTEXT 3 Main steps of the ‘Data’ management Preparation of production and long term preservation Current archive Processing Storage Access Acquisition Long term archive Phases of the project which produces the data 0 A B C D EFPost F Production Maintenance Access Transfer Preservation Destruction or transfer to another organism

4. WGISS - 40 CONTEXT 4 Preparation phase  Should start at the early stages of the project  An archiving plan shall be initialized Production  Production of the data according to guidelines of the preparatory steps  An iterative cycle is carried out (data acquisition / (re)processing / storage / access)  Data are managed in the current archive  Software and documentation are managed on dedicated means : software and documentation configuration management Preservation  Before the service removal phase (F), the responsibility of the Archive changes (transfer of data and responsibility)  New data can be provided by an external source  Archiving system maintenance (including evolution and migration) shall be taken into account  User needs related to data access shall be taken into account (eg. selection criteria)

5. WGISS - 40 METHODOLOGY 5 During the development (0, A, B, C, D ) and operation phases (E)  Application of the CNES RNC (CNES normative referential)  RNC-CNES-E-ST-80-100 : ‘Long term data preservation : applicable requirements to the Project’  These requirements aim to check the compliance of the Project with the CCSDS OAIS model  Archiving plan describing the activities needed at each step of the project (starting from the early phases (A) to prepare the preservation phase  The CCSDS PAIMAS standard is used to elaborate the archiving plan During the operation phase (E) in order to prepare the service removal phase (F)  Application of the CNES RNC (CNES normative referential)  RNC-CNES-E-ST-80-101 : ‘Long term data preservation : applicable requirements to the Archive’  These requirements aim to check the compliance of the Archive with the CCSDS OAIS model  Archiving plan describing the activities needed during the exploitation phase to prepare the preservation phase (transfer to the long term archive)  The CCSDS PAIMAS standard is used to elaborate the archiving plan  Carrying out of the CNES procedure (SERAD)  SERAD-PRO-4-0310-CNES : ‘Space data preservation procedure’  SERAD operation procedure which describes the activities to be carried out for the space data preservation

6. WGISS - 40 METHODOLOGY 6 Phases of the Project Project / Archive interaction Documentation delivered by the Project Comment Phase 0 The Archive entity must be identified Phase A - PRR Preliminary Definition Archiving plan, draft Preliminary requirement review : a preliminary agreement between Archive and Project shall be explicit Phase B - PDR Formal Definition Archiving plan, full version Preliminary definition review : a formal agreement between Archive and Project shall be explicit Phases C and D Formal Definition Archiving plan, final version Ground segment design, realisation and qualification Phase E Transfer and validation phase Process transfer acceptance : - Data conformity. - Transfer process validation Archiving plan, revision (if needed) Acceptance report A revision of the archiving plan is needed depending on technical events that can occur during the phase E (failure of an instrument, mission prolongation) Phase E - routine Transfer and validation phase In depth validation Data and documents are provided to the archive as they are generated. Consistency and completeness test are performed when required Phase F – service removal Archive becomes the only reference site for the project data which are archived Project Phases / PAIMAS phases correspondances

7. WGISS - 40 METHODOLOGY 7 Archiving plan content (when elaborated during the operation phase – E)  Purpose of the preservation and target user community  Legal and contractual aspects  Data policy  Preservation responsibility  Access rights  Data (identification of the activities to be carried out)  Identification and description of data to be long term archived  If needed : »data analysis »development of the data models (transfer, archive) »data organisation (SIP, AIP)  Tools to be developped (if needed)  Data analysis tools  Archiving system  Risks and constraints  Planning

8. WGISS - 40 METHODOLOGY 8 CNES SERAD operational procedure for the space data preservation

9. WGISS - 40 DOCUMENTATION PRESERVATION 9 Office documentation  CNES rules require the documentation to be delivered as Technical Data Packages (TDP) constituted by MS Word Document and Acrobat PDF documents associated with a descriptive file in XML (cf. ECSS-M-ST-40 – Configuration and Information Management) XML documentation  CNES rules require the XML documents to be conform to a XML schema (XML V1.0) with dedicated rules to elaborate XML interface documentation (RNC-CNES-E-HB-80-503) TOOLS  During the development and operation phases of the Project, a dedicated documentation configuration management tool is used : Baghera After the service removal phase  a part of the Project documentation is transferred to the so-called ‘corporate memory’  a part of the Project documentation is also provided to the dedicated Archive together with the data (cf. CNES Tools : POLDER SIPAD / SERAD access tool)  Documentation describing the user products (format, content,...)  Documentation describing the data processing (algorithm specification)

10. WGISS - 40 SOFTWARE PRESERVATION 10 CNES approach  CNES rules do not require to archive the software  In case where the software shall be preserved, the following recommendations shall be applied  Source code delivery  Installation and user documentation delivery  Validation environment delivery TOOLS  During the development and operation phases of the Project, the software configuration management is taken into account by a dedicated Service (SGC) After the service removal phase  Software is not preserved  On the initiative of the Project, the SGC service store for the long term certain software (including source code) on CNES archiving resources (STAF) => ‘inactive’ or ‘dead’ archive,  Exception for POLDER  Data acess and Scientific processing software  In that case software (source code) is considered as data (application of access rights restrictions) or as documentation (free acces rights)

11. WGISS - 40 DOCUMENTATION – CNES CORPORATE MEMORY 11

12. WGISS - 40 12

13. WGISS - 40 13

14. WGISS - 40 14

15. WGISS - 40 15

16. WGISS - 40 16