Assets
Assets

Assets

📖 Afaqy Knowledge Base / Smart Taxi / Admin Portal / Assets

CONTENTS

Vehicles

The Vehicles module allows administrators to manage and monitor all registered vehicles within the system.

It provides visibility into:

  • Device pairing
  • Driver assignment
  • Account ownership
  • Wasl connectivity status
  • Vehicle configuration

Overview

The Vehicles page displays a table of registered vehicles for the selected account.

image

Administrators can:

  • Search for vehicles
  • Filter by account
  • View device identifiers
  • Monitor Wasl connection status
  • Edit vehicle configuration
💡

Administrators can control the visibility of any column—such as Account Name, GPS IMEI, Tablet IMEI, Driver Assigned, Wasl Status, Wasl Driver, Status, Sim Card, Status, Installation Date, and Expiration Date—by clicking the icon to show or hide columns as needed

Search

A search bar allows administrators to search by:

  • Vehicle Name
  • GPS IMEI
  • Tablet IMEI
  • Driver Name

Results update dynamically.

Account Filter

An account dropdown allows administrators to:

  • View vehicles under a specific client account
  • Switch between accounts

The table updates based on the selected account.

Vehicle Table Columns

The Vehicles table includes:

  • Vehicle Name – Unique vehicle identifier
  • Account Name – Associated client account
  • GPS IMEI – GPS device identifier
  • Tablet IMEI – Tablet device identifier
  • Driver Assigned – Linked driver
  • Wasl Status – Regulatory connection state
  • Edit Action (Pencil Icon) – Opens vehicle configuration

Wasl Status

The Wasl Status column indicates the connection state between the vehicle and the regulatory system.

Examples:

  • Connected – Vehicle successfully synchronized
  • Other statuses may reflect pending or disconnected states

This status helps administrators verify compliance integration.

Editing a Vehicle

Clicking the pencil icon opens the Edit Vehicle page.

The Edit page consists of two main sections:

  1. General Information
  2. Technical Configuration (Pulses & Sensors)

1. General Information

This section controls the vehicle’s operational identity and status.

Vehicle Name

Displays the vehicle identifier.

image

Taxi Type

Administrators can select:

  • Public
  • Airport

Optional:

  • Mecca Taxi (checkbox)

Taxi type affects fare logic and operational classification.

GPS IMEI

Identifier of the installed GPS device.

Used for:

  • Location tracking
  • Route mapping
  • Distance calculation

Status

Vehicle status can be set to:

  • Active — Vehicle can operate and start trips
  • Inactive — Vehicle cannot initiate trips

Tablet IMEI

Identifier of the in-vehicle tablet.

Used for:

  • Fare display
  • Passenger interface
  • Device authentication

Assigned Driver

Displays or defines the driver linked to the vehicle.

Installation Date

Date when the device or configuration was installed.

SIM Card Number

  • Defines the SIM installed in the vehicle tablet/device.
  • Used for connectivity.

Expiration Date

Defines the operational validity period of the vehicle configuration.

2. Pulses Configuration

The Pulses section defines speed and mileage calibration parameters.

These values affect how the system calculates:

  • Distance
  • Speed
  • Fare
⚠️

Improper calibration may result in inaccurate fare or distance calculation.

Fields

Speed/Mileage: Defines pulse mode.

Speed Constant: Numeric constant used in speed computation.

Pulse Count Per Circle: Number of pulses generated per wheel rotation.

Mileage Per Circle: Distance covered per wheel rotation.

image

3. Sensors Configuration

The Sensors section defines digital input mappings connected to vehicle hardware.

Digital Inputs

  • Digital Input 1
  • Digital Input 2
  • Digital Input 3
  • Digital Input 4

Each input can be mapped to a sensor.

Example Sensor Mappings

  • seat-sensor-1
  • seat-sensor-2
  • seat-sensor-3
  • sos-sensor

These sensors are used for:

  • Passenger seat detection
  • SOS trigger detection
💡

Correct configuration ensures proper passenger validation, accurate trip dispatch and SOS event handling

Operational Impact

Vehicle configuration directly affects:

  • Trip generation
  • Fare accuracy
  • GPS route availability
  • Passenger validation logic
  • SOS functionality
  • Regulatory synchronization

Improper configuration may result in:

  • Incorrect fare calculations
  • Missing trip routes
  • Failed compliance dispatch

Saving Changes

At the bottom of the Edit Vehicle page:

  • Save — Applies changes
  • Cancel — Discards changes

Changes only take effect after clicking Save.