Solution · Intelligence
Battery Field Testing Assistant
- Telegram
- eBatt
- Ollama
- Qdrant
- ERPNext
- n8n
- Edge Tablet
The problem
A capacity discharge test or a cell impedance survey is run against IEEE 450, 1188 or 1106 depending on the chemistry, with manufacturer thresholds and temperature corrections on top, while the engineer manages arc-flash and hydrogen hazards from a paper checklist. What she noticed on site reaches the maintenance system days later, when the paperwork is filed, if it reaches it at all.
What I built
A guided workflow that picks the IEEE procedure for the battery type, trends impedance against the baseline as the readings come in, watches each cell during discharge for reversal or a sudden fall, corrects capacity for temperature, and produces the report to the standard before the engineer leaves site. A Telegram bot takes voice or text notes from any engineer on the crew and feeds them through the same pipeline, so no laptop is needed.
The logic flow
Click any node for what it does, what it hands on, and where a person is required.
What it returns
The checklist cannot be skipped because the workflow will not advance past it, a failing cell is flagged during the discharge rather than in next month's spreadsheet, and the report exists when the engineer drives away. The observations reach ERPNext the same day.
Why it fits
An asset owner's assistant can summarise IEEE 450, 1188 and 1106 now, and tell its owner what a capacity discharge test or an impedance survey ought to show; it cannot tell them what their cells did. A testing firm that meets the smarter customer with an AI-written report template has sped up the part the customer can already do. It has left alone the part that was always slow: an observation made on site reaching the maintenance system days later, when the paperwork is filed, if it reaches it at all.
This assistant moves the value to the moment of measurement. It picks the procedure the standard requires for the chemistry and will not let the engineer past a safety checklist that deals with arc-flash and hydrogen hazards, and once testing starts it trends each cell's impedance against its baseline as the readings arrive, watches every cell during the discharge for reversal or a sudden fall, and corrects capacity for temperature. It flags a failing cell during the discharge rather than in next month's spreadsheet. The report exists, to the standard, before the engineer drives away, and anyone on the crew can send a voice note from a phone that reaches ERPNext the same day.
One five-year strategy this could serve, sketched rather than planned, sells the battery's record instead of the test visit. Give the owner, and the tools the owner now checks a report with, access to trended impedance and discharge results across every string you test, each result traceable to the procedure and the thresholds it was held to. Then price the service on the continuity of that record rather than on the day on site. A customer who can check a report against the standard will keep paying the firm whose measurements their own assistant has learned to trust. Nobody else holds those readings.
See it run
Want one of these?
Every part of it is open source and self-hostable. What I bring is the failure record and the judgement about where your gates should sit.