Dual OTP-Based Sign In/Out: Handle Boarding/Deboarding flow to show OTP

https://moveinsync.atlassian.net/browse/PB-51142

Overview

The current boarding and deboarding process lacks a robust verification mechanism, leading to potential security risks and inefficiencies.

There is no systematic way to confirm the presence of employees at designated pickup and drop-off points, increasing the chances of unauthorized boarding or incomplete trip tracking.
 To address these concerns, an OTP-based authentication system is required to ensure secure verification & enhance employee safety

Scope

This enhancement will impact the following stakeholders:

• Employees: Will receive and share OTPs with the driver for trip validation.

• Drivers: Will validate the boarding and deboarding OTPs in the system before proceeding with the trip.

Non-Functional Requirements

OTP Flow for Employees & Drivers

OTP Display on the Home Screen of Employee App

Non-Functional Requirements

• Scalability: The OTP system should support a high volume of trip requests without performance degradation.

• Performance: OTP validation should be completed within 2 seconds to ensure a seamless experience.

• Logging & Auditing: Maintain an audit log of all OTP transactions to track validation and ensure compliance.

• Geo-Fencing: OTP validation should be restricted based on geo-tagged locations to prevent misuse.

• Localization: Support multi-language for diverse user demographics.

• Accessibility: Ensure that the workflows adhere to WCAG 2.1 AA guidelines

Acceptance Criteria

1. Employees must receive an OTP for boarding confirmation once the trip is accepted. This will be via SMS, email & notification.

2. If the driver rejects the trip then do not show OTP.

3. The deboarding OTP should be displayed once the employee has successfully signed in.

4. The driver should only be able to punch the OTP(boarding or deboarding) when within a set radius of the pickup or drop point. Existing cab arrival geofence property can be used to set this boundary.

5. The system must ensure all OTP transactions are logged for audit and compliance purposes.

6. After deboarding the user should receive an SMS/In-App notification that they have successfully signed of
    Subject: Your Trip is complete!
   Body: Dear User,
   Your Trip is complete. Hope you enjoyed the journey!
   Action on App: Tapping on the notification would take the user to the main screen and expand the card.

Areas of Impact

• Mobile App: Android & iOS (Employee and Driver interfaces)

• Mobile App Server

• ETS

https://moveinsync.atlassian.net/browse/PB-51912
Dynamic QR on driver app: Deny entry to adhoc riders

https://moveinsync.atlassian.net/browse/PB-53179

[Driver App]: Dynamic QR

Problem

Adhoc users board the bus, leaving no seat for planned users. Need a mechanism so that drivers can deny adhoc riders if they cannot be accommodated.

Scope

Attendance via QR (driver app).

User Journey

• An employee has a QR attached to its trip card. It is unique to his/her booking.

• The driver app clicks on the scan QR button.

• The employee shows QR in front of the driver app.

• Immediately, Driver App Displays Red/Green feedback based on whether there is a seat for him (empty unplanned seats).

NOTE: This feature works only for shuttle

FEATURE_QR_CODE_SCAN_FOR_PASSENGER

https://moveinsync.atlassian.net/browse/PB-53062
Security Sign off - Enhanced customizable roles and duration configurations

Context:

The Security Sign-Off feature is currently enforced at the end of every trip, requiring the Security Supervisor (SPOC) to complete a breath analyzer check and manually sign off. This rigid enforcement does not account for operational flexibility across different shifts, trip types, or personnel roles — leading to inefficiencies and unnecessary manual interventions outside critical periods.

Requirements:

• Time-Based Enforcement

  • Security sign-off should be mandatory only during a configured time window (e.g., night shifts), and optional/skippable outside of it.

• Direction-Based Applicability

  • Sign-off enforcement should be restricted to Login or Logout trips based on configuration (e.g., only for Logout trips).

• Role-Based Access Control

  • Ability to configure which user roles (e.g., Security Supervisor, Admin) are allowed to perform the sign-off, via a multi-select role configuration.

ETS : release/06-2025

Device Service : release/06-2025

Tripsheet domain : release/06-2025

ENABLE_SECURITY_CHECK_FOR_TRIPS = true

APPLICABLE_TIME_FRAME_FOR_MANDATORY_SECURITY_SIGN_OFF = 0000-0001

APPLICABLE_TRIP_DIRECTION_FOR_SECURITY_SIGN_OFF = ALL

APPLICABLE_TRIP_TYPES_FOR_SECURITY_SIGN_OFF = REGULAR

ENABLE_SECURITY_CHECK_FOR_ADHOC_TRIPS = true

