Model T Pipeline — MT-007 — Predictive Maintenance

E-LITMUS

EV Charger Health Monitoring — Universal Predictive Maintenance for Charging Infrastructure

DATE: 2026-02-14 PROJECT: MT-007 VERTICAL: EV Charging Infrastructure STATUS: Pilot ARCHITECTURE: Edge-First ML

Executive Summary

e-Litmus is a universal health monitoring system for EV charging infrastructure, providing charger-agnostic predictive maintenance across all major brands (ABB, Tritium, Kempower, Alpitronic, etc.).

The platform combines 7-sensor hardware (RF arcing detection, thermal imaging, barometric pressure, current/voltage, CAN/Modbus logging, vibration, environmental) with cloud ML analytics for real-time anomaly detection (4-hour response window) and IGBT degradation trending (weeks-to-months advance warning) R39R40, enabling CPOs to shift from reactive firefighting to planned maintenance. [Karanam & Tal, EVS36, 2023; Nazar et al., PHM Europe 2020]

Value proposition: 25% downtime reduction R12, 30-35% maintenance cost savings R2, and uptime-driven revenue growth. Pilot-ready for Q2 2025 with first 3 CPOs.

25%
Downtime reduction
4-Hour
Anomaly response window
€50-200/mo
Per charger SaaS pricing
7 Sensors
Multi-modal monitoring

The Problem

EV Charger Downtime Crisis

+10%
Revenue opportunity via uptime
-7-10%
OPEX reduction potential
€567K/year
Additional revenue (1000-charger network)
3-4×
ROI Year 1

Charge Point Operators (CPOs) face a critical challenge: unpredictable charger failures that reduce uptime and increase operational costs. Every hour of downtime means lost revenue, frustrated customers, and emergency repair expenses.

The global predictive maintenance market is projected to reach $47.8B by 2029 R1, driven by the urgent need to minimize unplanned downtime across industrial assets. For EV charging infrastructure, this challenge is particularly acute: charger availability directly impacts revenue, as every minute of downtime translates to lost charging sessions.

The Financial Impact of Downtime

For a 1000-charger network:

  • Lost Revenue: Just 2% downtime = €567K/year in missed charging sessions R2
  • Emergency Repairs: Reactive maintenance costs €750-1,650/charger/year R12
  • Customer Churn: Unreliable chargers drive EV drivers to competitors
  • Warranty Disputes: Misdiagnosed failures lead to €115K+ component replacements

According to Siemens' True Cost of Downtime 2024 report R2, unplanned industrial asset failures cost enterprises an average of 11% annual revenue. For CPOs, this translates to millions in lost opportunity.

CPO Operational Challenges

Modern Charge Point Operators manage complex, multi-vendor fleets across distributed locations. Key challenges include:

Why Traditional Monitoring Fails

The Market Gap

CPOs need a universal health monitoring system that works across all charger brands, detects anomalies in real time and trends component degradation weeks-to-months in advance, providing actionable diagnostics — not another billing platform.

According to IoT Analytics State of IoT 2025 R3, only 26% of industrial IoT projects successfully transition from pilot to production due to lack of clear ROI and operational integration. e-Litmus solves this by targeting a single, measurable KPI: uptime-driven revenue growth.

The Solution

Charger-Agnostic Predictive Maintenance

e-Litmus monitors EV charger health through non-invasive sensors and 2-level analytics — no charger manufacturer lock-in.

Inspired by successful predictive maintenance implementations in industrial sectors (see Tractian, Artesis), e-Litmus brings AI-driven asset health monitoring to EV charging infrastructure. Unlike SKF's motor monitoring systems or Sensemore's vibration analytics, e-Litmus is purpose-built for the unique failure modes of DC fast chargers.

€195K → €23K
Year 1 setup → Year 2+ annual cost
Multi-Vendor
Works with ABB, Tritium, Kempower
Weeks-Months
IGBT degradation trending
2-Level
Edge + Cloud analytics

7-Sensor Suite with Full Specifications

