DotcodesDefaultCodes < Cargooffice

Tags: view all tags
---++ Description of default codes and actions

For new Cargo Offices these dotcodes can be found at Backoffice -&gt; Disptach -&gt; Dot Codes

---+++ BJ : Begin Job (jobID)

SMS-users need to define a .DOT code to pass the shipmentID. BJ has a shipmentID. For SMS-users the shipmentID will be remembered by the system as being the 'Active Shipment' for this driver. For PDA-users a shipmentID will be passed anyway.<br /> For SMS-users all following messages will be registered to the same shipmentID until the driver sends a new .BJ message.
   * At present time the contents field inside the action should list:<br /> shipmentID : {shipmentID}<br /> pickupSentBit : 2<br /> pickupStatus : begin job

---+++ BW: begin work (hhmm)

This dotcode reports that this node/driver has started to work this day.
   * At present time the contents field inside the action should list:<br /> update_trip_startTime(valueOf(BW))

---+++ DELNO : delivery not ok (remarks)

This dotcode reports that this particulair shipment was not delivered well.<br /> After typing a dotcode the user can type the reasom why.
   * At present time the contents field inside the action should list:<br /> shipmentID : {shipmentID}<br /> deliverySentBit : 2<br /> deliveryStatus : delivery not ok<br /> status : +{sent} delivery not ok ({nodeID} reported: {DELNO})

---+++ DELOK : delivery ok

This dotcode reports that this particulair shipment was delivered well.
   * At present time the contents field inside the action should list:<br /> shipmentID : {shipmentID}<br /> deliverySentBit : 2<br /> deliveryStatus : delivery ok<br /> status : +{sent} delivery ok

---+++ DELRE : delivery ok (remarks)

This dotcode reports that this shipment was delivered though there is a remark attached to it.
   * At present time the contents field inside the action should list:<br /> shipmentID : {shipmentID}<br /> deliverySentBit : 2<br /> deliveryStatus : delivery with remarks<br /> status : +{sent} delivery with remarks ({nodeID} reported: {DELRE})

---+++ DELWA : delivery warehouse

This dotcode reports that this shipment was delivered at the warehouse.
   * At present time the contents field inside the action should list:<br /> shipmentID : {shipmentID}<br /> pickupSentBit : 2<br /> pickupStatus : delivery warehouse<br /> status : +{sent} delivery warehouse ({nodeID} reported: {DELWA})
---+++ EDODO: end odometer (km)

This dotcode reports the end value of the odometer.

update_trip_endODO(valueOf(EDODO))
---+++ EJ : end job

This dotcode reports that working on this particular job has ended.<br /> This dotcode is mostly used by distributers informing they are back at base or warehouse.
   * There is no action attached to it, because it is only reporting information. If desired the triangle inside the dispatch planboard could be configured inside a different colour (green).

---+++ EW : end work (hhmm)

This dotcode reports that this node/driver has finished working this day.<br /> When this driver also had entered a .BW when starting his workday, the calculation of his working hours could be easily added to a statistics sheet.
   * At present time the contents field inside the action should list:<br /> update_trip_endTime(valueOf(EW))

---+++ LO : loading (hhmm)

This dotcode reports the loading time
   * There is no action attached to it, because it is only reporting information.

---+++ LOLA : longitude-latitute report

This dotcode reports the current longitude-latitude position
   * At present time the contents field inside the action should list:<br /> update_node_lola({LOLA})

---+++ POD: Proof of delivery

This dotcode reports a proof of delivery of goods delivered at delivery address.<br /> Signame is the name of the receiver of goods.
   * At present time the contents field inside the action should list:<br /> shipmentID : {shipmentID}<br /> signame : {POD}<br /> sigdate : {sent}<br /> status : +{sent} POD (signed by: {POD})

---+++ PUPNO: pick-up not ok (remarks)

This dotcode reports that this particulair shipment was not picked up well.<br /> After typing a dotcode the user can type the reason why.
   * At present time the contents field inside the action should list:<br /> shipmentID : {shipmentID}<br /> pickupSentBit : 2<br /> pickupStatus : pick-up not ok<br /> status : +{sent} pick-up not ok ({nodeID} reported: {PUPNO})

---+++ PUPOK: pick-up ok

This dotcode reports that this particulair shipment was picked up well.
   * At present time the contents field inside the action should list:<br /> shipmentID : {shipmentID}<br /> pickupSentBit : 2<br /> pickupStatus : pick-up ok<br /> status : +{sent} pick-up ok

---+++ PUPRE: pick-up ok (remarks)

This dotcode reports that this shipment was picked up though there is a remark attached to it.
   * At present time the contents field inside the action should list:<br /> shipmentID : {shipmentID}<br /> pickupSentBit : 2<br /> pickupStatus : pick-up with remarks<br /> status : +{sent} pick-up with remarks ({nodeID} reported: {PUPRE})

---+++ PUPWA: pick-up warehouse

This dotcode reports that this shipment was picked out of the warehouse.
   * At present time the contents field inside the action should list:<br /> shipmentID : {shipmentID}<br /> pickupSentBit : 2<br /> pickupStatus : pick-up warehouse<br /> status : +{sent} pick-up warehouse ({nodeID} reported: {PUPWA})

---+++ REST: resting (hhmm)

This dotcode reports the resting time
   * There is no action attached to it, because it is only reporting information.

---+++ STODO: start odometer (km)

This dotcode reports the start value of the odometer.

update_trip_startODO(valueOf(STODO))
---+++ UL: unloading (hhmm)

This dotcode reports the unloading time
   * There is no action attached to it, because it is only reporting information.

---+++ WAIT: waiting (hhmm)

This dotcode reports the waiting time
   * There is no action attached to it, because it is only reporting information.

---+++ XX: delay (hhmm)

This dotcode reports the delay time
   * There is no action attached to it, because it is only reporting information.

---+++ Actions you can use to update trip status

<div id="_mcePaste">update_trip_status(new_status)</div> <div id="_mcePaste">update_trip_startODO(ODOreading)</div> <div id="_mcePaste">update_trip_endODO(ODOreading)</div> <div id="_mcePaste">update_trip_startDate(date)</div> <div id="_mcePaste">update_trip_endDate(date)</div> <div id="_mcePaste">update_trip_startTime(time)</div> <div id="_mcePaste">update_trip_endTime(time)</div> <div id="_mcePaste">update_trip_restTime(time)</div>

---+++ Actions you can use to update node information

update_node_lola(lon lat)
---++ Testing
   * You are able to test these dotcodes by using the shipment screen in dispatch.<br /> --&gt; Select a node and click the PDA button.
   * More info about how to use PDA's read our [[PdaDescription][PDA description]].
Also read [[DotcodesOffsetting][offsetting date and time for drivers]].

<br /><br /> -- Main.RutgerRutgers - 27 Sep 2006 / 25 Aug 2008

-- PieterHoekstra - 30 Nov 2012
Topic revision: r5 - 2012-11-30 - PieterHoekstra