Trip Lifecycle
Trip Lifecycle

Trip Lifecycle

📖 Afaqy Knowledge Base / Smart Taxi / Driver App / Trip Lifecycle

CONTENTS

Overview

The Trip Lifecycle represents the complete operational journey of a trip, beginning when a driver initiates a trip and ending when the trip is successfully completed and synchronized with the Smart Taxi ecosystem.

image

The Driver App serves as the primary operational interface responsible for managing trip states, synchronizing operational data, and ensuring accurate fare calculation and regulatory compliance throughout the trip.

A trip progresses through a series of operational stages that are reflected across:

  • Driver App
  • Passenger Tablet
  • Admin Portal
  • Client Portal
  • Reports
  • Regulatory Systems (WASL)

Purpose

The Trip Lifecycle is designed to:

  • Standardize trip execution
  • Ensure accurate fare calculation
  • Support passenger transparency
  • Maintain operational visibility
  • Enable real-time monitoring
  • Support regulatory compliance
  • Generate reliable reporting data

Trip Lifecycle Stages

A trip typically progresses through the following stages:

  1. Driver Available
  2. Trip Initiation
  3. Active Trip
  4. Trip Monitoring
  5. Trip Completion
  6. Passenger Feedback
  7. Compliance Synchronization
  8. Reporting & Archival

1. Driver Available

Before a trip can begin, the driver must be in an operationally available state.

Requirements include:

  • Successful authentication
  • Valid operational session
  • Active vehicle assignment
  • Device synchronization
  • Connectivity availability

Once these conditions are met, the driver is ready to initiate trips.

2. Trip Initiation

Purpose

Trip Initiation marks the official start of a passenger trip.

When a trip is started, the Smart Taxi ecosystem establishes a new operational trip record and begins synchronizing trip data across all connected systems.

Operational Actions

During trip initiation, the system may:

  • Generate a unique Trip ID
  • Record trip start timestamp
  • Associate the trip with the driver
  • Associate the trip with the vehicle
  • Activate fare calculation
  • Begin GPS tracking
  • Activate passenger tablet trip mode
  • Initiate compliance workflows

Passenger Tablet Activation

When the trip begins, the passenger tablet transitions from the idle state to the active trip state.

Passengers may begin viewing:

  • Trip information
  • Fare information
  • Distance calculations
  • Driver information
  • Trip status

The passenger experience becomes synchronized with the trip lifecycle.

3.Active Trip

Overview

The Active Trip state represents the period between trip initiation and trip completion.

During this stage, the Driver App continuously exchanges operational information with backend systems.

Real-Time Synchronization

The Driver App continuously synchronizes:

  • GPS location
  • Distance traveled
  • Waiting time
  • Trip status
  • Operational events
  • Compliance events

Synchronization occurs throughout the trip.

Fare Processing

During an active trip, the fare engine continuously calculates:

Basic Fare: The initial charge applied at trip start.

Distance Fare: Calculated based on distance traveled.

Waiting Time Fare: Calculated when vehicle movement falls below operational thresholds.

Long-Distance Fare: Applied when configured distance thresholds are exceeded.

Peak Pricing: May include:

  • Night fare
  • Weekend fare
  • Other configured fare rules

VAT: Applicable taxes are calculated according to configured fare settings.

4. Trip Monitoring

Operational Visibility

Trip activity becomes visible throughout the Smart Taxi ecosystem.

Administrators and client operators may monitor:

  • Active trips
  • Vehicle activity
  • Driver activity
  • Operational metrics
  • Compliance status

Operational visibility supports real-time monitoring and investigation.

Passenger Experience

During an active trip, passengers may view:

  • Current fare
  • Distance traveled
  • Trip duration
  • Driver information
  • Taxi information

Information displayed on the passenger tablet updates dynamically.

5. Trip Completion

Purpose

Trip Completion marks the end of operational trip activities.

The Driver App finalizes trip information and initiates post-trip workflows.

Completion Actions

When a trip ends, the system may:

  • Record trip end timestamp
  • Finalize distance calculations
  • Finalize fare calculations
  • Calculate total fare
  • Apply VAT
  • Close operational trip records
  • Trigger passenger feedback workflows

Fare Finalization

The final fare may include:

  • Basic fare
  • Distance fare
  • Waiting time fare
  • Long-distance fare
  • Peak fare adjustments
  • VAT

The final amount becomes available for reporting and reconciliation.

6. Passenger Feedback

After trip completion, the passenger tablet transitions to the feedback screen.

Passengers may:

  • Rate the trip experience
  • Submit feedback
  • Complete the trip workflow

Feedback data becomes available for operational review.

7. Compliance Synchronization

Following trip completion, regulatory synchronization workflows may execute.

Examples include:

  • Trip dispatch confirmation
  • Regulatory acknowledgment processing
  • Compliance reporting
  • Audit trail updates

Successful synchronization supports regulatory requirements.

8. Reporting & Archival

Completed trips become available throughout the Smart Taxi reporting ecosystem.

Trip data may appear within:

  • Dashboard metrics
  • Trip Status records
  • Trip Log Reports
  • WASL Reports
  • Operational analytics

This information supports reconciliation, auditing, and performance monitoring.

Operational Impact

The Trip Lifecycle directly affects:

  • Fare accuracy
  • Passenger experience
  • Regulatory compliance
  • Operational visibility
  • Report generation
  • Revenue calculations
  • Fleet performance analysis

Any interruption during the lifecycle may result in incomplete operational records or synchronization issues.

Best Practices

  • Verify operational readiness before starting a trip
  • Ensure device synchronization remains active throughout the trip
  • Monitor connectivity during operations
  • Confirm trip completion before ending operational sessions
  • Review synchronization issues immediately
  • Ensure compliance-related workflows complete successfully