1 / 72

Space Network (SN) Access System (SNAS) Customer Interface Meeting #11

Space Network (SN) Access System (SNAS) Customer Interface Meeting #11. December 15, 2009. Agenda. Project Status Release 3 Content MOC Client details client.prop Consolidated Menus GUI Display changes Graphical Timeline (DAS) Common User Issues O&M Client details View Differences

Albert_Lan
Download Presentation

Space Network (SN) Access System (SNAS) Customer Interface Meeting #11

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 (SN)Access System (SNAS) Customer Interface Meeting #11 December 15, 2009

  2. Agenda • Project Status • Release 3 Content • MOC Client details • client.prop • Consolidated Menus • GUI Display changes • Graphical Timeline (DAS) • Common User Issues • O&M Client details • View Differences • View History • Delete Users • Broadcasting

  3. Project Status

  4. Milestones • SNAS Release 3 • System / Beta Testing Nov/09 – 12/31/09 • TRR 11/19/09 • Acceptance Testing 12/03/09 - 1/15/10 • Customer Interface Meeting #11 today • Additional Training WSC and NOM provided as needed • DRR 1/26/10 • Transition to operations 1/27/10 • Upgrade of OPS mode servers 1/27-2/05/10 • SNAS Release 4 • PDR for Constellation changes 3/26/10

  5. 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 DCN 001 boarded 452 CCB (12/23/09) • ICD between SN/CSM (DCN 002) CCB approved (10/29/07) • Security Documentation 452 approved (10/29/07) • Acceptance Test Plan (Release 3) Final, 12/03/09 • MOC Client Users Guide tba Rel. 3 Client (1/15/10) • O&M Client Users Guide tba Rel. 3 Client (1/15/10) • Server Operators Guide 4/24/09

  6. Current Beta and WSC Versions • Release 2 • Resident on • WSC OPS servers connected to NCC & DAS - 09/23/09 • Beta OPS servers connected to ANCC – 11/17/09 • Release 3.0 • Resident on • WSC EIF servers connected to ANCC (& HMD DAS) - 12/03/09 • Beta EIF servers connected to ANCC - 12/02/09 • Linux OS (5.4), Oracle (10.2.0.4), JRE (1.6.0_15) • Neither release tested on Windows Vista or 7, or Mac 10.2

  7. Customer Community Status • Operational Projects using SNAS • 26 Projects (39 SICs) registered on WSC Operational (OPS) server • DAS users transition from SWSI to SNAS on 11/05/09 • NCC users • AIM, ALOS, ATV, EO-1, GALEX, GLORY, HST, HSTDS, HTV, IBEX, ISS, LSAT-4, NPOESS, OCO, SDO, SORCE, SPTR-2, THEMIS, TIMED, WISE • DAS users • 1K-ETE, DAS test • NCC & DAS users • CNOFS, ETE / SHADOW, FGST, LDBP, SWIFT • Beta Testing • 41 Projects (50 SICs, 133 users) configured on EIF server • Most active projects: HST, WISE, JSC, ALOS, GPM

  8. Release 3 Content

  9. Release 3 Stats • Candidate.0 • 12 Wishlist enhancements • 4 from JSC; 2 from HST; 3 from WSC; 3 miscellaneous • 6 Operational Discrepancy fixes • 56 Bugs • MOC Client • OAM Client • Server • Miscellaneous • Candidate.1 • 7 Operational Discrepancy fixes • 5 Bugs • MOC Client • Server

  10. SNAS COTS Upgrades • Beta EIF and WSC EIF • Open, Closed and Data Servers • RedHat Linux 4.7 OS upgraded to 5.4 • JRE 1.0.6_5 upgraded to 1.0.6_15 • Data Server • Oracle 10.2.0.3 RDBMS upgraded to 10.2.0.4 • OPS Failover to WSC EIF Data Server • Spare hard disks provided from GSFC to WSC with OS 5.4 • Oracle will be upgraded as soon as the original WSC OS 4.7 data is backed up to USM and reapplied to the newly installed GSFC OS 5.4 disks • This will provide quicker turnaround in the event of WSC Ops Data Server (still at OS 4.7) failure (2 hours versus 12 hours)

  11. Release 3 Content Details (1 of 8) • 12 Wishlist enhancements • W/L 13: Combine NCC and DAS scheduling • Handling DAS requests on the Timeline similar to NCC • W/L 25 Provide tools to support log management. • W/L 41 COTS upgrades (Linux, JRE, Eclipse, etc.) • W/L 42 Streamline MOC main menu • W/L 46 Allow O&M to select a user to send message to • W/L 47 Localization of client.prop file • W/L 53 Provide O&M review history • W/L 59 Add Event ID to Confirmed Events Reports • W/L J/L11 It's preferable to provide the capability for user to select colors of Alert panel text and background • W/L J/L 16 The default start time of Active Events Summary should be the current time • W/L 61-13 Pattern display drops, until configuration is saved. • W/L 61-14 Display doesn't index back to where user's last input was made

  12. Release 3 Content Details (2 of 8) • Operational Discrepancy fixes • DR 52475 High Availability - failed counts not incrementing • DR 56490 KASAR normal SSC GUI will not except values • DR 56491 Continuous red alerts when DAS is disconnected • DR 56494 SNIF sends SARs for unassigned SIC on another SIC's connection • DR 56495 NumberFormatExceptions in SNIF log files • DR 56500 TCP/IP Message causes exception. • DR56443 A large number of requests disappeared from the EIF database • DR56493 O&M Client must warn user when manual SNIF restart is required • DR56501 Intermittent display update issue on Active Events Summary • DR56524 SNIF transmitter thread queue overstock when connection is down • DR56526 SNAS O&M Client Cannot Delete Obsolete User Accounts • DR56786 Lost Connectivity with DAS and SDIF On SNAS • DR56879 SNIF exception when Acq Failure Notification message received

  13. Release 3 Content Details (3 of 8) • Bugs • MOC Client General • Localization of client.prop file (Bug 407) • Uncaught exception when user's certificate files not found (Bug 419) • Unnecessary pull down options (Bug 203) • Intf check’s on Orbital Parameter panel can’t be modified. (Bug 649) • Define Orbital Constraints panel has multiple bugs (inclu… (Bug 679) • After MOC Client logout/login without exiting, hourly TUT stops (Bug 700) • Issues with User-Defined TDRS Constraint Setup (Bug 709) • Functionality discrepancy for MOC Controller position (Bug 708) • Add checkbox to reverse the background of the Alert Summary display from blank to white (Bug 715) •  MOC Client log file using local timezone on SAR data details (Bug 544) • Bulk import does not validate the reference Id against…(Bug 641) • The bulkSar panel needs a relative time option (Bug 690)

  14. Release 3 Content Details (4 of 8) • MOC Client General (cont’d) • Incorrect Services displayed on Active Schedule Request Summary (Bug 428) • Duplicate active events have incorrect "Service Type Antenna" info (Bug 523) • Schedule Request Summary Filters upper/lower bounds field for Start Time (Bug 653) • Active Events Summary Filters Event ID Criteria upper/lower bounds field for Start Time (Bug 659) • Cannot print fully detailed Active Events Summary (Bug 673) • Active Event Summary panel is pulsing (Bug 675) • Active Schedule please wait notification panel not always closed when data received (Bug 676) • Rejected RR can’t be corrected and resubmitted (Bug 703) • No status update at the auto refresh interval on Active Event Summary (Bug 721) • Title of ActiveEventsSummary printout should not read 'Active Schedule Summary'. (Bug 720)

  15. Release 3 Content Details (5 of 8) • MOC Client : Graphic Timeline • Request auto refresh active schedule data from DAS at only a third of the NCC auto refresh rate Summary (Bug 689) • USMs periodically disappear and reappear on Graphic Timeline (Bug 704) • Deactivation of Save to Timeline Button for Graphical Timeline Replace Requests (Bug 710) • MOC Client : EPS Setup and configuration • Need a Recurrent Scheduling Request Message for the EPS ICD (Bug 672) • Need a Schedule Request Summary message for EPS (Bug 695) • SRM files from EPS interface contain multiple SRMs. (Bug 681) • Not All EPS response messages using EpsTmpDir variable (Bug 688) • EPS native USM file transfer duplicated (Bug 712)

  16. Release 3 Content Details (6 of 8) • MOC Client – EPS Recurrent Scheduling • Need DB commit/ rollback capability when saving / deleting from RS (Bug 658) • RS Edit superprototype panel - OPS locking up (Bug 696) • Exception when modifying RS pattern (Bug 701) • Panels locked by under popping Critical popup panel (Bug 702 • RS Pattern editor loses panel focus (Bug 706) • RS pattern names longer than 15 characters cause exceptions (Bug 725)

  17. Release 3 Content Details (7 of 8) • Client - Server • SNAS log files must not contain binary data (Bug 159) • Various StreamCorruptionExceptions (Bugs 536, 608, 661 • Return receipts being lost between SAM and MOC Client (Bug 545) • SAM-Sve connections lost due to timeouts (Bug 610) • EnumExtStatusExpCode enum error (Bug 655) • SAM is triggering a "Full" garbage collection every 11 seconds (Bug 660) • MOC Client disconnect from SAM - digit count range invalid (Bug 661) • SAR Panel doesn’t stop one of its threads when it closes. (Bug 667) • Duplicate calls to addWindowListener n SnasFrame subclass .. (Bug 668) • String values should be compared using .equals, not == (Bug 669) • AlertProcessor receipt timer should be cancelled on Logout. (Bug 677) • SAM Encounters “ArrayIndexOutOfBoundsException” (Bug 697) • Cleanup code causes multiple MOC Client windows to get Nu…( Bug 682)

  18. Release 3 Content Details (8 of 8) • O&M Client • OAM Client cannot approve/reject a request (Bug 207) • Alias missing from Available SSC panel (Bug 417) • KASARIF panels store UI Channel ID I Channel wrong (Bug 705) • MOC does not get notified of SSC changes for a DAS SSC. (Bug 713) • Purge Database utility does not purge UPD_LOG (Bug 717)

  19. Release 3 Acceptance Testing • Release 3 installed on WSC EIF servers for AT on 12/03 to • Run through (16) test cases and red lining procedures • Perform various checkouts of functionality • Perform Regression testing • Opened 6 Internal Discrepancy reports (IDR) • 27386 TSW message on TCP/IP Interface alert message missing data • 27385 EPS File Type Entry fields complain even when not needed • 27384 Bulk Replace is losing TSW constraining • 27382 SNAS delivery 3 isn't generating UPD selects on AT • 27381 Certain GUI should remain open after using the send button • 27378 Ingest TSWs without transmitting them • 27356 Shift Change Does not always take effect

  20. MOC Client details client.prop changes

  21. client.prop file changes • Localization of client.prop file • MOC Client can start up with a centrally controlled property file (with mission defaults), or override it with a local user configured file by supplying the runmocclient (.bat or .bash) with a path parameter to use a local, user preferences • .bat file: • javaw -Xms256m -Xmx512m -cp SNAS-COTS-client.jar;SNASmocclient.jar;resources.jar gov.nasa.gsfc.snas.mocclient.gui.MainControlPanel . absolute path for local user property file • .bash file : • java -Xms256m -Xmx512m -classpath ".:./SNAS-COTSclient.jar:./SNASmocclient.jar:./resources.jar" gov.nasa.gsfc.snas.mocclient.gui.MainControlPanel . absolute path for local user property file • EPS property allows creation of temporary EPS directory so that the file ingestion process is not interrupted • Import files are moved from import into this temporary directory for archive • EpsEnabled : false (previous in Rel 2) • EpsTmpDir : ./tmp (new in Rel 3) • User can choose whether to append multiple NCC or DAS messages to a single file or create individual files for each native message • If property set to true, multiple messages are written to a file. If false, each file will contain only one message. • MultiNativeMsgPerFile : true • New property for Start Time on Active Event Summary filter panel • User can specify whether the Start Time field contains current day or a day prior to current day (in days) • ActiveEventSummaryAllowablePriorDays : 0

  22. MOC Client details Menu Changes

  23. Menus – Release 2 vs 3 Menus with no changes User View Scheduling Control/Monitor Help Menus with changes Mission Setup Orbital & Vector Import Reports & Queries

  24. Menus – Release 2 vs 3 (2 of 4) • Mission Setup • Release 2 • Release 3

  25. Menus – Release 2 vs 3 (3 of 4) • Mission Setup

  26. Menus – Release 2 vs 3 (4 of 4) • Orbital/Vector Import access • Reports & Query access

  27. MOC Client Details GUI Displays

  28. Reports and Event Id • Reports under Reports and Queries menu option can now have and Event ID associated with each request • Controlled by checkbox on the selection panel

  29. Converted Submit to Create, Transmit, etc Panels containing a Submit button were in some cases converted to labels specific to the actual action to be performed

  30. Graphical Timeline DAS Scheduling

  31. Graphical Timeline Scheduling Tool (1 of 9) • Current Release 2 Layout

  32. Graphical Timeline Scheduling Tool (2 of 9) • Release 3 Layout

  33. Graphical Timeline Scheduling Tool (3 of 9) • DAS User can now schedule DAS Requests from the Time line • Resource Allocation Requests (RAR), • Resource Allocation Modification Requests (RAMR) • Resource Allocation Delete Requests (RADR) • This capability is similar to scheduling NCC requests introduced in Release 2

  34. Graphical Timeline Scheduling Tool (4 of 9)

  35. Graphical Timeline Scheduling Tool (5 of 9) • Double clicking on item with left mouse button shows possible list of requests that may be scheduled in the same period • Selecting one of the Request Ids from the list (item now boxed in Red) brings up additional options

  36. Graphical Timeline Scheduling Tool (6 of 9) • As with NCC Requests, user can select to see the Request details in one of the Detail Panes, or Clone the original request

  37. Graphical Timeline Scheduling Tool (7 of 9) • Clicking on the same area the user can compare the multiple requests

  38. Graphical Timeline Scheduling Tool (8 of 9) • User can select to generate a RAMR or RADR to any original request

  39. Graphical Timeline Scheduling Tool (9 of 9) • Or the user can view the Full Details of a request including SSC data

  40. Common User Issues

  41. User Issue List • Mission Parameter displays after updates • Schedule Request and Active Event Summary panel filtering • Summary panel updates and timing • EPS Node message transfers • UPD panels not displaying

  42. User Issue #1 • Mission Parameter displays after updates • When MOC Manager or O&M DBA changes items for a SIC • SUPIDENS, SSCs, PEs • Changes from Manager only seen by O&M DBA until Approved • Any other mission users only will see the original (SSC) parameters • Once Approved by O&M DBA, then changes are updated in database and become available to all users of the SIC • Changes are seen in panels only if the user terminates and then returns to the panel displaying the data • Approvals posted to squawk box on client panel of logged in users • Alert message is broadcast to all users of the SIC where the changes were made (if logged on, remains for 24 hours)

  43. User Issue #2 • Schedule Request and Active Event Summary panel filtering • Some Schedule Request types do not have a Start Time • Schedule Delete Requests (SDR) • Wait List Requests (WLR) • These requests won’t show using Start Time as the filter • Like wise, some Active Events don’t have Stop Times • Having a calculated Stop Time that is based on the Nominal Event Start time plus greatest service

  44. User Issue #3 • Summary panel updates and timing • The Schedule, Active Event and Graphic Timeline panels have a property • to activate the panel refresh (true or false) • and its own refresh time in the client.prop file • Refresh rates may be set differently, for example if one for 15 secs, the other to 60 secs, then the data is out of sync • When panels are opened the refresh clocks are initiated • Schedule Requests are generated by the user and saved in the SNAS DB and are updated when responses are received from the NCC (SRMs) or DAS • Active Events display are the result of USMs being sent by the NCC and then saved to the SNAS DB, and DAS events are pulled directly from the DAS • All this may lead to the panels updating data at different times • Panels can be re-synced by using the reload button

  45. User Issue #4 • EPS Node message transfers • client.prop file contains EPS activation entry • Turn on automatic EPS transfers • Sets default tmp directory if import, export, and archive directories are not specified in the EPS Node setup itself • All NCC and DAS request and response messages must be set for each node for the appropriate import (to NCC/DAS) or export (from) folder • Naming convention, Pass message Enabled, extension, and folder • Each NCC/DAS message must have the Forward Flag set to True to be passed to or from the NCC or DAS in EPS • Messages may be duplicated in a mission EPS structure if multiple nodes have the same message Forwarded (export) to same or a different directory • Note: The Active Event Upload process is controlled differently in that it is a mission setting set by the O&M DBA in conjunction with the MOC Manager and is outside of the EPS controls (saved to active_sched directory by SvE/SNIF)

  46. User Issue #4 (cont’d)

  47. User Issue #5 UPD panels not displaying data UPD's are not showing after selecting a service from the UPD Summary panel If MOC Client’s platform clock is not synchronized with the correct GMT then the user will only see a brief flashes of the UPD Details screen

  48. O&M Client details

  49. O&M Client – Change Control (1 of 6) • When MOC Managers submit mission data updates controlled in NCC, then the O&M DBA must update the data in the NCC DB • An O&M User is notified as soon as they log on to the O&M Client with a MOC Approval panel, or can bring up later from under System Monitor, then View Approval at a later time • The MOC Approval panel has been updated in Release 3 with a View Request and View History panels

  50. O&M Client – Change Control (2 of 6) Selecting the MOC Manager submitted change activates the new selection buttons Selecting View Request brings up a viewing panel as seen for an SSC change

More Related