1. PDS4 Deployment Planning (Discussion) PDS MC F2F Columbia, Maryland Dan Crichton August 28, 2012 1

2. Overall PDS4 is following a phased release of its data standards and software “Deliver and deliver often” At build 3, PDS should call its standards and software “beta” and expose to a focused community for feedback Freeze model, where possible, for beta test at 3a Bring the community into comment and make them part of the process (focused user testing) Don’t rush to call everything perfect Worry about dropping the beta context after MAVEN and LADEE ingest 2

3. PDS4: Beta Deployment for Users 3

4. PDS4 Beta Concept PDS4 is brought online for user access in a “beta” state “Rough around the edges” is okay Data is added over time Tools are added over time Users are recruited to participate and provide feedback Improvements are made Tools and capabilities leave beta state over time, but new tools should show up there 4

5. 5

6. Deployment Planning By September (Build 3a) Initial software for build 3a becomes available Post PDS4 artifacts online for public access and review October – March 2013 Install and setup core PDS4 software at nodes and ensure everything is working Improvements in core software; new user services/tools online Begin early user tests (e.g., Atmos) April – July 2013 (Build 3b) Post more migrated data sets online User testing/feedback Continued tool/service development Iterate user tests with more data online over time Prepare for LADEE/MAVEN distribution in 2014/2015 6

7. Data Standards Already being tested with missions Need to test it with users Get a few migrated data sets online and ask for a “user review/testing” Atmospheres has already proposed being an early test case Recommend every node follow this approach 7

8. Software Core PDS4 software infrastructure has been transparently replacing what existed in PDS3 at EN Setup registry and PDS4 infrastructure at nodes Post PDS4 data for users online Use this drive the user tools and services (translation, viewing, etc) 8

9. User Tools/Services Transformation of labels (XML to …) Leverage XSLT libraries (September 2012 +) Transformation of data (March 2013 +) Leverage OAL replacement that ARC is building Leverage other tools (e.g., transcoder libraries) Viewing/visualization of data (March 2013+) Search/access to data (September 2012+) 9

10. Phasing PDS4 Online 10 PDS3 Pipeline PDS3 Ingest Current Missions PDS3 Archive @ DNs PDS3 Services Central Catalog Users PDS4 Ingest PDS4 Registry PDS4 Archive @ DNs PDS4 Pipeline PDS4 Services New Missions PDS Portal Harvest Product Metadata (PDS3) toPDS4 Transform Datasets + Products Dataset Metadata (PDS3) Dataset Metadata (PDS3) Metadata Index NOTE: PDS3 Services phased out overtime

11. Backup 11

12. Lifecycle Discussion 12 Project Lifecycle Pre- Formulation Implementation Project Lifecycle Gates & Major Events Project Reviews PDSMC Concept Review (Dec 2007) Study/ Concepts Project Plan PDS4 Prelim Architecture PDSMC Impl Review (July 2008) PDSMC Preliminary Design (August 2009) PDSMC Arch Review (Nov 2008) Build 1b Internal Stds Assessment (Dec 2010) PDS System Review (Mar 2010) Build 1c IPDA Stds Assessment (April 2011) PDS System Review II (June 2011) Build 1d External Stds Assessment (Aug 2011) Operational Readiness Review (data providers) (November 2011) PDS4 Design Begin Study Project Build 1: Prototype Build 2: Production Build 3 1a 1b 1c 1d KDP: Study KDP: Prelim Design KDP: Project Plan & Arch Operational Readiness Review (users) (Summer 2013)

13. ATMOSPHERES NODE CAPABILITIES for Beta Testing Requirement Freeze the 910beta Information Model for testing Possible Migrated Data Phoenix atmospheric data available in days(ASCII) 5 bundles Three accelerometer data sets to follow (ASCII) Odyssey, MGS and MRO Ground-based MAUI Jupiter data set (FITS) Tested as a FITS data set –could be brought up Web Page Access Lynn says he can bring up the Phoenix help pages on the same schedule that the students can supply the bundles. The front page (see slide 2) The 5 data set pages