Difference between revisions of "11.7 Logistics Activities Monitor"

From UNHRD Customer Service Sales
Jump to: navigation, search
Line 16: Line 16:
 
At each hub level, the hub manager nominates a DOTS focal point who grants consistency of local sales and operational data by the use of '''[https://dots.wfp.org/workspace/report/ri.report.main.report.ff7d23e9-f19a-4804-acef-dc45c772cf73 UNHRD Alerts page]''' on DOTS.  
 
At each hub level, the hub manager nominates a DOTS focal point who grants consistency of local sales and operational data by the use of '''[https://dots.wfp.org/workspace/report/ri.report.main.report.ff7d23e9-f19a-4804-acef-dc45c772cf73 UNHRD Alerts page]''' on DOTS.  
 
Ideally an alternate to the mail Focal point should be nominated too , to perform same roles in case of focal point absence.
 
Ideally an alternate to the mail Focal point should be nominated too , to perform same roles in case of focal point absence.
Below the tasks to be performed;
+
DOTS focal points must ensure that involved staff and Hub Manager are promptly informed in case of wrong data, to ensure that required correction are applied, when applicable, to grant solidity of sale flows and consistency of operational data.
 +
Below the tasks to be performed:
  
 
'''List of duties of DOTS focal point:'''
 
'''List of duties of DOTS focal point:'''
Line 29: Line 30:
  
 
• Submit to Hub manager the graphic related to SOs in progress (sample graphic below):
 
• Submit to Hub manager the graphic related to SOs in progress (sample graphic below):
 +
 +
[[File:DOTS1.png]]
 +
• Check the number of open ODs (i.e. OD without Good Issue) in progress and compare it with data related to previous week
 +
 +
• Consult the list of ODs with Good Issue not posted and notify the Logistics team for outstanding ODs, if reasons are not known
 +
 +
• When required, escalate to Hub Manager the long outstanding ODs
 +
 +
• Submit to Hub manager the graphic related to ODs in progress (sample graphic below):
 +
 +
[[File:DOTS2.png]]
 +
 +
• Check the number of open PODs (i.e. OD without Proof of Delivery) in progress and compare it with data related to previous week
 +
 +
• Consult the list of PODs not posted and notify the Customer Service team for outstanding PODs, especially if long outstanding, to apply SOP criteria for posting of POD when confirmation from consignee is not received
 +
 +
• Submit to Hub manager the graphic related to PODs not posted (sample graphic below):
 +
 +
[[File:DOTS3.png]]
 +
 +
• Consult the list of ODs without the means of transport and notify the Logistics team accordingly
 +
 +
• If same ODs remain without means of transport between the weeks, escalate the matter to Hub Manager
 +
 +
• Submit to Hub manager the graphic related to ODs without means of transport  (sample graphic below):
 +
 +
[[File:DOTS4.png]]

Revision as of 18:37, 3 December 2020

Receive new UNHRD Customer NFI/Service Request
Performer: DOTS Focal Points
Role: DOTS Local Focal Points
Transaction : DOTS report


At each hub level, the hub manager nominates a DOTS focal point who grants consistency of local sales and operational data by the use of UNHRD Alerts page on DOTS. Ideally an alternate to the mail Focal point should be nominated too , to perform same roles in case of focal point absence. DOTS focal points must ensure that involved staff and Hub Manager are promptly informed in case of wrong data, to ensure that required correction are applied, when applicable, to grant solidity of sale flows and consistency of operational data. Below the tasks to be performed:

List of duties of DOTS focal point:

Perform a weekly check of data related to operations by accessing the “UNHRD Alerts” page on DOTS and disseminate information at hub level to grant consistency of sales and operational data:

• Check the number of SO in progress and compare it with data related to previous week

• Consult the list of SOs in progress and notify SO creators for outstanding SOs, if reasons are not known.

• When required, escalate to Hub Manager the long outstanding SOs

• Submit to Hub manager the graphic related to SOs in progress (sample graphic below):

File:DOTS1.png • Check the number of open ODs (i.e. OD without Good Issue) in progress and compare it with data related to previous week

• Consult the list of ODs with Good Issue not posted and notify the Logistics team for outstanding ODs, if reasons are not known

• When required, escalate to Hub Manager the long outstanding ODs

• Submit to Hub manager the graphic related to ODs in progress (sample graphic below):

File:DOTS2.png

• Check the number of open PODs (i.e. OD without Proof of Delivery) in progress and compare it with data related to previous week

• Consult the list of PODs not posted and notify the Customer Service team for outstanding PODs, especially if long outstanding, to apply SOP criteria for posting of POD when confirmation from consignee is not received

• Submit to Hub manager the graphic related to PODs not posted (sample graphic below):

File:DOTS3.png

• Consult the list of ODs without the means of transport and notify the Logistics team accordingly

• If same ODs remain without means of transport between the weeks, escalate the matter to Hub Manager

• Submit to Hub manager the graphic related to ODs without means of transport (sample graphic below):

File:DOTS4.png