Voltimax IoT Platform - Roadmap
Project Overview
Voltimax IoT Platform is a comprehensive energy management and IoT device integration platform for:
- Device management (batteries, inverters, EV chargers, solar systems, meters)
- Real-time telemetry collection and analytics
- Energy optimization using price-based and solar forecasting algorithms
- Protocol integration (OCPP 2.1, SunSpec, Modbus, MQTT)
- Multi-tenant SaaS with edge gateway components
Current Version: 1.0-beta Tech Stack: .NET 10, ASP.NET Core, PostgreSQL, Elasticsearch, Azure (Functions, Service Bus, Blob), Vue.js
Note: TimescaleDB was evaluated but not adopted - Elasticsearch provides sufficient time-series capabilities for current needs.
Visual Timeline
Current State Assessment
Platform (Backend/API) - Completed
- Core REST API with OpenAPI/Scalar documentation
- Entity Framework Core data access layer
- Metrics ingestion and Elasticsearch storage
- EPEX Spot price integration
- Solar forecasting services (PVGIS, Quartz Solar)
- Energy Advisor rules-based evaluation engine
- Multi-tenant architecture with Keycloak
- Azure Functions for background processing (pricing ingestion, telemetry processing)
- OpenTelemetry + Elastic APM observability
- Gateway bidirectional communication (MQTT/HTTP via Azure Service Bus)
For detailed platform roadmap, see Platform (Backend/API).
Frontend (Vue.js) - In Progress
- Basic application structure
- TypeScript SDK (auto-generated from OpenAPI)
- E2E testing with Playwright
- VitePress documentation site
For detailed frontend roadmap, see Frontend (Vue.js).
Gateway (Edge) - Completed
- Modbus TCP/RTU protocol handler
- HTTP control interface
- OCPP 2.1 protocol support
- Local persistence and buffering
- Command execution engine
- Simulation mode for testing
- Strategy Framework with IStrategy interface, AbstractStrategy base, StrategyFactory
- Implemented Strategies: NetZero (PID control), Charge, Discharge, Null
For detailed gateway roadmap, see Gateway (Edge).
Roadmap Sections
Detailed roadmap information is organized into the following documents:
- Platform (Backend/API) - API stabilization, data services, external integrations
- Frontend (Vue.js) - Energy advisory UI, asset management, gateway management, administration
- Gateway (Edge) - Strategy expansion, protocol & control, fleet management
- Documentation - Core documentation, developer documentation
- Future Considerations - Deferred features and review triggers
- Technical Debt & Testing - Code quality, testing gaps, maintenance
- CI/CD & DevOps - Pipeline infrastructure, deployment, security
Cross-Phase Dependencies
Understanding dependencies across phases helps coordinate parallel work and avoid blockers:
Platform > Frontend Dependencies
| Frontend Phase | Depends On | Rationale |
|---|---|---|
| F1 (Energy Advisory UI) | P2 (Energy consumption forecasting) | Dashboard requires forecasting data for optimization views |
| F1 (Price-based optimization) | P3 (EPEX pricing - completed) | Requires day-ahead and intraday pricing data |
| F3 (Gateway Management UI) | G3 (Configuration sync) | UI needs backend API for pushing config changes |
| F4 (Audit log viewer) | P1 (Audit logging) | Requires audit data to be captured and queryable |
Platform > Gateway Dependencies
| Gateway Phase | Depends On | Rationale |
|---|---|---|
| G1 (TimeOfUseStrategy) | P3 (Tariff configuration API - not yet implemented) | Strategy needs tariff schedules for optimization |
| G1 (ArbitrageStrategy) | P3 (EPEX pricing - completed) | Requires real-time spot market prices |
| G3 (Bidirectional communication) | P1 (Platform API command endpoints - not yet implemented) | API must expose gateway command endpoints |
| G3 (Configuration sync) | P1 (Audit logging) | Config changes must be audited for compliance |
Gateway > Frontend Dependencies
| Frontend Phase | Depends On | Rationale |
|---|---|---|
| F1 (Battery steering controls) | G1 (Strategy implementations) | UI controls for selecting and configuring strategies |
| F3 (Gateway detail view) | G2 (Safety interlocks, offline mode) | Display gateway capabilities and operational status |
External Dependencies
| Phase | External Blocker | Impact |
|---|---|---|
| P3 (IEC 61850 support) | Library licensing decision (€10k-50k) | Blocks utility substation integration |
| P3 (Carbon tracking) | Third-party API selection | Delays grid carbon intensity features |
| P2 (Energy forecasting) | Historical data accumulation (3+ months) | Cannot validate accuracy until sufficient data exists |
| G2 (Safety interlocks) | Battery specification database | Requires complete specs for all supported battery models |
Notes
- Roadmap priorities may shift based on customer feedback
- Each phase includes corresponding documentation updates
- Security reviews required before each major release
- Gateway phases may run in parallel with Platform/Frontend
- Consider community feedback for protocol prioritization
- All strategies must be simple and deterministic (no ML/AI in control loops)