TransVoyant MMSI Look-up

The TransVoyant MMSI (Maritime Mobile Service Identity) Look-up job will use the job instance’s ESCs to find supported Delivery Schedule time table entries which do not have an MMSI specified, but which do have a Vessel Name and/or an IMO (International Maritime Organization) identifier.

For each time table entry, the TransVoyant MMSI retrieval web service will be called and the highest ranking MMSI returned will be selected. The MMSI will be set on the time table entry using either the first or second Vessel Tracking Number field.

The following Job Parameters may be specified when defining a TransVoyant MMSI Job Definition:

Parameter 1 – MMSI Field (Required): Specifies in which Vessel Tracking ID field the MMSI identifier is stored. IMO is assumed to be stored in the other tracking ID field.
- 1: The MMSI identifier is stored in Vessel Tracking ID 1
- 2: The MMSI identifier is stored in Vessel Tracking ID 2
Parameter 2 – Look-ahead horizon (Optional): Specifies the number of days in advance of the departure date of the sailing schedule that qualifying voyages should be picked for MMSI look-up.

For example: If this parameter is set to 30, no TTE having a departure date more than 30 days out (from system date) should be processed by this job.

Entity Selection Criteria Usage

ESCs specified for this job type must select time table entries. A time table entry is specified by the fields “Delivery Schedule ID”, “Timetable ID”, and “Timetable Entry ID”. findEntities API format ESCs should return these three fields. SQL format ESCs should return DLVY_SCHD_CD, ITNR_TMTBL_CD, and ITNR_TMTBL_ENT_CD.

Note: A default ESC is provided as a guide with the TM bootstrap schema and as part of the upgrade process. The default ESC may be modified or used as a guide when creating new ESCs for this job type.

Note: For more details, see the "Job Server" topic in the Transportation Manager System Administration Guide.