Custom Cab Fleet Management & CRM Enterprise Suite — Multi-tenant, AI Dispatch, Unlimited API Flexibility

The Enterprise Cab Platform built by PrecisionTech is emphatically not a boxed product. There is no standard version, no licence key, and no fixed feature set. Every deployment is a bespoke, ground-up engineering engagement — architected around the specific business model, operational scale, regulatory environment, and technology ecosystem of the client.

This distinction is fundamental and must be understood before any engagement:

• Boxed SaaS products (the category most competitors operate in) deliver a fixed feature set, a shared database architecture, and a pre-determined workflow. Operators must adapt their business to the software's constraints.
• PrecisionTech's custom enterprise suite is the inverse — the software is engineered to precisely match the operator's business model. If your business has a unique pricing logic, a non-standard dispatch hierarchy, a proprietary driver grading algorithm, or an industry-specific compliance requirement — we build it as a core module, not a workaround.

What "custom" means technically:

• Custom database schema — no pre-defined data model constraints. If you need to track 47 custom fields per vehicle, we design the schema around that requirement.
• Custom API surface — every endpoint, webhook, and integration point is designed around your specific data exchange requirements. We do not force your integrations to adapt to our API format.
• Custom UI/UX — no white-labelling of a generic UI. Every interface — Super Admin console, Corporate portal, Vendor dashboard, Driver PWA — is designed and built to your brand and workflow specifications.
• Custom business logic — pricing algorithms, dispatch rules, SLA escalation logic, payment settlement rules, and report definitions are all implemented as configurable business logic, not hard-coded constraints.

PrecisionTech brings 30 years of enterprise software development experience — serving thousands of global clients — to every cab platform engagement. The result is a platform that is genuinely owned by the operator, not licensed from a SaaS vendor on terms that can change at any renewal.

The 6-tier login hierarchy is the architectural feature that most clearly distinguishes the Enterprise Cab Platform from any off-the-shelf taxi dispatch software. It enables genuinely multi-tenant, multi-stakeholder operations where every party — the platform operator, corporate clients, employees, coordinators, vendors, and drivers — has a precisely scoped, isolated, role-appropriate interface.

Tier 1 — Super Admin (Platform Operator Layer):

• Global visibility and control across all tenant organisations
• Creates and manages corporate client accounts with custom configuration per client
• Controls platform-wide pricing templates, vehicle categories, zone definitions
• Manages billing and revenue across all tenants — with per-client invoicing
• Access to aggregate fleet analytics, SLA compliance across all vendors, and platform health metrics
• Configures API integrations at platform level (GDS, ERP, payment gateways)

Tier 2 — Corporate Admin (Organisation Layer):

• Isolated data environment — sees only their organisation's data, users, trips, and billing
• Configures travel policy for their employees — permitted zones, vehicle categories, spending limits
• Manages employee roster and cost centre assignments
• Selects from the Super Admin's approved vendor pool or requests new vendor onboarding
• Accesses departmental billing reports and reconciles against their ERP

Tier 3 — Corporate User (Employee Layer):

• Self-service booking portal with policy guardrails — only sees options permitted by their Corporate Admin
• Books rides, tracks vehicle in real time, receives OTP for trip start, rates driver
• Accesses personal trip history, receipts, and duty slips
• Cannot exceed budget limits or book outside permitted zones without coordinator override

Tier 4 — Corporate Coordinator (Power-User Layer):

• Books on behalf of multiple employees simultaneously — ideal for executive assistants and travel desks
• Manages duty rosters — assigns recurring trips to employees with day/time/route templates
• Bulk scheduling for employee shifts, airport transfers, event logistics
• Generates trip reports for HR audits, expense reimbursement, and cost centre allocation

Tier 5 — Vendor (Fleet Owner/Operator Layer):

• Fleet owner or sub-contractor portal — manages their own vehicles, drivers, and trip assignments
• Real-time trip assignment board — accepts, rejects (within SLA), or reassigns trips to their drivers
• Driver performance dashboard — tracks their drivers' ratings, SLA compliance, and earnings
• Settlement dashboard — tracks earnings per trip, disputes, and payment status
• Completely isolated from other vendors — no cross-vendor data visibility

Tier 6 — Driver (Operator Layer):

• PWA for zero app-store dependency (instant onboarding without Play Store / App Store approval) + Native iOS/Android for full-feature experience
• Trip notification with route preview and customer details
• GPS navigation (integrated Google Maps / MapmyIndia)
• Customer OTP verification at trip start
• Trip start, waypoint, and trip end management
• SOS emergency button with real-time alert to dispatch and coordinator
• Earnings dashboard, document upload, compliance status

Why this matters: Most cab management software offers 2–3 roles (admin, driver, customer). The 6-tier hierarchy enables the platform to serve genuinely complex enterprise use cases — a corporate travel company managing 200 corporate clients each with their own employees and coordinators, using 80 vendor-operators each with their own driver fleets, all federated under a single master control layer. No boxed product achieves this architecture without months of customisation work — if at all.

The real-time GPS telematics layer of the Enterprise Cab Platform is built on a high-throughput, low-latency event streaming architecture — designed to track hundreds or thousands of vehicles simultaneously without degradation in update frequency or positional accuracy.

Architecture components:

• Vehicle location source: Driver's mobile device GPS (iOS/Android native location services or PWA Geolocation API) reporting at 2–5 second intervals. For enterprise fleets with dedicated GPS hardware: OBD-II dongle integration or hard-wired GPS tracker integration via our device API.
• Data pipeline: Location events transmitted as JSON payloads over WebSocket connections to our real-time processing cluster. WebSocket eliminates HTTP polling overhead — the server pushes updates to the client browser without repeated HTTP requests.
• Processing layer: Location events processed through an event streaming platform (Apache Kafka-based architecture) — enabling parallel processing for multiple downstream consumers: live map update, dispatch engine, driver behaviour analytics, geofence triggers, and SLA monitoring.
• Map rendering: Sub-3-second update cycle on the Super Admin and Corporate Admin live fleet map. Vehicle markers animate smoothly between GPS position updates using interpolation algorithms — no jarring jumps on the map interface.
• Geofencing: Server-side geofence evaluation for every location event — triggering automated actions (arrival notification, zone violation alert, school/restricted zone entry notification) without client-side computation overhead.

Driver behaviour telematics (optional module):

• Harsh braking detection: Accelerometer data from mobile device or OBD-II dongle identifies deceleration events exceeding threshold g-force values
• Speed violation: GPS-derived speed compared against road speed limits (integrated HERE Maps or MapmyIndia speed limit data)
• Idle time: GPS speed below threshold for defined duration triggers idle time event — fuel cost attribution
• Fatigue detection: Total driving hours tracked per driver per shift — alert triggered when approaching regulatory limits
• Route adherence: Planned route vs. actual path comparison — deviation alerts for corporate clients with strict route policies

Fleet tracking KPIs available to Super Admin and Corporate Admin:

• Active vehicles on map (live count)
• Vehicles on trip / available / idle / offline
• Average response time from booking to driver assignment
• ETA accuracy (planned vs. actual arrival time)
• Per-vendor SLA compliance rate (% trips completed within agreed time)
• Driver behaviour score (composite metric from telematics events)

Scalability: The telematics architecture is designed and tested for simultaneous tracking of 5,000+ vehicles on a single deployment instance. Horizontal scaling via container orchestration (Kubernetes) supports unlimited fleet growth without re-architecting the tracking layer.

The AI-driven algorithmic dispatch engine is one of the highest-value modules of the Enterprise Cab Platform — replacing manual dispatcher decision-making with a real-time, multi-variable optimisation system that assigns trips to drivers faster, more consistently, and with significantly better outcomes than human dispatch.

Dispatch algorithm — inputs and variables:

• Driver proximity: Real-time GPS position of all available drivers — Euclidean distance and road-network distance (via routing API) to pickup location
• Driver status: Available, on-trip (with ETA to completion), offline, on-break — real-time status from driver app heartbeat
• Driver performance score: Historical rating, SLA compliance rate, cancellation rate, customer rating — weighted in assignment preference
• Vehicle category match: Booking request vehicle category vs. driver's vehicle category — exact or upgrade match logic
• Corporate client preferences: Preferred vendor list, blacklisted drivers (if any), vehicle type preferences per corporate policy
• Traffic and ETA: Real-time traffic data from routing API (Google Maps Platform, MapmyIndia) — actual travel time, not straight-line distance
• Shift end proximity: Driver approaching end of permitted shift hours is deprioritised for long-distance trips
• Load balancing across vendors: Configurable algorithm to distribute trips fairly across the vendor pool — preventing monopolisation by a single vendor

Dispatch modes supported:

• Fully automated dispatch: Algorithm assigns trip to optimal driver — driver receives notification and must accept within configurable timeout (30 seconds default). If not accepted, cascades to next-best driver automatically.
• Semi-automated dispatch: Algorithm generates ranked recommendation list for human dispatcher — dispatcher reviews and confirms. Retains human oversight while eliminating manual search.
• Manual dispatch: Human dispatcher browses live map and assigns manually — available as fallback mode or for VIP trip handling.
• Priority dispatch: VIP or SLA-critical trips are routed through a separate priority queue — bypassing standard queue and assigned to highest-rated available drivers.

Outcomes achieved by the AI dispatch engine (reference deployments):

• 28% reduction in empty-leg trips (improved vehicle utilisation)
• Average trip assignment time reduced from 4.2 minutes (manual) to 18 seconds (AI dispatch)
• Driver idle time reduction of 22% in urban operations
• SLA breach rate reduction of 41% in the first quarter post-deployment
• Customer satisfaction score improvement of 0.4 points (on a 5-point scale) within 3 months

Machine learning enhancement (optional advanced module):

• Demand prediction: historical trip data + time-of-day + day-of-week + calendar events → pre-positioning drivers in high-demand zones before demand materialises
• ETA accuracy improvement: ML model trained on historical actual vs. predicted arrival times for specific zones and time slots — progressively improving ETA predictions
• Driver churn prediction: ML model identifying drivers at risk of deactivation based on behavioural signals — enabling proactive retention action by operations team

The Enterprise Cab Platform is built on an API-first architecture — meaning every functional capability of the platform is exposed as an API endpoint, and the platform is designed from the ground up to consume any external API. The integration surface is genuinely unlimited — if an API exists, or if a data exchange protocol can be defined, we can integrate it.

Inbound API integrations (external systems pushing data into the platform):

• Global Distribution Systems (GDS): Amadeus, Sabre, Travelport (Galileo, Apollo, Worldspan) — enabling travel management companies (TMCs) to book ground transportation directly from their GDS workflow without leaving their existing reservation system. Cab availability, pricing, and booking confirmation are surfaced within the GDS interface via our API.
• Corporate Travel Booking Tools: SAP Concur, Egencia, KDS, Cytric — integration with enterprise travel and expense management platforms so employees booking flights also book coordinated ground transport
• Online Travel Agencies (OTAs): MakeMyTrip Corporate, Yatra for Business, ClearTrip for Work — enabling ground transport to be booked as part of the complete travel itinerary
• Airport transfer aggregators: Inbound API from third-party airport transfer booking engines — ground transport bookings land directly in our dispatch queue without manual re-entry

Outbound API integrations (platform pushing data to external systems):