Sensor Type Specification What It Detects Typical Failure Mode
Voltage Sensor 0-1000V DC, ±0.5% accuracy, 100 samples/sec Grid voltage stability, power module degradation AC-DC converter failure, grid fluctuations
Current Sensor 0-500A DC, Hall-effect, ±1% accuracy, 100 samples/sec Charging current anomalies, module load imbalance Power module degradation, cable resistance
External Temp/Humidity -40°C to +85°C, ±0.3°C; 0-100% RH, ±2% Ambient environmental conditions, seasonal variations Thermal runaway risk assessment
Internal Temp/Humidity -40°C to +125°C, ±0.3°C; 0-100% RH, ±2% Cabinet thermal health, cooling efficiency Fan failure, blocked air intake, insulation breakdown
Barometric Pressure 300-1100 hPa, ±1 hPa accuracy, 10 samples/sec Cooling system airflow restrictions, filter clogs Air filter blockage (see case study below)
Acoustic MEMS Microphone 20Hz-20kHz, 94dB SPL, digital PDM output Fan speed anomalies, mechanical noise, arcing sounds Bearing wear, fan blade damage, electrical arcing
RF Scanner (RTL-SDR) 24 MHz - 1.7 GHz, 2.56 MSPS sampling Electromagnetic interference (EMI), RF noise from failing components Capacitor failures, arcing, switching noise from degraded IGBTs

Non-Invasive Installation: All sensors mount externally on charger cabinet. No modification to charger internals required. Installation time: 2-4 hours/charger with standard tools. Compatible with all DC fast charger enclosures (IP54/IP55 rated).

Edge Computing Module

e-Litmus uses industrial-grade edge gateways powered by NXP i.MX RT1170 or Infineon AURIX platforms for on-device machine learning inference.

Component Specification
Processor Arm Cortex-M7 @ 1 GHz + Cortex-M4 @ 400 MHz (dual-core)
RAM 2 MB SRAM, 64 MB SDRAM
Storage 16 GB eMMC (local data buffer, 7-day retention)
Connectivity 4G LTE Cat-M1/NB-IoT modem, Ethernet (10/100 Mbps), optional Wi-Fi
Power 12-24V DC input, <5W typical operation
ML Framework TensorFlow Lite for Microcontrollers (TFLite Micro), optimized for edge inference
Operating Temp -40°C to +85°C (industrial grade)

GSM Connectivity

The edge gateway transmits aggregated health metrics via 4G LTE every 10 minutes (configurable: 5-60 min). Data payload: ~2 KB/transmission = ~288 KB/day/charger. Annual bandwidth: ~105 MB/charger (minimal data costs).

Network carriers: Compatible with global LTE networks (Vodafone, T-Mobile, AT&T, etc.). eSIM support for multi-region deployments.

Real Case Study: Air Filter Clog Detection

Incident: DC fast charger (ABB Terra 184) reduced power output to 30% mid-session, stopping vehicle charge at 60% SOC. Customer complained; OEM remote diagnostics blamed vehicle BMS.

e-Litmus Diagnosis (10 minutes before power drop):

  • Barometric Pressure: Dropped from 997.0 hPa (baseline) to 994.0 hPa (abnormal) R23
  • Internal Temperature: Spiked from 25°C to 60°C (cooling failure indicator)
  • Current Sensor: Power modules de-rated to prevent thermal damage (automatic protection mode)
  • Acoustic Sensor: Fan RPM remained constant (fan operational, airflow restricted)

Root Cause: Air filter 80% clogged with dust, restricting airflow to cooling fans. Cabinet pressure differential indicated poor ventilation.

