space network access system (snas) beta test quick start october 12, 2007 sn project and the...

Space Network Access System (SNAS) Space Network Access System (SNAS)

BETA Test Quick StartBETA Test Quick Start

October 12, 2007

SN Project and the Customer Commitment Office

Customer Interface Meeting #7

NASA/GSFC Code 452

July 26, 2007

Beta TestingBeta 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

Near Earth Networks ServicesNear Earth Networks Services


NASA/GSFC Code 452

July 26, 2007

Beta Testing PreparationBeta Testing PreparationSystem ConfigurationSystem 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



NASA/GSFC Code 452

July 26, 2007

Points of ContactPoints of ContactQuestions / FeedbackQuestions / Feedback

Beta Testing:

– Chii-der Luo

– [email protected]

– (301) 805-3609

Test Problem Reporting:

– Scott Robinson


– (301) 286-0934

Wish List Request:

– Joe Clark


– (301) 486-4227

Customer Liaison:

– Dave Warren


– (301) 805-3681



NASA/GSFC Code 452

July 26, 2007

Beta Testing PreparationsBeta Testing Preparations

Presented By:

Dave Warren



NASA/GSFC Code 452

July 26, 2007

Beta Testing PreparationBeta Testing PreparationRegistration/Client setupRegistration/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 StatementStep 7: Select ‘Generate Certificate’ and follow the step by step instructionsStep 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.txtStep 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 parametersThe most recent draft of the MOC Client Users Guide can be accessed directly from the Client’s Main Menu Help option.



NASA/GSFC Code 452

July 26, 2007

Beta Testing PreparationBeta Testing PreparationSteps 1- 5Steps 1- 5

• Materials available on SNAS Website:

– Rules of Behavior

– Draft User’s Guide

– Problem Reporting



NASA/GSFC Code 452

July 26, 2007

Beta Testing PreparationBeta Testing PreparationSteps 6 - 7Steps 6 - 7



NASA/GSFC Code 452

July 26, 2007

Beta Testing PreparationBeta Testing PreparationSteps 9 - 11Steps 9 - 11



NASA/GSFC Code 452

July 26, 2007

Beta Testing PreparationBeta Testing PreparationStep 12Step 12



NASA/GSFC Code 452

July 26, 2007

Beta Testing Preparation Beta Testing Preparation Step 12 (Continued)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



NASA/GSFC Code 452

July 26, 2007

Beta Testing DataBeta 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



NASA/GSFC Code 452

July 26, 2007

FunctionalityFunctionality

Presented By:

Dave Warren



NASA/GSFC Code 452

July 26, 2007

MOC ClientMOC ClientUser RolesUser 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



NASA/GSFC Code 452

July 26, 2007

MOC ClientMOC ClientAccess AssignmentsAccess Assignments (1 of 3)(1 of 3)


R = Read; W = Write; X = Execute; FA = Full Access; LA = Limited Access; NA = No Access

Mission Manager

Scheduler / Planner

Controller Report Observer

User > FA FA FA LA LALog-in X X X X XLog-out X X X X XSw itch User X X XChange Passw ord X X X X XPreferences X X X X XExit X X X X X

View > FA FA FA FA FASystem Clocks X X X X XSystem Status Indicators X X X X XSystem Status Graphics X X X X X

Mission Setup > FA LA LA LA LAMission Spacecraft Characteristics >

Spacecraft Characteristics R/W RUser Interface Channels R/W R

EPS Configuration >EPS Setup R/W R RFile & Message Settings >

Pass NCCDS Messages R/W R/W R/WPass DAS Messages R/W R/W R/W

Service Types >Available Service Specif ication Codes (SSCs) R/W R RService Specif ication Codes (SSCs) DAS R/W R RService Specif ication Codes (SSCs) NCC R/W R R

Scheduling Defaults >Default Scheduling Parameters R/W R RPrototype Events R/W R RRS Edit Superprototypes R/W R RUser Defined TDRS Constraints R/W ROrbital Parameters R/W RDefine TSW Set IDs R/W RDefine Orbital Constraints R/W RAvailable Prototype Events R/W R


NASA/GSFC Code 452

July 26, 2007

MOC ClientMOC ClientAccess Assignments Access Assignments (2 of 3)(2 of 3)



Mission Manager

Scheduler / Planner


Orbital View & Vectors > FA FA LA NA NAGenerate Geocentric X XGenerate Geodetic X XImport >

State Vector X XBulk IIRV X XTCW X XPSAT X XUAV X XTSW X XTransmit TSWs X X X

Scheduling > FA FA LA NA NATDRS Unscheduled Time (TUT) X X XScheduling Tools >

TSW Summary X XGraphical Timeline X X XSchedule Request Summary X XActive Schedule Summary X X XTime Shift X X

DAS Requests >TDRS Visibility Request X X XResource Allocation Request (RAR) X XResource Allocation Delete Request (RADR) X XResource Allocation Modif ication Request (RAMR) X X XPlayback Request (PBKR) X XPlayback Delete Request (PBKDR) X XPlayback Modif ication Request (PBKMR) X X


NASA/GSFC Code 452

July 26, 2007

MOC ClientMOC ClientAccess Assignments Access Assignments (3 of 3)(3 of 3)



Mission Manager

Scheduler / Planner


NCC Requests >SAR X XSDR X XWLR X XASAR X XRR X XRecurrent Scheduling X XImport - NCCDS Message X X

Control & Monitor > FA LA FA NA LAPerformance Statistics X X X XAlert Stream X X X XUPD Summary X X X X

Reports & Queries > FA FA FA FA NAConfirmed Events Listing Report X X X X Confirmed Schedule Report X X X X Rejected/Declined Events Report X X X X Queries >

Schedule Data X X X X Service Type X X X X Prototype Events X X X X Service Specif ication Codes X X X X User Environment X X X X TDRS Scheduling Window s X X X X

Help > FA FA FA FA FAUsers Guide R R R R RAbout SNAS User R R R R RAbout SNAS Client Version R R R R RSecurity Warning R R R R RContact Information R R R R R


NASA/GSFC Code 452

July 26, 2007

MOC ClientMOC Client Build 1Build 1 FunctionalityFunctionality

• 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



NASA/GSFC Code 452

July 26, 2007

MOC ClientMOC Client Build 2 Build 2 FunctionalityFunctionality

• 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



NASA/GSFC Code 452

July 26, 2007

MOC ClientMOC Client Build 3 / 4 Build 3 / 4 FunctionalityFunctionality

• 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


space network access system (snas) beta test quick start october 12, 2007 sn project and the...

Documents