Skip to main content
GullySystem
Manufacturing · Software for eV component manufacturers

Trace cell lots, weld records and end-of-line tests to each battery pack built.

EV component makers build NMC and LFP battery modules and packs, wind traction motor stators and assemble inverters, onboard chargers and DC-DC converters. This software ties cell lots, laser busbar weld checks, battery management board firmware, hipot and isolation tests and the shipped serial together. Every pack stays accountable. When a warranty pack comes back, you open its serial and see the cell lot, the busbar weld log and the hipot result.

At a glance

A battery pack begins as cylindrical or prismatic cells sorted on a cycler for capacity and DCIR. They are grouped into modules, joined by laser welded or ultrasonic bonded busbars and fitted with a battery management system (BMS) board. Each cell carries its own history. Every step leaves data that a vehicle maker may ask to see years after the pack has shipped.

EV component software keeps all of it on the pack serial. Cell lot, weld record, BMS firmware and end-of-line result sit together, so an engineer answers a warranty query from one screen. Without that, the engineer opens cycler exports, torque logs and tester printouts side by side, still unsure they describe the same pack.

How the work runs today

Orders arrive from two-wheeler makers, bus builders and fleet converters with a pack variant and a build schedule. Stores hold cells in graded trays, and a tray is closed to a module only after the cycler file for that lot is matched to its label. Operators stack cells into the fixture, fit busbars and record nutrunner torque or weld parameters. Then the BMS is fitted and flashed, the cooling plate and thermal pad go in, and the case is closed.

Each pack goes to an end-of-line station for insulation resistance, hipot, cell voltage balance and CAN communication checks. Results are saved against the serial. A passed pack is brought to storage voltage, labelled with its UN 38.3 transport marking and packed. A failed pack goes to the rework bay with a defect code, then back to the tester. Nothing ships untested.

Where it breaks

What goes wrong for eV component manufacturers without a proper system.

Cycler grading files sit on one PC

Capacity and DCIR readings leave the cycler as a CSV that stays on the grading PC. Nobody links it to the module trays built from those cells, so a weak cell cannot be found later.

Weld and torque records carry no pack serial

Pull tests on a busbar sample and nutrunner torque curves are logged at the station. The pack serial is not on them. A questionable weld cannot be pinned to the pack that holds it.

BMS firmware versions rest on a note

Boards are flashed from a laptop at the station. Which firmware build went into which pack is jotted on a sheet, if it is jotted at all, and field updates are even less certain.

End-of-line failures leave no defect trail

A pack trips on isolation resistance or a CAN timeout, is reworked and passes. The faulty sense wire, the replaced board and the retest reading are never collected, so repeat faults stay hidden.

Variants multiply across one bench

Packs differ by series and parallel count, cooling plate, connector and label. When two variants share a bench, a pack with the wrong power connector or label can reach the vehicle maker before anyone notices.

What the software does

What we would build for eV component manufacturers.

Named the way your team already talks about the work. We start with whichever part the audit shows is costing you most.

Cell lots and grading

Book cell lots at receipt, store cycler capacity and DCIR for each tray, and issue graded groups to module builds by lot so matched cells stay together.

Module and pack build

Follow modules through stations, noting busbar weld or bolt torque, thermal pad and cooling plate fitted, the fixture used and the operator at each step.

Firmware and board records

Record the BMS board serial and the firmware build flashed into each pack, with the date, the flashing laptop and the station used.

End-of-line testing

Store isolation, hipot, cell balance and CAN results against the pack serial, with limits set by your engineers, and hold any failed unit.

Rework and defect codes

Log a failed pack’s defect code, the sense wire or board replaced and the retest reading, so recurring causes show up in one list.

Variant, label and despatch control

Hold each pack variant with its series-parallel layout, connector, label and UN 38.3 transport rules, then print serial labels and packing lists.

Before you talk to a supplier

A requirements checklist for eV component manufacturers.

What to cover, which reports to ask for and what to put to every vendor, ready to print or save as a PDF.

Open the checklist
Ready product

A product already built for eV component manufacturers.

It is adapted to how your business works before it goes live, and anything your trade needs that it lacks is added then.

EV Component Manufacturer Management Software

Cell lots graded by capacity and DCIR, busbar weld and bolt torque records, BMS firmware versions, hipot and balance tests, rework and serial despatch for EV component makers.

See the product
Solutions inside

The business modules eV component manufacturers use most.

Each one is also available on its own, or inside a system built for you.

How it works

How the work runs from Bengaluru for your city.

  1. 1

    The audit, by call

    A screen-share and a look at the sheets, accounting reports and WhatsApp groups your team uses. No travel needed.

  2. 2

    A written proposal

    Scope, what we build first and the cost, agreed in writing before anything starts.

  3. 3

    Build in short rounds

    Working screens shared every few weeks. Your team tests them from your own office.

  4. 4

    Go-live, in person when it helps

    For data migration and training we can come to your city. Travel is agreed in advance.

  5. 5

    Support online

    Fixes, changes and hosting handled remotely by the same team that built it.

Common questions

Questions eV component manufacturers ask before they call.

Can a pack be traced to its cells?

Yes. Cell lots and graded trays link to module builds, and modules link to the pack serial. A warranty query on one pack opens the whole chain, from cycler file to shipment.

Does it record firmware versions?

Yes. The BMS board serial and firmware build are logged for each pack at the flashing station, and both appear on the serial record beside the test results.

Do you handle motors and chargers as well as packs?

Yes. A stator winding route or an inverter and onboard charger assembly route can sit beside the pack route, each with its own tests and serial records.

Who decides the test limits?

Your engineering and safety staff do. Limits for isolation, hipot and cell balance are entered with them and reviewed during implementation, then changed only by named users.

What happens after I share my requirements?

An engineer reads what you send and replies within one business day. We then look at the software, spreadsheets and WhatsApp groups your business runs on today and write down what works, what slows your team down and what is missing. A demo login, a screen-share or a few screenshots are enough. You get a short written summary ordered by priority, with no obligation to hire us afterwards.

How much will the software cost?

We don’t publish a price, because it depends on what the system has to do. That first review settles the scope, and the cost goes into a written proposal before any work starts.

Related

Related industries.

Category

Part of a wider group.

Talk to us

Tell us how your business runs today.

A few lines on your spreadsheets, software and WhatsApp groups is enough. We reply the same working day.

  • No obligation
  • A reply within one business day
  • Your details stay private

Start with your requirements

Seven short steps that tell us what you need. An engineer reads them before getting in touch.

Share your requirements