1 / 60

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

Space Network (SN) Access System (SNAS) Customer Interface Meeting # 10. July 21, 2009. Agenda. Project Status MOC Client Review Requirement and Setup Role and Responsibilities Release 2 and 2.1 Functionality client.prop File Properties Screen Updates Proposed Release 3 design

odell
Download Presentation

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

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 # 10 July 21, 2009

  2. Agenda • Project Status • MOC Client Review • Requirement and Setup • Role and Responsibilities • Release 2 and 2.1 Functionality • client.prop File Properties • Screen Updates • Proposed Release 3 design • Graphical Timeline layout to include DAS scheduling items • Other • External Processing System (EPS) • Automatic File exchange • TCP/IP capability

  3. Project Status

  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 • 2.1 Maintenance patch System / Beta Testing 6/01–26/09 • Acceptance Testing 7/01–17/09 • Transition to Operations 8/10-12/09

  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

  6. SNAS EPS ICD UpdatesJoe Clark 20 July 2009

  7. Change Summary • TCP/IP can be used as interface protocol as of SNAS Release 2 • New Reports and supporting information • Modified relationship between MOC Client and EPS 7

  8. Reports Added • Reports • Confirmed Events Report • Requested Events Report • Untransmitted Events Report • Activity Log Report • Requested Events Listing • Report Request and Report Response Messages Updated • Report Request Message values provided in Table 5-11 • Report Response Message values provided in Table 5-12 • Table 4-12 updated with complete list of reports • Report formats provided in new Appendix B • Active Schedule • Information on porting the Active Schedule to an EPS is provided in Section 4.1.8 8

  9. Modified Relationship between MOC Client and EPS • Initial Concepts • MOC Client could or would interface with one EPS • Message exchange would be either interactive or automatic • Mode controlled by a single software switch • Updated Concept • MOC Clients and EPSs • MOC Client can interact with 0, 1 or more EPSs • EPS can interact with 1 or more MOC Clients • Message Exchange • Automatic or interactive mode is selected on a message by message basis • Selection of mode for each message type is set in the Client.prop file on each MOC Client 9

  10. Current Beta and WSC Versions • Release 1.0 SN Operational version • Resident on Beta OPS and WSC OPS servers - 01/05/09 • Release 2.0 Wishlist and discrepancy additions • 2.1 patch Additional items from JSC • Resident on Beta EIF and WSC EIF servers - 06/26/09 • Move to Beta OPS and WSC OPS on week of August 9th • Release 3.0 Linux OS upgrade, Constellation requirements, wishlist and discrepancy • Move to Beta EIF in September 2009

  11. Customer Community Status • Operational Projects • 14 Projects (20 SICs) registered on WSC Operational (OPS) server • TIMED, THEMIS, WISE, SPTR-2 missions using SNAS • Beta Testing • 30 Projects (43 SICs, 114 users) configured on EIF server • Most active projects: HST, WISE, JSC, ALOS, THEMIS, LDBP • Release 2 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

  12. Release 2 Statistics • Consisted of 5 candidates installed on I&T servers for Beta testing • 09.candidate.1 delivered 22 bug fixes • 09.candidate.2 delivered 17 bug fixes • 09.candidate.3 delivered 8 IDR and 15 bug fixes • 09.candidate.4 delivered 2 DR, 7 IDR and 36 bug fixes • 09.candidate.5 delivered 2 IDR and 4 bug fixes • List of DR, IDR, and Bug fixes are identified in the RELEASENOTES.txt file downloaded with the MOC Client software

  13. Release 3 Contents • Provide tools to support log management. (W/L) • COTS upgrades (Linux, JRE, Eclipse, etc.) (W/L) • SNAS/Server - High Availability - failed counts not incrementing (DR) • Failed to receive USM from NCCDS Replacement SHO (IDR) • Notification of O&M change to MOC Client fails (IDR) • No way to manually export reports. (Bug) • Localization of client.prop file (W/L) • Combine NCC and DAS scheduling (W/L) • Streamline MOC main menu (W/L) • Allow O&M to select a user to send message to individual users (W/L) • Provide O&M review history (W/L) • Add Event ID to Confirmed Events Reports (W/L) • Complete processing of deleting a SIC (W/L) • RS Pattern display is dropped, until configuration is saved. (W/L) • Indexing user's last RS input that was made (W/L) • The default start time of Active Events Summary should be the current time (W/L)

  14. Release 3 Schedule Implementation 5/09 – 9/09 System Testing 9/09 – 10/09 Beta Testing 9/09 – 11/09 Acceptance Testing 11/09 – 12/09 ORR 12/09 Transition to Operations 12/09 Operational Availability 01/10

  15. MOC Client Review Requirement and Setup Role and Responsibilities

  16. Requirements and Setup (1 of 3) • Client provides GUI for performing SNAS MOC activities • Software requirements: • Java Runtime Environment (JRE) 1.6, available from client download or from Sun Microsystems websites • Standard Web browser (e.g., Internet Explorer, Apple Apache, Mozilla Firefox) to download Client, digital certificates, and view TUT • Supported OS(s): Windows (XP), MAC OS (10), Linux, UNIX • sFTP server to be supplied by the MOC (for Client-EPS node transfers) • Platform requirements • Desktop, laptop or workstation with static IP address • Users must have registered static IP address for each platform • Minimum hardware requirements: • 1.5 GHz processor or greater • 2 GB Random Access Memory (RAM) • (tested with .5GB but processing is very slow) • 60 GB hard disk space (application, log space, file storage) • 1024x768, 32 bit color display • No specific monitor size required

  17. Requirements and Setup (2 of 3) • Critical configuration steps after Client download • Move certificate files to appropriate SNAS folder (/certs) • Re-specify certificate location and name in the property file (client.prop) • Configure MOC platform directory structure if single Client application is shared among multiple users • Configure additional user settings in client.prop file • Reset runclient’s .bat* file command (optional) • javaw = no log display (Windows only) • java = display log dynamically • Configure the correct Java Runtime Environment (JRE) for your Client: • If MOC platform running multiple java applications requiring different java versions, each Java application has a start-up script, i.e. runclient.bat for a Windows environment, or runclient.bash or runclient.csh for a Linux or Unix environment. • *To view the MOC Client logging in real-time for debugging purposes, modify the • runclient.bat file, changing “javaw” to “java” before executing the client.

  18. Requirements and Setup (3 of 3) • For Linux or Unix environment the JREs may be located in the home directory • a. JRE 1.5.0 located at /home/cots/jre1.5.0/bin/java • b. JRE 1.6.0 located at /home/cots/jre1.6.0/bin/java • Locate the SNAS runclient.bash (or .csh) file and open it with your text editor and insert a line before your $JAVA statement • a. set JAVA = "/home/cots/jre1.5.0/bin/java" • b. set JAVA = "/home/cots/jre1.6.0/bin/java“ • Save change. When you start your Client it will then run under the JRE you assigned to it in the start up file (i.e. .bash or .csh). • For Windows environment, put JRE’s in Program Files folder under Java: • a. JRE 1.5.0 located at C:\"Program Files"\Java\jre1.5.0\ • b. JRE 1.6.0 located at C:\"Program Files"\Java\jre1.6.0\ • Locate the SNAS runclient.bat file and open it with notepad to • a. Change “javaw to C:\"Program Files"\Java\jre1.5.0\bin\javaw” (to use v1.5.0 ) • b. Change “javaw to C:\"Program Files"\Java\jre1.6.0\bin\javaw” (to use v1.6.0) • Save change. When you start your Client it will then run under the JRE you assigned to it in the start up file (i.e. .bat).

  19. Roles and Responsibilities (1 of 7) • MOC Manager • Initially setup by WSC’s O&M DBA for the assigned MOC supervisor, or for the Network Operations Manager – • someone assuming project responsibility for defining/controlling mission’s engineering parameters an/or MOC personnel assignments for the life of the mission • additional Manager roles can be assigned by the first Manager • Establishes and edits mission data including • Additional users and roles (Scheduler, Controller, Support, and Observer), • Spacecraft characteristics, default scheduling and orbital parameters, • Service Specification Codes (SSC) and Prototype Event (PE) IDs, • EPS Nodes and extensions for file/message transfers, • Prototype and superprototype events (recurrent scheduling), • User and orbital constraints (orbital processing), and TSW Set IDs

  20. Roles and Responsibilities (2 of 7) • Scheduler • Assigned by MOC Manager • Plans, creates, modifies, transmits and monitors schedule requests for TDRS resources via NCC and/or DAS • Generates, imports and transfers state vector, TCW/TSW, PSAT/UAV data • Controller • Assigned by MOC Manager • Updates original schedule requests (via replace or delete requests), • Monitors real-time event performance (UPD) from NCC and/or DAS • Generates reconfiguration requests for real-time flows (GCMRs) • Support • Assigned by MOC Manager • Execute reports and canned queries, gathering scheduling and real-time summary data and configuration information • Observer • Assigned by MOC Manager • Initiates scheduling and real-time monitoring displays that have no privileges

  21. Roles and Responsibilities (3 of 7) • General access

  22. Roles and Responsibilities (4 of 7) • Mission Setup access

  23. Roles and Responsibilities (5 of 7) • Orbital/Vector Import access

  24. Roles and Responsibilities (6 of 7) • Scheduling access

  25. Roles and Responsibilities (7 of 7) • Control & Monitor access • Reports & Query access

  26. Release 2 and 2.1 Functionality

  27. Release 2 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 27

  28. Release 2 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) 28

  29. Release 2 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 29

  30. Release 2.1 Updates • client.prop file • EPS setup temp directory issue • Make RS bulk SAR output directory configurable • Change default directory from home to current when importing an RS-generated bulk SAR file • client.logging.xml file • User ID added to the client log file names for better identification • Client GUI • Provide manual reload capability on TSW summary panel (similar to the "Filter" button on summary panels) • TSW summary display should be sorted by Start Time as default • Change default time selection/filter for Schedule Request Summary to Start Time • Allow larger font size when printing schedule request summary Alert Messages • Do not use the word "Submit" on buttons (ex. Submit GCMR) unless the action is actually submitting to NCC/DAS

  31. Release 2.1 Updates (cont’d) • Provide the capability of displaying contents of an RS superprototype / prototype in a format similar to that in UPS • TUT response received via EPS TUT request does not follow EPS ICD -- repetitive TDRS and services; and one extra column of 1 (1st column) • Incorrect UPD Summary Status in SNAS • Kill Timeline does not kill child SAR panel • Transmit TSW panel enhancement • Saving Scheduled Requests to DB without transmission (for RRs) • Client – Server Connections • Client to server communications hung • Data base Updates • KaSAR IF service type • Provide the capability of copying EPS setup and RS-related setup (prototypes and patterns) from one SIC to another SIC

  32. MOC Client Properties • The client.prop file is located in MOC Client’s home directory • In Release 2, client property changes can be made • directly to client.prop file using a text editor (prior to logon) or • using the Client Properties panel under the User option on the Main menu (changes take affect after re-login)

  33. New/Updated Client Properties (1 of 5) • ##### Squawk Box Properties ShowSquawkBox : true • ##### Hourly TUT Retrieval Properties## HourlyTutActivated : true HourlyTutDirName : ./hourlyTut HourlyTutFilePrefix : tut HourlyTutFileExt : tut • ##### Schedule Request Summary Properties ScheduleRequestSummaryAutoRefresh : true # number of seconds ScheduleRequestSummaryAutoRefreshInterval : 20 • ###### Active Event Summary Properties ActiveEventSummaryAutoRefresh : true # number of seconds ActiveEventSummaryAutoRefreshInterval : 20 • ##### Timeline Summary Properties TimelineAutoRefresh : true # number of seconds TimelineAutoRefreshInterval : 20

  34. New/Updated Client Properties (2 of 5) • ##### Recurrent Scheduling Properties # RsBulkFileDir - The dir in which RS will drop the generated bulk file RsBulkFileDir : . # RsBulkFileExt - the ext of the generated bulk file RsBulkFileExt: blk • ##### EPS (FTP) Properties # EpsImportDirPollTime - time (in minutes) delay between # searches for files in EPS import dir. Minimum is 1 minute. EpsImportDirPollTime : 5 # EpsTmpDir - import files are moved from import dir into this # tmp dir temporarily EpsEnabled : false EpsTmpDir : ./tmp

  35. New/Updated Client Properties (3 of 5) • #### EPS (TCP Alternative) Properties (13 parameters) # EnableEpsTcpIp - enables the EPS TCP/IP option EnableEpsTcpIp : false # MocLocalHostName - the host name that EPS TCP node uses to # connectto MOC client MocLocalHostName : localhost # EnableSchedulingServices - enable the NCC scheduling service # connections on ports: {SchReqSvcPort, SchStatusSvcPort, # AcqStoreSvcPort, TswStoreSvcPort}. # The SNAS O&M DBA needs to enable mission's scheduling # service EnableSchedulingServices : true # EnableRealtimeServices - enable the NCC realtime service # connections on ports: {PmDataSvcPort, ReconfigSvcPort}. # The SNAS O&M DBA needs to enable mission's realtime service EnableRealtime Services : false

  36. New/Updated Client Properties (4 of 5) • #### EPS (TCP Alternative) Properties (cont’d) # SchReqSvcPort - NCC SchReq Service port that EPS TCP node uses to # connect to MOC client SchReqSvcPort : 35101 # SchStatusSvcPort - NCC SchStatus Service port that EPS TCP node uses # to connect to MOC client SchStatusSvcPort : 35102 # PmDataSvcPort - NCC PmData Service port that EPS TCP node uses to # connect to MOC client PmDataSvcPort : 35103 # ReconfigSvcPort - NCC Reconfig Service port that EPS TCP node uses to # connect to MOC client ReconfigSvcPort : 35104 # AcqStoreSvcPort - NCC AcqStore Service port that EPS TCP node uses to # connect to MOC client AcqStoreSvcPort : 35105 # TswStoreSvcPort - NCC TswStore Service port that EPS TCP node uses to # connect to MOC client TswStoreSvcPort : 35106

  37. New/Updated Client Properties (5 of 5) • #### EPS (TCP Alternative) Properties (cont’d) # EpsNccNativeHexDumpOn - to log all EPS-TCP NCC Native data # in Hex EpsNccNativeHexDumpOn : true # EpsNccNativeHexBlockSize - the block size for aligning # EPS-TCP NCC Native data Hex logs EpsNccNativeHexBlockSize : 20 # EpsNccNativeAsciiDumpOn - to log all EPS-TCP NCC Native # data in ASCII EpsNccNativeAsciiDumpOn : true # MaxNumOfRetransmits - maximum number of retransmits when an # EPS-TCP request is not able to be stored in the database # with non-fatal status or not responded to by the server # in timely manner. MaxNumOfRetransmits : 1

  38. Screen Updates – Default Scheduling Parameters • Control for Use TSW on SAR and Recurrent Scheduling panels Note: user needs to logoff and back in again for new defaults to take affect

  39. Screen Updates – Summary Filtering (1 of 3) • Filtering prior to Scheduling Request Summary panel display

  40. Screen Updates – Summary Filtering (2 of 3) • Filtering prior to Active Events Summary panel display

  41. Screen Updates – Summary Filtering (3 of 3) • Filtering prior to Graphical Timeline panel display

  42. Screen Updates – User Specified UPD Ranges • Selecting option for UPD Parameter Ranges allows the user to add, modify or delete warning and critical range values for UPD parameters

  43. Screen Updates – Query Active Event Upload • From the Reports and Queries, the user can see the parameter settings for their Active Event Upload file updates

  44. Screen Updates – Recurrent Scheduling • Display Superprototype / Prototype Text

  45. Screen Updates – Creating SAR from TUT (1 of 6) • On any TUT row on Graphical Timeline, right clicking on TUT brings up TUT composite panel • Right clicking on any of the service rows brings up TUT SAR Menu

  46. Screen Updates – Creating SAR from TUT (2 of 6) • Once SAR panel appears, select SUPIDEN and PE/SSC, then adjust timing (Nominal start/duration, Event Start), click on Save to Timeline

  47. Screen Updates – Creating SAR from TUT (3 of 6) • Returning to Timeline, user can see new SAR which hasn’t been transmitted yet

  48. Screen Updates – Creating SAR from TUT (4 of 6) • Right clicking on new but un-transmitted SAR brings up Timeline Menu to Delete, Save To DB or Transmit it • Selecting Transmit activates an notification alert

  49. Screen Updates – Creating SAR from TUT (5 of 6) • At the Alert Stream panel, the SRMs and USM are displayed, and once received, the Timeline updates the SAR status and adds USM

  50. Screen Updates – Creating SAR from TUT (6 of 6) • Right clicking on SAR allows user to bring up menu to view data by sending it to a Detail Panel

More Related