Part of Onboard BMS should estimate battery’s State-of-Health independently from the cloud and Focus on building the most reliable, safe, and autonomous BMS.

Because Energy infrastructure (including batteries) must be autonomous.

The functions which are required at each time point during operation should also run locally, guaranteeing the system safety. An advanced version of these functions will run in the cloud with advanced algorithms, which provide higher accuracy while requiring high computation power.

In other words, the onboard monitoring and control becomes a fallback for the cloud BMS. Jacob Gabrielson from AWS advises to avoid fallback for a number of good reasons.

I think that cloud monitoring and analysis of the data from batteries should focus only on the functions such as fleet management, capacity planning, battery failure alerts, and informing better onboard BMS algorithms. I think we shouldn't directly control batteries from the cloud in real time.

With different kinds of alarm functions, which can be set up for the original and virtual data points, the operators can be informed by the UI as soon as the fault of the systems is identified, increasing the chances of preventing damaging effects and thus improving the system reliability.

For safety and reliability, I think it's important that the onboard BMS identifies anomalies and failures and sends alerts to the cloud or directly to operators. The sending mechanism can still fail, but with a lower probability. The onboard BMS can also send a message directly to the operator or the user (bypassing the cloud) and physically beep to attract the attention of nearby people.

More generally, Decentralise and diversify.

Part of Digital twin for battery systems: Cloud BMS with online SoC and SoH estimation.

Part of the Big data → small data trend.