WrightZone Weighbridge Software Manual
Menu
Index

Scale Footer - (RDA) Real Daily Availability

The (RDA) Real Daily Availability grid is designed to offer transport and/or daily operators an instant real-time snap shot of past, current, and future; scheduled pre-entry, onsite and, exit transactions within any day. When transport managers are required to schedule in excess of 60 vehicles an hour being one every minute and up to 500 a day having the necessary visibility, flexibility and management control is business critical hence the RDA report (offering this very function and feature) is broken down into hourly blocks; set under the Tools Menu; Options, Movement Counts tab. The RDA report is vehicle movement counts as per resource consent guidelines and not vehicle or docket counts.
 
The first rule in optimizing a limited resource, so to maximize production and avoid bottle necks, is to set the constraints, on capacity limits that you know of first. Under WZWB, constraints that determine your capacity which can all be set in the system are your business trading hours, the quantity of loaders to load vehicles, your own transport fleet, the outsourcing of transport and/or resource consent, that can determine a maximum vehicle movement count per hour, day, week and even month. In acknowledging your capacity by default, limits the variables of prediction; having adopted this philosophy and coupling it with feature rich, user friendly planning and scheduling capability, users are empowered with a simple Real Daily Availability grid offering pre-entry and forward order management to capacity.
  
Scale Footer - (RDA) Real Daily Availability
 
The RDA grid is built on a sophisticated algorithm known as the 'correlation coefficient of +1' which produces a perfect positive correlation between the (EHM) Entry Hourly Maximum, count and the (EDM) Entry Daily Maximum, count (in whole numbers) which is user defined and set.  An RDA value of zero means optimized; negative or positive means under or over scheduled (pre-entry booked and/or entered onsite) respectively.
 
RDA Cause & Effect Function Summary 
 
1

RDA Date

The RDA Date offers history and bookings availability of past dates with rolling hourly block calculated recommendations on both, current date and future date; over or under, vehicle movement count capacity constraints.
      
1. RDA Date
  • Past Date selection typically offers missed opportunity vehicle movement counts in not meeting an RDA value of zero meaning optimized.
  • Past Date selection with a negative value in either of the EHM or EDM counts is expected to invoke management review of capacity constraints supporting reasoning to increase capacity.
  • Current Date is the default date offering a rolling equation by the hour meaning the processing of one transaction (addition of pre-entry confirmed, process of pre-entry confirmed to onsite or direct onsite save) effects the current and future EHM and EDM Booking Availability counts. And as per the WZWB design recommendation or guidance in adhering to profit centre capacity constraints, is provided to all users in real time.
  • Future Date not only adds to Product Forecasting totals assisting in product manufacturing decisions but allows profit centre logistics, transport managers to plan and schedule product demand; availability with logistics capacity ahead of time.        
2

Pre-Entry

The Pre-Entry hourly block count is increased based on the pre-entry scheduled and confirmed event Start Time. Pre-Entry Counts are made up of pre-entry scheduled and confirmed current, or future date hourly bookings; with past dates and current day historic hourly blocks equating to a zero count (even though the confirmed pre-entry transaction may still exist).
   
2. Pre-Entry
 
With any scheduled pre-entry transaction and corresponding event being confirmed, for a current or future hour and date;
  • Pre-Entry Counts are increased reducing the daily and corresponding hourly booking availability count.
  • Pre-Entry Counts are decreased, on processing the transaction to being onsite (across hours and dates).
  • Pre-Entry Counts are decreased, on confirmed pre-entry transaction or event Delete.
3

Onsite

The Onsite hourly block count is increased in processing a pre-entry transaction to being saved onsite and saving a vehicle onsite directly which results in decreasing the (RDA) bookings availability count.  The Onsite hourly block count is decreased on completing exit weigh or docket production. 
 
3. Onsite
  • Onsite Delete does not reduce the count because the vehicle has been entered onsite and therefore is considered a true and valid transaction. The Onsite transaction Delete can be verified and further queried within the Dispatch grid.
  • A No-Onsite transaction does not Add a count.
4

Movements/RDA Totals

The Movement/RDA Totals, objective is to report quickly in real time an instant easily read report of Daily Availability being the unders and overs of vehicle movements for the profit centre. Unlike the Dispatch and Consent Management grids this report provides cause and effect in that if users confirm a Pre-Entry Scheduled transaction and/or processes a transaction to being onsite; being the cause; what is the effect on daily availability to capacity maximums, by profit centre working hours. 
 
4. Movements/RDA Totals
  • Right click to open the report Pop out for refresh and copy to WZXCEL or MS Excel.
  • Past date movement counts can be reconciled and matched to both the Dispatch and Consent Management grids.
  • Totals are always as per the one Default Profit Centre users are logged into.
5

Exit

The Exit hourly block count is increased on processing an onsite transaction through to completion being that of exit weigh or docket production.
 
5. Exit
 
6

Booking Availability

The Booking Hour Availability calculation produces an equilibrium of constant vehicle movements by profit centre working hours within any one day up to the (EDM) Entry Daily Maximum vehicle movement count. i.e. With an EDM of 200 and 10 working hours in the day (200/10=20) results in an average 20 Entry Hourly Movements, per hour (reflected in the RDA report). But the average is not the (EHM) Entry Hourly Maximum value set (as per Movement Counts) this total could be set to 40 which means that on managing the business to optimum capacity, with an EDM of 200, could see working hours halved to just 5 hours per day.
 
Imagine three loaders, being able to load an average of 30 vehicles per hour combined and a resource consent limit of 200 EDM. With efficient planning and scheduling, the profit centre could meet the 200 EDM count and complete this successfully within just 7 business working hours producing a result of increasing the quality and time to service customers, (vehicle drivers) and optimizing operations' efficiency, which works in increasing customer retention, through customer satisfaction and growing, business profitability.
         
On any new and current day the Booking Hour Availability calculation starts in dividing the EDM count by the quantity of working hours, subtracting from availability confirmed pre-entry transactions and directly entered onsite transactions and because hours are rolling, so are the Hourly Availability Counts with each transaction processed providing users with:
  • Continuing guidance and recommendation on under utilizing (being the current and future positive Booking Availability count) and/or on exceeding any (EHM) Entry Hourly Maximum count.  
  • Booking Availability color coded notification on meeting or exceeding the EHM count.
6. Booking Availability
  • A positive count for a current and future date communicates Daily by Hour Booking Availability and means users can schedule with maximum capacity not reached. 
  • A negative count for a current and future date communicates Daily by Hour Booking Unavailability and means users should not add additional counts to the hour but can optionally reschedule (with recommendation provided) so to remain within maximums.
  • A positive count for a past date communicates the Daily by Hour Booking Availability and means underutilized showing users the difference between completed movements versus the maximum capacity that was available.  
  • A negative count for a past date communicates the Daily by Hour Booking Unavailability and means exceeding capacity maximums which is typically when profit centres are employing Movement Counts as a target to reach. Continually exceeding targets can inhibit the quality and time to service of customers (vehicle drivers) or justify a need a for increased capital investment but the advantage under WZWB is being able to provide easily, the necessary measurement.
  • Exceeding resource consent restrictions of either the EHM or EDM counts incurs significant penalties with Active Time and Percentage Warning optional toolsets designed to inform and discourage users from exceeding such restrictions,  however when set as a target; can be employed for user encouragement to meet or exceed them.