Back to Back trips (Beta)

B2B - Introduction

A back to back trip definition is restricted to employee logout trip followed by employee login trip.

Marking Back-2-Back trips as and when these are generated and then allocating these to vendors - is a key cost saving proposition for transport team and for MIS in turn. There is significant latent cost saving potential in this regard. Wipro - who is one the more cost-conscious client currently operate at 4% B2B trips. With this feature in place, we are expecting to enhance B2B by 10%-12% (of course it is subjective to lot of external factors, like company policy, B2B parameters etc.)

Configuration setting

Following warning message is shown to user if they try to enter too deviant values for these parameters:

Trigger for generating Back to back pair

Trigger for back-to-back trip generation is provided at the route management page under “Manage Trip Sheets”

Trigger is provided only for the logout trips (by definition). Once triggered, algorithm checks logout trips against all login trips (till round journey time threshold is met) and checks for feasible B2B pairs. If more than one pair (corresponding to a particular logout trip) is possible, algorithm ranks these pairs and suggest one with highest score. {smaller dead leg higher the score, smaller wait time higher the score and likewise}.

“Only logout trips which are not any vendor/cab yet and are not already in a B2B pair are considered eligible for B2B”

hence, It is advised to run “generate B2B” before “Allocate vendor” to logout trips.

Vendor,Cab and Escort assignment

If one of the trips (login or logout) is assigned a vendor/cab and other trip is unassigned. Automatically copies vendor/cab to unassigned trip.

Algorithm takes into account if any othe trip in B2B pair has an escort and decides on feasibility accordingly.

Checking B2B trips on Route editor page

A back-2-back trip is marked with following symbol on route editor page.

When mouse is taken over the B2B symbol following information will be shown over the hover.

Changes in B2B identified routes

If routers make any changes to the B2B identified routes - these changes include (but not restricted to):

• Changing employee order
• Add/Remove employee
• Changing pick up/drop time
• Vendor cab allocation

Whenever any change is made, following warning is shown:

Once the changes are saved, system verifies if the B2B thresholds are still meeting. If not, B2B status is void.

Hence, in order to minimize this, it is advised to run Generate B2B once trip-sheet is finalized (or almost finalized)

Checking B2B trips on vendor login page

Once a vendor is assigned a B2B pair, it can be seen on vendor login page as well.

When first time vendor assigns cab to any one of the pair is copied to other trip also. In order to void this pair, vendor can assign different cabs to these trips. - {consistent with vendor/cab assignment}

B2B trips on vendor track sheet and tripsheets

B2B trips are printed on the vendor track sheet together. All such pairs are printed at the bottom of vendor track-sheet. In similar manner B2B pair is shown together on trip-sheets as well.

B2B allocation report

Available under business analytics section. “Back to Back Allocation Report” is new report with this feature.

Feature is currently under beta testing at one of the sites in NCR. To adopt this feature, please contact product@moveinsync.com or aman@moveinsync.com