MDPTS: Built In Message Processing

The new Multi-Device Position Tracking System (MDPTS) Omnitracs Interface can handle macro messages from the vehicle. These messages can in turn be used to update the orders in the dispatch system.

The omnitracs interface has the ability to process messages using a built in procedure. This is enabled via the UseBuiltIn entry in the INI file.

The built in functions are as follows:

  • Agent.DL
  • Agent.PU
  • Customs.Arrive
  • Customs.Clear
  • Customs.Delay
  • Customs.Seal.Apply
  • Customs.Seal.Change
  • Customs.Seal.Possess
  • Customs.Seal.Remove
  • Delay
  • DL.Arrive
  • DL.Attempt
  • DL.Complete
  • DL.Delay
  • DL.Redirect
  • Ferry.Arrive
  • Ferry.Depart
  • Ferry.Onboard
  • PU.Arrive
  • PU.Attempt
  • PU.Complete
  • PU.Delay
  • PU.Redirect
  • Trailer.Drop
  • Trailer.Switch
  • Van2Van.DL
  • Van2Van.PU
  • Whse.Depart
  • Whse.Return

Function Actions

Agent.DL looks for a field identifying the Agent name and then loops through the remaining fields for order numbers. For each order the system will update hauler activity if the vehicle is assigned to the order and the activity is being set off at a third party hauler. The order status is set to 45. An event (325) will be triggered.

Agent.PU looks for a field identifying the Agent name and then loops through the remaining fields for order numbers. For each order the system will update hauler activity if the vehicle is assigned to the order and the activity is being loaded from a third party hauler. The order status is set to 46. An event (326) will be triggered.

Customs.Arrive looks for a number of fields identifying order numbers. For each order number the system will update the hauler activity setting the status to 74. Assuming the vehicle was assigned to the order and the order marked as picked up, the order is also updated with the status set to 74 and the last known location as “at Customs”. An event (306) will be triggered.

Customs.Clear looks for a number of fields identifying order numbers. For each order number the system will update the hauler activity setting the status to 75. Assuming the vehicle was assigned to the order and the order marked as picked up, the order is also updated with the status set to 75 and the last known location as “left Customs”. An event (307) will be triggered.

Customs.Delay is not yet coded

Customs.Seal.Apply looks for a single field for the trailer (optional), a single field for identifying the party that applied the seal, and a list of seals. It will update the hauler activity for any order loaded but not delivered by the vehicle. It will update the master list of seals setting the use date, and unit. It will update the order adding an entry for the seal number, who applied it, and when it was applied. The order status will be set to 22 (Seals Changed) and an event (320) will be triggered.

Customs.Seal.Change is not yet coded

Customs.Seal.Possess looks for one or more seal numbers and updates the master list of seals setting the Assigned, AssignedTo, and Unit fields. The Unit fields are set to the vehicle. The AssignedTo field is the driver name.

Customs.Seal.Remove looks for a single field for the trailer (optional), a single field for identifying the party that removed the seal, and a list of seals. It will update the hauler activity for any order loaded but not delivered by the vehicle. It will update the master list of seals setting the broken date, location, and who broke it. The order status will be set to 22 (Seals Changed) and an event (321) will be triggered.

Delay is not yet coded

DL.Arrive looks for a single order number field. It will update the hauler activity setting the DL_When1 date and the status to 44. It will also attempt to update a local runsheet setting the arrival time for a delivery activity. This is done assuming the vehicle is assigned to the order. The order’s arrive at destination time is set (time zone too) if the delivery complete time is not yet set. The order status is set to 44. An event (303) is triggered.

DL.Attempt is not yet coded

DL.Complete looks for a field identifying the POD name and then loops through the remaining fields for order numbers. For each order it will update the hauler activity setting the date & time, the status to 12000, and marking the activity as delivery done. It will also update local runsheet setting the departure time for a delivery activity. This is done assuming the vehicle has been assigned to the order. The order’s delivery completed time will be set (time zone too) if not already set, the status set to 12000, the DelDone flag is set. An event (304) is triggered.

DL.Delay is not yet coded

DL.Redirect is not yet coded

