Accessing and Understanding the Postal Notifications Report

Accessing and Understanding the Postal Notifications Report

  • What is the Postal Notification Report?

Postal Notification report displays the top 1000 records before the selected date of the data collected and submitted to the USPS for the GPS reporting requirement. This report displays information relevant to the postal contract and trip combinations that are under the USPS GPS reporting mandate.


  • How can I access the report?

From the top LoadTrek.net menu select Reports -> Data Views -> Daily Activity -> Postal Notifications, then select the date. The report will display postal trip information prior the midnight of the selected date.


  • Why is the report empty?

The report is empty if no data has been submitted to the USPS. Please check the following items:

  • Contracts are checked for 'Electronic Access' on the Customer Info form.

  • All locations have a defined NASS code on the Location Info form.

  • Postal Trip Numbers are entered into the Load Ref field.

  • Drivers are signing on, requesting and executing routes.


  • What fields are submitted to the USPS?

The following fields are NOT submitted: PID, PEntryTime, PSubmitTime, PLoad, PLoadDetail, PVehicleID, PDeviceID, PSerialID


  • What is the difference between PEntryTime, PSubmitTime, PEventID?

Please see the description of each field below:

  • PEventID - the date and time the entry has been generated by the device in the vehicle - generated first.

  • PEntryTime - the date and time the entry has arrived from the device and was entered into the database - generated second.

  • PSubmitTime - the date and time the entry has been submitted to the post office - generated third.


  • What is a normal time difference between PEventDT, PEntryTime and PSubmitTime?

The normal time lapsed between PEventDT and PEntryTime is 1-20 minutes; between PEntryTime and PSubmitTime is 15-45 minutes.



  • Why is there a large time gap between PEventDT and PEntryTime?

If the device is out of coverage for an extended period of time the packets will not be transmitted to the LoadTrek server for the duration of the out-of-coverage state. When the device returns into coverage, all packets will be re-transmitted resulting in the time gap between those fields.


  • Why is there a large gap between PEntryTime and PSubmitTime?

If the data packet form the mobile device arrives without a valid geocode, LoadTrek.net will attempt to retrieve it before submitting to the USPS. After a number of hours the packet will be submitted regardless.


  • Why do we see a high instance of 0.0 geocodes with the phone solution?

Most smart phones employ a GPS-assist technology instead of full GPS 12 channel chips. The phone relies on the cellular tower signal and the timestamp in addition to GPS to complete the triangulation of the geographic position. If the phone is out of coverage it may not reliably capture the geocode coordinates resulting in the unreliable reading. NOTE: this does not apply to the complete LoadTrek.mobile solution which feature full GPS system.


  • What can we do to improve the reliability of the GPS capture with the phone?

The placement of the phone is paramount to the reliable GPS capture. We recommend using a phone mount that places the phone in the closest proximity to the window and unobstructed view of the sky.


    • Related Articles

    • Understanding the Equipment Troubleshooting Report

      Understanding the Equipment Troubleshooting Report Purpose LoadTrek users may reference the information below for an introduction to using the Equipment Troubleshooting Report. This report can serve as an effective starting point for internal ...
    • Reviewing the Audit Postal Compliance Report

      Purpose & Scope Users can identify discrepancies between the database and the spreadsheet, investigate the cause and take corrective action. To View the Audit Postal Compliance Report LoadTrek.net users should follow the steps below. Determine proper ...
    • Reviewing the Audit Postal Compliance Report

      Reviewing the Audit Postal Compliance Report Purpose & Scope LoadTrek.net users should follow the steps below to view the Audit Postal Compliance Report. This reporting tool compares the selected spreadsheet from the USPS (No Ping Report) with the ...
    • Auditing Postal Routes to ensure Postal Compliance

      Purpose Compliance personnel may reference this document as a guide to discover reasons for poor PING reporting. The most common causes for poor reporting are either a result of a missed step in setup, or poor driver execution. If these factors are ...
    • Permission Grouping Postal

      Permission Grouping Postal Purpose & Scope LoadTrek users should reference the information below for information about using Permission Grouping, and definitions of primary user groups and recommended permissions. Procedure Download the attached PDF.