1 / 36

Space Network Access System (SNAS) Operational Readiness Review - Release 2 (ORR-R2)

Space Network Access System (SNAS) Operational Readiness Review - Release 2 (ORR-R2). April 29, 2009 NASA Code 452 Space Network (SN) Project. SNAS ORR Release 2 (R2) Agenda. Welcome/Introduction Rose Pajerski R2 Contents Chii-der Luo R2 Acceptance Testing Mike Miller

sanne
Download Presentation

Space Network Access System (SNAS) Operational Readiness Review - Release 2 (ORR-R2)

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. Space Network Access System (SNAS) Operational Readiness Review - Release 2(ORR-R2) April 29, 2009 NASA Code 452 Space Network (SN) Project

  2. SNAS ORR Release 2 (R2) Agenda Welcome/Introduction Rose Pajerski R2 Contents Chii-der Luo R2 Acceptance Testing Mike Miller Requirements Verification Status Joe Clark WSC O&M Preparation Activities Marty Antholzner WSC O&M Evaluation/Recommendation Marty Antholzner SNAS Follow-on Activities Rose Pajerski Mission Readiness Ame Fox 2

  3. Purpose of Review • The objectives of the review are to provide a comprehensive briefing to • Summarize SNAS Release 2 new functionality • Present results of acceptance testing activities • Present transition plans and activities • Brief on the system, personnel and documentation readiness for transition • Demonstrate the system’s readiness to support NCCDS and DAS operations at WSC • Readiness criteria • All applicable functional, subsystem testing, etc. has been successfully completed • All RFAs / issues from previous reviews have been satisfied according to plan • All known significant system discrepancies have been identified and dispositioned • Interfaces under configuration management • Operations personnel identified, trained and ready • Upon completion of this review, the SNAS team seeks approval to proceed with Release 2 transition to operations for both NCCDS and DAS interfaces. 3

  4. Prior Milestones • SNAS Release 1 Milestones • Acceptance Testing (NCCDS Support) 6/23 - 8/29/08 • Customer Training 7/30/08; 12/12/08 • WSC Operations Training 8/26/08, 10/27/08 • Performance Testing 8/28/08 • ORR 9/04/08 • Delta-ORR 12/07/08 • Transition to Operations 1/05/09 • SNAS Release 2 Milestones • System / Beta Testing 12/29/08 - 4/24/09 • Acceptance Testing 3/04 - 4/17/09 • Customer Training WSC and NOM provided, as needed • ORR 4/29/09 • Transition to operations 5/18/09 4

  5. Project Documentation System Requirements Doc. (DCN 003) CCB approved (2/18/09) Operations Concept Doc. (DCN 003)CCB approved (2/18/09) ICD between DAS/SNAS CCB approved (5/03/06) ICD between EPS/SNAS (working DCN 001) CCB approved (orig. 11/15/06) ICD between SN/CSM (DCN 002) CCB approved (10/29/07) Security Documentation 452 approved (10/29/07) Acceptance Test Plan (Release 2) Final, 3/04/09 MOC Client Users Guide Rel. 2 delivered with Client O&M Client Users Guide Rel. 2 delivered with Client Server Operators Guide 4/24/09 5

  6. Release 2 Contents Chii-der Luo 6

  7. SNAS Release 2 Contents Enhancements: Inputs from customers Problems Resolutions 8 IDRs resolved 7

  8. New/Enhanced Functionality (1 of 3) Graphical Timeline enhancement Allow cloning of SAR by drag-n-drop Allow saving of “planning” SARs on Timeline and/or database Show TUTs and TSWs at service level Improve selection criteria Provide auto refresh capability Schedule Request Summary and Active Events Summary panels enhancement Provide filtering capability Provide auto refresh capability TUT processing enhancement Allow saving of retrieval criteria (TDRS, services, etc.) Automatic (hourly) save of TUTs on client workstation Provide capability to build and submit types 2-7 IIRVs 8

  9. New/Enhanced Functionality (2 of 3) Bulk schedule requests processing enhancement Allow user to specify action (submit, save to DB, no action) for each request Provide multiple submission capability Allow multiple eligible requests to be submitted to NCC on one click SUPIDEN processing enhancement Add notification to applicable users upon a SUPIDEN update Update applicable RS prototype Allow specifications of numeric type UPD parameter alarm ranges Low and high warning ranges (yellow) Low and high critical ranges (red) 9

  10. New/Enhanced Functionality (3 of 3) Implement a TCP/IP interface with MOC system Provide a 6-port TCP/IP interface similar to SNAS-NCC interface as defined in SN/CSM ICD Allow MOC system to interface with NCC via SNAS without modifications Allow duplicate request ID for different SIC Enhancement to SNIF on handling of NCC connection status changes Provide O&M Client capability to view alerts 10

  11. IDRs Resolved in Release 2 8 IDRs were resolved in SNAS Release 2: 11

  12. Release 2 Acceptance Testing Mike Miller

  13. Customer Community Milestones • Operational Projects • 14 Projects (20 SICs) registered on WSC Operational (OPS) server • TIMED mission actively scheduling using SNAS • Beta Testing • 30 Projects (43 SICs, 95 users) configured on EIF server • Most active projects: HST, JSC, LDBP, THEMIS, WISE • Acceptance Testing • WSC AT participants: • JSC ISS & Shuttle • MOC operational data sets used: • HST, JSC, LandSat, TRMM, Swift • MOC operational scenarios: • JSC • DAS Transition testing • GLAST, LDBP, Swift 13

  14. Acceptance Testing (1 of 4) 3 new Test Cases were developed for new requirements 10 Release 1 Test Cases were updated based to support Verification of enhanced functionality Regression Testing Release 2 Testing (3 versions) Test specific fixes to Open IDRs and internally (dev) reported bugs All verified Regression Tests of Test Group 2 (MOC Client Functionality) was rerun Both NCCDS and DAS testing was performed TO&A developed regression tests executed successfully Shadowed communications during real events using HMD DAS Successfully monitored live UPD traffic 14

  15. Acceptance Testing (2 of 4) Final Release 2 ORR results are based on Candidate 03 Candidate 01: Initial set of Test Cases were run on new requirements 22 Internal bugs were resolved from Rel. 1 Candidate 02: Approximately 50% of the formal R2 Test Cases were executed 16 Internal bugs and 2 IDRs were resolved Candidate 03: 100% of the R2 Test Cases were re-executed in addition to mission specific functions and overall system operations testing 11 internal bugs and 5 IDRs were resolved 3 IDRS with workarounds remain Open 15

  16. Acceptance Testing (3 of 4) Open IDR Descriptions #26911: SNAS hangs up if child window is open when time lines closes After opening SAR panel from the Timeline, if the Timeline is discarded the SAR panel locks the MOC Client up #26897: Schedule connection with multiple SICs causes multiple scheduling connections After adding a new Project that has multiple SICs, the SNIF will automatically reset but brings up two connection sets instead of one #26892: Client loses knowledge of SSC's in bulk file After importing a Bulk Schedule file, sometimes the Bulk SAR review and approve panel displays all SARs as invalid (red), but if the user logs out and back in again, all correct SARs are displayed as valid (green) 16

  17. Acceptance Testing (4 of 4) • Release 2 passed acceptance testing with the following notes • Importing of DAS bulk schedules not tested – function not used operationally • Ingest of PSAT/UAVs tested successfully against Candidate 2 – was not re-verified in Candidate 3 • Limited verification of TCP interface – tested successfully in I&T environment • The three Open IDRs against Candidate 3 have workarounds identified, and will be transferred to the CDS DR system following software promotion 17

  18. SNAS/DAS Customer EIF Testing • SWIFT, GLAST, and LDBP successfully completed interface and MOC operations testing • 3 of 4 DAS customers ready to transition from SWSI to SNAS – CNOFs still to be verified 18

  19. Requirements Verification(SRD DCN003) Joe Clark

  20. Requirements Verification Numbered Requirements in 452-SRD-SNAS DCN 003 Release 1 Total requirements: 961 Release 2 requirements added: 16 Requirements not subject to verification Deleted in DCN 002 or DCN 003: 85 Higher level requirements: 93 Verification results Release 1 Compliance accepted: 764 Release 2 Compliance accepted: 780 20

  21. WSC O&M Activities Marty Antholzner

  22. WSC O&M Activities New Database procedures were created and/or updated Scripts for DB Hot backup were updated New scripts created to trim/clean up Oracle output Alert, audit and trace logs dumped on /opt/oracle/admin Remove old ../EIF2/ARCH logs Unload/Load Scripts originally supporting SWSI were updated Move data from one instance (OPS) to another (EIF) Copy one mission dataset (STS 2124) to another (STS 2125) Investigating Migration script originally supporting data transfers from NCCDS to SWSI for new missions Lacks JSC ISS and STS parameter transfer Lacks new Mission IF service type transfer Inconsistent copy of multiple IF Channel Codes for missions 22 22 22

  23. WSC O&M Activities • Preparing for WSC TOCC Operations • Working with SNAS/DAS Customers to ensure readiness for transition • Awaiting CNOFS coordination / testing • Make customer connections to SNAS • Complete final training for CSC/SS monitoring of DAS • Initial familiarization / training has been done • Training plans and MOC Client user’s guide available • WSC Tech Ops to ensure training accomplished • Update the CSC/SS consoles with the SNAS MOCC clients 23 23 23

  24. WSC O&M Evaluation/Recommendation Marty Antholzner 24

  25. WSC O&M Evaluation/Recommendation Marty Antholzner 25

  26. Evaluation/Recommendation Based upon the closure of the RFAs and action items as briefed, WSC recommends that SNAS R2 be declared operational with the understanding that the following will be completed: Training session for the WSC scheduler and console operators (OS, SS and CSCs) Operations procedures (or any needed Alert Notices) in place WSC O&M is ready to support Release 2 SNAS MOCC usage and customer transition per NASA direction. WSC will issue a NAM providing notification of transition Planned transition date on 5/18/09 26 26 26

  27. Review Inputs Goal is to address any remaining issues at this ORR Extensive customer involvement in Release 2 testing Continuing extensive support once Release 2 is operational RFAs will be accepted until Thursday (4/30) COB But we’d like to hear about them today Turn them in to Shina for processing Keiji Tasaki is the NASA POC for this review 27 27

  28. Post-Release 2 Schedule Release 2 Maintenance Update Address remaining IDRs May require client download Schedule Implementation 4/1/09-5/22/09 WSC delivery and Acceptance testing 5/25/09-6/19/09 Operational Availability 7/3/09 Release 3 Implementation 3/09 – 9/09 System Testing 9/09 – 10/09 Beta Testing 10/09 – 12/09 Acceptance Testing 11/09 – 12/09 ORR Dec. 09 Operational Availability Jan. 10 28 28 28

  29. Post ORR-R2 Activities Respond to RFAs turned in Thursday, 4/30 Support Customers with their Transition to SNAS Support JSC ISS / STS Transition Schedule Customer Interface Meetings Host Customers at WSC Work with Network Operations Managers (NOMs) and Mission Commitment Engineers (MCEs) WSC and NOMs will provide customer training as needed SNAS project will give existing customers a three month lead time prior to delivering new releases Plan and support HST Transition (6 months after SM4) Resolve JSC reported delay receiving UPDs 7 to 8 sec. delay reported in EIF Test Mode Identified as time tag error originating with ANCC Occurrence in Operation Mode is being investigated Sample recorded data set provided in Backup Slides 29 29 29

  30. Mission Readiness Ame Fox 30

  31. Mission Readiness for Transition (1 of 2) Legend 31 31 31

  32. Mission Readiness for Transition (2 of 2) Legend 32

  33. In Closing • ORR-R2 Objectives Completed • Acceptance testing is complete • All functional requirements have been verified • All non-functional requirements have been addressed • Documentation is complete and under CM at WSC • Thank you for your attendance • RFAs • Due date: Thursday, 4/30/09 • Submit to Shina Sangani-Dave (Code 452, PAAC II) • Email: shina.sangani-dave-1@nasa.gov 33 33

  34. Backup Slides 34 34

  35. Sample Data for Delay in EIF Mode with ANCC 35

  36. Acronyms ANCC Auxiliary Network Control Center ADPE Automated Data Processing Equipment AT Acceptance Testing CIM Customer Interface Meeting CCB Configuration Control Board CDS Comprehensive Discrepancy System CM Configuration Management CSM Customer for Service Management DAS Demand Access System DR Discrepancy Report EC Engineering Change EIF Engineering Interface EPS External Processing System GALEX Galaxy Evolution Explorer Glory Solar Irradiance Gap Filler GPM Global Precipitation Mission GSFC Goddard Space Flight Center HA High Availability HMD Hardware Maintenance Depot HSF Human Space Fight HST Hubble Space Telescope HTSI Honeywell Technical Solutions Inc IBEX Interstellar Boundary Explorer ICD Interface Control Document IDR Intermediate Discrepancy Report IF Intermediate Frequency ISS International Space Station JSC Johnson Space Center LOP Local Operating Procedure MCE Mission Commitment Engineer NCCDS Network Control Center Data System NOM Network Operations Manager NPOESS National Polar-orbiting Operational Environmental Satellite System NENS Near Earth and Network Services O&M Operation and Maintenance PVM Performance Verification Matrix RFA Request For Action RTVM Requirements Traceability and Verification Matrix SERB System Engineering Review Board SIC Spacecraft Identification Code SN Space Network SNAS Space Network Access System SP&M Special Projects & Missions SPTR South Pole TDRS Relay SRD System Review document SRR System Requirements Review SSC Service Specification Code STS Space Transportation System SUPIDEN Support Identification Swift Swift Gamma Ray Burst Explorer SWSI SN Web Services Interface TBS To Be Scheduled TDRS Tracking and Data Relay Satellite TO&A TDRS Operations and Analysis TOCC TDRS Operations Control Center TRMM Tropical Rainfall Measurement Mission WSC White Sands Complex 36 36

More Related