Solidstudio - eMobility Software

A few weeks ago in Lyon I presented "The Hidden Failures in EV Networks: Is It a Matter of Detection, or Action?" at the 7th Annual EV Charging Infrastructure Development Forum. Several people asked for a recording. There was none, so we recorded it properly 🎥. The talk opens with one real charging session: ✔️ authorization fine, energy flowing ✔️ twenty minutes at flat zero ✔️ station reporting "available" the whole time Nobody on the operator's side ever saw it. Then we multiplied it: on one pilot of 15,000 sessions, almost 1,000 were zero sessions the operator knew about. Another 640 had anomalies nobody knew about. 💡 My honest view after nine years of building software for operators: detection is rarely the bottleneck. The signals are in the data. What separates networks that perform from networks that frustrate drivers is how fast a detected problem turns into a resolved one - and how much of that is actually in the operator's control. 🎥 If you'd like to watch the full recording, grab the link in the comments below.

⚡ A charging station can report "available" for twenty minutes while nobody can charge. Your dashboard will not tell you. The driver will not either. They just leave. That is a hidden failure. Our CEO Paweł Małkowiak first gave this talk at the 7th Annual EV Charging Infrastructure Development Forum in Lyon. Now it is recorded: 15 minutes on why most networks are full of them, and why detecting them is only half of the job. What he covers: ✅ One real charging session, from a clean start to twenty minutes at zero power. ✅ The loop every operator has to close: detect, understand, act, confirm. ✅ Three ways of running a CPMS, and how much of that loop each one lets you close. ✅ For engineers: what EV Network Intelligence runs on under the hood, and why it is not an LLM wrapper. The advantage of a bigger network? Economies of scale. The trap? An operations team that grows with it, watching dashboards. Hidden failures do not hide from the data. They hide from the dashboards. Watch the talk 👇

Since April, data for public charge points has to reach the Mobilithek in DATEX II format. We have that running in production for a German operator today, not on a roadmap. Read how EWE Go, one of the largest charging networks in northern Germany, handles reporting, roaming and the rest of it.

One of northern Germany's largest charging networks runs on our platform. DATEX II reporting to Mobilithek, live in production. Here is the detail.

🔋 Germany has 12,819 registered charge point operators. The 10 biggest run under a third of the market. No single network covers enough of its own drivers' journeys, so roaming is not a growth feature here. It is the product. The advantage? A fragmented market rewards a platform that handles roaming and compliance from day one. The trap? Every operator carries the same duties as the biggest ones, with a fraction of the team. ✅ Only 2,215 of those 12,819 operators actually run charge points: 181,438 points across 47,576 sites ✅ Each one registers with Bundesnetzagentur, feeds live data to the Mobilithek, and meets Germany's Eichrecht metrology law ✅ Eichrecht alone costs over 500 EUR and 2+ hours per DC charge point to verify, and the real volume is 45,000+ verifications a year, not the official estimate of 6,000 Full breakdown of why the German market is shaped this way, and what it means for a platform decision. Read the full piece 👇

EWE Go operates one of the largest charging networks in northern Germany. Our case study covers what running that platform actually involves: DATEX II reporting to the Mobilithek in production, roaming across more than one route, and the operational detail behind both. If you operate charge points in Germany, it is the clearest picture we can give of how we work in this market.