1 / 16

SNAS Release 4 (10.2) Operational Readiness Review (ORR)

SNAS Release 4 (10.2) Operational Readiness Review (ORR). 3 March 2011. David Warren SNAS Development Lead Merri Benjamin WSC Systems Engineering Michael Miller WSC Tech Ops and Analysis Robert Voelkerding WSC Tech Ops and Analysis. SNAS Release 10.2 Operational Readiness Review.

keene
Download Presentation

SNAS Release 4 (10.2) Operational Readiness Review (ORR)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SNAS Release 4 (10.2) Operational Readiness Review (ORR) 3 March 2011 David Warren SNAS Development Lead Merri Benjamin WSC Systems Engineering Michael Miller WSC Tech Ops and Analysis Robert Voelkerding WSC Tech Ops and Analysis

  2. SNAS Release 10.2 Operational Readiness Review • Board Members • Don Shinners: NASA Station Director • Markland Benson: NASA Computer Systems Manager • Scott Greatorex, Chief, Network Integration Management Office • Dave Harshman: NENS Program Manager • Mike Nichols: TDRS Operations Manager • Brad Millard: Software Engineering Manager • James Jacintho: TO&A Software Test Lead • Joel Hutchins: IT Security • Delivery Points of Contact • Dave Warren: SNAS Software Development • Mike Miller: SNAS Lead Tester • Robert Voelkerding: DAS Tester • Merri Benjamin: O&M Tester

  3. SNAS RFA Form

  4. Agenda • Overview of Release 4 Contents Dave Warren • Overview of Acceptance Testing Mike Miller • Who, What, When, How • Test Results Summary / Details • MOC Client - NCCDS functions Mike Miller • MOC Client - DAS functions Robert Voelkerding • O&M ClientMerri Benjamin • Risk Assessment Mike Miller • Delivery 10.2 Status • Transition Readiness Mike Miller • Customer Readiness • Post ORR Activities • Execute Delivery • Delivery Timeline • Support Customer Transition

  5. Release 4 Contents Overview • 17 Operational Enhancements/New Features- Wish List (W/L) highlights • Add additional TUT filtering • Improve print capabilities • Add user control for TSW transmissions • Provide a capability for auto-recreate USMs • Provide EPS style reports on TCP/IP interface • Provide displays of TDRS payload constraints and SGLT status • Provide the capability to monitor HA and reset processes from the O&M Client • 20 Fixes to discrepancies (DRs) against the 10.1.1 baseline • 39 Fixes to discrepancies noted during testing (IDRs) • 103 Bug fixes - problems noted during software development/test and corrected by programmers

  6. Acceptance Testing Overview • New features added to both MOC Client and O&M Client • both MOC and O&M Client, and system regression testing • End-to-end testing • SNAS Client/EIF mode - to - WSC SNAS EIF servers - to ANCC • SNAS Client/EIF mode - to - WSC SNAS EIF servers - DAS HMD • WSC Testers • Mike Miller - MOC Client (NCCDS) • Robert Voelkerding - MOC Client (DAS) • Merri Benjamin - O&M Client • MOC supported testing • HST - W/L items (successful HST SNAS ORR - Jan. 20, 2011) • JSC - TCP/IP functionality • Other MOCs - executed their MOC operations (e.g., TSW, Graphical Timeline scheduling, Recurrent scheduling, etc.) • Weekly Acceptance Test Status Meetings - IDR work-off • Monthly SNAS System Engineering Review Board (SERB) • DRs against Ops baseline (added to candidate test baseline when possible) Test Results will be presented along with MOC evaluations and readiness

  7. Test Results Summary(MOC & O&M Clients) • Total of 78 tests were executed • 70 Passed • 3 Passed Conditionally • 5 Failed • As a result of testing • 16 new functions/enhancements verified • one W/L implementation needs to be modified (pertains to O&M Client) • 20 DRs are closed with Release 4 • 48 IDRs were generated • 6 were written against Candidate 5 and will be converted to DRs • 37 were fixed, verified, and closed • 2 fixed but failed at testing (will convert to DRs) • 3 will be closed to BUGs • 9 new DRs will be added • Low/Moderate risk discrepancies to be fixed in future release - details provided in the following slides

  8. Test Result Details • MOC Client/NCCDS functions - Mike Miller • 10 test cases were performed featuring 53 line items • All line items passed except for IDR 27913. No MOCs are currently using this feature and the IDR has been converted to DR 60952. • MOC Client/DAS functions - Robert Voelkerding • 4 test cases were performed featuring 9 line items • Several tests cases required that DRs be written, however, these anomalies were not test case line items, but were existing issues that are non-impacting. • O&M Client Test 2.1 - Merri Benjamin • 1 test case was performed featuring 16 line items • 4 IDRs were written against the test case  and converted to DRs. None are impacting, but documented as improvements that should be addressed in a subsequent release.  • 1 DR relates to automatic purging of a table which can be easily managed by the Oracle DBA.

  9. Risk Assessment The following items to be converted to DRs 1. IDR 27913 - TSW Time shift adding and not shifting records Likelihood = 2, Consequence = 3 2. IDR 28201 - Unable To Clone A Modified DAS Event Likelihood = 2, Consequence = 3 3. IDR 28207- Incorrect Service Start Time in UPD details Likelihood = 5, Consequence = 1 4. IDR 28208 - Loss of UPD Summary Window Contents Likelihood = 2, Consequence = 3 5. IDR 28336 - Sched Request Sum Incorrect –DAS test Likelihood = 2, Consequence = 3 6. IDR 27396 - IP GUI does not show Locked IPs Likelihood = 2, Consequence = 2 7. W/L 84 - ALL SIC user implementation Likelihood = 2, Consequence = 3 8. IDR 28316 - UPD LOG table purge Likelihood = 5, Consequence = 1 9. IDR 28225 - HA window remains open Likelihood = 2, Consequence = 3 All Low or Moderate Risk to Operations; Recommend Promote to Ops

  10. Delivery 10.2 Status

  11. Transition Readiness • Training • OPS DBA training completed 1/27/11 • Provided demonstration of new O&M Client windows • New procedure for uploading TDRS payload and SN status has been delivered • O&M Client User’s Guide updated • MOC Client users • No new procedures are required for the TOCC users • MOC Client users have received training both from WSC and using their own training infrastructure • No new Alert Notices have been generated • Customer Interface Meeting is scheduled for March 10th at 1330 EST • Delivery Plan and Checklist • Have been supplied • Configuration Management • Delivery letter and package has been prepared and is ready to ship to WSC • Final Test Report • The NENS-SN-ATR-0008 is being reviewed

  12. SNAS Customer Readiness (1 of 2) wbc - will be completed on

  13. SNAS Customer Readiness (2 of 2) wbc - will be completed on

  14. Post-ORR Activities • ORR Actions • RFAs accepted until March 3rd COB • Responses are due by March 7th • Execute Delivery March 9th • NAM with downtime and instructions for MOC Client Users • Pre-delivery activities March 7th through 9th • NAM delivery reminder issued • Transition to SNAS 10.2 March 9th (4 hours of downtime) • NAM of completion issued • Tech-Ops support of customer transition issues

  15. Delivery Timeline • March 9th  1600-2000 Step 1:  T-2/3 days: perform full image system backups - Juan GonzalezStep 2: T-Go/NoGo: request users to logoff - Mike Miller • T- 0 to T+4 hrs Step 3:  Perform cold database backups - Juan GonzalezStep 4:  Shutdown and restart - Juan GonzalezStep 5: Run scripts to update new Release 4 database schema - Juan GonzalezStep 6: Perform cold backup of Ops database only - Juan GonzalezStep 7: Activate Release 10.2 on OPS - Scott RobinsonStep 8: Validate successful delivery - Mike MillerStep 9:  Release NAM • Delivery Complete

  16. ORR Checklist • All validation testing is complete • Test failures and anomalies from validation testing have been resolved • All operational and enabling products necessary for normal and contingency operations have been tested and are in place • Training has been provided to users and operators • Operational contingency planning has been accomplished and personnel trained Recommend Release 4 Candidate 5 (10.2) be promoted to Ops

More Related