Space Network Access System SNAS BETA Test Quick Start

0
0
2657 days ago, 1095 views
PowerPoint PPT Presentation

Presentation Transcript

Slide 1

Space Network Access System (SNAS) BETA Test Quick Start October 12, 2007 SN Project and the Customer Commitment Office

Slide 2

Beta Testing: August through December for Build 4 HMD DAS accessible 9 – noon* ANCC accessible 24 hrs. daily* New abilities presented by means of patches (.jug record overhauls) Notifications to enlisted clients will be sent Generate Problem Reports as discovered Problems found in Clients Adverse procedural or work prepare stream (i.e. excessively numerous snaps?, more natural process?) Operational irregularities (i.e. missed the watercraft in enhancing past framework) Problem Reporting: Bugzilla: [Administrator: Scott Robinson] http://defiant.gsfc.nasa.gov/snasdev/bugzilla/Alternative reporting channel: SNAS Web webpage http://snas.gsfc.nasa.gov (by means of Customer Input) *registered clients will be told of timetable changes

Slide 3

Beta Testing Preparation System Configuration SNAS MOC Client least equipment necessities: 1.5 GHz processor or more prominent 1 GB Random Access Memory (RAM) (testing with .5GB) 60 GB hard plate space (application estimate, barring log space) 1024x768, 32 bit shading show SNAS MOC Client programming prerequisites: Java Runtime Environnent (JRE) 5.0, accessible from Sun Microsystems Standard Web program (e.g., Netscape, Internet Explorer) To see TUT, download SNAS MOC Client programming, and advanced authentications Supported OS(s): Windows (2000, XP), MAC, Linux, UNIX FTP or sFTP server is provided by the MOC Network association with the Test System Server at first situated in the GSFC CNE system, will move to Open IONET when allowed client must sign the Rules of Behavior Agreement client must give static IP address when enrolling for get to

Slide 4

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 j oe.clark@itt.com (301) 486-4227 Customer Liaison: Dave Warren d avid.warren2@honeywell.com (301) 805-3681 Points of Contact Questions/Feedback

Slide 5

Beta Testing Preparations Presented By: Dave Warren

Slide 6

Beta Testing Preparation Registration/Client setup Step 1: Complete MOC User data and MOC Mission data on Rules of Behavior Step 2: MOC clients must supply their static IP deliver to the SNAS System Administrator for the workstation that will be utilized to interface client's MOC Client to the SNAS Server (call Scott or put on fax, yet not through email!) Step 3: MOC client ought to fax "marked" Rules-of-Behavior to the SNAS System Administrator (fax to: 301-286-1727) Step 4: SNAS DBA will apply MOC client IP deliver to the Firewall IP channel and will give an email affirmation to the MOC client Step 5: MOC client gets to http://snastest-www.gsfc.nasa.gov/to download Client programming and testaments to the assigned workstation for beta testing Step 6: Select "Acknowledge" from the NASA Website Privacy Statement Step 7: Select 'Create Certificate' and take after the well ordered guidelines Step 8: Select 'Customer Software' and take after the way to download the Client programming:/download/programming/full_distribution/Step 9: Download the MOC Client Software, and JRE 1.5.0_6 (if necessary) Step 10: Read the MOC Client INSTALL.txt directions (counting the client.prop cert modification) and note existing issues in RELEASENOTES.txt Step 11: Start the MOC Client programming (by means of runmocclient.bat [Windows] or runmocclient.bash [Unix]) and take after the prompts to reset the secret word (Note: basic window shows the customer's product action including mistakes when they happen) Step 12: Mission Manager arranges introductory client and mission parameters The latest draft of the MOC Client Users Guide can be gotten to specifically from the Client's Main Menu Help choice.

Slide 7

Beta Testing Preparation Steps 1-5 Materials accessible on SNAS Website: Rules of Behavior Draft User's Guide Problem Reporting

Slide 8

Beta Testing Preparation Steps 6 - 7

Slide 9

Beta Testing Preparation Steps 9 - 11

Slide 10

Beta Testing Preparation Step 12

Slide 11

Beta Testing Preparation Step 12 (Continued) Mission Manager to arrange clients 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

Slide 12

Beta Testing Data Pre-existing Beta Test information (from NCCDS) TDRS Ids/Groups SICs SSCs PEs O&M Approval information (from Mission Manager) User Accounts and Roles included SSC changes PE changes User Generated (reasonable beta testing) All mission defaults and qualities, and EPS hub information DAS Schedule & Playback Requests NCC Schedule Requests Orbital and Vector information by means of record imports

Slide 13

Functionality Presented By: Dave Warren

Slide 14

MOC Client User Roles User Access depends on the SIC and Role determination at Login Access to mission information depends on the SIC selection(s) Access to the MOC Client depends on the Role selection(s) Defaults to the most minimal get to level (if numerous Roles are chosen) Mission Managers Establishes User ID and SIC/Role access for all new client's (accessible electronically in the MOC Client) New client can get to SNAS after O&M favors the demand Mission Schedulers and Controllers New clients can get to proper menu usefulness in light of useful position

Slide 15

MOC Client Access Assignments (1 of 3)

Slide 16

MOC Client Access Assignments (2 of 3)

Slide 17

MOC Client Access Assignments (3 of 3)

Slide 18

MOC Client Build 1 Functionality 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

Slide 19

MOC Client Build 2 Functionality Demonstrated at CIM #6 Mission Setup Mission Characteristics – Spacecraft Characteristics, UIC EPS Configuration – Setup of Nodes & Message handling 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

Slide 20

MOC Client Build 3/4 Functionality Demonstrated at CIM #7 Scheduling SAR, SDR, RR era Bulk Scheduling Request Summary Displays – Schedule Request, Active Schedule Time Shift Timeline & Time Shift Display of TUT, TSW, User Constraints, USM, Requests information Real-time UPD GCMR Switch User MOC-O&M Data Exchange through Clients User Data SSCs & PEs Recurrent Scheduling

SPONSORS