Project Description
The objective of this project is to build a centralized dashboard system with integrated hardware communication, analytics, campaign management, and monetization capabilities.
This platform will serve:
Fleet operators
Advertisers
Government agencies
Internal admin teams
2. Project Scope
The development includes:
Web-based Admin Dashboard
Cloud-based Content Management System (CMS)
Edge Device Integration (vehicle-level hardware)
Real-time data ingestion & analytics
API integrations for GPS, media delivery, and reporting
3. Core Modules (MANDATORY)
3.1 Live Fleet Management Module
Features:
Real-time GPS tracking of all vehicles
Status indicators:
Active / Idle / Offline
Live map visualization (Google Maps / Mapbox)
Vehicle-level details:
Bus ID
Route
Speed
Device health
Alerts & notifications:
Device offline
Connectivity issues
3.2 Campaign Management System (CMS)
Features:
Campaign creation workflow:
Campaign name
Advertiser details
Creative upload (image/video formats)
Route-based targeting:
Assign campaigns to specific routes/regions
Time-based scheduling:
Dayparting (morning/evening/night)
Multi-display control:
Window displays
Rear panels
Emergency door displays
Campaign status tracking:
Active / Scheduled / Completed
3.3 Content Delivery & Edge Integration
Requirements:
Integration with vehicle-mounted edge devices
Secure content transmission (API-based)
Offline caching capability
Sync mechanism:
Cloud → Edge device
Edge → Cloud (logs & telemetry)
Device control:
Remote reboot
Display ON/OFF
Emergency override (critical for door display system)
3.4 Analytics & Reporting Module
Features:
Real-time dashboards:
Impressions (estimated)
Reach
Frequency
Route-wise analytics
Campaign performance tracking
Heatmaps (geo-performance)
Device uptime reports
Exportable reports (PDF/Excel)
3.5 Revenue & Billing Module
Features:
Revenue tracking:
Per campaign
Per vehicle
Advertiser billing system:
Invoice generation
Payment status tracking
Pricing logic:
Route-based pricing
Time-slot pricing
Dashboard metrics:
Total revenue
Monthly revenue
Revenue per bus
3.6 User Management & Access Control
Roles:
Super Admin
Operator (Fleet Owner)
Advertiser
Government User (restricted)
Features:
Role-based access control (RBAC)
Login & authentication (JWT / OAuth)
Activity logs
3.7 Emergency System Integration (CRITICAL)
This is a key innovation and must be handled carefully.
Requirements:
Emergency door display control
Automatic display shutdown on emergency trigger
Manual override from dashboard
Fail-safe communication with edge device
3.8 Notification & Alert System
Channels:
Email
SMS (optional)
Dashboard alerts
Triggers:
Device offline
Campaign errors
System failures
4. Technical Requirements
Frontend
React.js / Next.js
Tailwind CSS or equivalent
Responsive design
Backend
Node.js / Python (preferred scalable architecture)
REST / GraphQL APIs
Database
PostgreSQL / MongoDB
Cloud
AWS / GCP / Azure
Realtime
WebSockets / Firebase / PubSub
5. Integration Requirements
GPS APIs (hardware-based or third-party)
Map services (Google Maps / Mapbox)
Payment gateway (Razorpay / Stripe)
Media storage (AWS S3 or equivalent)
Edge device APIs (custom)
6. Performance Requirements
Handle 10,000+ vehicles (scalable architecture)
Real-time updates (<2 sec latency preferred)
High availability (99.9% uptime)
7. Security Requirements
End-to-end data encryption
Secure API authentication
Role-based data access
Device-level authentication
8. Deliverables
Fully functional dashboard (web app)
Admin panel
API documentation
Deployment setup (cloud)
Source code access
Testing & QA reports
9. Timeline Expectation
Phase 1 (MVP): 6–8 weeks
Phase 2 (Full System): 10–14 weeks
10. Proposal Requirements
The development company must provide:
Technical architecture plan
Timeline & milestones
Cost estimation
Team structure
Relevant experience (IoT / dashboards / ad-tech preferred)