Report to USCGS Healy Data and Communications Capabilities

James A. Moore
UCAR Joint Office for Science Support

The following report was prepared at the request of Lisa Clough, Chair of AICC. I will present a summary of the current status of Healy science data network (SDN) and other related communications capabilities and provide some recommendations for future enhancements to maximize utility and flexibility of the system. This will be done in the context of U.S. Coast Guard (USCG) support being provided to the Western Arctic Shelf Basin Interactions (SBI) Study.

The assistance from the USCG Healy crew was most appreciated. They were willing to answer all questions and are quite knowledgeable about most components of the SDN and related communications systems. I have assumed that the AICC members are familiar with the SDN capabilities so I do not plan to restate them here unless individual capabilities are specifically discussed.

General SDN Structure and Comments

The bandwidth aboard ship is certainly excellent for any scientific uses and data exchange among SDN users.

The SDN is completely separate from the USCG network aboard ship. The only minor issue here is that it is not possible to directly email USCG crew without messages being sent out over the satellite link and then returned onto the SDN. The solution at present seems to require the USCG personnel to have accounts on the SDN side to receive messages. This should work reasonably well but perhaps a more flexible solution might be considered so that the usually busy crew members don't have to take extra steps to log onto the SDN to receive messages from the scientific participants.

The typical connection to the SDN requires a fiber optic media interface. While these are available at some cost, the vast majority of users will come aboard ship with more typical RJ-45 (looks like a large wall phone jack). We spoke with the USCG and I believe it is their intention to provide an inventory of media converters that can be used by shipboard scientists. This is the right strategy and helpful to users. In addition the USCG will have some hubs or switches for multiple computer hook-ups in a single location such as a science laboratory. This is also a good strategy and useful to users.

The ship has configured Windows 2000 to act as the email server using Microsoft Outlook and support other services such as the web using Internet Explorer and FTP file exchange protocols. It was mentioned that there was an unfortunate occurrence of a computer virus being brought onboard on a science user workstation. It is important that the USCG keep up to date with virus protection software (e.g. Norton Utilities) and that they update this software continuously while at sea. This should be possible when the ship is connected to the Internet using the INMARSAT satellite data link. In addition, the USCG should require all science users to bring computers with virus protection installed, updated and functioning. The spread of viruses is so pervasive, especially via emails accessing the Microsoft Outlook software that these steps should be very important on all USCG deployments.

The last comment offered has to do with technician support for the SDN and users of the SDN. The USCG admitted that this support is sub optimal at the moment. For example, the Healy crew member responsible for the network in the upcoming SBI cruise in May has many other duty responsibilities. The USCG has had no choice but to minimize the network support responsibilities. Steps include limiting support to network connections for only computers with Windows 2000 operating systems as well as to offer no real assistance to users bringing Macs or Unix machines. While this is understandable every effort should be made to increase the flexibility and continuity of support.

The good news is that the USCG is working at this time on letting a contract to support SDN activities aboard all three polar class vessels. It should provide for continuity of technician support on all cruises, updates and improvements to the network on a regular basis and increased flexibility to support varied and unique requirements of science users. I was given the opportunity to review the statement of work prior during the preparation phase and it is clear that the USCG is committed to improving its service to science participants. It is important that the contract permit project scientists' direct access to the contractor personnel to work on support details for each cruise.

Data Communications Services and Comments

As part of recent improvements to the Healy a separate INMARSAT satellite communications system will be installed and operational for all cruises beginning in Spring 2002. This will permit all science users to have flexibility in the use of the satellite link. However, there is very big caution inherent in this flexibility and that is the matter of cost. The charge for INMARSAT is about $5.00 per minute for voice and $8.00 per minute for data. If one assumes 2 connections per day for one hour for data, a 30day cruise could cost nearly $30,000. Added charges for personal calls only increase the total. It would seem wise for the USCG, NSF and the scientists to work together to develop a strategy for efficient use of this resource recognizing that the cost can get out of hand very easily. Experience suggests that limited the size of incoming and outgoing emails and their attachments can help. Limiting the actual connect time is obvious although there are occasions when extended connections are reasonable. The point is that monitoring of the satellite communications resources is a critical function of someone on the cruise. A reasonable cost/time accounting procedure needs to be discussed and implemented.

It should be noted that the USCG offers an alternative satellite voice link using the Iridium system. The cost for voice links is only about $2.00 per minute but this system is not practical for data because of the narrow bandwidth possible. The USCG sells phonecards so costs become the responsibility of the user. The downside of this system is that the Healy offers only a single Iridium phone and it is in an inconvenient location in the Chief Scientist's quarters. Adding additional handsets located in more public areas of the ship should be considered. In addition, perhaps science users should be encouraged to bring their own Iridium phones aboard ship.

Underway Data and Documentation

Information about the underway data stream, instruments and archive procedures were provided to us. It is always difficult to provide up do date and complete information because system components and procedures are constantly changing. Part of the difficulty is that no one person can be committed to project to insure continuity in recordkeeping. It is suggested that the following components be part of a consistent documentation of the ship underway data;
          -Current instrument descriptions
          -Detailed parameter descriptions including measured or derived details units and resolution
          -Schematic that shows the position of all underway data sensors on the vessel.
          -Data format description and detail including file structure

Please note that in some cases information was complete for part of the underway data and instruments. In other cases it did not exist or was not readily available. Again I emphasize that is will improve with a more continuous support strategy via contractor.