System User Interface Specification

(PRELIMINARY)

Version: February 12, 1999

1.0) Introduction

This document defines the fishermen user interface to the software system. This interface is based upon a Windows type display presentation and interactions. All application buttons will be shown on the task bar, after the system has successfully completed its TBD power up test. The window's menu bar shall contain the menu items of the active application. User inputs shall be via the system's alphanumeric keyboard and mouse. On power-up, the system shall automatically start processes required to initialize, collect and store sensor data and provide VLS communication. [RCG is to check into this as an option. Currently, the Vessel Location System may not be able to easily integrate with our system.] The action of these programs shall be based upon system configuration data input when system [Joe update] hardware (sensors, external drives) and software (VLS, Nav) are installed.

2.0) Utility programs

Discussion

JBN: We did not discuss the utilities programs, e.g. to input system configuration parameters. I am assuming we will use window's NT utilities. Therefore, we need to override the normal power up to get to the Autoexec program and NT utilities.

RCG: I don't think it is a matter of overriding the normal power up sequence. I think one can include aliases of the programs to start up in a start up folder, or equivalent. It may also be possible to set up the registry to accomplish this.

JBN: 2/10 input - Start up folder sounds good to me, Do you want to take a cut at writing this part up or save as action for group inputs?

3.0) Primary Applications

The primary applications are: Wheelhouse, Navigation, VLS, Athena [data acquisition program)] and Exit.
Discussion

JBN 2/10 input--Bob, the Athena program is a automatic background program used to collect sensor data and does not require user interaction. Correct? If I have it wrong, please add a subparagraph to define this interaction.)

RCG: Yes, the Athena program should not require user interaction once the parameters are set up. I propose that the athena program start up at boot time, but that the task bar name/icon be hidden from view. I believe this can be done using the a properties option.

3.1) Wheelhouse

The Wheelhouse menu contains the following selections: Trip info, Fish catch, Sensor data, Whale sighting, Communications and Trip End.

3.1.1 Trip Info window

The Trip input window allows the user to enter trip critical information and enter or modify vessel data. This information is always defaulted to the previous trip entry. Vessel specific data, which are not normally changed on a trip basis, shall be accessed via an OPTION button within Trip input window. The system will always open following a successful power up with the Trip Info Window active. If this latter condition does not occur, the prior trip report is still active (see Par 3.1.5) or a fault is detected on power up.

The vessel specific inputs are: Vessel Name, USCG Doc. or State Reg. #, Home port, Captain Name

The Trip data inputs are: Date/time sailed (default to RTC on power up), Trip type (commercial, party or Charter), # of crew, # of anglers, Gear fished, Gear Mesh/ring size, Quantity of gear, Size of gear.

Figure 1 depicts the Trip input window with a brief explanation of the user entry fields. Figure 2 depicts the vessel input window (accessed by optional button in the Trip Window) and a brief explanation of user entry feilds.

[Input from Ken/Bob needed on figures.]

3.1.2 Catch Reporting Window

The Catch reporting Window provides the means for entering catch data from each set-out and retrieval cycle of gear. Data needed to define the gear set specifics from each cycle are also defined within this window.

Beside catch data, information entered in this window include: GPS location when gear was set out, GPS location of gear retrieval, time duration between gear set out and retrieval, average depth of gear, and set-out cycle number.

When an active net sensor is on board, the time and Lat./Long. at start and end locations for each tow will be determined based upon the loss (set-out) and recovery of net sensor RF signals, respectively. For each qualified loss of the net sensor RF signal, the Catch report's cycle number can be assigned. From processing of retrieved net sensor data at end of a tow, default values for duration time of tow and Ave. depth of tow can be recorded.

Discussion

RCG: I'm not sure how the average depth information will be computed. That may have to be entered by hand, or are you thinking that the system will use the values returned from the depth sensor and select the value?]

JBN: 2/10 - The gear sensor provides a depth reading along tow's path. By adding all these readings and dividing by total # of reading should give average depth.

RCG: 2/12 - I assume the average should be taken only of the deepest depth values.

Each of these data fields can be user modified.

The Fish Catch window also provides a user friendly method of recording estimated fish catch in near real time.

Discussion

JBN: Bob, the following paragraph is work in progress as related to system setup or configuration. Might be wise to ask Ken his method of system set up

Catch data transmission to shore are controlled by communication parameters defined during the hardware and software installation process. Communication parameters includes who is to receive Catch data, transmission times, and specifics of transmitted information. These system settings are maintained in an ASCII (text) configuration file that can be modified using any standard text editor such as notepad.

