space network access system snas beta test quick start l.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Space Network Access System (SNAS) BETA Test Quick Start PowerPoint Presentation
Download Presentation
Space Network Access System (SNAS) BETA Test Quick Start

Loading in 2 Seconds...

play fullscreen
1 / 20

Space Network Access System (SNAS) BETA Test Quick Start - PowerPoint PPT Presentation


  • 262 Views
  • Uploaded on

Space Network Access System (SNAS) BETA Test Quick Start. October 12, 2007 SN Project and the Customer Commitment Office. Beta Testing. Testing: August through December for Build 4 HMD DAS available 9 – noon* ANCC available 24 hrs. daily*

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Space Network Access System (SNAS) BETA Test Quick Start' - daniel_millan


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
space network access system snas beta test quick start

Space Network Access System (SNAS) BETA Test Quick Start

October 12, 2007

SN Project and the Customer Commitment Office

beta testing
Beta Testing

Testing:

  • August through December for Build 4
  • HMD DAS available 9 – noon*
  • ANCC available 24 hrs. daily*
  • New capabilities introduced via patches (.jar file updates)
    • Notifications to registered users will be sent
  • Generate Problem Reports as found
    • Problems found in Clients
    • Adverse procedural or work process flow
      • (i.e. too many clicks?, more intuitive process?)
    • Operational inconsistencies
      • (i.e. missed the boat in improving on previous system)

Problem Reporting:

  • Bugzilla: [Administrator: Scott Robinson]
    • http://defiant.gsfc.nasa.gov/snasdev/bugzilla/
  • Alternative reporting channel:
    • SNAS Web site http://snas.gsfc.nasa.gov (via Customer Input)

*registered users will be notified of schedule changes

beta testing preparation system configuration
Beta Testing PreparationSystem Configuration
  • SNAS MOC Client minimum hardware requirements:
    • 1.5 GHz processor or greater
    • 1 GB Random Access Memory (RAM) (testing with .5GB)
    • 60 GB hard disk space (application size, excluding log space)
    • 1024x768, 32 bit color display
  • SNAS MOC Client software requirements:
    • Java Runtime Environnent (JRE) 5.0, available from Sun Microsystems
    • Standard Web browser (e.g., Netscape, Internet Explorer)
      • To view TUT, download SNAS MOC Client software, and digital certificates
    • Supported OS(s): Windows (2000, XP), MAC, Linux, UNIX
    • FTP or sFTP server is supplied by the MOC
  • Network connection to the Test System
    • Server initially located in the GSFC CNE network, will move to Open IONET when permitted
    • Client user must sign the Rules of Behavior Agreement
    • Client user must provide static IP address when registering for access
points of contact questions feedback
Beta Testing:

Chii-der Luo

chii-der.luo@honeywell.com

(301) 805-3609

Test Problem Reporting:

Scott Robinson

james.robinson@honeywell.com

(301) 286-0934

Wish List Request:

Joe Clark

joe.clark@itt.com

(301) 486-4227

Customer Liaison:

Dave Warren

david.warren2@honeywell.com

(301) 805-3681

Points of ContactQuestions / Feedback
beta testing preparations

Beta Testing Preparations

Presented By:

Dave Warren

beta testing preparation registration client setup
Beta Testing PreparationRegistration/Client setup

Step 1: Complete MOC User information and MOC Mission information on Rules of Behavior

Step 2: MOC users must supply their static IP address to the SNAS System Administrator for the workstation that will be used to connect user’s MOC Client to the SNAS Server (call Scott or put on fax, but not through email!)

Step 3: MOC user should fax ‘signed’ Rules-of-Behavior to the SNAS System Administrator (fax to: 301-286-1727)

Step 4: SNAS DBA will apply MOC user IP address to the Firewall IP filter and will provide an email confirmation to the MOC user

Step 5: MOC user accesses http://snastest-www.gsfc.nasa.gov/ to download Client software and certificates to the designated workstation for beta testing

Step 6: Select ‘Accept’ from the NASA Website Privacy Statement

Step 7: Select ‘Generate Certificate’ and follow the step by step instructions

Step 8: Select ‘Client Software’ and follow the path to download the Client software: /download/software/full_distribution/

Step 9: Download the MOC Client Software, and JRE 1.5.0_6 (if needed)

Step 10: Read the MOC Client INSTALL.txt instructions (including the client.prop cert adjustments) and note existing issues in RELEASENOTES.txt