• ERP systems: SAP S/4HANA, Oracle ERP Cloud, Microsoft Dynamics 365, Tally — automated posting of confirmed trip data (employee, cost centre, trip cost, GST component) directly to the client's ERP. Eliminates manual expense entry and enables real-time P&L visibility of ground transport costs.
• Payment gateways: Razorpay, PayU, CCAvenue, Cashfree, Instamojo (India); Stripe, Square (international); Telr, PayFort, PayTabs (GCC) — dynamic payment gateway selection based on transaction currency, amount, and regulatory requirements
• Accounting software: QuickBooks, Zoho Books, FreshBooks — automated invoice generation and reconciliation
• HRMS / Attendance systems: ADP, Darwinbox, Keka, Zoho People — triggering cab booking automatically based on employee shift scheduling data (employee starts a night shift → system automatically schedules pickup cab)
• Communication platforms: SMS via Twilio, MSG91, ValueFirst; WhatsApp Business API — automated notifications (trip assigned, driver en-route, OTP, trip completed, invoice) sent through preferred communication channel
• IoT and telematics hardware: Meitrack, Concox, Teltonika GPS tracker APIs; OBD-II dongle data feeds — hardware-grade GPS accuracy alongside or instead of mobile device GPS

Bidirectional API integrations:

• GST/e-Invoice API (IRP/GDS integration): Automated e-invoice generation and QR code embedding for every trip — GST-compliant invoice delivered to corporate client in real time. ITC reconciliation support.
• Emergency services integration: Integration with corporate security operations centres — SOS trigger from driver app sends real-time GPS position to security team API endpoint

API formats supported: REST (JSON), SOAP (XML), GraphQL, WebSocket (real-time), webhook (event push), file-based (SFTP CSV/Excel for legacy system integrations). No integration requirement is too non-standard — PrecisionTech has 30 years of enterprise system integration experience across every protocol and data format.

Multi-tenancy in the Enterprise Cab Platform means that a single platform instance simultaneously serves multiple independent organisational clients (tenants) — each with their own isolated data environment, custom configuration, and branded interface — while sharing the underlying infrastructure for cost efficiency.

Two multi-tenancy models we implement:

1. Platform-level multi-tenancy (the operator serves multiple corporate clients):

• A cab operator or fleet management company deploys the Enterprise Cab Platform and onboards multiple corporate clients as tenants
• Each corporate client (tenant) gets: their own branded web portal, their own employee/coordinator roster, their own travel policy configuration, their own vendor assignment, their own billing and invoicing, and their own reporting — all isolated from every other corporate client
• The Super Admin (platform operator) manages all tenants from a single master console with aggregate visibility
• A new corporate client can be onboarded in minutes via the Super Admin interface — no new deployment required

2. Vendor-level multi-tenancy (the platform manages multiple fleet operators):

• Multiple vendors (fleet owners, sub-contractors) operate under the platform with their own isolated environments
• Each vendor sees only their own vehicles, drivers, trip assignments, and earnings — never another vendor's data
• The Super Admin can configure which vendors serve which corporate clients and in which zones

Data isolation architecture:

• Logical isolation (schema-based or row-level security): All tenant data stored in a shared database with tenant_id foreign key on every table. Row-level security (RLS) enforced at the database layer — queries automatically scoped to the authenticated tenant's data. No application-level filtering bypass can expose cross-tenant data.
• Physical isolation (dedicated schema or database per tenant): For enterprise clients with contractual data isolation requirements, we deploy dedicated database schemas or completely separate database instances per tenant — zero data mixing at the storage layer.
• API-level isolation: Every API call is authenticated with a tenant-scoped JWT token. The API gateway rejects any request that attempts to access resources outside the authenticated tenant's scope — enforced before the request reaches the application layer.
• Encryption: All tenant data encrypted at rest with tenant-specific encryption keys (in AWS KMS or Azure Key Vault). Cross-tenant key access is architecturally prevented.

Custom configuration per tenant:

