Version Available From: The Beginning
Concepts of the Mileage Rectifier
The Mileage Rectifier is a separate application that links to the information held within Business Manager. Its icon is very much like that used for Business Manager, and can usually be found alongside it on your desktop or wherever else you use to access the applications.
The Rectifier is designed to meet the Mileage and Travel calculation needs of Clients who require more than simply calculating between Visits. The Rectifier can be used to add rules and bespoke requirements to how mileage is calculated e.g. too and from home, not including Visits with an interval greater than 60 minutes etc. The requirements are set by applying sets of rules to the mileage totals. This document gives a brief overview of Mileage Rectifier functionality. However, in reality it’s more like that you will have a set of rules built for you by iCareHealth’s Support Team or by a Consultant. This document will also show you how to run a rule set once built, which is a really easy process.
Remember, as with the standard method for calculating mileage, the system will only recognise the mileage and distance a Worker has completed if contained within the same Shift. The system still works by calculating routes based on Pinpointed Client or Location addresses so ensure these are accurate.
Running the Mileage Rectifier
- If a Mileage Rule has been built for you, ensure you know where it is located on your computer. It will be a file with an MR2 file type
- Log into the Mileage Rectifier as a supervisor user and Click File > Open in the top left
- Navigate to the mileage rule MR2 file and select it, click Open
- The rules contained in the file will be applied, you may check them if you wish
- When satisfied, click the Run button in the bottom right of the screen
- Select a date range for Visits and Shifts you would like to include. The selected date is inclusive
- Click Start
- It is possible to abort the process but this will not cancel changes made to records already processed
- A list of any errors is displayed for you to review
- Where the system cannot find a suitable route, an ‘as the crow flies’ distance is applied and travel time is set to zero.
It’s more than likely that a Mileage Rectifier rule set will built with you by Support or a Consultant, but to highlight some options that may pique your interest when deciding whether to implement the Rectifier or not some settings are listed below. These may also help current users who wish the tweak their rule set.
- ApplyCmmMileage - Uses the mileage calculated by the GPS locations returned by Mobile. This adjustment also allows you to calculate mileage travelled within a visit. For travel time, the start/end times of the visits and shifts are used.
- ApplyConstant - Adjust the mileage by a fixed amount e.g. you could add 5 miles to every distance, multiply distances by 2, set travel times to a fixed value like 10 minutes
- ApplyMaxCapping - Allows you to set a maximum value for a distance or time e.g. any mileage above 10 would be capped at 10.
- ApplyMileage - Applies the calculated travel and distance figures to the Visit.
- ApplyMinCapping - Allows you to set a minimum value for a distance or time e.g. any travel time below 3 minutes gets capped to 3 minutes.
- ApplyPostcodeMatch - Applies an adjustment to the mileage based on a postcode match e.g. for visits that have an address ‘IP11 2DS’ set the mileage to 0, or any visits in SE1 or SE2, add 3 minutes to the travel time.
- ApplyValueForGap - Applies an adjustment if a gap of a certain number of minutes is detected before or after the visit e.g. if a gap of 60 minutes is detected prior to a visit, set mileage to 0.
- MilesToKms - Converts the mileage values to Kilometres
- Reset - Resets the distance and time values to zero.
- SubtractValue - Subtracts a set amount from the distance or time, but will not allow negatives e.g. subtract 3 miles from the first and last visit.
- Throttle - This slows down the Mileage Rectifier. If network/internet bandwidth or CPU utilisation is too high, setting a throttle value will slow down the process.
- ApplyValueForGapApplies an adjustment if a gap of a certain number of minutes is detected before or after the visit e.g. if a gap of 60 minutes is detected prior to a visit, set mileage to 0.
- MilesToKms - Converts the mileage values to Kilometres
- Reset - Resets the distance and time values to zero.
- SubtractValue - Subtracts a set amount from the distance or time, but will not allow negatives e.g. subtract 3 miles from the first and last visit.
- Throttle - This slows down the Mileage Rectifier. If network/internet bandwidth or CPU utilisation is too high, setting a throttle value will slow down the process.
- Address for start and end of shift – Amend the address used to calculate the mileage to from first Visit in the Shift, and from the last Visit in the Shift. The Default value is the worker’s home address, but all locations set up in Business Manager will also be available for selection.
- Filter Workers - Allows the user to select on certain workers to apply the mileage logic to. Can be filtered by individual, category, contract or group. The default value is for workers not to be filtered.
- Visit types to ignore - Visits of the selected types will be ignored. The mileage values will not be adjusted for visits of these types, and the routes between the preceding and following visits will bypass this address. This should be used if you have ‘Travel time’ / ‘break’ or similar visits configured. Visits marked as ‘Break’ are also automatically ignored.
Note: Multiple Adjustments, each with different configurations, combine to make a ‘Set’ of rules. These Sets of rules can be saved as a file and run through the rectifier whenever you like. As such, you can have multiple ‘Sets’ of rules and run them against different worker contracts etc. To solve particularly complex business logic problems against one group of workers, you can even run 2 ‘Sets’ of rules one after the other to achieve the desired outcome.
Comments
0 comments
Article is closed for comments.