Space Network (SN) Access System (SNAS) Orientation & Training

1. Space Network (SN)Access System (SNAS) Orientation & Training July 30, 2008

2. Agenda • Project Status • Training • System Installation and Setup • MOC Client Basics • MOC Manager Setup • Vector Processing Overview • Scheduling Process Overview (NCCDS) • Real-Time Operations • Troubleshooting • SNAS Acronyms • Glossary

3. Project Status • Release 1 • Release 2 • Beta and WSC Management

4. Release 1 • TRR held June 6th • 11 Request for Action (RFA) submitted and responded to • Acceptance Testing started 6/16, running through 8/15 • MOC Client functions • Group 1 - System Configuration for Mission and User • 9 of 13 tests completed  • EPS Configuration and DAS set-up tests still to be completed • Group 2  - MOC Client Functions • 15 of 35 tests completed  • DAS Scheduling, Recurrent Scheduling, and Reports still be completed (most all of the SNAS/NCCDS functionality has been tested, e.g., SAR, SDR, WLR, GCMR, etc.) • Other Groups: O&M Client Functions, System Security, Server and Performance • ORR Scheduled for September 4th at WSC

5. Release 2 • Major Wishlist items implemented in Release 2: • Push updated TUT to MOC client • Retrieve latest TUT within 5 minutes of availability • Automatically send updated TUT to MOC client • Allow the user to select schedule requests in a bulk file for transmission or save to database only • Each request has transmission/save to DB/no action options • Add a Confirmed Events Report • Show confirmed events/services/parameters • Enhancement to Timeline • Graphical SAR panel • Drag and drop of cloned SAR • Allow user configurable alarm limits on numeric UPD parameters • Five configurable ranges: low critical, low warning, normal, high warning, high critical • Enable/disable connections to NCCDS without restarting SNIF process • Applicable to both schedule and real time connections • Provide TCP/IP interface as alternative to EPS • Streaming of messages that conform to SN/CSM ICD • Provide O&M client with display of alerts • Display alerts on request

6. Beta and WSC Management • Release 0.1 06/10/08 Version for Acceptance Testing (and ongoing Beta testing on I&T) • Test team to determine need for updates to complete AT • Release 0.2, Release 0.3, etc. until testing completed • Beta version will be kept in step with AT version • Release 1.0 ~08/22/08 Version to go to Operations • Release 2.0 ~10/08/08 Added R2 Wishlist functionality • AT testers to repeat functional and regression testing • MOC transitioning can start after 9/04/08 using Release 1.0 • Follow WSC registration and approval process • Work with O&M DBA for mission data (SIC, SSC, PE, etc,) • Capability for NCCDS connectivity only, as DAS users must transition all at one time (DAS port limitation)

7. SNAS Training • Section 1System Installation and Setup • CapabilitiesSNAS architecture & components • Certificate and Client Download • Client Configuration

8. Capabilities • Standards-based customer interface for performing TDRS scheduling, real-time service monitoring and control • Supports full NCCDS / Mission Operations Center interface (ICD Space Network / Customers for Service Management) • Supports full Demand Access System (DAS) ICD SNAS/DAS • Java-based Graphical User Interface (GUI) • Cross-platform compatible client application (Windows, Unix, etc.) • Accessible from the Internet, NISN Open & Closed IONets • Secure access through encryption (between Client and Server), certification, and authentication

9. Capabilities (cont’d) • Provides Internet and Open IONet access to TDRSS Unscheduled Time (TUT) • Orbiting or stationary state vector generation based on user input of geocentric (time, position & velocity) or geodetic (time, latitude, longitude, & altitude) coordinates • Provides local External Processing System (EPS) interface for exchange of files between SNAS MOC Client and other MOC platforms • Supports legacy Orbital Data Processing and Recurrent Scheduling functionality performed by User Planning System • Test mode for performing Engineering Interface (EIF) testing and user training • Maintenance of mission data by MOC Manager

10. SNAS Architecture