Step 11: Start the MOC Client software (via runmocclient.bat [Windows] or runmocclient.bash [Unix]) and follow the prompts to reset the password

(Note: underlying window displays the client’s software activity including errors when they occur)

Step 12: Mission Manager configures initial user and mission parameters

The most recent draft of the MOC Client Users Guide can be accessed directly from the Client’s Main Menu Help option.

beta testing preparation steps 1 5
Beta Testing PreparationSteps 1- 5
  • Materials available on SNAS Website:
    • Rules of Behavior
    • Draft User’s Guide
    • Problem Reporting
beta testing preparation step 12 continued
Beta Testing Preparation Step 12 (Continued)
  • Mission Manager to configure users and mission parameters:
      • Add User Account
      • Mission Spacecraft Characteristics >
        • Spacecraft Characteristics
        • User Interface Channels
      • EPS Configuration >
        • EPS Setup
        • File & Message Settings >
          • Pass NCCDS Messages
          • Pass DAS Messages
      • Scheduling Defaults >
        • Default Scheduling Parameters
        • Prototype Events
        • RS Edit Superprototypes
        • User Defined TDRS Constraints
        • Orbital Parameters
        • Define TSW Set IDs
        • Define Orbital Constraints
        • Available Prototype Events
beta testing data
Beta Testing Data
  • Pre-existing Beta Test data (from NCCDS)
    • TDRS Ids/Groups
    • SICs
    • SSCs
    • PEs
  • O&M Approval data (from Mission Manager)
    • User Accounts and Roles added
    • SSC changes
    • PE changes
  • User Generated (realistic beta testing)
    • All mission defaults and characteristics, and EPS node data
    • DAS Schedule & Playback Requests
    • NCC Schedule Requests
    • Orbital and Vector data via file imports
functionality

Functionality

Presented By:

Dave Warren

moc client user roles
MOC ClientUser Roles
  • User Access is based on the SIC and Role selection at Login
    • Access to mission data is based on the SIC selection(s)
    • Access to the MOC Client is based on the Role selection(s)
    • Defaults to the lowest access level (if multiple Roles are selected)
  • Mission Managers
    • Establishes User ID and SIC/Role access for all new user’s (available electronically in the MOC Client)
    • New user can access SNAS after O&M approves the request
  • Mission Schedulers and Controllers
    • New users can access appropriate menu functionality based on functional position
moc client build 1 functionality
MOC ClientBuild 1Functionality
  • Demonstrated at CIM #5
    • User Login/logoff, Change User Password
    • Main Menu Bar, Clock, System Status Indicators
    • Create State Vectors (Geocentric, Geodetic)
    • Import State Vectors
    • Available SSCs
    • Edit DAS SSCs
    • TDRS Unscheduled Time (TUT)
    • DAS TDRS Visibility Request
    • Resource Allocation Request (RAR)
    • Resource Allocation Delete Request (RADR)
    • Resource Allocation Modification Request (RAMR)
    • Playback Request (PBKR)
    • Playback Delete Request (PBKDR)
    • Playback Modification Request (PBKMR)
    • Alert Message Log
moc client build 2 functionality
MOC Client Build 2Functionality
  • Demonstrated at CIM #6
    • Mission Setup
      • Mission Characteristics – Spacecraft Characteristics, UIC
      • EPS Configuration – Setup of Nodes & Message processing
      • Scheduling Defaults - Default Scheduling Parameters, User Define TDRS Constraints, Orbital Parameters, Define TSW Set Ids, Define Orbital Constraints, Available Prototype Events
    • Orbital View & Vectors
      • Import TCW, PSAT, TSW
    • Scheduling – TUT, TSW Summary
    • Reports
      • Confirmed Events, Confirmed Schedule, Rejected/Declined Events
      • Queries for Schedule Data, Service Type, Prototype Events, Service Specification Codes, User Environment, TDRS Scheduling Windows
moc client build 3 4 functionality
MOC Client Build 3 / 4Functionality
  • Demonstrated at CIM #7
    • Scheduling
      • SAR, SDR, RR generation
      • Bulk Scheduling
      • Request Summary Displays – Schedule Request, Active Schedule
      • Time Shift
    • Timeline & Time Shift
      • Display of TUT, TSW, User Constraints, USM, Requests data
    • Real-time
      • UPD
      • GCMR
    • Switch User
    • MOC-O&M Data Exchange via Clients
      • User Data
      • SSCs & PEs
    • Recurrent Scheduling