1 / 31

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

SNAS Release 4 (10.2) Operational Readiness Review (ORR). 18 February 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. Context of Review .

bruis
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) 18 February 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. Context of Review • Release 1 (08.1) ORR (09/04/08) and Delta-ORR (12/05/08) • Product development - to-field implementation and begin Operational Phase • Limited use by MOCs as full capabilities not implemented until Release 2 • Release 2 (9.1) ORR (4/29/09) followed by DRR (09/18/09) • Added in UPS-like capabilities, graphical timeline and other enhancements • Did not promote to Ops until DRR (09/18/09) - added JSC requested modifications - required for JSC/ISS operations • Release 3 (10.1) DRR (03/02/09) • upgraded OS and added in fixes and other operational enhancements • Release 3.1 (10.1.1) DRR (06/29/10) • Optional MOC Client upgrade – to address 3 items for JSC • Release 3.1.2 (10.1.2) • SvE improvement to address performance problem-Server delivery only • Release 4 (10.2) ORR – today • User Wish List (customer desired features) and fixes added Goal for today’s review is the approval to promote Release 4 (10.2) to Operations

  3. ORR Entrance/Success Criteria NASA SE Handbook

  4. Review Objectives • All validation testing is complete • Provide test results • Test failures and anomalies from validation testing have been resolved • Outstanding problems are low risk and will be converted to DRs • All operational and enabling products necessary for normal and contingency operations have been tested and in place • Users’ Guides updated • LOP updates • Training has been provided to users and operators • O&M Client (Ops DBA) training completed • MOC Client users have had opportunities for EIF testing (CIM is scheduled) • Operational contingency planning has been accomplished and personal trained • Delivery Plan and Checklist has been developed with fallback plan included

  5. Agenda • Overview of Release 4 contents • Enhancements (User Wish Lists) and Fixes • Release 4 – Test Builds • Overview of Acceptance Testing • Who, What, When, How • Test Results • MOC Client - NCCDS functions • MOC Client - DAS functions • O&M Client • Risk Assessment • Delivery Readiness • Training • Delivery Checklist and CM • Customer Readiness • Post ORR Activities • Execute delivery • Support customer transitions

  6. Release 4 Contents Overview(Details in backup slides) • 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) • Problems noted and fixed during testing • 103 BUG fixes - problems noted during software development/test and corrected by programmers

  7. Release 4 Test Builds Background • Initial Test baseline delivered to WSC EIF in August 2010 • Successful TRR on 08/12/10 • Baseline Acceptance Test Plan (ATP) completed • During Acceptance Test Phase, subsequent builds were delivered to address problems noted during testing (fixes to IDRs) • ATP updated with additional tests • The final build Candidate 5 was fully regression tested • Test Build history • Candidate 1 – 08/10/10 • Candidate 2 – 09/01/10 • Candidate 3 – 10/12/10 • Candidate 4 – 11/10/10 • Candidate 5 – 12/03/10

  8. 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 - to 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

  9. Test Results- Summary(MOC & O&M Client) • Total of 78 Tests were executed • 70 PASSED • 3 PASSED CONDITIONALLY • 5 FAILED • As a result of testing • 16 new functions/enhancements were 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

  10. Test Result DetailsMOC Client/NCCDS functions MOC Client/NCCDS functions - Mike Miller • Test 1.1 - TUT Processing • TUT Filtering - PASSED • TUT Data file verification - PASSED • Test 1.2 - TSW and Recurrent Scheduling • TCW Processing - PASSED • Failure to process PSATs - PASSED • Ingest TSW without transmitting - PASSED • No- retransmit capability for TSW - PASSED • TSW time shift - FAILED • Close IDR 27913 and write a DR • Setting up scheduling defaults - PASSED • True Mode of TSW - PASSED • Miscounting of requests in Bulk Scheduling - PASSED • Order of Tracking Services in Recurrent Scheduling - PASSED • Transmitting State Vectors - PASSED

  11. Test Result Details MOC Client/NCCDS functions continued MOC Client/NCCDS functions – Mike Miller • Test 1.3 – General scheduling improvements • Printer capabilities and display of SSCs - PASSED • Print full detail option - PASSED • Issues related to Reports - PASSED • Graphical Timeline checkout - PASSED • Verification of Bulk Modify displays - PASSED • Scheduling limitations - PASSED • Replace Requests during on-going SHOs - PASSED • Timeline Null Pointer Exception for lack of USM - PASSED • Implementing ASAR for queued events in Timeline - PASSED • Corrupted requests when start and end times blank - PASSED • Error in time in setting Absolute Time format - PASSED • Issues with PE alias handling - PASSED • Omitting minimum duration for PE - PASSED • Add information for return receipt message - PASSED • Incorrect antenna numbers in Confirmed Events - PASSED • Incorrect antenna gain values in Confirmed Event Details - PASSED • Missing active event in Confirmed Event Report - PASSED • Bulk modify capability to update stored requests only - PASSED

  12. Test Result DetailsMOC Client/NCCDS functions continued MOC Client/NCCDS functions - Mike Miller • Test 1.4 - General Client process improvements • SSC update delete by MOC Client - PASSED • Formatting issue for receiver frequency in SSC panels - PASSED • Test 1.5 - Conflict scheduling processes • NCC-queued definition in Schedule Request summary - PASSED • Premature event completion status - PASSED • Concurrent Summary panel updates - PASSED • Active Schedule Summary upload file lock - PASSED • Auto USM write to an external computer- PASSED • Test 1.7 - Schedule Request Summary, Active Schedule, Graphical Timeline improvements • Window improvements - consistent view for all SAR windows - PASSED

  13. Test Result DetailsMOC Client/NCCDS functions continued MOC Client/NCCDS functions - Mike Miller • Test 1.8 – Upgrades to system configuration functions • Switch user changes - PASSED • Alert stream color change - PASSED • Issues with login/logout and role changes - PASSED • Change to Login dialog exception box - PASSED • Login password feedback - PASSED • Add in 3 displays- TDRS/SN status - PASSED • Test 1.9 – EPS functionality • Issues with FTP - PASSED • Manage EPS node detail file extension - PASSED • Mission EPS output folder not handled by re-create USM - PASSED • FTP/TCP problem with processing vectors - PASSED • Issues with TCP/IP - PASSED • TCP/IP processing code - DAS UPDs - PASSED • Enable report capability for TCP/IP similar to FTP - PASSED • Test 4.4 - End-to-end testing– general regression testing - PASSED • Test 4.5 – Performance Loading test - PASSED

  14. Test Result DetailsMOC Client/DAS Functions MOC Client/DAS functions - Robert Voelkerding • Test 1.6 - Processing upgrades for DAS functions • Error in message for DAS Playback - PASSED • DAS alert missing at login - PASSED • DAS SSC difference in MOC and O&M client windows - FAILED • Close IDR 28200 and write a BUG • Capability to incorporate DAS SSCs in PE-PASSED • RAR and RAMR blocked on Active Events window - FAILED • Close IDR 28201 and write DR • DAS playback search problem - PASSED • Test 4.1 - DAS Vector transmissions - PASSED • Test 4.2 - General DAS scheduling functions - PASSED CONDITIONALLY • Close IDR 28207 and write DR • Close IDR 28208 and write DR • Close IDR 28336 and write DR • Test 4.3 - DAS Playback functions - PASSED

  15. Test Result DetailsO&M Client Functions O&M Client Test 2.1 - Merri Benjamin • MOC Client Activity monitor functions (W/L 69) - PASSED • O&M Registered Users GUI updates (W/L 76) - PASSED • Missing IP for O&M users in Users GUI - PASSED CONDITIONALLY • Close IDR 27396 and write DR • All SIC implementation (W/L- 84) - FAILED • Write a DR • Retrieve SIC/USER Alert functions - PASSED • Purging from the O&M Client - PASSED • Database Purge Utilities - FAILED • Close IDR 28316 and write DR • Delete User Account enhancement - PASSED • Updates to SUPIDEN notification to MOC Clients - PASSED • O&M Client have HA access to reset processes- PASSED CONDITIONALLY • Close IDR 28225 and write DR • Close IDR 28226 and write a BUG • Modification of Prototype Event Parameters - PASSED • Re-use of several O&M windows (remain open) - PASSED • Active Event Purges - PASSED • Add User problems - PASSED • SvE error when disabling an account - PASSED • O&M Client keep alive - PASSED

  16. Test Results- 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 ALL SIC user implementation Likelihood = 2, Consequence = 3 8. IDR 28316 UPD LOG table purge Likelihood = 5, Consequence = 2 9. IDR 28225 HA window remains open Likelihood = 2, Consequence = 3 All Low or Moderate Risk to Operations; Recommend Promote to Ops

  17. Delivery 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 schedule for March 3rd at 1330 E.S.T • 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 • Is prepared and requires review and sign off. • The NENS number NENS-SN-ATR-0008

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

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

  20. Post-ORR Activities • Today : ORR Actions • March: Execute delivery • 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 • Beyond: Support customer transition

  21. Delivery timeline • Prior to March 9th • Step 1:  T-2/3 days Perform full image system backups  - Juan Gonzales • March 9th  1600-2000 • Step 2: T-Go/NoGo: request users to logoff - Mike Miller • Step 3:  Perform cold database backups - Juan Gonzales • Step 4:  Shut-down and restart - Juan Gonzales • Step 5: Run scripts to update Release 4 database schema - Juan Gonzales • Step 6: Perform cold backup of Ops database only - Juan Gonzales • Step 7: Activate Release 4 10.2 on OPS - Scott Robinson • Step 8: Validate successful delivery - Mike Miller • Step 9:  Release NAM • Delivery Complete

  22. 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

  23. Release 4 ORR BACKUP SLIDES

  24. Release 4 Contents (Overview)Wish List • Wish List (W/L) – Operational Enhancements/New Features and Requester • W/L 21 - Filter TUT report for TDRSs and services (SWIFT) • W/L 35 - Change Print characteristics (HST) • W/L 49 - Allow display of all services on SAR GUI w/o scrolling (NOM) • W/L 63 - Keep Recurrent Scheduling GUIs open (JSC/OET) • W/L 64 - User control of TSW transmission (TRMM/OET) • W/L 66 - Change Switch User identity (JSC) • W/L 67 - Change password feedback ((JSC) • W/L 70 - More details for Return-Receipt related messages (OET) • W/L 72 - Display TDRS payload constraints and Status (NOM) • W/L 7 - Receive EPS style reports on TCP/IP interface (JSC) • W/L 81 - Automated option for Re-create USM function (HST) • W/L 82 - TUT filter for Graphical Timeline (NOM) • W/L 85 - Ingest TSW without transmitting them (TRMM/OET) • W/L 87 - Adjust request and event start/stop time display and use (JSC) • W/L 62 – SvE reset from O&M Client (Ops DBA) • W/L 69 – Improvements to MOC Client Activity GUI (Ops DBA) • W/L 84 – Implement All-Sic setting (Ops DBA)

  25. W/L 72 – 1 of 3 figures now accessible with SNAS

  26. W/L 72 – 2 of 3 figures now accessible with SNAS

  27. W/L 72 – 3 of 3 figures now accessible with SNAS

  28. DRs against 10.1.2 (current baseline) • DR 59900 - SAM disconnects related to TUT • DR 55689 - O&M Client logon recycle • DR 58131 - Events marked complete prior to execution time • DR 59561 - Active schedule lock file problem • DR 58760 - SARs completed before granted • DR 58676 - SRMs error off due to same request ID in system • DR 58722 - Slow response during THEMIS support • DR 59159 - CNOF socket inactive • DR 58105 - Erroneous ISS MA message • DR 58128 - No status on Schedule Request Summary • DR 58249 - JSC unable to schedule SMA services • DR 58107 - JSC Scheduling Connection problem • DR 58129 - Directory warning for TCP/IP node • DR 58091 - Errors while running Purge Data • DR 58130 - TCP/IP Node stopped receiving SRMs when sFTP node • DR 58133 - Shift Change Does not always take effect • DR 58233 - Unable to Approve or Reject MOC SSC Modification • DR 58711 - TSW Generation Problem (AR #097044) • DR 58822 - Incorrect Antenna Numbers in confirmed Events listing • DR 58850 - Incorrect Antenna Gain Values in confirmed Event Details

  29. IDRs-Problems noted during testing • Delivered in Candidate 5 • IDR 28110 - DAS Playback search failure • IDR 28034 - Auto USM function cannot find destination directory • IDR 28017 - Active Schedule GUI does not allow RAMR • IDR 28016 - Cannot clone RAR from Active Schedule • Delivered in Candidate 4 • IDR 27993 - Unnecessary automatic recreation of USMs • IDR 28008 - Reports do not show active events • IDR 28010 - TCP SARs Details not showing correct Freeze Int. • IDR 28015 - Flaw in OAM HA message processing • IDR 28022 - Unable to adjust services added to SAR via PE • IDR 28023 - Endless SAR panel dialog box trap encountered • IDR 28029 - Auto ingest file submission loops • IDR 28033 - Can't submit SAR with NCC-defined Prototype Event

  30. IDRs-Problems noted during testing • Delivered in Candidate 3 • IDR 27855 - Auto Recreate USM Properties – file Directory setup • IDR 27877 - O&M Client – registered Users and IP – O&M Accounts • IDR 27901 - Confirmed Events Listings showing old events • IDR 27908 – Re-specifiable changes lost in Graphical Timeline • IDR 27918 - Concurrent Modification Exception in SvE • IDR 27919 - Import of Bulk file reports unexpected errors • IDR 27929 - TSW error doesn’t allow for re-transmission • IDR 27930 - Unable to perform replace request during ongoing SHO • IDR 27931 - Bulk (Modify) replace GUI corrupts the request • IDR 27940 - Bulk Modify fails - Reject for invalid parameter • IDR 27941 - TCP/IP Processing code – DAS UPDs • IDR 27949 - GUI Scheduling Request Issues • IDR 27950 - Issues Logging Out / Logging In MOC Client Sessions • IDR 27913 – TSW Time Shift not adding records

  31. IDRs-Problems noted during testing • Delivered in Candidate 2 • IDR 27491 - No status back on msgs through TCP/IP with invalid Ids • IDR 27847 - TCP/IP Send problem for big reports • IDR 27854 - TSW Summary - retrieving from db is timing out • IDR 27855 - Auto Recreate USM Properties - File directory setup • IDR 27856 - Client.prop file default settings with Auto USM on. • IDR 27860 - Schedule Request Summary - ASAR dynamic updates • IDR 27859 - Graphic Timeline – ASAR not included • IDR 27875 - TSW Record Validation • IDR 27876 - Graphic Timeline-generating a SAR • IDR 27884 - EPS vector processing generates incorrect error message • Delivered in Candidate 1 • IDR 27396 : IP GUI doesn't show all Ips • IDR 27503 : SRMs not going to TCP • IDR 27609 : The Graphic Timeline needs to also show

More Related