11. SNAS Components • Client platform • Desktop, laptop or workstation with static IP address • Minimum hardware requirements: • 1.5 GHz processor or greater • 2 GB Random Access Memory (RAM) (testing with .5GB) • 60 GB hard disk space (application, log space, file storage) • 1024x768, 32 bit color display • Open Server • Proxy server to allow • Open IONet and Internet-based users to connect to SNAS and access TUT • User requests directed to Closed Server through NISN Secure Gateway • Responses to users from Closed Server through NISN Secure Gateway • Closed Server • Hosts most of SNAS server applications • Manages user login sessions and communications with NCCDS, ANCC, and DAS • Data Server • Manages (Oracle) database storage, RAID access

12. Software Components • Client • Provides Graphical User Interface for performing SNAS MOC activities • Software requirements: • Java Runtime Environnent (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 is supplied by the MOC (for Client-EPS node transfers) • Servers • Service Access Method (SAM) • Process that allows user Clients to access SNAS services • Tracks user requests and provides responses to the Client • Separate instances run on Open and Closed Servers • Service Enabler (SvE) • Server process provides interface for Client with Data Server and DB • Processes users requests and generates responses • Communicates with Client through SAM • Separate SvE required for each SNAS server string (Ops versus EIF)

13. Software Components (cont’d) • SNAS-NCCDS Interface (SNIF) • Server process that communicates with NCCDS using SN/CSM ICD messaging protocol • Separate SNIF required for each of NCC and ANCC operations • SNAS-DAS Interface (SDIF) • Server process that communicates with DAS using DAS/SNAS ICD messaging protocol • Separate SDIF required for each of DAS (Operational DAS and HMD DAS test bed) • Data Manager • Provides connection to Oracle RDBMS and SNAS Database • Interface to RAID storage for customer configuration and scheduling data • Open TUT Server • Web server mirrors TUT services provided by NCCDS on Closed IONet • TUT data updated hourly on the Open & Closed servers by the NCCDS • MOC Clients will need to pull the TUT data from either server manually (Release 10

14. Certificate and Client Download (1 of 7) • New User Preparation • Rules of Behavior must be read and signed by each user and the user’s supervisor, and submitted to SNAS O&M DBA prior to access privileges being granted (user’s role should be specified) • Static IP address(es) must be provided (faxed or phoned) to the SNAS O&M DBA so that access to SNAS Server for first time Client download and certificate generation can be set up. • SNAS O&M DBA will update the ‘filter’ allowing user access, and notifies the new user via email (or phone) • User visits SNAS download website to generate certificate and download Client software (JRE software also provided on servers) • Beta • Open IONet address http://snastest-www.nascom.nasa.gov • Operations • Open IONet address http://snas-www.nascom.nasa.gov/ • Closed IONet address http://snas-www.ops.nascom.nasa.gov/ • Note: certificate is only available for download for 30 minutes after generation.

15. Certificate and Client Download (2 of 7) • Opening screen for Certificate / Client download • Select ‘Accept’ to respond to NASA Website Privacy Statement

16. Certificate and Client Download (3 of 7) • Select ‘Generate Certificate’ button and follow the step by step instructions Note Client version, requirements, and JRE download link

17. Certificate and Client Download (4 of 7) • Follow Certificate generation instructions Eventually move certificate zip file to the SNAS certs folder

18. Certificate and Client Download (5 of 7) • Download Client Software • Patch • Full

19. Certificate and Client Download (6 of 7) • Windows installation • Once file is on computer open the archive (SNASmocclient.zip). Select "extract" to extract the SNAS application files to a directory. The default directory is is the current directory where the archive is located. • The user can specify which directory to install the software. Ensure that the "All Files" and "Use folder names" options are selected. • Locate your key archive file (xyz-jdoe-key.zip) and select "extract" to extract the cert files. • This file should have been downloaded first as it contains your private key and your public SNAS certificate. If you have not already done so, you will need to generate your user certificates at the SNAS website. • Copy your certificate files into the "certs" directory in your expanded client. See the MOC User’s Guide for Client setup and installation instructions (including the client.prop cert adjustments)

20. Certificate and Client Download (7 of 7) • Unix/Linuxinstallation • Untar the archive (SNASmocclient.tar.gz or SNASmocclient.zip). This results in a directory tree that begins with "snas" • % cd to/an/installation/directory • % cp /my/download/directory/SNASmocclient.tar.gz . • If using the ".tar.gz" archive: • % gzip -d SNASmocclient.tar.gz • % tar xf SNASmocclient.tar • If using the ".zip" archive: • % unzip SNASmocclient.zip • % cd snas • Locate your key archive file (xyz-jdoe-key.zip). This file should have been downloaded first as it contains your private key and your public SNAS certificate. • This file should have been downloaded first as it contains your private key and your public SNAS certificate. If you have not already done so, you will need to generate your user certificates at the SNAS website. • Copy your certificates file into the "certs" directory in your expanded client: • % cp /my/download/directory/xyz-jdoe-key.zip certs/ See the MOC User’s Guide for Client setup and installation instructions (including the client.prop cert adjustments)

21. Digital Certificates • Each SNAS MOC Client user generates their own unique digital certificate using the web-based generation tool • User certificates expire one year after creation then the user will revisit the SNAS website to generate a new certificate • Certificates remain available for download by the user for 30 minutes

22. Client Configuration (1 of 5) • Preplanning step – decide your Client usage • Configure SNAS directory structure for single user versus multiple users of single Client application • Single application, single user directory (currently in Install.txt) snas | +-------------+---------+-------+--------+--------+------------+--------+--------+----------+ | | | | | | | | | | active_sched bulk_sched logs certs rctdm ttm upd sv_DAS sv_NCC tsw | | | | | +----+----+ +----+----+ + + + | | | | | | | archive current archive current archive archive archive active_sched/ -- Directory to Store Active Schedule bulk_sched/ -- Directory to Store Bulk Schedule Requests certs/ -- Certificate Directory certs/SNAS-ca-cert.der -- SNAS Certificate Authortity Public Certificate logs/ -- SNAS Client Log Directory logs/current/ -- SNAS Client Current Log Directory logs/archive/ -- SNAS Client Archive Log Directory ttm/ -- Time Transfer Message Log Directory rctdm/ -- Return Channel Time Delay Message Log Directory tsw/ -- TSW Import Directory tsw/archive -- TSW Import Archive Directory sv_NCC/ -- NCC Vector Import Directory sv_DAS/ -- DAS Vector Import Directory sv_NCC/archive/ -- NCC Vector Import Archive Directory sv_DAS/archive/ -- DAS Vector Import Archive Directory upd/current/ -- UPD Current Log Directory upd/archive/ -- UPD Archive Log Directory

23. Client Configuration (2 of 5) • Single application, multiple users with External Processing System

24. Client Configuration (3 of 5) • 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 • 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 it.

25. Client Configuration (4 of 5) • For Windows environment, put JRE’s Program Files folder: • a. JRE 1.5.0 located at C:\"Program Files"\jre1.5.0\ • b. JRE 1.6.0 located at C:\"Program Files"\jre1.6.0\ • Locate the application’s runclient.bat file and open it with notepad to • a. Change “javaw to C:\"Program Files"\jre1.5.0\bin\javaw” (to use v1.5.0 ) • b. Change “javaw to C:\"Program Files"\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).

26. Client Configuration (5 of 5) • 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 application’s 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).

