1 / 38

Space Network Access System (SNAS) Delta - Operational Readiness Review (D-ORR)

Space Network Access System (SNAS) Delta - Operational Readiness Review (D-ORR). December 5, 2008 NASA Code 452 Space Network (SN) Project. Delta ORR Agenda. Welcome/Introduction Rose Pajerski ORR RFA Status Rose Pajerski Post ORR Acceptance Testing Merri Benjamin

neola
Download Presentation

Space Network Access System (SNAS) Delta - Operational Readiness Review (D-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. Space Network Access System (SNAS) Delta - Operational Readiness Review (D-ORR) December 5, 2008 NASA Code 452 Space Network (SN) Project

  2. Delta ORR Agenda • Welcome/Introduction Rose Pajerski • ORR RFA Status Rose Pajerski • Post ORR Acceptance Testing Merri Benjamin • 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

  3. Purpose of Review • The primary objectives of this review are to give evidence of closure of all open issues/RFAs determined from the September 4th ORR and receive concurrence to deliver Release 1 to SN Operations. • Provide status of RFAs • Provide status of the WSC defined actions for O&M readiness • Summarize post-ORR testing and status IDRs • Summarize requirements verified (SRD requirements sign-off) • Review documentation status (deliverables from development to operations) • Also provided are SNAS Release 1 follow-on activities • Release 2 status • Customer Transition activities

  4. Summary of ORR-identified Open Items • SNAS/DAS testing incomplete • Due to unavailability of DAS/HMD for SNAS testing, many SNAS/DAS Test cases were not able to be completed by scheduled September 4 ORR • Discrepancies discovered in testing needing resolution • Replace Request functions • TSW import functions • JSC-identified Open Items • RFA#7/#15 • WSC IT Security • Security Audit process needed to be defined

  5. Review Board • Joe Stevens, (chair), NASA GSFC Code 730 • Joe Aquino, NASA JSC ISS/STS • Markland Benson, NASA WSC Code 583 • Dave Campbell, NASA GSFC Code 584, HST • Curtis Emerson, NASA GSFC Code 453 5

  6. Prior Milestones • SNAS Release 1 Milestones • System Requirements Review 7/08/03 • Delta-System Requirements Design Review 4/28/05 • Preliminary Design Review 9/12/05 • Critical Design Review 5/04/06 • Implementation 6/5/06 - 7/20/07 • Integration/System Testing 8/07 - 5/08 • Beta Testing 8/07 - 8/08 • Server Shipment to WSC 5/06-12/08 • System Installation and Checkout 5/14-30/08 • Test Readiness Review 6/6/08 • Acceptance Testing (NCCDS Support) 6/23-8/29/08 • Customer Training 7/08-8/08 • WSC Operations Training 8/26/08, 10/27/08 • Performance Testing 8/28/08 • ORR 9/4/08 • Acceptance Testing (DAS Support) 12/2/08 • RFA Responses Concurred 12/3/08 6

  7. Moving Forward Schedule Scheduled Completion • Delta-Operational Readiness Review 12/5/08 • Rel. 1 Operational Availability 12/12/08 • Customer Training • CIM #9 12/10/08 • Customer Sites TBS • DAS Customers Transition to SNAS (as a group) TBS • End SWSI and UPS fixes/releases TBS 7

  8. Project Documentation System Requirements Doc. (DCN 002) CCB approved (4/30/08) Operations Concept Doc. (DCN 002) CCB approved (11/15/06) ICD between DAS/SNAS CCB approved (5/03/06) ICD between EPS/SNAS CCB approved (11/15/06) ICD between SN/CSM (DCN 002) CCB approved (10/29/07) Security Documentation 452 approved (10/29/07) System Test Document Final, 5/16/08 Acceptance Test Plan Final, 6/04/08 Program Verification Matrix (PVM) Final, 11/28/08 MOC Client Users Guide Final delivered with Rel. 1 O&M Client Users Guide Final delivered with Rel. 1 Server Operators Guide Final to SN CCB 8

  9. ORR RFA Status Rose Pajerski

  10. ORR RFAs • 15 RFAs submitted following ORR • 3 related to IT Security • 2 related to Server HW O&M (recovery and maintenance) • 4 related to software • 6 related to general operations - clarification/provide more details • All RFA responses have concurrence for closure from submitters

  11. ORR RFAs – IT Security • #9 – Include Security Controls in POA&M • Response: POA&M updated • Status: Closed • #11 – Security Audit Log – auditing not ready • Response: Developed and documented procedures for collecting and securing audit data • Per Rich Pearce email on September 16, 2008 • All the key audit log data with audit info, is either being written to the messages file and/or var/log/secure directory files to make auditing a capability. • Other audit capabilities (e.g., setting watches on key files, etc.) while eventually needed are not considered warranted at this time due to the frequent impacts they can cause if not properly planned and tested. • Status: Closed • #14 – Security Audit Log - audit events applicable to server environment • Response: Configured servers to capture required events • See response to RFA 11 • Status: Closed

  12. ORR RFAs – HW O&M • #1 – Hardware Disaster Recovery • Assess hardware failure modes and failure rates, document sparing philosophy and disaster recovery procedures and procure spare and vender agreements to meet availability requirements for SNAS • Response: • Server redundancy in design • Performance/loading test verified sufficient capacity to support operations on one string • Duality in RAID - two controllers, four disk drives into two logical volumes • Spares parts procured and in logistics at WSC • Service agreements/warranty documentation provided to WSC HMD • SNAS Team exploring feasibility of I&T server systems as backup to Ops • Status: Closed • #10 – Hardware Recovery Procedures • Need hardware recovery procedures documented – server sparing • Response: • A sparing plan for SNAS has been developed and all spares are available - spare KVM and KVM cables, spare HP system disk, NAS disk, tape drive, and spare APS battery are included in the sparing plan. • WSC ADPE Tech LOP developed – floor checks and system monitoring • Hardware maintenance according to WSC generic local operating procedures - ADPE Depot Engineers will order and/or replace any defective parts at the request of System Administrator. • Status: Closed

  13. ORR RFAs – Software • #6 – IDR 26451 Replace Request (RR) • IDR 26451 Replace Request – Reconcile Bugzilla and the CDS IDR. Make determination which is master. • Response: • IDR #26451 will serve as the master discrepancy report for this problem. • IDR #26451 was fixed and verified in Candidate 7 and regression tested in Candidate 8. The IDR is closed. • Status: Closed • #8 – HA bouncing resources between nodes • Need documented mitigation strategy for OPS. Recommend resolution prior to SNAS/DAS ORR. • Response: • Error in the HA configuration file on the SNAS "Open" servers at WSC has been corrected. Change made to default setting. • HA's management of the resources is now working as expected. IDR# 26487 closed. • Status: Closed

  14. ORR RFAs – Software (cont’d) • #7/#15 – JSC identified 21 “mandatory” items for SNAS to implement • Response: • 11 (#1, 2, 7, 8, 9, 10, 15, 16, 17, 18, 20) have been resolved in SNAS Release 1 • 2 (#3, 6) were resolved by software fixes in ANCC/NCCDS software • 2 (#11, 21) are enhancements and will be implemented in Release 2 scheduled to be delivered for Acceptance Testing in January, 2009 • 4 (#5, 13, 14, 19) are also enhancements and can be implemented in Release 3 • 1 (#4) is not a discrepancy and clarifications were provided to JSC • 1 (#12) could not be replicated • Status: Closed

  15. ORR RFAs – General Operations (1 of 3) #2 – Need NISN Rep for SNAS Would be desirable to have a NISN POC for SNAS and WSC connectivity issues Response: WSC TO&A is updating the procedures in the 450-OIP-DSMC, to state that all NISN issues are to be directly communicated to the NISN Comm Manager who will contact the appropriate personnel within the NISN organization. Status: Closed #3 – O&M Monitoring Create non-DBA role for O&M client access for read-only system monitoring, and create audit log with read-only access (or other restriction as required). Response: O&M Client access will be restricted to WSC Database personnel and WSC TO&A Test   The audit log read-only access addressed in RFA #11 Status: Closed

  16. ORR RFAs – General Operations (2 of 3) • #4 – Estimated Delivery/Installation • Follow up with NISN contact to obtain an estimated delivery / installation of out-of-band connectivity monitoring • Response: • This item is outside of the scope of the current TO-60 SNAS project. The Engineering Change (EC) documentation does not include this “out-of-band” monitoring activity as it was determined that this feature is not a requirement of the SNAS installation. • Status: Closed • #5 – Update SNAS architecture drawings • Update all drawings in ORR packages and other relevant documents to reflect NISN managed hardware that’s a part of the SNAS installation • Response: • Updated drawings have been generated, and will be included in the next update of the Server Operator's Guide, the User's Guides for the MOC and O&M Clients, the SRD and the OCD • Status: Closed

  17. ORR RFAs – General Operations (3 of 3) #12 – Version Information on Website Put version that Clients should be on SNAS website Response: New web page has been developed and posted on the SNAS home page. The page can be reached using the “Software” tab. As new releases or other updates become available, the developer will notify the web maintainer by email. The web maintainer will make the appropriate changes to the page contents. Status: Closed #13 – Security controls for UPDs Write an IDR or DR Response: A test was run with MOC Clients connected to both the SNAS Ops Servers (AT) and the SNAS I&T Servers (Beta Test) UPDs were transmitted to both the SNAS I&T Servers and the SNAS Ops Servers, The UPDs were never transmitted to the Beta MOC Client. There is no SNAS system discrepancy. ANCC/NCCDS database configuration changes can be made so a unique destination name is assigned per SIC and avoid “broadcasting” of UPDs. Follow-on meeting with JSC, GSFC, and WSC TO&A has occurred to discuss future database changes. Status: Closed

  18. Post-ORR Acceptance Testing Merri Benjamin

  19. Post – ORR Acceptance Testing • ORR results were based on Candidate 5 • Release summary post Candidate 5 • Candidate 6 fixes: IDRs • 26308 - The SNAS Notification Dialog box doesn't close • 26506 - Delete TSW with exact time boundary • 26507 - Invalid Message ID (XXXXXXX, non-numeric) contained in TSW messages • 26520 - Logins were not accepted for multiple Clients • 26523 - SNIF connection management problem • Candidate 7 fixes: IDRs • 26451 - Problem with RR/Clone from Active Schedule Summary • Candidate 8 fixes: IDRs • 26507- Invalid Message ID (XXXXXXX, non-numeric) contained in TSW messages 19

  20. Post – ORR Acceptance Testing (cont’d) • Candidate 8 Testing • Test specific fixes to Open IDRs • All but one verified fixed (#26488) • Regression test – rerun of Test Group 2 • Both NCCDS and DAS testing • TO&A developed regression tests executed successfully • Test plan to be used for future maintenance releases • Candidate 8 Testing Results • Closed 7 IDRs (Opened from Release 5 and on) • One new IDR (#26661) • Remaining Open IDRs • IDR 26488 – HA failed counts not incrementing • Not a factor in promoting Candidate 8 to Release 1 • Being investigated – possible HA-Linux patch required for resolution • This IDR will be transferred to CDS DR database at OPS delivery • IDR 26661 – DAS stale User Performance Data • Not a factor in promoting Candidate 8 to Release 1 • Being investigated – possible DASCON problem • This IDR will be transferred to CDS DR database at OPS delivery 20

  21. Requirements Verification(SRD DCN002) Joe Clark

  22. Requirements Verification • Numbered Requirements in 452-SRD-SNAS DCN 002 • Total requirements: 961 • Requirements not subject to verification • Deleted in DCN 002 or DCN 003: 85 • Higher level requirements: 93 • Implementation postponed: 9 • Verification results • Compliance accepted: 764 • Not verified: 10 • Inspection and verification against standards 7 • Operational procedures in place: 3

  23. WSC O&M Preparation Activities Marty Antholzner

  24. WSC Open Items – Status (1 of 3) 24 24

  25. WSC Open Items – Status (2 of 3) 25 25

  26. WSC Open Items – Status (3 of 3) 26 26

  27. WSC O&M Evaluation/Recommendation Marty Antholzner

  28. Evaluation/Recommendation Based upon the closure of the RFI and action items as briefed, WSC recommends that SNAS be declared operational with the understanding that the following will be completed: CIM training session to include WSC schedulers and console operators (OS, SS) Schedule coordination under way (scheduled for 12/10/08) Operations procedures in place TSI acceptable, formalization to be completed post CIM training Successfully completed DAS/SNAS Candidate 8 testing in the DAS HMD. Awaiting formal delivery of Release 1. WSC O&M is ready to support SNAS MOCC usage and customer transition per NASA direction. WSC OPS DBA functions for Customer support can commence WSC TOCC Operations will utilize O&M Client to monitor system HMD ADPE Techs will provide 24X7 monitoring of Server System 28 28

  29. SNAS Follow-on Activities Rose Pajerski 29

  30. Post-Release 1 Schedule • Release 2 • Implementation 8/08 – 12/08 • System Testing 11/08 – 1/09 • Beta Testing 12/08 – 2/09 • Acceptance Testing 1/09 – 2/09 • ORR 2/27/09 • Transition to Operations 2/09 – 3/09 • Operational Availability 3/9/09 • Release 3 1/09 – 9/09 30 30

  31. Post Delta-ORR Activities • Respond to RFAs turned in today • Finalize WSC SNAS OPS, EIF configurations • Finalize Release 1 documentation • Server Operator’s Guide • WSC Operations Procedures • Support Customers with their Transition to SNAS • Schedule Customer Interface Meetings • Host Customers at WSC • Visit Customer Sites • Work with Network Operations Managers (NOMs) and Mission Commitment Engineers (MCEs) • Plan and support DAS Customer Group Transition 31 31

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

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

  34. In Closing • Delta-ORR Objectives Completed • All RFA responses have received concurrence from originators • Acceptance testing is complete • All functional requirements have been verified • All non-functional requirements have been addressed • All WSC actions have been completed or have a documented plan for completion • Documentation is complete and under CM at WSC • Closing remarks from review board • Thank you for your attendance • RFAs • Due date: Today • Submit to Shina Sangani-Dave (Code 452, PAAC II) • Email: shina.sangani-dave-1@nasa.gov 34 34

  35. Backup Slides 35 35

  36. Deferred Requirements • Planned for Release 2 • 3.7.2.2.1 • “The SNAS shall display the system alert history over at least the last 24 hours for SNAS System Administrators, including alerts from the SNAS Application Servers as a minimum.” • 3.7.2.2.2 • “The SNAS shall display the system alert history over at least the last 24 hours for SNAS System Administrators, including alerts from the SNAS Database Servers as a minimum.” • 3.7.2.2.3 • “The SNAS shall display the system alert history over at least the last 24 hours for SNAS System Administrators, including alerts from the SNAS Certificate Servers as a minimum.” • 3.8.2.3.1 • “The MOC user shall have the ability to set applicable thresholds in the configuration settings for UPD parameters.” • 3.8.2.3.2 • “The MOC user shall have the ability to set applicable thresholds in the configuration settings for Alerts.” • Not Yet Scheduled • 3.4.2.1.6.4 • “The SNAS shall support importing Generic TDRS Views (GTV).” • 3.4.2.17.1.d • “The SNAS shall provide the capability to generate TSWs based on GTV.” • 3.8.9.1.3.c • “The EPS interface shall support 452-ICD-SNAS/EPS message 97/09 (Orbital Data Status)” • 3.8.9.2 • “The SNAS MOC Client application shall maintain a local log of all messages exchanged across the EPS interface.”

  37. Organization SN Project Manager Code 452 Keiji Tasaki SNAS Product Development Lead Rose Pajerski Resource/Business Manager Paula Tidwell IT Security Curtis Emerson Implementation Contractor NENS Systems Engineering Contractor ITT Product ManagementContractor PAAC-II NASA Contractor 37 37

  38. Acronyms ANCC Auxiliary Network Control Center ADPE Automated Data Processing Equipment AT Acceptance Testing CIM Customer Interface Meeting CCB Configuration Control Board CSM Customer for Service Management DAS Demand Access System DBA Data Base Administrator EC Engineering Change 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 ISS International Space Station JSC Johnson Space Center LOP Local Operating Procedure 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 PE Prototype Event PVM Performance Verification Matrix RFA Request For Action RTVM Requirements Traceability and Verification Matrix SA System Administrator 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 SRR System Requirements Review SSC Se4rvice Specification Code STS Space Transportation System SUPIDEN Support Identification Swift Swift Gamma Ray Burst Explorer TDRS Tracking and Data Relay Satellite TO&A TDRS Operations and Analysis TRMM Tropical Rainfall Measurement Mission TSW TDRS Schedule Window WSC White Sands Complex 38 38

More Related