Ferry.Arrive will loop through all orders assigned to the vehicle that have been marked as picked up and deliver today or in the future. It will set the order’s last known location as “at Ferry” and trigger an event (322).

Ferry.Depart will loop through all orders assigned to the vehicle that have been marked as picked up and deliver today or in the future. It will set the order’s last known location as “left Ferry” and trigger an event (324).

Ferry.Onboard will loop through all orders assigned to the vehicle that have been marked as picked up and deliver today or in the future. It will set the order’s last known location as “on Ferry” and trigger an event (323).

PU.Arrive looks for a single order number field. It will update the hauler activity setting the PU_When1 date and the status to 43. It will also attempt to update a local runsheet setting the arrival time for a pickup activity. This is done assuming the vehicle is assigned to the order. The order’s arrive at pickup time is set (time zone too) if the pickup complete time is not yet set. The order status is set to 43. An event (301) is triggered.

PU.Attempt is not yet coded

PU.Complete looks for a field identifying the POP name and then loops through the remaining fields for order numbers. For each order it will update the hauler activity setting the date & time, the status to 10, and marking the activity as pickup done. It will also update local runsheet setting the departure time for a pickup activity. This is done assuming the vehicle has been assigned to the order. The order’s pickup completed time will be set (time zone too) if not already set, the status set to 10, the LoadDone flag is set. An event (302) is triggered.

PU.Delay is not yet coded

PU.Redirect is not yet coded

Trailer.Drop looks for a trailer number to be dropped and an optional trailer number to be picked up. It will update any hauler activity assigned to the vehicle + trailer + DL_When1 date and update the DL_When2 time and mark the activity as DL Done. It will do this for Setoff (S), Empty (E), and Unload later (U) delivery activities. It will update the location of the dropped trailer as the location on the hauler activity. It will also add the trailer to the Trailer Dropped list. If the pickup trailer has been identified the system will update the Trailer Dropped list setting it as picked up. Any pickup hauler activity for Whse Load (W), Empty (E), or Remain on Trailer (R) will be updated as PU done and the PU_When2 time set. No events are triggered by this activity.

Trailer.Switch looks for a trailer number to be dropped and a trailer number to be picked up. It will update any trailer switch hauler activity assigned to the vehicle + dropped trailer + DL_When1 date and update the DL_When2 time and mark the activity as DL Done. It will update any trailer switch hauler activity assigned to the vehicle + pickup trailer + PU_When1 date and update the PU_When2 time and mark the activity as PU Done. No events are triggered by this activity. The date on the hauler activity must match the date of the message.

Van2Van.DL looks for a list of orders and updates the hauler activity for the vehicle. The activity must be a Van-to-Van delivery action with a scheduled date of between yesterday and tomorrow (a 3 day window) and the pickup action must be marked as done. The delivery date & time are set to the message timestamp. No events are triggered. The order’s Last Known Location is set to the vehicle’s position.

Van2Van.PU looks for a list of orders and updates the hauler activity for the vehicle. The activity must be a Van-to-Van pickup action with a scheduled date of between yesterday and tomorrow (a 3 day window) and neither the pickup or delivery action must be marked as done. The pickup date & time are set to the message timestamp. No events are triggered. The order’s Last Known Location is set to the vehicle’s position.

Whse.Depart will update hauler activity that loaded from the warehouse but has not yet been marked as done. This activity must have the vehicle and trailer assigned and match. The activity status will be set to 14 and will be marked as PU Done. The order status will be set to 14. The order’s depart warehouse time will be set (time zone too) and an event (300) triggered. Still need to code for whse load activities that have been marked as PU done (as per the bar code scanning system). Also need to determine changes to Local Runsheet handling if any.

Whse.Return is not yet coded

Future

Some of these actions may also be applied to other messages from the Omnitracs integration. Omnitracs messages like “Depart Geofence” could be used to trigger the “Whse.Depart” activity.

Additional functions such as SaveToFile may also prove useful when additional systems are involved (such as Mule ESB, or ArcESB) or other API end points need to be used with out processing the Omnitracs message.

Bookmark the permalink.

Comments are closed.