The Scheduler Event Recurrence function works in a similar way to creating recurring appointments in MS Outlook but under WrightZone Weighbridge users can create multiple recurrences within any one day described as a recurrence hourly pattern. The recurrence hourly pattern has been specifically designed to provision for logistics or transport capacity constraints; business (opening) working hours or Consent Management limitations are two such real world examples. In setting the constraints within the system first we limit the variables of prediction which makes for the planning and scheduling of forward orders accurate and easy.
Once principal constraints are set, start and finish times are system defaulted leaving operations users or logistics management to simply and quickly, create the plan. The plan consists of three main data groups:
1. Recurrence Hourly pattern:
Defines the quantity of vehicles required to fulfill the job/order for any one day.
Defines the periodicity or travel time for transport from one location to the end destination. (Or more commonly the transport travel time, from the profit centre to the customers destination.)
Defines the group being the quantity of unique transport vehicle ID's to fulfill the job/order for any one day.
AND optionally;
2. Recurrence pattern:
Multiples the Hourly pattern to recur by day, week, month, year and intermediate combinations of each.
3. Range of recurrence:
Applies only when the (AND) Recurrence pattern is used offering choices to either not end the Recurrence pattern or end it by occurrence quantity or a particular date.
Primary Features:
Fast, Easy and Efficient
Multiply any one pre-entry transaction into a quantity of 50 plus from the pre-entry transaction itself or on creation of an event or recurring event inside scheduler in seconds.
WZWB calculates and back calculates in real time Capacity and Group quantities including Finish time based on user input and edit of the
the system prepares a result, based on known constraints.
The Pre-Entry Plan can be created as Tentative; Confirmed or a combination of both.
Creation of multiple recurring patterns inside a single recurring pattern e.g. A recurring pattern built from the Event recurrence window can consist of varying vehicles, haulers, products, destinations even customers and orders using the
Capacity is a system calculated field always reporting a positive value and is designed to communicate the under ultilisation of any one vehicle. Capacity is directly linked to Master Recurrence Maintenance informing users of under ultilisation before its visually displayed. Capacity should be seen as guide for users in optimizing transport movements based on fulfilling the pre-entry (forward order) quantities within any one day.
A capacity count of zero means vehicles are fully utilised and at capacity in fulfilling the order.
A capacity count of two means a possibility of a vehicle being under utilised by 2 transport movements or deliveries which always remains subject to the hourly pattern, quantity and group values; user set.
Quantity is is the amount of pre-entry transactions (or transport Service Requests) to fulfill the Order or Job within any one day.
Quantity is user editable and is defaulted from the Pre-Entry window on click of the Scheduler button.
The minimum value system defaulted is a quantity of 2 because an hourly recurring pattern is not recurring with a quantity of 1.
In contradiction (to the above statement) the system will allow users to set a quantity of 1 because a recurring pattern can recur every first or second day or every Monday of every week. Such combinations are common hence the system allows a quantity of 1 for the hourly recurring pattern however if users are trying to schedule the one and only pre-entry transaction for one day only we recommend using the Remove Recurrence button where the pre-entry transaction becomes a simple and single scheduled event.
Periodicity is the transport or delivery time required to complete the pre-entry transaction (scheduled event or service request); the time between the point of origin and the point of consumption.
Periodicity is system defaulted to 30 minutes, is user editable and increments in blocks of 15 minutes for easy input.
Group is the quantity of unique vehicle or truck registrations.
Group quantity of 1 means the one vehicle ID will complete the run or pre-entry quantity set although it doesn't have to be the case because users have the ability to modify or increase the plan detail via the Master Recurrence Maintenance window (below).`
The Group count can never be greater than the Quantity count and its main purpose; system calculated and/or user-defined, is to split Quantity counts into groups of the same vehicle ID based on known and user input constraints of working hours or start time, periodicity and the pre-entry transaction recurrence quantity for any one day.
The vehicle ID doesn't have to be recorded with the pre-entry transaction as it may not be known at the time alas if the profit centre has their own fleet we can assume the transport manager will know what trucks and what drivers he is tentatively planning on using to fulfill the days order. The example (above) finalised within the Master Recurrence window demonstrates the transport manager having set vehicle ID, FAD145 as Group 1, BFH226 as Group 2 and CSG292 as Group 3, concluding 3 Groups with each group containing the same vehicle ID and summarising, a daily run for each.
Any one Group can consist of any number of vehicle ID's or Haulers, they can even be left blank; they key is offering the ability to create a plan with what is known, no matter how little or vague the information known, is. All the transport manager need know, or guess is how many unique vehicle or truck registrations might be required fulfill the order and if he doesn't know this information the system will automatically calculate the recommended Group quantity based on the start time, the quantity and periodicity values set.
The hourly recurrence pattern multiples any one pre-entry transaction into a single day inside working hours AND the recurrence pattern multiples the daily hourly recurrence pattern quantity into days, weeks and months.
When False (above) the recurrence pattern is only that of the hourly recurrence pattern meaning recurs inside any one day only.
AND When True the hourly recurrence pattern set for any one day is multiplied into multiple days, weeks or even months and like combinations.
Range of recurrence is not available with the hourly recurrence pattern AND is only available as an option when including the hourly recurrence pattern with the (standard) recurrence pattern. Range of recurrence is used to determine the finish date of the recurrence pattern offering three primary options of no end date, end after so many occurrences and end by a particular (which includes the date set).
Close All is used as a short-cut to close multiple windows being that of the single Event window and the Event recurrence windows. There are multiple examples of where both the single Event window and the Event recurrence window are opened together and this is because Event recurrences are dependent on creation of single Event in the first instance. Examples include creating a New recurring event from either the Pre-Entry window or the Scheduler Pop out or Scheduler Toolbar and when enquiring from the single Event window into the into the Event recurrence hence Close All offers a quick simultaneous closing of both windows.
Remove recurrence as the name implies will remove an existing recurrence. There are situations where remove recurrence should be used in the first instance making navigation for certain tasks easy for users but at the same time there are situations or conditions within system that prohibit access to this function.
Users creating the recur function from the Scheduler button in the Pre-Entry window are drilled down into the Event recurrence window because as per the systems design we assume that users are wanting to multiply the pre-entry transaction and therefore plan and schedule in bulk being the more common activity when compared to scheduling a single pre-entry transaction (which can be dragged and dropped from either the Pre-Entry Planner or Pre-Entry Grid into Scheduler content area). In the situation where users want to create a single event (without the drag and drop toolset) the Remove recurrence button will send users directly to the single Pre-Entry Event where they can quickly and easily save or edit the events' scheduled Start time.
From any (non-completed) single Pre-Entry Event a recurrence can be created, deleted (Remove recurrence) and created again so long as occurrences have not been saved in the Master Recurrence Maintenance window.
When occurrences are saved via Master Recurrence Maintenance being the visual and final stage of the logistics and transport plan the Event recurrence window is reported as Scheduled and Locked by User disabling the Remove recurrence function and setting the Event recurrence window to being read only.
Save is the setting or recording of the recurrence values only. Save closes the Event recurrence window (here in) where users are then automatically returned to the Pre-EntryEvent - untitled window. The recurrence process is not complete until users have opened the Master Recurrence Maintenance window which offers a visual representation of your transport or logistics scheduling plan. The Master Recurrence Maintenance window is opened only from the Pre-Entry Event - Untitled window with successful save of both the recurrence hourly pattern (as the minimum recurrence criteria) and pre-entry creation.
Successful Save will return users to the Pre-Entry Event - Untitled window (below) where Save inside the Event window will open the Master Recurrence Maintenance window being the final stage of your transport or logistics plan.
