The Main Dispatch is a vital component your WrightZone Weighbridge Software as it's design brings together in a seamless Pivot Grid concepts and function of Vehicle Counts versus Movement Counts, Pre-Entry (being planning and forecasting) versus Actual on a per day basis as it's most primary function, with field dimensions of Month, Year the usual Hauler, Customer, Vehicle ID, Order, Tare, Gross and Net weights and more all adding to offer users in depth analysis of your dispatch operations whether this be at a single profit centre level for Basic Users or across multiple for Administration Users.

 

The Dispatch Grid is a precursor to Consent Management reporting with Entered and Docket Count fields as per docket and therefore dispatch counts; the Destination Price field offers an average of the from Location to Destination unit Price including Order and Price book combinations.  

 

Primary Features:

      

 

The Grid Default setting offers a view of the Dispatch Grid in it's simplest form alas it's primary purpose is that of counting where calculations which are sophisticated in comparing actual versus budget on a number of levels

From the simplest level we start with Entered and Docket (or Entry and Exit) Counts with Entered meaning saved to the Onsite Grid and Docket meaning saved to the Exit Grid.

Entered Counts are physical, docket or Vehicle Counts where a transaction has been saved to the Onsite Grid. Whether the No Onsite Count Radio is True or False a count of 1 is added to the Entered Count field.

Docket Counts are also physical, docket or Vehicle Counts where a transaction has been saved to the Exit Grid. Whether the No Onsite Count Radio is True or False a count of 1 is added to the Dockets Count field.

The only discrepancy that will occur between these fields is a user having deleted an Onsite transaction where as a result the Entered Count will be that of 1 with the Docket (Exit) Count being of no count because the transaction was deleted while Onsite.   

 

Understanding the calculations occurring within the Dispatch Grid is not a requirement as the reporting and counts provided are accurate, secondly only a minority of profit centres have a requirement to identify the difference between Vehicle and Movement Counts although there is advantage for any profit centre in completing analysis down to this level because without it counts are simply not accurate (which is surprisingly common of competing applications).

 

The Onsite Count radio button is employed by profit centres that are limited by Council or Land Use restrictions. A Vehicle Count equates to that of a docket count and it's when a vehicle obtains two dockets (as the most common example) for the one entry and exit into the profit centre where Vehicle Counts are no longer true or a match to that of Movement Counts. It's here users can set True the Onsite Count radio button (creating a No Onsite (or non-movement) Count below) for one of the two docket transactions which works to producing the two groups of Movement Counts versus Vehicle Counts (which are simply all docket counts or movement plus non-movement counts).

 

Movement Count Calculations

The Dispatch Grid, Default View offers analytical information as per the majority of WZWB User requirements alas behind the simplicity of this Pivot Grid Senior Management are delivered every opportunity to ask the important questions:

 

Dispatch: A total of 17 Pre-Entry transactions between the 9th to the 12th of May 2016 communicates planning is not a priority for the profit centre and based on this information Pre-Entry is used to plan for just what is known where delete is simply not applicable. Proposed Movements versus Movements Complete is a match where Entered (Entry Onsite save) versus Docket (Exit or Vehicle Count) save is not for the 11/05/2016. The Entry Onsite Delete reports a WZWB User having deleted two onsite transactions (which can be verified within Audits window) and is calculated as an Entered Count of 575 - 2 (Entry Onsite Delete Counts) = 573 (Docket or) Vehicle Counts. Vehicle Counts totaling 573 - 1 (Exit Onsite Count) totals 572 Proposed Movement Counts.    

 

Proposed:

Pre-Entry

Pre-Entry Delete:

Entry Onsite Delete:

Exit Onsite Count:

Movement Complete:

Remaining: