1. Cyberinfrastructure Release 2 Production Readiness Review 12 December 2013

2. Agenda TimeTopicPresenter 1000/1300Introduction: Entry and Exit Criteria Kathy Carr 1015/1315Overview of Project StateMike Kelly 1030/1330R2 DemonstrationTim Ampe / Luke Campbell 1130/1430R2 Engineering Status - Test and Integration Tim Ampe 1200/1500R2 VerificationKathy Carr 1230/1530R2 DeploymentRod Cressey 1245/1545Wrap-up / Q&AKathy Carr

3. Entry Criteria The entry criteria for PRR are completion of the review artifacts listed in Table 5 of Section 4.2. of the CI System Life Cycle Plan: Artifact SetContent ManagementSystem Life Cycle Plan LCO, LCA & IOC Report and Response ITV Strategy Integration and Verification Plan (baselined) RequirementsNone DesignNone ImplementationSource code repository Test Reports (baselined) Integration and Verification Procedures (baselined) Integration Report (baselined) Verification Report (baselined) Beta Testing Report (baselined) Defect List DeploymentIntegrated and Verified Release (baselined) Deployment Plan (baselined)

4. Success Criteria / Exit Criteria (from SEMP and CI System Life Cycle Plan) Have all of the blocker and major defects been corrected? Is the integrated and verified release mature and stable enough for deployment into a production environment? Is the integrated and verified release ready for PMO acceptance? Is there appropriate final documentation to inform and train the user and operations communities? Is the release ready to transition to operation?

5. R2 Timeline LCO: Aug 30 – Sep 1, 2011 LCA: March 20-21, 2012 IOC: Nov 16, 2012 Beta Testing: December 2012 – January 2013 Pathfinder Testing: Feb 1, 2013 – March 28, 2013 MIRR: Sept 18, 2013 Load Tests: Oct 24, 2013; Dec 11, 2013 PRR: Dec 12, 2013

6. R2 Assumptions for Production/Operations R2 will only be used by Marine IOs and will not be exposed to external users. The San Diego facility will host OOINet R2 after PRR during initial operations. OOINet will be in state such that, upon passing the PRR, the Marine Operators can begin using it for their operational tasks the next day for the deployed Endurance platforms. The initial tasks of the Marine Operators may be to transition “planned” assets into a “deployed” state and to edit the information about those assets. Thus OOINet must support those tasks. No non-operational information will be included in production baseline version of OOINet. For example, the CI Bench Test Facility will not be listed. No data or metadata entered in the system will be lost during software upgrades during production.

7. PRR Documents CI Release 2 System Integration Test Procedures -2160-00100 CI Release 2 System Integration Test Report - 2160-00101 CI Release 2 Verification Procedures - 2160-00103 CI Release 2 Verification Report - 2160-00104 (Confluence) CI Release 2 Beta Test Plan - 2160-00105 CI Release 2 Beta Test Report - 2160-00106 CI Release 2 Test Report - 2160-00102 CI Deployment Plan - 2160-00200

8. Additional Release 2 documents R2 LCO Report R2 LCA Report R2 IOC Report R2 Pathfinder Effort Summary (2013-04-04) R2 Load Test Report (1152-02191; 2013-11-13) Online Help Documentation

9. Load Tests October 24, 2013December 11, 2013 # participants3126 Length of test3 hours Test ProcedureVersion 0-05Version 2-01 Functionality Coverage100% of test steps (95% of functionality) # Blockers20 # Majors28TBD # Minors61TBD

10. Next Steps If R2 passes PRR: – R2 will move to the Production environment – MIOs may start using it to manage deployed marine platforms – PMO will begin validation testing. (R2 won’t actually be in “Operations” until PMO validation testing is complete.) If panel determines that R2 is not ready to transition to operations: – R2 will remain in the Transition phase until whatever Actions we determine are completed.