1.     Function keys, cursor positioning, and screen option entry are all supported means of system navigation.

2.     SSA standard function keys are listed across the bottom of the screens to allow rapid access to commonly used functions.

3.     The "Option" field on each screen allows experienced users to move from one area of the system to another without having to navigate through menus.

4.     A selection may be made by positioning the cursor beside any menu item and depressing the enter key.

5.     Pop up help is available throughout the system for all Control File definitions. By positioning the cursor on any Control File defined code field and depressing "F1" the system will display all codes defined for use in that field.

6.     Procedural help, or screen level help as it is frequently called, is available throughout the system. This help feature may be defined by each individual institution and is intended to simplify training regarding institutional procedures and policies. Selecting "F1" with the cursor positioned in any field that is not a control file defined field will result in the display of the procedural help screens defined for the displayed screen.

7.     The time of day and application date may be viewed in the upper left hand corner of each online screen.

8.     The online identifications used for each screen are consistent and logical. All branch Activity screens begin with the letter "A"; Control file screens begin with "C"; Maintenance, with "M"; Reporting, with "R", etc. Inexperienced users can access menus listing the various Inquiry screens by simply entering an "I" in any option field. From the displayed Inquiry menu they can then select any of the inquiry features listed on the menu.

9.     Informational displays on each screen assist branch and technical support personnel in answering questions for end users. These standard displays include the system application date, the online map associated with each screen, and the signin code of the user.

10.   Online error and instructional messages are displayed when appropriate throughout the system. These "people language" messages identify input errors and provide hints and reminders of functionality.

11.   The user defined literals, or "labels", make it easy to define fields to reflect current system terminology. This minimizes training and confusion generally associated with a change in systems.