(a) Unless otherwise specified, this section applies to all VMS units, MCSs, and bundles. Units that can operate as both an EMTU and EMTU-C must meet the requirements for both an EMTU and an EMTU-C in order to gain type-approval as both. Depending on the reporting requirements for the fishery(s) in which the requester is seeking type-approval, an EMTU-C type-approval may not require the inclusion of a dedicated message terminal and display component at the time of approval, but the capability to support such a component must be shown. To be type-approved in any given fishery, a VMS unit must meet messaging information requirements under the applicable VMS regulations and requirements in effect for each fishery or region for which the type-approval applies. The VMS unit must also meet the following requirements:

Ask a business law question, get an answer ASAP!
Thousands of highly rated, verified business lawyers.
Click here to chat with a lawyer about your rights.

(b) An EMTU must be able to run software and/or applications that send email messages for the purpose of complying with VMS reporting requirements in Federal fisheries that require email communication capability. An EMTU-C must be able to run or connect to a device that can run such software and/or applications. In such cases, the EMTU/EMTU-C messaging must provide for the following capabilities:

(1) Messaging from vessel to shore, and from shore to vessel by authorized entities, must have a minimum supported message length of 1 KB. For EMTU-Cs, this messaging capability need only be functional when in range of shore-based cellular communications.

(2) There must be a confirmation of delivery function that allows a user to ascertain whether a specific message was successfully transmitted to the MCS email server(s).

(3) Notification of failed delivery to the EMTU/EMTU-C must be sent to the sender of the message. The failed delivery notification must include sufficient information to identify the specific message that failed and the cause of failure (e.g., invalid address, EMTU/EMTU-C switched off, etc.).

(4) The EMTU/EMTU-C must have an automatic retry feature in the event that a message fails to be delivered.

(5) The EMTU/EMTU-C user interface must:

(i) Support an “address book” capability and a function permitting a “reply” to a received message without re-entering the sender’s address.

(ii) Provide the ability to review by date order, or by recipient, messages that were previously sent. The EMTU/EMTU-C terminal must support a minimum message history of 50 sent messages—commonly referred to as an “Outbox” or “Sent” message display.

(iii) Provide the ability to review by date order, or by sender, all messages received. The EMTU/EMTU-C terminal must support a minimum message history of at least 50 messages in an inbox.