Solution: Dispatched technician with 10-minute filter cleaning procedure. Avoided €115K controller replacement (OEM's initial diagnosis). Charger back online same day.

Impact: Prevented 3-day downtime, saved warranty claim dispute, preserved customer relationship. Total cost: €140 service call vs. €115K+ parts + 72h downtime.

Technology Highlight: 2-Level Analytics

Level 1: Edge Analytics (Per-Charger):

Level 2: Backend Analytics (Fleet-Wide):

Inspired by deep learning approaches for predictive maintenance (Nature Scientific Reports, 2020) R39 and machine learning for industrial asset monitoring (Nature, 2023) R40.

Architecture

VPS-Based Cloud Platform (4-Server Architecture)

e-Litmus deploys on a lean, cost-effective 4-VPS cluster architecture (pilot scale, 1000 chargers), with horizontal scalability to 6-8 VPS for production (10K+ chargers). Inspired by modern cloud-native patterns (see AWS IoT Core architecture), but deployed on VPS infrastructure for cost control and data sovereignty.

VPS Server Services Resources Purpose
VPS-1: Frontend & Gateway
([server-1-ip])
• Nginx (API Gateway + Static files)
• React Web App (bundle)
• Prometheus + Grafana (monitoring)
2 cores, 4 GB RAM, 50 GB SSD Load balancing, TLS termination, user interface, system monitoring
VPS-2: Application Services
([server-2-ip])
• Ingestion Service (Node.js/Python)
• Processing Service (Python ML pipeline)
• Keycloak (OAuth2/JWT authentication)
4 cores, 8 GB RAM, 100 GB SSD Tenant validation, MQTT publishing, LSTM RUL prediction, anomaly classification
VPS-3: Data Layer
([server-3-ip])
• PostgreSQL 15 (Primary)
• Redis 7 (Cache)
• TimescaleDB extension (timeseries optimization)
4 cores, 16 GB RAM, 200 GB SSD Timeseries storage (sensor data, health metrics), session caching, query optimization
VPS-4: Message Broker
([server-4-ip])
• Eclipse Mosquitto 2.0 (MQTT broker)
• AWS IoT Core (roadmap: cloud-native deployment option)
2 cores, 4 GB RAM, 50 GB SSD Lightweight message queue for sensor data (MQTT broker, right-sized for 16 msg/sec @ 1000 chargers)

Total Infrastructure Cost: ~€140-185/month for 4 VPS servers (Hetzner, OVH, or similar providers). Scales to 1000 chargers without additional hardware.

Data Flow Architecture

End-to-End Data Pipeline (10-minute telemetry cycle):

  1. Telemetry Box (edge gateway on charger) → Aggregates 7 sensor readings, runs edge ML (Isolation Forest) → Generates health score + anomaly flags
  2. POST to API → HTTPS POST to api.platform.com/api/v1/ingest with Keycloak JWT token (tenant-specific credentials)
  3. Nginx (VPS-1) → TLS termination, load balancing → Routes to Ingestion Service (VPS-2)
  4. Ingestion Service (VPS-2) → Validates tenant_id from JWT → Parses JSON payload → Publishes to MQTT topic box/sensors/raw
  5. MQTT Broker (VPS-4) → Lightweight message queue (Eclipse Mosquitto 2.0) → Decouples ingestion from processing (right-sized for 16 msg/sec)
  6. Processing Service (VPS-2) → Subscribes to MQTT topics → Runs LSTM RUL prediction, failure classification → Writes to PostgreSQL (VPS-3)
  7. PostgreSQL (VPS-3) → Stores timeseries data (TimescaleDB hypertables), health analytics, alerts → Redis caches recent data for dashboards
  8. React Web App (VPS-1) → Real-time dashboard via WebSocket → Displays fleet health, alerts, RUL predictions

Multi-Tenancy Architecture (Keycloak)

e-Litmus supports multi-tenant SaaS deployment using Keycloak realms for data isolation. Each CPO (Tenant-1: Ionity, Tenant-2: Fastned, Tenant-3: Milence) operates in a separate security realm with dedicated JWT signing keys and database partitions.

Tenant Keycloak Realm Client ID Client Secret Database Partition
Tenant-1 (Ionity) tenant-1 tenant-1-box [client-secret-1] ionity_data (schema)
Tenant-2 (Fastned) tenant-2 tenant-2-box [client-secret-2] fastned_data (schema)
Tenant-3 (Milence) tenant-3 tenant-3-box [client-secret-3] milence_data (schema)

Tenant Isolation Mechanisms:

Firmware Configuration (Edge Gateway)

Each telemetry box is pre-configured with tenant-specific credentials during manufacturing/provisioning:

Python Firmware Config Example (Tenant-1):

KEYCLOAK_CONFIG = {
    "realm": "tenant-1",
    "client_id": "tenant-1-box",
    "client_secret": "[client-secret]",
    "auth_url": "https://api.platform.com/auth/realms/tenant-1/protocol/openid-connect/token",
    "api_endpoint": "https://api.platform.com/api/v1/ingest"
}

# Device sends telemetry every 10 minutes
TELEMETRY_INTERVAL_SEC = 600  # 10 minutes

# Edge ML model (TFLite Micro, runs on NXP i.MX RT1170)
EDGE_ML_MODEL = "isolation_forest_v2.tflite"
ANOMALY_THRESHOLD = 0.85  # 85% confidence for alert trigger
                

Scalability & Performance

Metric Current Capacity (4 VPS) Horizontal Scaling
Devices Supported 1000 chargers Add VPS-5 (PostgreSQL replica) → 2500 chargers
Ingestion Rate 1 POST/sec (600 devices × 10-min intervals) Nginx load balancer → 10 POST/sec (6000 devices)
Database Size ~100 GB/year (1000 chargers, 10-min telemetry, 7-day retention on edge) TimescaleDB compression → 30% reduction, archive old data to S3-compatible storage
Processing Latency Edge: <10ms (on-device), Cloud: <2 sec (ingestion → MQTT → DB) MQTT QoS 1 (at-least-once delivery) → parallel processing across multiple subscribers
Availability 99.5% (single VPS failure tolerated via Nginx failover) PostgreSQL replication → 99.9% (multi-AZ deployment)

Infrastructure Monitoring: Prometheus scrapes metrics from all services (Nginx, MQTT Broker, PostgreSQL, Ingestion/Processing services). Grafana dashboards visualize system health, ingestion rates, processing delays, database performance. Alerts via email/SMS for critical failures.

Security & Compliance

Technology Stack Summary

Layer Technology Documentation
Edge Gateway NXP i.MX RT1170 / Infineon AURIX, TensorFlow Lite Micro NXP i.MX RT1170
API Gateway Nginx 1.24+ (Alpine Linux) Nginx Docs
Ingestion Service Node.js 20 (Express.js) / Python 3.11 (FastAPI) Node.js, FastAPI
Database PostgreSQL 15 + TimescaleDB 2.11 (timeseries extension) PostgreSQL, TimescaleDB
Cache Redis 7 (Alpine Linux) Redis
Message Broker Eclipse Mosquitto 2.0 (MQTT) Mosquitto | MQTT Protocol
Processing Service Python 3.11, scikit-learn, TensorFlow 2.15 (LSTM models) TensorFlow, scikit-learn
Authentication Keycloak 26.4.5 (OAuth2, JWT, multi-tenancy) Keycloak Docs
Frontend React 18.2, TypeScript 5.0, Chart.js (real-time dashboards) React
Monitoring Prometheus 2.45, Grafana 10.0 Prometheus, Grafana

Business Value & ROI

Quantified Benefits

Real Diagnostic Case Study

Incident: "Charger Stopped at 60%" — Avoiding €115K Misdiagnosis

Location: Highway charging hub, ABB Terra 184 DC fast charger (180 kW rated)

Date: July 2024 (e-Litmus pilot deployment)

Timeline of Events

Time Event Diagnosis Source
09:00 Customer arrives, plugs in vehicle (40% SOC, 2023 Tesla Model 3 LR)
09:02 Charging session starts, initial power: 150 kW (normal) OCPP log (charger → CSMS)
09:12 e-Litmus Edge Alert: Barometric pressure anomaly detected (997.0 hPa → 994.0 hPa, -3.0 hPa drop) e-Litmus Edge Gateway (Isolation Forest model, 85% confidence)
09:14 Internal temperature rises: 25°C → 45°C (abnormal for ambient 20°C) e-Litmus Temperature Sensor
09:16 Power output de-rates: 150 kW → 100 kW (thermal protection mode) OCPP log + e-Litmus Current Sensor
09:18 Internal temperature reaches 60°C, power further reduced: 100 kW → 50 kW e-Litmus Temperature + Current Sensors
09:20 Charging session stops (vehicle at 60% SOC). Customer complaints: "Unreliable charger!" Customer feedback + CSMS incident report
09:25 OEM Remote Diagnostics: "No hardware faults detected. Vehicle BMS likely requested power reduction. Customer vehicle issue." ABB remote diagnostic report
09:30 e-Litmus Root Cause Analysis: "Air filter clog detected. Pressure differential indicates restricted airflow. Dispatch technician for filter cleaning." e-Litmus Backend Analytics (multi-sensor correlation: pressure + temp + current)

Sensor Data Analysis

Graph 1: Barometric Pressure (09:00-09:30):

Graph 2: Internal Cabinet Temperature (09:00-09:30):

Graph 3: Charging Current (09:00-09:30):

Graph 4: Acoustic Sensor (Fan Speed Analysis):

Competing Diagnoses

Diagnosis Source Conclusion Recommended Action Cost
Customer "Charger is broken, I want a refund!" Avoid this charging network Lost customer, brand damage
OEM (ABB) "No hardware faults. Vehicle BMS issue." No action (blame vehicle manufacturer) $0, but unresolved issue, customer dissatisfaction
OEM Service (if escalated) "Temperature sensor fault. Replace main controller." Replace entire power controller module €115K parts + labor, 3-day downtime
e-Litmus "Air filter clog. Clean filter, charger fully operational." Dispatch technician, 10-minute filter cleaning €140 service call, same-day resolution

Resolution & Impact

Action Taken (based on e-Litmus diagnosis):

  1. Technician dispatched within 30 minutes (local maintenance crew)
  2. Air filter inspection revealed 80% clog (dust, pollen accumulation over 6 months)
  3. Filter cleaned in 10 minutes (no parts replacement needed)
  4. Charger tested: internal temperature returned to 25°C, full 180 kW power output restored
  5. Customer notified: "Technical issue resolved, free charging voucher as apology"

Financial Impact:

Scenario Cost Downtime Outcome
Without e-Litmus (OEM route) €115K (controller replacement) + €14K (labor, shipping) 72 hours (parts delivery + installation) €130K total cost, 72h revenue loss (€1,400), customer churn
With e-Litmus €140(service call) 30 minutes (diagnostic + resolution) €140total cost, no revenue loss, customer retained
Savings €129,860 + avoided customer churn + warranty claim dispute prevented

Additional Benefits:

Key Insight: Multi-Sensor Correlation

Why e-Litmus succeeded where OEM failed:

  • OEM Dashboard: Only monitors OCPP data (voltage, current, transaction logs) → saw temperature spike, blamed sensor fault
  • e-Litmus: Correlates 7 sensors (pressure + temp + current + acoustic + external temp + humidity + RF) → identified pressure anomaly as root cause, not symptom
  • Machine Learning: Isolation Forest model detected pressure drop 8 minutes before power de-rating → early warning enabled proactive diagnosis

This is the power of charger-agnostic, multi-sensor predictive maintenance.

Competitive Positioning

Unique Value Proposition

"The only charger-agnostic predictive maintenance platform for CPOs, reducing OPEX 7-10% and increasing revenue 10% through uptime optimization. 2-level analytics: edge (per-charger) + backend (fleet-wide benchmarking)."

vs. CSMS Platforms (Hubject, ChargePoint)

vs. Charger OEM Dashboards (ABB Ability, Kempower Cloud)

vs. Generic IoT Platforms

Business Model

Pure SaaS Subscription

e-Litmus operates on a SaaS subscription model with transparent, predictable pricing R8. Year 1 includes hardware deployment, integration, and 12-month SaaS access. Year 2+ is pure software subscription with minimal operational costs.

Year Pricing What's Included Per-Charger Cost
Year 1 €195K (1000 chargers) Hardware setup, integration, training, 12-month SaaS €195/charger
Year 2+ €23K/year Recurring SaaS subscription, platform maintenance, model updates €23/charger/year

Flexible Deployment Options:

Target Customers

ROI Analysis: 1000-Charger Network

Baseline Assumptions (typical CPO with 1000 DC fast chargers):

Parameter Value Source
Fleet Size 1000 DC fast chargers Typical mid-size CPO (Ionity, Fastned scale)
Pricing €0.45/kWh EU average DC fast charging rate
Sessions per charger/month 150 sessions Industry benchmark (high-traffic locations)
Average session energy 35 kWh Typical 20-80% SOC charge on 400V EV
Current uptime 92% CPO industry average (8% downtime from failures, maintenance)
Maintenance cost/charger/year €750-1,650 Industry standard (reactive + scheduled maintenance)

Revenue Impact: +2% Uptime Improvement

e-Litmus predictive maintenance reduces unplanned downtime from 8% to 6% (2% uptime gain) through early failure detection and scheduled repairs.

Metric Before e-Litmus After e-Litmus Impact
Uptime 92% 94% (+2%) +2% utilization
Total sessions/month 150,000 153,000 (+3000) +3000 sessions/month
Additional revenue/month 3000 × 35 kWh × €0.45 = €47,250 +€47.3K/month
Additional revenue/year €567,000/year R1R12

OPEX Impact: -30% Maintenance Cost Reduction

Predictive maintenance shifts repair work from emergency reactive to scheduled proactive, reducing labor costs, parts waste, and unnecessary component replacements.

Cost Category Before e-Litmus After e-Litmus Savings
Maintenance cost/charger/year €750-1,650 €525-1,155 (-30%) €225-495/charger/year
Total maintenance cost/year (1000 chargers) €750K-1,650K €525K-1,155K €225K-495K/year
Emergency call-outs (night/weekend) 120/year @ €460/call = €55K 30/year @ €460/call = €14K (-75%) €41K/year
Unnecessary part replacements €115K/year (avg 1 controller/year misdiagnosed) €0 (root cause diagnostics prevent waste) €115K/year

Conservative OPEX Savings Estimate: €225K-495K/year (excluding emergency call-out savings and parts waste prevention).

Year 1 ROI Calculation

€567K
Additional revenue (+2% uptime)
€220K-500K
Maintenance savings (-30% OPEX)
€805K-1085K
Total Year 1 benefit
€195K
e-Litmus Year 1 cost
Scenario Total Benefit e-Litmus Cost Net Benefit ROI
Conservative €567K + €220K = €787K €195K €592K 3.0×
Optimistic €567K + €500K = €1,067K €195K €872K 4.5×

Payback Period: 3-4 months (assuming conservative scenario). R1R2

Year 2+ Economics

Year 2 and beyond: e-Litmus subscription cost drops to €23K/year (pure SaaS, no hardware costs). Benefits remain constant as long as fleet is maintained.

Year Total Benefit e-Litmus Cost Net Benefit ROI
Year 2 €805K-1,085K €23K €782K-1,062K 35-47×
Year 3 €805K-1,085K €23K €782K-1,062K 35-47×
Year 4 €805K-1,085K €23K €782K-1,062K 35-47×
Year 5 €805K-1,085K €23K €782K-1,062K 35-47×

5-Year Total Net Benefit: €610K (Year 1) + €782K (Year 2) + €782K (Year 3) + €782K (Year 4) + €782K (Year 5) = €3.74M (conservative scenario).

Competitive Pricing Benchmark

Solution Type Typical Pricing Limitations
e-Litmus SaaS PdM €195K Y1 → €23K/year None (charger-agnostic, multi-vendor)
ABB Ability OEM Dashboard Bundled with chargers (no standalone) ABB chargers only, reactive alerts
Kempower Cloud OEM Dashboard €5K-10K/year/site (10-20 chargers) Kempower only, no predictive analytics
Tractian (industrial PdM) Generic IoT $50-100/sensor/month = $600-1200/year Not EV-specific, requires custom integration
Artesis (motor monitoring) Motor PdM $500-1500/motor/year Motors only, not DC chargers

Why e-Litmus Wins on Economics

  • Charger-Agnostic: Works across ABB, Tritium, Kempower, Alpitronic, Delta (no vendor lock-in)
  • Predictive, Not Reactive: Real-time anomaly detection + weeks-to-months degradation trending vs. post-failure alerts
  • Turnkey SaaS: No custom integration, no platform development (vs. generic IoT platforms)
  • Transparent ROI: Measurable uptime/revenue impact (vs. abstract "asset health" metrics)
  • Low TCO: €23/charger/year (Year 2+) vs. €550-1,100/year for industrial IoT sensors

Implementation Roadmap

e-Litmus follows a phased market entry strategy, starting with pilot deployments to validate ROI, then scaling through direct CPO sales, CSMS partnerships, and OEM licensing.

Phase 1: Proto (July 2024 - December 2024)

Objective: Solution prototyping, customer development, first pilot deployment

Milestone Status Details
Solution prototyping ✅ Complete 7-sensor suite finalized, edge gateway tested (NXP i.MX RT1170)
Customer development ✅ Complete Interviews with 15 CPOs, 8 CSMS providers, 5 charger OEMs
First CPO partnership ✅ Signed Zynetic (Norway CPO, 200-charger fleet)
Pilot field installation ✅ Complete 20 chargers deployed (ABB, Tritium, Kempower mix)
Data collection & validation ⏳ In Progress 6-month telemetry collection (Jul-Dec 2024), ROI validation

Key Partners:

Phase 2: MVP (2025)

Objective: Legal incorporation, seed funding, expand pilot deployments, validate commercial model

Milestone Target Date Details
Legal incorporation Q1 2025 Register in Norway (close to pilot customer), establish IP protection
Seed investment Q1 2025 Target: €500K-1M (angels, EV-focused VCs, accelerators)
Active pilots Q2-Q4 2025 Ionity (pan-EU CPO, 500+ chargers)
• Epic Charging (Netherlands CPO, 150 chargers)
• Target: Fastned, Milence, Electra, Charge&Go
Research partnerships Q3 2025 Fraunhofer IAO (Germany), SINTEF (Norway) — joint research on EV infrastructure reliability
Manufacturing setup Q4 2025 First batch production (500 units), CE certification, supplier agreements

Target Customers (Pilot → Commercial):

Phase 3: Traction & Capitalization (2026-2027)

Objective: Commercial deployments, sustainable subscription revenue, platform partnerships, OEM licensing

Revenue Stream Target Details
Direct CPO Sales 10-15 contracts (5000-10000 chargers) Pure SaaS model (€195K Y1 → €23K/year thereafter)
CSMS Platform Partnerships 2-3 integrations Hubject, ChargePoint white-label → revenue share (20-30% of SaaS fee)
OEM Licensing 1-2 charger manufacturers ABB, Tritium, Kempower → built-in predictive maintenance (licensing fee: €45/charger)
Mass Production 5000-10000 units/year Contract manufacturing (Asia), CE + UL certifications complete

Geographic Expansion:

Phase 4: Scaling (2027-2030)

Objective: Sales scaling, Series A funding, M&A exit options

Key Sales Channels

Channel Target Customers Approach
Direct Sales (Proto → MVP) CPOs (Ionity, Fastned, Milence, etc.) Startup events (Startupnight, Energieheld), industry conferences (Power2Drive, EVS)
Partner Sales (Traction) CSMS platforms, O&M providers White-label integration, revenue share agreements
OEM Licensing (Scaling) Charger manufacturers (ABB, Tritium, Kempower) Built-in predictive maintenance feature, licensing fee per charger
M&A Exit (Scaling) CSMS platforms, charger OEMs Acquisition by platform player seeking predictive maintenance capabilities

Competitive Moat

Why e-Litmus is defensible:

Promwad Competencies

Promwad brings 20+ years of embedded systems and IoT platform development expertise to e-Litmus:

Relevant Experience

Delivery Capabilities

Why Promwad for e-Litmus:

e-Litmus requires deep embedded systems expertise (7-sensor hardware integration), automotive protocol knowledge (CAN/Modbus), and multi-tenant SaaS architecture. Promwad has delivered all three for 300K+ automotive telematics units and industrial IoT platforms.

External Links

References & External Links

#SourceCategory
R1MarketsandMarkets: Predictive Maintenance Market ($47.8B by 2029)Market Research
R2Siemens: True Cost of Downtime 2024 Report (PDF)Market Research
R3IoT Analytics: State of IoT 2025 — Connected Device TrendsMarket Research
R4IoT Analytics: IoT Project Success Rates 2025Market Research
R5McKinsey: IoT Implementation Timeline Best Practices 2024Market Research
R6Tractian — AI-driven predictive maintenance for manufacturingPredictive Maintenance Platforms
R7Artesis — Motor current signature analysis (MCSA) for predictive maintenancePredictive Maintenance Platforms
R8Artesis ROI Calculator — Interactive tool for PdM business casePredictive Maintenance Platforms
R9Sensemore — Vibration monitoring and predictive maintenance platformPredictive Maintenance Platforms
R10Sensemore: Predictive Maintenance SolutionsPredictive Maintenance Platforms
R11SKF Condition Monitoring Systems — Industrial bearing and motor health monitoringPredictive Maintenance Platforms
R12OXMaint: Predictive Maintenance Case StudyPredictive Maintenance Platforms
R13Caterpillar Product Link — Heavy equipment telematicsOEM Fleet Management
R14Volvo CareTrack — Construction equipment monitoringOEM Fleet Management
R15John Deere Operations Center — Agricultural equipment fleet managementOEM Fleet Management
R16Komatsu KOMTRAX — Mining equipment remote monitoringOEM Fleet Management
R17Samsara — Connected operations platform (fleet, equipment, industrial)OEM Fleet Management
R18Schneider Electric: Motor Management SolutionsIndustrial IoT & Edge Computing
R19Schneider EcoStruxure Asset Advisor — Industrial asset health analyticsIndustrial IoT & Edge Computing
R20Siemens Industrial Edge Management — Edge computing for automationIndustrial IoT & Edge Computing
R21AWS IoT Core — Managed IoT service (inspiration for e-Litmus cloud architecture)Cloud & AI Infrastructure
R22AWS: Volkswagen Industrial Cloud Case StudyCloud & AI Infrastructure
R23NXP i.MX RT1170 — Crossover MCU for edge ML (used in e-Litmus gateway)Semiconductor & Hardware
R24NXP Industrial IoT SolutionsSemiconductor & Hardware
R25PostgreSQL Documentation — Relational database (e-Litmus data layer)Open-Source Software
R26TimescaleDB Documentation — Timeseries extension for PostgreSQLOpen-Source Software
R27Eclipse Mosquitto Documentation — Lightweight MQTT broker (message queue)Open-Source Software
R28MQTT Protocol Specification — IoT messaging protocol (ISO/IEC 20922:2016)Open-Source Software
R29Keycloak Documentation — Open-source identity and access management (multi-tenancy)Open-Source Software
R30Nginx Documentation — High-performance web server and reverse proxyOpen-Source Software
R31Redis Documentation — In-memory data store (caching layer)Open-Source Software
R32TensorFlow — Machine learning framework (LSTM RUL models)Open-Source Software
R33scikit-learn — Python ML library (Isolation Forest, anomaly detection)Open-Source Software
R34React — JavaScript library for building user interfaces (dashboard)Open-Source Software
R35Node.js — JavaScript runtime (ingestion service)Open-Source Software
R36FastAPI — Python web framework (alternative ingestion service)Open-Source Software
R37Prometheus Documentation — Monitoring and alerting toolkitOpen-Source Software
R38Grafana Documentation — Observability and dashboarding platformOpen-Source Software
R39Nature Scientific Reports: Deep Learning for Predictive Maintenance (2020) — Open access research on LSTM/CNN modelsAcademic Research
R40Nature: Machine Learning for Industrial Asset Monitoring (2023) — Anomaly detection techniquesAcademic Research
R41Zynetic (Norway CPO, 200-charger fleet) — Pilot partner, deployment completeActive Pilots
R42Ionity (Pan-EU CPO, 500+ chargers) — Pilot discussions ongoingActive Pilots
R43Epic Charging (Netherlands CPO, 150 chargers) — Pilot target Q2 2025Active Pilots
R44Fastned (Netherlands CPO, highway charging network)Target Customers
R45Milence (Daimler/Volvo/Traton joint venture, heavy-duty EV charging)Target Customers
R46Electra (France CPO, urban fast charging)Target Customers
R47Charge&Go (Germany CPO)Target Customers
R48Atlante (Italy CPO, PNRR-funded network)Target Customers
R49Fraunhofer IAO (Germany) — Research partner for EV infrastructure reliabilityResearch Institutions
R50SINTEF (Norway) — Joint research on predictive maintenance for EV chargingResearch Institutions
R51NXP Semiconductors — Hardware platform provider (i.MX RT1170 evaluation boards, technical support)Technology Partners
R52Infineon Technologies — Alternative MCU platform (AURIX family for industrial edge)Technology Partners
R53Demo Request: Email demo@e-litmus.io for live dashboard walkthroughContact & Demo
R54Pilot Program: 50-charger pilot available for Q2 2025 (first 3 CPOs, discounted pricing)Contact & Demo
R55Partnership Inquiries: CSMS platforms, OEMs — contact partners@e-litmus.ioContact & Demo

Disclaimer: e-Litmus is a Promwad-incubated startup concept (2024). Pilot deployments are ongoing. All technical specifications, ROI calculations, and customer lists are based on market research and preliminary pilot data. This presentation is for business development and investor engagement purposes.

Ready to Start?

Let's discuss how e-Litmus can protect your EV charging infrastructure.

Request Pilot Proposal