Brand Name: Transvia Product Type: Multi-Tenant SaaS Marketplace for Corporate Transportation

PROJECT NAME
Transvia

Transvia is the official name of the platform.
All references in code, documentation, repositories, environments, and design assets should use the name "Transvia".

Examples:
- transvia-api
- transvia-admin
- transvia-driver-app
- transvia-passenger-app
- Transvia Dashboard
- Transvia AI Engine

(Built using Fleetbase as the core fleet & tracking system)

────────────────────────────────────────
1. PROJECT OVERVIEW
────────────────────────────────────────

This project is NOT a sellable product but a SaaS MARKETPLACE platform that connects:

• Transport Companies (fleet owners with vehicles + drivers)
• Corporate Clients (companies needing daily employee transportation)
• Drivers
• Passengers (employees)

The platform acts as a neutral intermediary.
All contracts are signed:
- Between the Platform and Transport Companies
- Between the Platform and Corporate Clients

There is NO direct contract between Transport Company and Corporate Client.

The platform operates globally (not country-specific) and must be scalable, multi-language, and multi-currency.

────────────────────────────────────────
2. CORE BUSINESS MODEL
────────────────────────────────────────

• SaaS monthly subscriptions (Transport Companies & Corporate Clients)
• Platform fees applied per contract
• Commission embedded in vehicle rental price
• VAT applied automatically
• No price increase compared to traditional market pricing

Transport companies list vehicles at their normal market price.
Corporate clients see competitive or lower prices.
Platform revenue is generated via:
- Platform fees
- Subscription plans
- Contract handling fees
- Value-added services (AI analytics, reports)

Contracts can be:
• Monthly
• Quarterly
• Semi-Annual
• Annual

Contracts cannot be canceled unilaterally by either company.
Only the platform controls contract lifecycle.

────────────────────────────────────────
3. USER ROLES
────────────────────────────────────────

• Super Admin (Platform Owner)
• Transport Company Admin
• Corporate Client Admin
• Driver
• Passenger

Each role has strictly isolated data access.

────────────────────────────────────────
4. CORE SYSTEM – FLEETBASE
────────────────────────────────────────

Fleetbase is used as the core fleet system for:

• Vehicle management
• Driver management
• GPS tracking
• Routes & trips
• Geofencing (pickup/drop-off points)

Fleetbase must be extended (custom modules) for:
• Passenger attendance
• Contract-based trip assignment
• Multi-company SaaS isolation
• AI analytics integration

Fleetbase is the single source of truth for movement data.

────────────────────────────────────────
5. DASHBOARDS
────────────────────────────────────────

### A) Super Admin Dashboard (Platform Owner)

• Global map of all companies
• Company icons/logos on map
• Click company → view all vehicles & routes
• Revenue analytics
• Contract management
• Subscription management
• AI system control
• VAT & invoicing overview
• Payment gateway control
• Audit logs

---

### B) Transport Company Dashboard

• Live map of own vehicles
• Vehicle & driver list
• Assign drivers to vehicles
• Driver performance metrics
• Delay analysis (traffic / passenger / vehicle)
• Contract-linked income
• Monthly reports
• Vehicle health insights

---

### C) Corporate Client Dashboard

• Live map of contracted vehicles
• Employee attendance reports
• Route performance
• Delay statistics
• Monthly & yearly reports
• AI-based recommendations (for large companies)
• Exportable reports (PDF / Excel)

────────────────────────────────────────
6. MOBILE APPLICATIONS
────────────────────────────────────────

### A) Driver App

• Live GPS tracking (Fleetbase)
• Route visualization
• Expected vs actual time
• Passenger list per trip

At each pickup point:
A popup automatically appears with passenger info:
• Photo
• Full name

Driver must select ONE option only:
• Arrived on time
• Waiting
• Not at pickup point
• Delayed by X minutes

Additional features:
• Passenger contact & chat
• Incident reporting
• Offline tolerance

---

### B) Passenger App

• Live vehicle map
• Route & all pickup points
• Vehicle photo & driver photo
• Notification when vehicle approaches
• Button: “I am at pickup point”
• Trip history
• Profile management
• Driver rating

Passenger receives notification showing what the driver recorded
(on time / delayed / absent).

────────────────────────────────────────
7. ATTENDANCE & STATUS LOGIC
────────────────────────────────────────

• Attendance is recorded per passenger per trip
• Data is immutable after confirmation
• Used for:
- Reports
- AI analysis
- Company evaluations
• Presence / absence / delay is visible to:
- Corporate client
- Transport company
- Platform admin

────────────────────────────────────────
8. AI & ANALYTICS ENGINE
────────────────────────────────────────

### Input Data
• GPS tracks
• Trip durations
• Driver behavior
• Passenger attendance
• Vehicle reliability
• Route congestion
• Historical performance

### AI Outputs
• Driver performance score
• Vehicle reliability score
• Route efficiency score
• Transport company ranking
• Delay prediction
• Contract optimization suggestions

### Special Logic
• Large corporate clients receive AI-recommended transport companies
• Small companies choose manually
• AI explains recommendations transparently

────────────────────────────────────────
9. CONTRACT & PRICING LOGIC
────────────────────────────────────────

• Transport company sets base vehicle price
• Platform adds:
- Platform fee
- VAT
- Optional displayed discount
• Corporate client sees final price
• Platform margin handled internally

Supports:
• Single vehicle contracts
• Multi-vehicle contracts (e.g. 30 vehicles)
• Consolidated invoicing

────────────────────────────────────────
10. PAYMENTS & BILLING (SaaS)
────────────────────────────────────────

Supported gateways:
• Stripe (subscriptions, cards)
• PayPal (international)
• CMI (local corporate payments)

Use cases:
• SaaS subscriptions
• Contract payments
• Multi-vehicle invoices

Features:
• Auto-renewal
• Grace periods
• Invoicing
• Internal ledger
• VAT handling
• Webhooks for payment status

────────────────────────────────────────
11. SECURITY & COMPLIANCE
────────────────────────────────────────

• Role-based access control
• Company-level data isolation
• Encrypted sensitive data
• Payment PCI compliance
• Full audit logs

────────────────────────────────────────
12. RECOMMENDED TECH STACK
────────────────────────────────────────

### Backend
• Node.js (NestJS) OR Laravel
• REST + WebSockets
• PostgreSQL
• Redis

### Fleet Core
• Fleetbase (extended via plugins)

### Frontend (Web Dashboards)
• React.js or Next.js
• Tailwind CSS
• Mapbox or OpenStreetMap

### Mobile Apps
• Flutter (preferred) OR React Native

### AI & Analytics
• Python
• FastAPI
• Pandas
• Scikit-learn / TensorFlow (later phase)

### Payments
• Stripe SDK
• PayPal SDK
• CMI API

### DevOps
• Docker
• CI/CD
• Cloud hosting (AWS / GCP / Azure)

### Design
• Figma (mandatory)
• Design System
• UX focused on minimal interaction

────────────────────────────────────────
13. PROJECT EXPECTATIONS
────────────────────────────────────────

The developer/team is expected to:
• Analyze feasibility
• Propose final architecture
• Estimate cost & timeline
• Respect scalability & SaaS best practices
• Deliver clean, documented code

This document represents the full scope and vision of the project.