Any trip will require a marshal/escort on the basis of the female constraint set for shift while generating the route under the RMD (Route Management Dashboard).
Definition: Female constraints are rules set for a shift or a trip to calculate and define if a trip requires a marshal, depending on the pick up sequence in login direction and drop sequence in logout direction.
Types of female constraints/Escort Rule:
First/Last female: In a trip sequence, if the first pick up is female in login direction and the last drop is female in logout direction, the trip will require a marshal/escort.
Second/Second last female: In a trip sequence, even if the second pick up is female in login direction and the second last drop is female in logout direction, the trip will require a marshal/escort.
Any female: If there is a female present on a trip, then the trip will require a marshal/escort.
Disable: When this flavour is set, trips will not require a marshal/escort.
Types of Marshal status in a trip:
Marshal Required: This banner will be displayed on the MoveInSync driver application, indicating that the trip requires marshal and the female or special needs employee will not be allowed to board before a marshal signs in on the device.
Marshal Maybe Required: This banner will be displayed on the MoveInSync application, indicating that the trip may require marshal/escort if the first pick up male employee or the last drop male employee is marked no show.
Good to go: This banner will be displayed when no marshal/escort is required to sign in the female employee.
Type of Marshall status calculation flavors, which are a part of the admin/backend configuration:
Planned: Here the marshall status/trip banner will be honored as per the planned sequence.Example: If as per the planned login trip the male employee was the first pick up and female employee was the second pick up then as per planning, the trip does not require a marshall/escort, but even if the male employee is marked no show changing the sequence to the female employee being the first pick up the trip status will still be good to go honoring the planned calculation.
Hybrid: Here the marshall status/trip banner will recalculate if the in a login trip the male employee was the first pick up and female employee was the second pick up then as per planning, the trip does not require a marshall/escort, but even if the male employee is marked no show changing the sequence to the female employee being the first pick up the trip status will get updated to marshal required.
Note:
Upon these escort rules set we calculate the trip banner. However, it is configurable whether to Warn, Block or Allow the female employee to sign in for a marshal-required trip.
We can set the configurations to only allow other employees to sign in before the escorts signs in on a marshal required trip.
We can set the configuration to only allow the escort to sign off once all employees have signed off in a marshal reqired trip.
Troubleshooting Steps to verify what was the female constraint set for a trip:
How to check on the ETS portal?
Search the trip ID on the dashboard and check the date, shift and direction.
Click on “Routes”.
Select the date and then select the office as per the information of the trip search on the dashboard.
Open the shift and open history to check what was female constraint set while generating the shifts route.
How to verify from the device health:
Search the trip ID on the dashboard.
Click on “Tripsheet” or trip ID in a blue colored hyperlink.
Open the device health.
Press Ctlr+F and search for “Escort Rule received for trip id : (followed by the trip ID)”. For example: Escort Rule received for trip id : 1091673.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article