Figure 2 depicts the Catch reporting window and a brief explanation of user entry fields.

3.1.3 Sensor Data

This window allows the user to reveiw details of information recorded by the on-board sensors. Sensor data are automatically transmitted to shore. Sensor data are also used aboard to provide catch reporting information (reference section 3.1.2), and provide surface and sub-surface temperature plots for the Navigation windows (reference section 4).

Discussion

RCG: we still need to define how the separate navigation program gets these data.

JBN: 2/10- Bob, for info only, the commercial Navigation software builds a file of temperature vs. lat/long for use in building a temperature overlay on their Map displays. Ken, if he decides to do this part himself, will have to build a similar file.

Within this window the user can specify which sensors to display and in which format. Sensor data can be shown in an along track format (lat, long) or in time based chart format, (values versus time).

Discussion

JBN: 2/8 - Bob, what is a reasonable time for life of sensor information for charts? My opinion is a fishermen would be mainly interested in seeing water temp. data no longer than a trip.

RCG: -2/10 - I agree, but assume that one of our products could be historical data plots made available to the vessel on-demand. But it wouldn't surprise me if the fishermen, once they get used to this system, would want to see all "their" data from previous trips.

JBN: 2/10 - We need to look at available hard disk space to determine a reasonable cut-off. For base design, we can allocate a block of hard disk space with minimum room for a 30 day trip (long lines) and maximum of 1 year of data.

A specific presentation will be shown based upon user selection of the following items:

Discussion

RCG: 2/10 - the system should allow the user to select only those data parameters available on the trip.

JBN: 2/10 - I agree if you are referring to on-board sensor. No sensor = no data anyway.

RCG: 2/12 - I am referring to all available sensor data, whatever data are being collected.

3.1.4 Communications

This window provides a user the means to send and retrieve e-mail. Details TBD.

Discussion

JBN: 2/8 - Bob, would this be the best place for the user to define transmission parameters? When to transmit and what to transmit?

RCG: 2/10 - we could include code in here to edit the configuration file to adjust these parameters. Perhaps initially, these parameters can only be changed using a text editing program as noted above. But because of the cost of data transmission there may be some parameters that the user cannot change.

JBN: 2/10 - I am beginning to think we need one window to set up all the system parameters. The Windows system configuration type approach make sense.

3.1.5 Trip End

Before the program can exit, any remaining data must be telemetered to shore and the Port and State landed Fields, and Date Landed fields required by the NMFS trip report form need to be completed. Once the data are successfully transmitted (or at least some number of transmissions are tried] and the required fields are entered, the final trip report can be generated and transmitted/printed. [We need details about how this will be done].

A new trip information window will not be opened if active trip is not successfully ended in this manner.

Discussion

RCG: We'll need some kind of override, especially since we cannot guarantee a successful data transmission.

JBN 2/10 - How about if instead of opening into new trip info window on power-up we open on this window which defines what actions are needed to close last trip report?

3.1.6 Whale Sighting

[MIT input]

4.0) Navigation

The navigation program is a commercial software package from TBD [e.g. CAP'N]. This package has been modified to allow overlays of sub-surface and surface temperature data from on-board sensor.

Discussion

RCG: I agree about the surface temperature, although I didn't think the program was modified; rather, we need to provide the program with the data in some "acceptable" format. I didn't think the commercial software package could handle the sub-surface data.

JBN: 2/10 - The commercial approach does not care how data gets to the file just that a file exist which gives temperature at a given GPS location. I can see how different file names are used to depict use of surface temperature or net sensor file. User has menu button to select, surface temp., gear temp. or no temp. to overlay within their selected map presentation. Here, again a time parameter must be defined on age of temp. data is to be displayed. 24 hours is a reasonable time for Nav. use.

5.0) Exit

The exit button puts the system into an automatic shut series of actions needed to ensure all active processes are properly completed to enable an orderly restart of the system. This includes all stored data to be either transmitted, as required, or saved on the hard disk for restart at the same point in the trip. A message is provided to the user to define status of system for proper shutdown.

Discussion

RCG: this is another place to ensure that the "Trip end" requirements are met. See section 3.1.5.

JBN: 2/10 - A button selection to ask if trip is ended, or just shutting unit down for night makes sense here. If user selects trip end, system puts him into Trip end window.

rcg: 2/12 - I didn't think the system would ever be shut down. Cetainly, if there are such things as an engine temperature sensor, the system shouldn't be shut down unless the vessel were in port.

6.0) VLS

[Bob TBD]