APPLICABLE_ROLES_FOR_PERFORMING_SECURITY_SIGN_OFF = security-supervisor

Here are the roles names that need to be used

• PROJECT_MANAGER → projectmgr

• ROUTE_MANAGER → routemgr

• BILLING_MANAGER → billingmgr

• TRANSPORT_MANAGER → transportmgr

• OPERATIONS → operations

• EMPLOYEE → employee

• SITE_ADMIN → siteadmin

• ADMIN → admin

• ESCORT → escort

• USERAUDITOR → userauditor

• VENDOR_MANAGER → vendormgr

• VENDOR_BILLING_MANAGER → vendorbillingmanager

• SCHEDULE_MANAGER → schedulemanager

• TRACKER → tracker

• BILLING_AUDITOR → billing-auditor

• SYS_ADMIN → sysadmin

• PLATFORM_VENDOR_BILLING_MANAGER → platform-vendor-billingmanager

• TRANSPORT_MANAGER_NO_BILLING → transportmanager-nobilling

• BILLING_MASTER → billing-master

• VENDOR_RISK_MANAGER → vendor-risk-manager

• COMPLIANCE_MANAGER → compliance-manager

• SECURITY_SUPERVISOR → security-supervisor

• SPOT_BOOKING_MANAGER → spot-booking-manager

• EXECUTIVE_ASSISTANT → executive-assistant

• COMPLIANCE_AUDITOR → compliance-auditor

• TRANSPORT_MANAGER_NO_COMPLIANCE → transportmanager-nocompliance

• FINANCIAL_CONTROLLER → financial-controller

• SENIOR_BILLING_AUDITOR → senior-billing-auditor

• SUPER_AUDITOR → super-auditor

• MIS_SUPPORT → mis-support

Example :
 If this feature needs to be enabled for TRANSPORT_MANAGER_NO_BILLING use the role name transportmanager-nobilling in the property

https://moveinsync.atlassian.net/browse/PB-53163
Managing Seat Booking for Kids During the Office Commute

https://moveinsync.atlassian.net/browse/PB-53175

Managing Seat Booking for Kids During the Office Commute: Driver App

• Not a feature of Driver App enablement

Driver App

• In the co-passenger list, employees with kids will be indicated as:

  • [Employee Name] (Kids: X)

• No separate sign-in needed for kids. When the employee signs in, kid presence is auto-recorded.

Known limitation : 

1. Maximum cab capacity won’t be calculated in this

2. Not yet implemented for shuttle.

https://moveinsync.atlassian.net/browse/TB-37660

Scoped Security Sign-Off Handling on Trip End.

Interference.https://moveinsync.atlassian.net/browse/TB-37661

Prevent Cross-Trip Security Sign-Off 

PB-52024

[XL ETS] Enforce no show feature enablement

Problem Statement:

Drivers often mark employees as "No Show" without adequate verification, leading to disputes and lack of accountability. Introducing precise geo-location and wait-time validation ensures transparency and accuracy..
Objectives:

1. Prevent premature or false "No Show" tagging by drivers.

2. Enable better accountability through geo-location and time tracking.

3. Reduce disputes between drivers and employees regarding presence and waiting time.

Scope:

• Implement location verification, timer functionality, and a drop-down reason selector for no show marking

• Store data collected (geo-location and timestamps) for auditing and dispute resolution.

• Send an email, msg notification to the employee that includes the geocoord data of driver

• Integrate these data points in the no-show report.

Driver App

FEATURE_NO_SHOW_EMPLOYEE_ENABLE = true

ENABLE_NO_SHOW_BUTTON_BASED_ON_GEO_FENCE= false

ENABLE_NO_SHOW_BUTTON_BASED_ON_TIME = false

ENABLE_ENHANCED_NO_SHOW = true

ENHANCED_NO_SHOW_TRIP_TYPE = REGULAR,SHUTTLE,SPOT (Not working for Rentlz)

ENHANCED_NO_SHOW_TIMER = ____

ENHANCED_NO_SHOW_GEOFENCE = ____

ENHANCED_NO_SHOW_VERIFICATION = true

ETS Config

APPROVAL_POST_NO_SHOW_CHECK Existing property : false

NO_SHOW_EMPLOYEE_EMAIL_NOTIFIATION_TO_TM_RECIPIENTS Existing Property : Should have comma seperated emails

SEND_NO_SHOW_EMAILS_FROM_SCHEDULER : True

ENABLE_NO_SHOW_EMPLOYEE_EMAIL_NOTIFICATION