Cross-Platform EV Charging Locator

Заказчик: AI | Опубликовано: 22.02.2026
Бюджет: 10000 $

PRODUCT REQUIREMENTS DOCUMENT (PRD) Fleet Depot Charge Point Management & Energy Orchestration Platform Version: 1.0 Owner: Founder / Product Lead Market: Europe (initial focus) Target users: Fleet operators, depot managers, charge point operators, logistics companies, municipalities --- 1. PRODUCT VISION Build the most advanced Charge Point Management and Depot Energy Orchestration platform for commercial electric fleets (buses, eHGVs, eLCVs). The platform will guarantee vehicle readiness, optimise depot energy usage, autonomously manage charging infrastructure, and support multi-operator commercial charging with integrated payments and settlement. This system becomes the central intelligence layer for electric fleet depots. --- 2. PRODUCT OBJECTIVES Primary objectives 1. Ensure all fleet vehicles reach required SoC before scheduled departure. 2. Optimise depot energy usage within grid constraints and tariffs. 3. Enable third-party/subcontractor charging with billing and settlement. 4. Provide hardware-agnostic CPMS supporting multiple charger manufacturers. 5. Automatically detect and resolve charger faults. 6. Meet EU regulatory and billing requirements. 7. Provide enterprise-grade reliability and scalability. Success metrics (KPIs) - ≥99.5% charger uptime - ≥98% vehicle readiness achieved - ≤5% manual intervention for charger faults - Energy cost reduction vs unmanaged charging ≥20% - System availability ≥99.9% --- 3. USER TYPES Fleet Operator - Owns vehicles - Needs readiness guarantee - Needs cost optimisation - Needs reporting and billing Depot Manager - Monitors chargers and energy usage - Handles exceptions - Manages subcontractors Subcontractor / Third-Party Fleet - Uses depot charging - Pays per session or contract - Requires access control System Admin - Configures system - Manages integrations - Maintains platform --- 4. CORE PRODUCT MODULES 4.1 Charger & Hardware Management (CPMS Core) Requirements - Support OCPP 1.6J minimum - OCPP 2.0.1 readiness - Multi-vendor charger support - Real-time status monitoring - Remote control of chargers - Firmware management - Diagnostics and logs Features - Charger onboarding workflow - Connector-level monitoring - Charging session tracking - Meter value ingestion - Smart charging profiles - Remote start/stop - Availability control Fault commands supported - Reset (soft/hard) - Unlock connector - Change availability - Clear cache - Trigger diagnostics - Firmware update --- 4.2 Depot Energy Orchestration Engine Purpose Optimise energy usage while guaranteeing vehicle readiness. Inputs - Grid capacity limit - Charger capacity - Vehicle battery size - Current SoC - Target SoC - Departure time - Tariffs (time-of-use) - PV/BESS data (optional) - Weather data (optional) Outputs - Charging schedules per vehicle - Power allocation per charger - Readiness risk score - Cost optimisation plan Capabilities - Dynamic load balancing - Peak shaving - Cost optimisation - Priority charging logic - Rolling optimisation every 1–5 minutes - Event-driven recalculation Readiness engine System must ensure: Vehicle SoC ≥ required SoC by departure time If not achievable: - Alert operator - Suggest reassignment - Prioritise vehicle --- 4.3 Fleet & Scheduling Integration Required integrations - Fleet management systems - Dispatch systems - Telematics providers - Route planning tools Data exchange - Vehicle ID - Battery capacity - Route assignment - Departure time - Required SoC - Vehicle arrival time Features - Automatic charger assignment - Readiness dashboard - Predictive energy demand - Vehicle swap suggestions - API-first architecture --- 4.4 Subcontractor Charging & Payments Access methods - RFID - Mobile app token - QR code - Contract ID - Optional roaming (OCPI-ready) Pricing models - kWh pricing - Time-based pricing - Session fee - Idle fee - Subscription - Dynamic pricing Payment methods - Credit/debit card - Mobile wallets - Invoice billing - Account balance - RFID billing Finance features - Automated invoicing - VAT handling per EU country - Revenue split between operators - Settlement reporting - Export to ERP/accounting Compliance - PSD2/SCA via PSP - MID-compatible metering - GDPR data handling --- 4.5 Autonomous Fault Detection & Self-Healing Detection System must detect: - Charger offline - Connector locked - Session failure - Power anomalies - Communication loss - Meter faults Automated resolution System attempts automatically: 1. Reconnect 2. Soft reset 3. Hard reset 4. Unlock connector 5. Reconfigure charger 6. Firmware push 7. Reassign vehicles Escalation If unresolved: - Create incident - Notify operator - Log diagnostics Learning capability - Track success of fixes - Identify recurring failures - Predict future faults --- 4.6 Operator Control Tower (Dashboard) Depot view - Live grid load - Total charging power - Charger status map - Active sessions - Cost per hour Fleet readiness board - Vehicle SoC - Target SoC - Departure countdown - Risk indicator (green/amber/red) Maintenance panel - Fault alerts - Automation attempts - Firmware status - Service logs --- 4.7 Reporting & Analytics Required reports - Energy usage per depot - Cost per vehicle - Charger uptime - Fault frequency - Revenue from subcontractors - CO₂ reporting (optional) Export formats - CSV - API - ERP integration --- 5. NON-FUNCTIONAL REQUIREMENTS Performance - Support 10,000+ chargers - Real-time telemetry processing - <2 second dashboard updates - Scalable multi-depot support Reliability - 99.9% uptime target - Offline charger tolerance - Data buffering and recovery Security - TLS encryption - Role-based access control - Audit logs - Secure API authentication - Penetration-test ready Compliance - GDPR by design - Data retention policies - VAT compliance EU - MID meter compatibility - AFIR-ready architecture --- 6. SYSTEM ARCHITECTURE REQUIREMENTS Backend - Microservices or modular monolith - REST API + webhooks - Event-driven architecture - High availability deployment Data - Relational DB for core data - Time-series DB for telemetry - Secure object storage for logs Infrastructure - Cloud-native deployment - Containerised services - CI/CD pipelines - Monitoring & observability --- 7. INTEGRATIONS REQUIRED Must support - Fleet management APIs - Telematics providers - Payment gateways - ERP/accounting systems - Energy providers - Smart grid APIs (future) --- 8. MVP SCOPE Phase 1: - OCPP charger management - Basic energy optimisation - Fleet schedule integration - Readiness dashboard - Manual payments/invoicing Phase 2: - Autonomous fault recovery - Advanced optimisation - Subcontractor billing - Settlement automation Phase 3: - AI prediction - Cross-depot optimisation - Energy trading integration - V2G readiness --- 9. SUCCESS CRITERIA FOR DELIVERY The platform is considered successful when: - Fleet vehicles consistently reach required SoC before departure - Depot energy costs are reduced - Charger downtime is minimised through automation - Subcontractor billing works end-to-end - Platform supports multi-depot enterprise fleets --- 10. LONG-TERM PRODUCT POSITIONING This platform will evolve into: A Fleet Energy Operating System (Fleet-EOS) Serving: - Bus depots - Logistics hubs - Municipal fleets - Multi-operator charging depots - European commercial EV infrastructure End goal: Become the core operating platform for electric commercial transport depots across Europe. Once the software is ready we will need a minimum of 3 weeks to test out the product for any issue an bugs and need to be fixed before the release of any payment. Codes to be pass once the project is complete