27. Section 2MOC Client Basics • Client Properties • User Login • Main Menu Display options • ‘User’ Options • ‘View’ Options

28. MOC Client Functionality • MOC Client overview • MOC Manager is setup by the O&M DBA at WSC • MOC Manager can then establish and edit mission data including users and roles, spacecraft characteristics, EPS extensions for file/message transfers, Service Specification Codes and Prototype Event IDs, default scheduling and orbital parameters, prototype and superprototype events (recurrent scheduling), user and orbital constraints (orbital processing), and TSW Set IDs • Create separate mission roles for users: Planner/Scheduler, Controller, Support, and Observer • MOC User based on Role (i.e. Scheduler, Controller, etc.) • Generate or Import and transfer state vector, TCW/TSW, IIRV, PSAT/UAV, and bulk schedule files • Plan, create, modify, transmit and monitor schedule requests for NCC and/or DAS resources • Monitor NCC and DAS network connections and real-time event performance, and reconfigure real-time parameters (GCMRs) • Execute reports and canned queries for schedule requests and user environment configuration information

29. MOC Client Properties (1 of 14) • MOC Client properties in client.prop file in client download folder • Ten panels (view only) align with sections in client.prop file to view client’s configuration parameters but for Release 1 parameter changes made directly to client.prop file using text editor (prior to logon) • Certificates • CaPropFilePath - file name of the properties file that contains the fingerprint(s) of the Certificate Authority's public certificate that is to be accepted. The file is distributed with the Client software, and the user should change neither the file nor the property value. • caPropFilePath : ./CA.prop • CertificateAuthorityFile - file name of the certificate authority's public digital certificate. This is used to check the digital signature on the certificate presented by the server for authentication. The file is distributed with the Client software, and the user should change neither the file nor the property value. • CertificateAuthorityFile : ./certs/SNAS-ca-cert.der