• Custom branding (logo, colours, domain — white-label support)
• Custom pricing rules (zone-based rates, time-of-day multipliers, vehicle category pricing)
• Custom workflow configuration (approval workflow for trip requests, SLA definitions)
• Custom report definitions (KPIs specific to the corporate client's business requirements)
• Custom notification templates (branded SMS, email, WhatsApp content)

A Progressive Web App (PWA) is a web application that uses modern browser APIs to deliver an app-like experience — offline capability, push notifications, camera access, GPS location, and home screen installation — without requiring distribution through the Apple App Store or Google Play Store.

Why we build the Driver App as a PWA (in addition to native apps):

1. Zero app-store dependency for driver onboarding:

• App Store and Play Store approvals take 3–7 business days and can be rejected or delayed arbitrarily. For platform operators onboarding 500 new drivers simultaneously for a city launch, a week-long app approval delay is operationally devastating.
• PWA installation: driver visits a URL, taps "Add to Home Screen" — full app experience in under 30 seconds. No app store account required, no app store approval required.

2. Update deployment without driver action:

• Native app updates require drivers to download the new version from their app store — and fragmented version adoption creates platform inconsistency. With PWA, the latest version is served automatically — every driver is always on the current version without any action required.

3. Lower device requirement:

• PWA runs on any smartphone with a modern browser — including Android devices with limited storage that cannot accommodate a large native app. Critical for Indian markets where budget Android devices are common among drivers.

4. Single codebase, cross-platform:

• PWA works on both iOS Safari and Android Chrome with a single codebase — no platform-specific maintenance overhead.

PWA vs. Native App — capability comparison in our Driver App:

• GPS location tracking: Both PWA and native — full real-time GPS location sharing
• Push notifications (trip assignments, updates): Native — full support. PWA on Android — full support. PWA on iOS — limited (iOS 16.4+ supports Web Push from home screen)
• Offline mode: Both — Service Worker caching enables core driver UI to function offline with queue synchronisation on reconnection
• Camera access (selfie verification, document upload): Both PWA and native — full camera API access
• Home screen icon: Both — PWA installs from browser, native installs from app store
• Performance: Native apps have advantage in CPU/GPU-intensive operations — rendering complex maps, processing accelerometer data for driver behaviour. For this reason, we provide native iOS and Android apps alongside the PWA — operators choose which distribution model to emphasise.

Our recommendation: Launch with PWA for rapid driver onboarding. Deploy native apps simultaneously for performance-sensitive features. All three (PWA, iOS, Android) share the same backend API — no data divergence between app types.

The dynamic pricing engine of the Enterprise Cab Platform is a configurable, rule-based pricing system that calculates trip fares in real time based on multiple dimensions — enabling operators to implement pricing models of any complexity without manual calculation or spreadsheet management.

Pricing dimensions supported:

1. Zone-based pricing:

• Define geographic zones on the map (airport zones, CBD zones, industrial zones, residential zones)
• Configure different base rates for each zone pair (Zone A to Zone B, Zone B to Airport, etc.)
• Override pricing for specific pickup/drop combinations — airport transfer pricing differs from intra-city zone pricing

2. Distance and time-based pricing:

• Base fare + per-km rate + per-minute rate (running time)
• Different per-km rates for different speed ranges (slow urban traffic vs. highway speeds)
• Minimum fare guarantee regardless of actual distance/time

3. Time-of-day and day-of-week pricing:

• Peak hours (morning and evening rush) with configurable multipliers
• Night surcharge for trips starting after midnight
• Weekend and holiday pricing tiers

4. Demand-based surge pricing:

• Surge multiplier activated automatically when demand in a zone exceeds supply by a configured threshold
• Configurable surge caps — maximum surge multiplier, maximum surge duration
• Surge transparency — customers see surge indicator and actual fare before booking confirmation
• Corporate clients can be exempted from surge pricing (contract rate always applies)

5. Contract rates for corporate clients:

• Each corporate client can have negotiated contract rates — fixed price for specific route types (airport transfer, inter-city, within-city)
• Contract rates override dynamic pricing for authorised corporate users
• Contract rate validity period, usage limits, and applicable vehicle categories configurable per contract

6. Vehicle category pricing:

• Separate pricing profiles for Sedan, SUV, Luxury, Tempo Traveller, Bus, and any custom vehicle category
• Pricing differentials between categories configurable by zone, time, and distance

7. Outstation and multi-day pricing:

• Fixed package pricing for outstation trips — one-way, round-trip, multi-day
• Per-km overage billing beyond package kilometres
• Night halt charges configurable by zone and vehicle category

8. GST and tax configuration:

• GST rate configurable per vehicle category (5% / 12% depending on AC status, per HSN code)
• Automated GST computation and display on fare breakup and invoice
• GSTIN of operator and corporate client captured on every invoice for ITC claim

All pricing rules are configured through the Super Admin console — no code change required to update rates. Price changes take effect immediately for new bookings. Historical trips retain their original pricing for invoice accuracy.

Corporate billing automation is one of the highest-ROI modules of the Enterprise Cab Platform — eliminating the manual billing reconciliation that consumes significant administrative time in traditional cab operations and creates disputes between operators and their corporate clients.

Billing architecture:

Trip-level billing:

• Every completed trip generates a digital trip record: employee name, employee ID, cost centre, pickup, drop, distance, duration, vehicle category, base fare, GST component, total fare, driver rating, trip completion time
• Trip records are the atomic billing unit — all higher-level invoices are aggregations of trip records
• Trip records are immutable — once a trip is completed, its financial record is locked. Disputes are managed through a dispute record linked to the trip, not modification of the original

Invoice generation:

• Real-time invoice: Trip receipt PDF/email delivered to the employee and coordinator immediately on trip completion
• Periodic consolidated invoice: Daily, weekly, or monthly consolidated invoice generated for the corporate client — covering all trips by all employees, grouped by cost centre, with GST component breakdown
• Credit note management: Cancelled trips, disputed trips, and refunds automatically generate credit notes linked to the original invoice
• GST-compliant invoice format: All invoices generated in GST-compliant format with: operator GSTIN, corporate client GSTIN, HSN/SAC code, taxable value, CGST, SGST/IGST, total amount. e-Invoice (IRN + QR code) generated automatically via integration with IRP API for B2B invoices above the e-Invoice threshold.

Cost centre allocation:

• Each employee assigned to one or more cost centres (departments, projects, entities)
• Trip costs automatically allocated to the employee's default cost centre — or the employee selects from their permitted cost centres at booking time
• Department-wise cost reports enable CFOs to allocate ground transport costs accurately to P&L

Payment and settlement:

• Corporate client payment: Invoice amount settled via bank transfer, corporate credit card, or automated payment gateway debit (with corporate client's pre-authorisation)
• Vendor/driver settlement: Trip earnings automatically calculated after deducting platform commission. Settlement to vendors via bank transfer (NEFT/RTGS/IMPS) or UPI on configurable settlement cycles (daily, weekly, monthly). Automated settlement via payment gateway API (Razorpay Route, Cashfree Split Settlement)
• TDS management: Vendor settlement amounts calculated after applicable TDS deduction. TDS certificates generated for vendors at financial year end.

ERP reconciliation:

• Trip data pushed to corporate client's ERP (SAP, Oracle, Dynamics, Tally) via API — eliminating manual expense entry
• Invoice data matched against purchase order (PO) in the ERP — three-way matching for AP automation
• Cost centre data aligned with ERP chart of accounts — no manual remapping of expense categories

The Enterprise Cab Platform supports complete white-labelling — every customer-facing interface can be delivered under the operator's own brand, with no PrecisionTech branding visible to end users.

White-label options:

Web portals:

• Custom domain for every interface — operator's domain (e.g., ops.yourcompany.com), corporate client portal (e.g., travel.clientcompany.com with CNAME configuration)
• Custom logo, colour scheme, typography, and UI theme per portal
• Custom email domain for all automated notifications (noreply@yourcompany.com)
• Custom favicon, meta titles, and social sharing cards

Mobile apps:

• PWA: Custom PWA name, icon, splash screen, and theme colour. Installed on driver's device home screen as "[Operator Name] Driver" — no mention of PrecisionTech
• Native iOS app: Published under the operator's Apple Developer account. Operator's App Store listing, screenshots, description, and in-app branding. PrecisionTech's name does not appear in the App Store listing.
• Native Android app: Published under the operator's Google Play Console account. Operator's Play Store listing. Custom package name (com.yourcompany.driverapp)
• Customer booking app (if required): Separate branded passenger app — iOS and Android — published under the operator's developer accounts

Multi-brand deployment:

• For operators running multiple brands (e.g., economy cab brand and luxury cab brand as separate products), we support multi-brand deployment within a single Super Admin — different branding, pricing, and vehicle categories for each brand, all managed from one control layer

Localisation:

• Multi-language UI — English, Hindi, regional Indian languages, Arabic (RTL), French, German — configurable per deployment
• Multi-currency support — INR, USD, EUR, AED, SAR, SGD — with real-time exchange rate integration for international platforms
• Local map integration — Google Maps (global), MapmyIndia (India), HERE Maps (international), Apple Maps (iOS native)

SLA monitoring and KPI reporting are built into the DNA of the Enterprise Cab Platform — not added as an afterthought. Every trip event, driver action, and system interaction generates structured data that feeds the reporting layer in real time.

SLA monitoring framework:

• Trip SLA: Per corporate client, configurable SLA definitions — driver must be assigned within X minutes, driver must arrive at pickup within Y minutes, trip must complete within Z% of estimated duration
• Real-time SLA breach alerts: Dispatcher is notified the moment a trip enters SLA breach risk zone — not after the breach has occurred. Alert triggers at configurable percentage of SLA window consumed.
• Escalation matrix: Configurable escalation path — first alert to dispatcher, second alert to supervisor, third alert to corporate client coordinator — with automated communication via SMS and WhatsApp
• Vendor SLA scorecards: Weekly and monthly SLA compliance rate per vendor — percentage of trips completed within SLA, average delay, cancellation rate. Vendor scorecards visible to both Super Admin and Corporate Admin.

Operational KPI dashboard (Super Admin):

• Total bookings today / this week / this month (with trend vs. prior period)
• Booking completion rate (vs. cancellation and no-show)
• Average trip assignment time (target: <2 minutes in AI dispatch mode)
• Fleet utilisation rate (active trips / total available vehicles)
• Revenue — total, by corporate client, by vehicle category, by zone
• Driver activity heatmap (geographic concentration of trip completions by hour)
• Customer satisfaction score (average post-trip rating)

Corporate client KPI dashboard (Corporate Admin):

• Total spend — today, week, month — vs. budget
• Trips by cost centre / department
• Top employees by trip count and spend
• Vendor performance rating — which vendors are serving their trips
• SLA compliance rate for their trips specifically
• Carbon footprint estimate (kg CO₂ per trip, based on vehicle category and distance — for ESG reporting)

Custom report builder:

• Drag-and-drop report builder enabling Super Admins and Corporate Admins to design custom reports without developer involvement
• 50+ pre-built report templates — accounting, operations, HR, compliance, ESG
• Report scheduling — automated email delivery (PDF, Excel) on daily/weekly/monthly schedule
• API export — all report data accessible via API for integration with BI tools (Power BI, Tableau, Metabase)

PrecisionTech's technology choices for the Enterprise Cab Platform are driven by three principles: performance at scale, maintainability over time, and client control (you own the code, not a SaaS vendor's shared infrastructure).

Backend:

• Primary API layer: Node.js (high-throughput event-driven architecture ideal for real-time WebSocket connections, GPS event streaming, and dispatch engine processing) OR Laravel/PHP (for organisations preferring the PHP ecosystem) — client chooses based on their team's expertise or our recommendation based on scale requirements
• Real-time layer: WebSocket server (Socket.io on Node.js) for live GPS position streaming, live dispatch notifications, and live trip status updates to all connected clients simultaneously
• Message broker: Apache Kafka or Redis Pub/Sub — decouples the GPS ingestion pipeline from the processing and display layers. Enables each downstream consumer (map, dispatch, analytics, geofence) to process events independently at its own rate
• Database: PostgreSQL (primary relational database — ACID compliance for financial transactions, trip records, and billing) + Redis (caching, session management, real-time driver status) + TimescaleDB or InfluxDB (time-series GPS data store — optimised for temporal queries on location history)
• Search: Elasticsearch — address autocomplete, driver search, trip search with full-text and geospatial query support

Frontend (Web):

• React.js (Super Admin console, Corporate Admin portal) — component-based architecture for complex, interactive dashboards
• Next.js — SSR/SSG for SEO-sensitive pages and corporate booking portal performance
• Leaflet.js or MapboxGL.js — interactive fleet map with custom marker clustering for large fleets

Mobile:

• React Native — iOS and Android native apps from a shared codebase (80%+ code reuse between platforms) with platform-specific performance optimisations for GPS and camera
• PWA — Service Worker, Web Push API, Geolocation API, Web Bluetooth (for OBD-II dongle integration via web standard)

Infrastructure:

• AWS (EC2, RDS, ElastiCache, MSK for Kafka, CloudFront CDN, S3, KMS) OR Azure OR GCP — client chooses cloud provider
• Kubernetes (EKS/AKS/GKE) for container orchestration — horizontal auto-scaling to handle demand spikes (festival seasons, large corporate events)
• Terraform — Infrastructure as Code for reproducible, version-controlled deployments
• CI/CD — GitHub Actions / GitLab CI — automated testing and deployment pipeline

Security:

• JWT + OAuth 2.0 — API authentication and authorisation
• AES-256 encryption at rest, TLS 1.3 in transit
• OWASP Top 10 — annual penetration testing
• WAF (AWS Shield / Cloudflare) — DDoS protection for customer-facing endpoints

The Enterprise Cab Platform processes significant volumes of personal data — employee names, phone numbers, GPS location history, payment data, biometric selfie verification images, and behavioural data (driver telematics). Compliance with India's DPDPA 2023 and applicable international privacy regulations is a design requirement, not an afterthought.

DPDPA 2023 compliance architecture:

• Consent management: Employees provide granular consent for GPS tracking, trip data storage, and communication at onboarding. Consent records are stored with timestamp, version of notice shown, and withdrawal capability.
• Data minimisation: Only PII strictly necessary for trip operation is collected. GPS history beyond configurable retention period (e.g., 90 days) is automatically purged.
• Right to erasure: Employee account deletion triggers automated purging of PII from active systems. Trip records may be retained in anonymised form for billing and compliance purposes.
• Data portability: Employee can request export of their trip history and personal data in machine-readable format (JSON/CSV).
• Data localisation: For Indian deployments, all PII stored on India-region cloud infrastructure (AWS Mumbai, Azure India Central, GCP Mumbai). No cross-border PII transfer without explicit consent and regulatory mechanism.

GDPR compliance (for operators serving EU residents):

• Standard Contractual Clauses (SCCs) incorporated in DPA with EU corporate clients
• GDPR Article 28 data processor obligations implemented — notification of sub-processors (AWS, Razorpay, etc.), breach notification to data controller within 24 hours
• Privacy by design — data minimisation, purpose limitation, storage limitation implemented at architecture level

Driver data protection:

• Driver GPS location shared with Corporate Admin only during active trip — historical driver location not accessible to corporate clients
• Driver documents (licence, insurance) stored with access restriction — accessible only to Vendor and Super Admin, not Corporate Admin or drivers of other vendors
• Driver biometric selfie (trip start verification) stored with encryption and retention limit

Payment data security:

• No raw card data stored on platform — payment is processed entirely through PCI DSS-compliant payment gateway (tokenisation model)
• UPI and wallet transactions processed through NPCI-regulated payment service providers

Applicable to UAE/GCC deployments:

• UAE PDPL (Personal Data Protection Law) compliance architecture — data residency in UAE, Arabic privacy notices, DPA with UAE data processors
• Saudi Arabia PDPL compliance for KSA-based operations

Yes — the Enterprise Cab Platform is fully capable of managing outstation, intercity, and multi-city fleet operations at scale. This is a specific strength of the custom-built architecture versus boxed products that are typically optimised for intra-city taxi operations.

Outstation trip management:

• Fixed package pricing: One-way and round-trip outstation packages with fixed base price, included kilometres, and per-km overage billing. Night halt charges per day beyond base.
• Driver and vehicle assignment: Dedicated driver and vehicle assigned for the full outstation trip duration — not reassigned mid-trip to other bookings.
• Route tracking: Continuous GPS tracking on outstation trips — operator and corporate client can monitor vehicle position throughout the multi-day journey.
• Toll and expense management: Driver logs toll expenses, parking charges, and state tax payments through the driver app. Expenses are validated, approved by coordinator, and added to the trip billing.
• Driver allowance management: Per diem, food allowance, and accommodation allowance for multi-day outstation drivers — calculated automatically based on trip duration and zone.

Multi-city operations:

• City-wise zone configuration: Separate zone maps, pricing configurations, and vehicle categories per city. A Mumbai trip and a Pune trip have completely independent pricing while managed from the same Super Admin console.
• City-wise vendor management: Different vendors operate in different cities — trip bookings automatically routed to vendors registered in the pickup city. Cross-city vendor assignment configurable for outstation trips.
• City-wise SLA configuration: Different SLA standards for different cities — metro cities typically have tighter SLAs than Tier 2 cities. Configurable per city or per corporate client-city combination.
• City expansion without new deployment: Adding a new city to the platform is a configuration exercise in the Super Admin console — new zones drawn, new vendors onboarded, city activated. No code deployment required for city expansion.

Airport transfer management:

• Flight number integration — trip scheduling linked to flight arrival time, with automatic trip time adjustment if flight is delayed (via flight status API integration)
• Meet-and-greet workflow — driver checks in at arrivals hall, triggers notification to passenger with driver location and signage instruction
• Terminal zone configuration — specific pickup zones per terminal, airport-specific pricing rules

Driver onboarding on the Enterprise Cab Platform is a fully digital, multi-step process that eliminates paper documentation while maintaining compliance with regional transport regulations.

Driver onboarding flow:

1. Vendor-initiated or self-registration: Driver is invited by their Vendor (fleet owner) via SMS link, or self-registers via the PWA if the operator enables self-registration.
2. Profile creation: Name, mobile number (OTP verified), date of birth, permanent address, emergency contact.
3. Document upload: Driver's licence (front and back image), vehicle RC (Registration Certificate), vehicle insurance policy, PUC (Pollution Under Control) certificate, state-specific permits if applicable.
4. Automated document validation: OCR extraction of document details (licence number, expiry date, vehicle number from RC) — matched against profile. Integration with Aadhaar verification API and DigiLocker for document authenticity.
5. Background check: Integration with third-party background verification API (e.g., AuthBridge, HireRight) for criminal record and licence validity check — automated with result pushed back to platform.
6. Profile review: Vendor reviews and approves the driver profile. Super Admin can configure whether Vendor approval is sufficient or Super Admin must also verify.
7. App activation: Approved driver receives PWA access link and native app download link. First login activates the driver in the dispatch pool.
8. Selfie verification: At each shift start, driver completes a facial recognition selfie — compared against the profile photo to prevent proxy driving.

Document expiry management:

• All document expiry dates captured at upload — system tracks expiry for every document
• Automated expiry alerts: 30 days, 15 days, 7 days before expiry — to driver and to Vendor
• Expired document = automatic deactivation from dispatch pool. Driver cannot receive new trip assignments until renewed document is uploaded and approved.
• Vehicle insurance expiry tracked separately per vehicle — vehicle with expired insurance is automatically removed from available fleet

Training and onboarding content:

• Embedded video training module in driver app — platform usage tutorial, customer interaction guidelines, safety procedures
• In-app quiz after training — minimum score required for dispatch activation
• Onboarding completion tracked per driver — incomplete onboarding prevents dispatch activation

Safety and emergency features on the Enterprise Cab Platform are customisable to the operator's specific safety protocols and regulatory requirements — particularly important for corporate clients with stringent duty-of-care obligations for employee travel.

Driver-side safety features:

• SOS emergency button: Prominent button in driver app — single tap triggers: real-time GPS alert to Super Admin and Vendor with driver location, automated SMS with live tracking link to driver's emergency contact, escalation to corporate client's security operations centre via API webhook (for enterprise clients with SOCs)
• Trip duration monitoring: If a trip exceeds its estimated duration by a configurable percentage without reaching the drop location — automated alert triggers to dispatcher
• Route deviation alert: If driver deviates significantly from the planned route — automated alert to corporate coordinator with current GPS location
• Night shift additional verification: For trips between midnight and 5 AM — configurable additional OTP verification step and mandatory check-in call protocol

Passenger-side safety features:

• Live trip sharing: Passenger can share a live trip tracking link with any contact — recipient can monitor the vehicle position in real time via browser without needing the app
• Driver verification: Passenger sees driver photo, vehicle number, and vehicle make before confirming trip start — verified via OTP that driver must receive from the passenger (not the app-generated one)
• Emergency contact notification: Corporate coordinator automatically notified if trip starts late or vehicle reaches drop zone without trip completion
• Journey replay: Full GPS path of every trip stored and replayable — available to Super Admin and Corporate Admin for investigation of safety incidents or disputes

Compliance features:

• POSH Act compliance — female employee after-hours travel protocols with mandatory confirmation workflow
• Corporate travel policy enforcement — no trip outside approved hours or approved zones without coordinator override
• Audit trail — every action on the platform (booking creation, modification, cancellation, dispatch decision, escalation) logged with user, timestamp, and IP address

PrecisionTech deploys the Enterprise Cab Platform in any deployment model that suits the client's infrastructure preferences, data sovereignty requirements, and IT governance policies. Unlike SaaS vendors who exclusively offer shared cloud infrastructure, we provide full deployment flexibility.

1. Public Cloud Deployment (most common):

• AWS, Microsoft Azure, or Google Cloud Platform — client's preferred cloud provider
• Infrastructure in the client's own cloud account (client-managed infrastructure) OR in PrecisionTech's managed cloud account (PrecisionTech operates the infrastructure)
• Region selection based on data residency requirements: AWS Mumbai / ap-south-1 for India data residency; UAE North for GCC
• Infrastructure as Code (Terraform) — reproducible, version-controlled infrastructure definition owned by the client

2. On-Premises / Private Cloud Deployment:

• Platform deployed on the client's own data centre infrastructure — bare metal servers, VMware vSphere, OpenShift
• Full source code delivered to client — client owns and operates the infrastructure independently after deployment
• Suitable for government or defence clients with strict data sovereignty requirements, or enterprises with existing data centre investments they wish to utilise

3. Hybrid Deployment:

• Sensitive data (PII, financial records) stored on on-premises or private cloud infrastructure
• Compute-intensive workloads (AI dispatch engine, GPS processing, analytics) run on public cloud for elasticity
• Data synchronisation between environments via encrypted private link (AWS Direct Connect, Azure ExpressRoute)

Source code ownership:

• Complete source code delivered to the client at project completion — no vendor lock-in, no perpetual licensing dependency
• Client can maintain, modify, and extend the platform independently using their own development team or any third-party vendor after delivery
• PrecisionTech provides optional Annual Maintenance Contract (AMC) for ongoing support, security updates, and feature enhancements

Support and SLA post-deployment:

• Standard AMC: 9×5 support, 4-hour critical bug response SLA, quarterly security patch deployment
• Premium AMC: 24×7 support, 1-hour critical incident response SLA, monthly security updates, dedicated account manager
• All support through the PrecisionTech helpdesk system — no phone numbers on the platform, support requests via ticketing system and contact portal

PrecisionTech follows a structured agile delivery process for Enterprise Cab Platform implementations — combining comprehensive discovery and architecture phases with iterative sprint-based development that keeps the client visible and in control throughout.

Phase 1 — Discovery & Architecture (Weeks 1–3):

• Business requirements workshop — stakeholders from operations, technology, finance, and corporate clients map all workflows, user journeys, pricing models, integration requirements, and compliance obligations
• Technical architecture document — database schema design, API architecture, integration blueprint, infrastructure plan, security design
• UI/UX wireframes — all interface screens wireframed and client-approved before development begins
• Project scope document and delivery timeline signed off by client

Phase 2 — Core Platform Development (Weeks 4–14 for standard scope):

• Sprint 1–2: Infrastructure setup (cloud, CI/CD, environments), database schema, authentication system, Super Admin core
• Sprint 3–4: Corporate Admin module, user management, booking engine (web)
• Sprint 5–6: Driver PWA + native app, GPS telematics pipeline, live map
• Sprint 7–8: Dispatch engine (manual + AI), Vendor portal
• Sprint 9–10: Billing engine, payment gateway integration, invoice generation
• Weekly sprint demo — client reviews completed features at end of each sprint. Feedback incorporated in subsequent sprint.

Phase 3 — Integration & Customisation (Weeks 14–18):

• API integrations (GDS, ERP, payment gateways, SMS, WhatsApp)
• Custom modules specific to client's business requirements
• White-label branding for all interfaces and mobile apps

Phase 4 — QA, UAT & Launch (Weeks 18–22):

• Comprehensive QA — functional testing, load testing (simulating 1,000+ concurrent users, 5,000+ GPS events/second), security penetration testing
• User Acceptance Testing — client's internal team tests all workflows against documented requirements
• Soft launch — limited user group (e.g., 50 drivers, 5 corporate clients) for real-world validation
• Full launch — platform opened to all users with 24×7 monitoring for launch week

Reference timelines (standard scope):

• MVP (core booking, dispatch, driver PWA, basic billing): 14–16 weeks
• Full enterprise suite (all modules, GDS + ERP integration, native apps): 20–26 weeks
• International deployment (multi-currency, multi-language, regional compliance): add 4–6 weeks

In a market filled with cab tech startups offering template-based platforms and SaaS subscriptions, PrecisionTech's 30 years of enterprise technology heritage — since 1994, serving thousands of global clients across India, the GCC, the UK, and Southeast Asia — creates fundamentally different outcomes for cab platform clients.

1. Architectural decisions that survive at scale:

• Startups optimise for launch speed — they build for 100 drivers and 10 corporate clients. When the platform scales to 5,000 drivers and 200 corporate clients, the architecture breaks and expensive re-engineering is required.
• PrecisionTech's engineers have built systems at enterprise scale for three decades. Our GPS telematics pipeline, multi-tenant architecture, and dispatch engine are designed for 10x your launch-day scale from Day 1 — because we have seen what scale stress does to under-engineered systems.

2. Cross-domain portfolio advantage:

• Our portfolio spans cloud (AWS, Azure, GCP), ERP (Tally, SAP integrations), payment gateways (12+ integrations in production), cybersecurity (ISO 27001 certifications), and mobility software — we have deep integration expertise across every system category that a cab platform needs to connect to. Newer vendors claim they can integrate — we have done it, documented it, and debugged the edge cases across hundreds of deployments.

3. International deployment experience:

• We have built localised platforms for UAE, Saudi Arabia, UK, and Southeast Asia — handling Arabic RTL UI, GCC payment gateways (Telr, PayFort), UAE and KSA transport regulation compliance, and multi-currency multi-entity billing. Most Indian cab tech vendors cannot claim international production deployments.

4. Source code delivery and true ownership:

• SaaS vendors retain your platform. If they raise prices, change terms, or shut down — your business is disrupted. PrecisionTech delivers source code — you own the platform unconditionally. Our 30-year client relationships are built on this trust model.

5. Financial stability and continuity:

• A cab platform is a decade-long investment. You need a technology partner that will exist in 10 years. PrecisionTech has been in business for 30 years — not a venture-funded startup on a runway countdown. Our clients' platforms are not at risk from a Series B funding failure.

Post-deployment support for the Enterprise Cab Platform is available through PrecisionTech's structured Annual Maintenance Contract (AMC) programme — providing peace of mind for operators who need a reliable technology partner for the long term.

Standard AMC (included in first year, renewable annually):

• Bug fixes: Critical bugs (system unavailable, booking engine non-functional, payment processing failure): 4-hour response, same-day fix deployment. High-priority bugs (feature malfunction, data display error): 24-hour fix deployment. Medium-priority bugs: 72-hour fix deployment.
• Security patches: Quarterly security dependency updates — OS patches, framework updates, dependency vulnerability remediations. Immediate patch for critical CVEs (CVSS 9.0+).
• Payment gateway updates: Payment gateway API version updates deployed as released by gateway providers — ensuring continuous payment processing capability.
• Monitoring and alerts: 24×7 infrastructure monitoring — uptime alerts, performance degradation alerts, error rate spike alerts. Incident response within SLA without client needing to raise a ticket.

Premium AMC:

• All Standard AMC inclusions plus: 24×7 support, 1-hour critical incident response, dedicated account manager, monthly security audit, priority feature development slot

Feature enhancement engagements:

• Post-delivery feature additions are scoped and quoted as separate development engagements — clear scope, clear timeline, clear pricing
• Annual platform roadmap review: PrecisionTech presents emerging technology enhancements (new AI dispatch capabilities, new integration options, new regulatory compliance features) to AMC clients — client selects items for their roadmap

Knowledge transfer:

• Complete technical documentation delivered at project end — architecture document, API documentation (OpenAPI/Swagger spec), database schema documentation, deployment runbook, and operations guide
• Admin training — Super Admin team trained on all configuration, reporting, and management functions
• Developer training — client's development team trained on codebase structure, development environment setup, and deployment procedures. Client can independently maintain and extend the platform after training.

All support requests handled via PrecisionTech's helpdesk portal — contact page for all support, sales, and technical enquiries. No phone numbers. Your ticket is handled by the engineering team that built your platform.