Your benches do the work. Your team makes the calls.

The AI proposes a sequence from your description: only blocks from the library, in a fixed format, no code, every assumption flagged. You give the approval. Limits and shutdown come from the DUT profile and the setup, never from the AI. It plays no part during the run. Without the AI, you assemble the sequence from building blocks yourself. No programming required.

Amperatec is in its pilot phase. With our first partners we set up: connecting instruments, approving sequences, unattended runs across several test benches, and analysis compared with earlier runs. Next come tests that a firmware or hardware change triggers by itself, and questions about every run in your own words.

If a reading reaches a limit from the DUT profile or the setup, the limit monitor shuts down and brings the instruments to a safe state. The run is marked as aborted, with the reason and the readings, and you are notified. Whether a test bench may run unattended is set by your risk assessment. Emergency stops and contactors stay hardware.

From your runs. The AI translates your question into a query on your runs; computing and plotting happen on your machine. Every answer names its source: run, DUT, firmware, test bench. No measurement data leaves your site for this.

Measurement data and sequences stay on the computer at the setup or on a server in your building. No cloud is required. For the AI proposal, which you then review and approve, only the description, the DUT profile and the setup's capabilities leave your network, never measurement data. The AI can be switched off. You install a Windows program; updates also work without internet access.

The instruments already in your lab: power supplies, electronic loads, multimeters, data loggers, multiplexers, power analyzers, climate chambers and CAN adapters, including different manufacturers in the same setup. If an integrator is missing, we build it, as long as the instrument has a documented interface.

The library contains charge, discharge, rest, pulses, temperature control, wait, measure, loops and conditions, plus CAN messages to a BMS. These form templates such as capacity, DCIR or pulse test. If your test needs a block that is missing, tell us. If it fits the product, we add it to the library. We don't build custom software outside Amperatec.

Yes. Lab and production are one product. An end-of-line test you develop in the lab runs with the same sequence at the end-of-line station, without new programming. Production has stricter rules: approval by a second person, serial number via scanner, pass or fail against fixed limits, an immutable record per serial number. The operator only sees serial number, start and result.

It starts with a setup at your test bench. We connect your existing instruments, build missing integrators and set up two or three tests you run often as sequences. After that you use Amperatec at the lab bench and at the end-of-line station alike. How billing works and what it costs, we discuss in a call once we know your instruments and tests.