30. MOC Client Properties (2 of 14) • ClientCertificateFile - file name of the user's public digital certificate. The user enters this when installing the Client software for the first time, or when installing a new certificate with a different file name. SNAS Client will allow multiple users to share the same application folder. For this to work, the Client needs to know all the registered users and where they store their certificates and passphrases. • mocuser1 certificates • mocuser1ClientCertificateFile : ./mocuser1/certs/company-user-cert.der • mocuser1PrivateKeyFile : ./mocuser1/certs/enc-company-user-key.der • mocuser2 certificates • mocuser2ClientCertificateFile : ./mocuser1/certs/company-user-cert.der • mocuser2PrivateKeyFile : ./mocuser1/certs/enc-company-user-key.der • mocuser3 certificates • mocuser3ClientCertificateFile : ./mocuser1/certs/company-user-cert.der • mocuser3PrivateKeyFile : ./mocuser1/certs/enc-company-user-key.der • CertificateExpirationWarning - number of days before a certificate expires that the user will receive an expiration warning during login. The warning will appear during each login session until a new certificate is installed. Certificates are generated with an expiration of 365 days. The warning value is initially set to 30 days. • CertificateExpirationWarning : 30

31. MOC Client Properties (3 of 14) • Login and Connection Properties • ServerIPAddress - domain name or IP address of the server used in the Login Panel. Note: SNAS has two servers, one for the OPS and one for EIF. Their preferred host names and ports might be different, by specifing host names for each mode, the application will attempt to find the appropriate host name and a port when given mode is selected. • for OPS • ServerIPAddressOPS : snas-ops.nascom.nasa.gov • ServerPortNumberOPS : 7810* • for EIF • ServerIPAddressEIF : snas-eif.nascom.nasa.gov • ServerPortNumberEIF : 7820* • ConnMode - defines whether to open the Login Panel with EIF mode selected. • ConnMode : OPS * Fictitious port numbers

32. MOC Client Properties (4 of 14) • UseSSL - defines whether the socket connection to the server will be encrypted. Since the operational servers do not allow unencrypted connections, this should always be set to true. • UseSSL : true • CipherSuite - defines the algorithm used to establish the SSL connection to the server. This is normally set to match the setting on the server and should not be changed unless under the direction of the SNAS DBA or System Administrator. • CipherSuite : SSL_RSA_EXPORT_WITH_RC4_40_MD5 • AccountExpirationWarning - number of days before a user's account expires that the user will receive an expiration warning during login. The warning will appear during each login session until the account is renewed. The SNAS DBA sets the account expiration time. • AccountExpirationWarning : 30

33. MOC Client Properties (5 of 14) • AckFrequencyMultiple - maximum time, in seconds, that the Client should wait before sending an acknowledgment (ack) to the server when the Client is receiving no data. The Client normally sends an ack after receiving data from the server, but only after the Client is able to process all the outstanding data on the socket. The redundant ack produced by this time ensures that the Client continues to receive data even if the server fails to receive the normal ack. The ack timeout also functions as a keepalive message to notify the Client when a connection problem has occurred, so that the connection doesn't remain in a half-open state where the server has closed the connection but the Client may think it is still open. • AckFrequencyMultiple : 120 • InputBufferSize - TCP socket read buffer size, normally set to match the server's output buffer size. The user should not change this unless directed to do so by the SNAS DBA or System Administrator. • InputBufferSize : 1024000

