From build to battery life
Trace every cell from material lot to cycle life, and build and test many cells without losing the thread.
A cell team answers the same questions every week. Which cathode lot went into the cells that faded early? Which cells go on test next, and on which equipment? Did the new electrolyte improve cycle life across every cell of the build? One build can produce dozens of cells across several designs, each made from specific material lots, electrodes and electrolytes, with some cells on test for months or years. When build sheets live in spreadsheets and cycler files pile up on separate computers, those answers take days. From build to battery life shows how to keep every cell connected to the materials and process that made it.
How do you trace a battery cell from material lot to cycle life?
Record each slurry, electrode and cell as a connected experiment, so every cell carries the material lots, electrodes and electrolyte it was built from. Bring cycler and instrument files in automatically and store the curves and summary values on the cell they describe, rather than matching files to cells by name. With the build, the lots and the test results on one record, a team can trace an early fade back to its lot, compare every cell in a build, and check each result against the release spec.
Who this guide is for
Cell design, process engineering, and test teams at companies that build and test lithium-ion and next-generation cells. For the wider platform view, see Uncountable for battery R&D.
What's inside
Inside this guide:
- Why a build of many cells creates more data than a spreadsheet can track
- Incoming materials, slurries and electrodes as structured, connected records
- Running cell builds at scale, with DoE-style designs across many cell factors
- Traceability from every cell back to its material lots
- Test requests, equipment scheduling and cycler data on each cell
- Releasing cells against a spec, including formation and DCIR checks
- Learning from every build, keeping records, and a practical path to get started
Build and test many cells without losing the thread. Download the guide.
FAQs
How cell teams record slurries, electrodes and cells as connected experiments, trace every cell back to its material lots, schedule tests and equipment, bring cycler data onto each cell, release cells against a spec, and learn from every build.
Cycler and instrument files are read and mapped to outputs, then stored as curves and summary values on the cell they describe. Files can also be pulled on a schedule from an SFTP or S3 folder, or sent through the external API.
Yes. Each slurry, electrode and cell is a connected experiment, so every cell traces back to the material lots, electrodes and electrolyte used to build it, and a lot change is visible across every cell that used it.
Formation and performance results, such as DCIR at 50% state of charge, are checked against the release spec for each cell, and every result shows a pass or a fail.
Cell design, process engineering, and test teams at companies that build and test lithium-ion and next-generation cells.
See the Platform Behind the Guide