34. MOC Client Properties (6 of 14) • OutputBufferSize - TCP socket write buffer size, normally set to match the server's input buffer size. The user should not change this unless directed to do so by the SNAS DBA or System Administrator. • OutputBufferSize : 1024000 • AutoReconnect - option to try to automatically reconnect to the server if the socket connection to the server is lost. • AutoReconnect : true • MaxReconnectAttempts - if AutoReconnect is true, this property is the maximum number of reconnection attempts that will be made each time the connection is lost. If AutoReconnect is false, this property has no effect. • MaxReconnectAttempts : 10 • ReconnectDelay - if AutoReconnect is true, this is the delay in seconds between each reconnection attempt. • ReconnectDelay : 30 • CompressSocket - indicates whether incoming data on TCP socket is compressed. This is normally set to match the setting on the server and should not be changed unless under the direction of the SNAS DBA or System Administrator. • CompressSocket : true

35. MOC Client Properties (7 of 14) • SelectSICsAtLogin - for multimission users, defines whether a dialog will appear prior to completion of login to allow selection of which SICs will be used for that session. This is normally set to false since most users are authorized for only a single SIC. Setting to false also indicates to use all authorized SICs for each session. • selectSICsAtLogin : true • Alert Panel Properties • BringToFront - option to bring the Alert Panel to the front (on top of any open panels or windows) when an alert message is received. Note that if the Set Warnings option in the Alert Panel is set and a critical message is received, the pop-up message will bring the Alert Panel to the front even if the BringToFront property is false. • BringToFront : false • DisplayWarnings - defines whether to display a dialog box whenever a critical (red) alert is received. If true, display a dialog box. • DisplayWarnings : false • Alert Audible - play a sound when a critical alert occurs. Acceptable values: BELL, WHISTLE, NONE • AlertAudible : BELL

36. MOC Client Properties (8 of 14) • Logging Properties • WriteToLog - indicates whether alerts should be logged. Alerts are logged to a file if this is set to true. • WriteToLog : true • LogDir - directory where the current (active) log file is created. • LogDir : ./logs/current • ArchiveDir - directory to which archived (old) log files are moved. • ArchiveDir : ./logs/archive • ArchiveLogAge - Keep logs that are younger than this value (days). • ArchiveLogAge : 120 • PurgeArchiveAfter - Archieve that are older that this value (days) will be purged • PurgeArchiveAfter : 90 • AlertAge - Alerts that are as young as this value (hours) will be kept • AlertsAge : 24

37. MOC Client Properties (9 of 14) • Logging Properties(cont’d) • MaxLogFileSize - maximum output log file size in bytes. When the log file reaches this size and SwitchLogFileAtMax is set to true, the current log file is closed and a new log file is started. • MaxLogFileSize : 100000 • UPD Properties • UPDDefaultFilePath - for User Performance Data (UPD), this property defines the path to the properties file that defines the default UPD layouts to use for each SIC and service type. • UPDDefaultFilePath : ./UPDs.prop • DASUPDPrimaryExpirationTime - time in seconds by which another DAS UPD must arrive after which a service is flagged as expired. • DASUPDPrimaryExpirationTime : 120 • DASUPDSecondaryExpirationTime - time in seconds by which another DAS UPD must arrive after which a service is removed from the list of active services in the UPD Summary Frame. • DASUPDSecondaryExpirationTime : 360

38. MOC Client Properties (10 of 14) • UPD Properties (cont’d) • NCCUPDPrimaryExpirationTime - time in seconds by which another NCC UPD must arrive after which a service is flagged as expired. • NCCUPDPrimaryExpirationTime : 20 • NCCUPDSecondaryExpirationTime - time in seconds by which another NCC UPD must arrive after which a service is removed from the list of active services in the UPD Summary Frame. • NCCUPDSecondaryExpirationTime : 30 • UPDLogging - defines whether UPD messages received from NCCDS or DAS are logged. • UPDLogging : false • UPDAge - UPDs that are as young as this value (hours) will be kept • UPDAge : 24 • UPDLogDir - directory where UPD messages received from NCCDS or DAS are written to. • UPDLogDir : ./upd/current

39. MOC Client Properties (11 of 14) • UPD Properties(cont’d) • UPDArchiveDir - directory to which archived (old) UPD messages are moved. • UPDArchiveDir : ./upd/archive • UPDMaxLogSize - maximum UPD log file size in bytes. When the UPD log file reaches this size, the current UPD log file is closed and a new UPD log file is started. • UPDMaxLogSize : 1048576 • DAS Playback Properties • DefaultPlaybackIP - default Destination IP Address for DAS Playback Planning Requests • DefaultPlaybackIP : 123.123.123.123 • DefaultPlaybackPort - default Destination Port Number for DAS Playback Planning Requests • DefaultPlaybackPort : 0722

40. MOC Client Properties (12 of 14) • Active Schedule Properties • asEnable - defines whether the Active Schedules received automatically from the SNAS server are written to files. • asEnable : true • asOutputPath - directory where Active Schedule files received automatically from the SNAS server are stored. If asEnable is false, this property has no effect. • asOutputPath : ./active_sched • Bulk Schedule Properties • BulkSchedDir - set the default directory for the file chooser when users select Bulk Schedule Requests from the Main Control Panel • BulkSchedDir : ./bulk_sched • Recommended Bulk Data File Size 300 kilobytes * 1 kilobyte * 1024 bytes • BulkDataFileSize : 307200 • Recommended BulkRequestSubmissionInterval is 2 seconds • BulkRequestSubmissionInterval : 2

41. MOC Client Properties (13 of 14) • Return Receipt Properties • MinutesToWaitForReceipt - Maximum number of minutes to wait for a Return Receipt from the server prior to retransmitting. • MinutesToWaitForReceipt : 2 • HoursToStaleReceipt - Number of hours that a server request will be managed after which it is purged from the receipt management queue. • HoursToStaleReceipt : 24 • RetransmitsOnDbFailure - Maximum number of times to retransmit when a return receipt indicates a server database error. • RetransmitsOnDbFailure : 2 • EPS Properties • EpsImportDirPollTime - time (in minutes) delay between searches for files in EPS import dir. Minimum is 1 minute. • EpsImportDirPollTime : 10 • EpsEnabled : false

42. MOC Client Properties (14 of 14) • Squawk Box Properties • ShowSquawkBox : true • Debug Properties • SSLDebug - defines whether debug output is generated by the SSL security system. If true, generate debug output. This is normally only useful to a developer when trying to troubleshoot problems. This can generate a lot of output, thus slowing down the SSL connection, default is set to false. • SSLDebug : false • ClientDebug - defines whether debug output is generated by the Client application. As with SSLDebug, this is normally only useful to a developer when trying to troubleshoot problems. • ClientDebug : true

43. User Login (1 of 6) • Executing the runclient.bat (Windows) or runclient.bash (Unix/Linux) file, a splash screen (with version identification) and Main Control menu appear, then a NASA IT Security Warning panel is displayed for the user to read and acknowledge, otherwise the client will terminate.

44. User Login (2 of 6) • Once the Security Warning is acknowledged, the Login and System Status Indicator panels appear (with the Host, Port and Mode defaulting to the client.prop settings). • User supplies User ID, Password, and Passphrase, and change Mode if necessary. • Clicking on the Login button, the Client attempts to establish a connection to server (using passphrase), and then validates user credentials.

45. User Login (3 of 6) • If the Client is out of date with the server, the User is notified of the version mismatch (occurs when the SNAS system has been updated and user has not downloaded the required Client version). • Once the server validates the user credentials, the client-server connection is fully established, allowing the User to select their assigned SIC(s) and role. • If the User tries to proceed without selecting a SIC and Role, the system will generate the following notification.

46. User Login (4 of 6) • If multiple SICs differing in role levels are selected, the user will be notified of the role mismatch. • Be aware of account and certificate expirations dates • After selecting the appropriate SIC and Role, the User is notified of a successful login to the designated IONet server for the chosen SIC.

47. User Login (5 of 6) • The User will notice that the Main Control panel will change • User Id, Role, and Mode will appear in the Main Control status area • System Status Indicators panel will automatically update showing the current connection state of the Client with the server processes • The Indicators panel can be terminated, and then re-displayed from the Main Control ‘View’ option

48. User Login (6 of 6) • User should notice the Main Control options are limited to the Role selected. For example User has logged in as a Controller • Specific options assigned • No Mission parameter editing • Limited Scheduling options • Full Control & Monitor (see MOC Users Guide for details)

49. Main Menu Display options (1 of 2) • Area for mission data exchanges notices from O&M (Hide or Show) depending on number of messages

50. Main Menu Display options (2 of 2) • Font sizing changes in all windows (smallest to largest)