Software · BTS 9.1

Test control that stands up to audit.

BTS 9.1 schedules the test, captures every channel at up to 1000 Hz, and keeps the record traceable from sample login to signed report.

Instrument control, LIMS workflow and analysis sit in one application. Test data is not re-keyed between systems, and every change to a record carries an operator and a timestamp.

Typical, model-dependent Windows workstation
Platform BTS 9.1
Lab workflow LIMS
Fieldbus SMBus / CAN · CAN-FD
Signal maps DBC support
Audit readiness Part 11 friendly
Sampling 10/100/1000 Hz

Sampling is selectable per model. Interface scope and compliance scope are confirmed at quotation.

Module test rack
CE-6000 system with its control interface — the same BTS 9.1 data model runs bench racks and production cabinets.
Module and pack test cabinet
CE-6000 module test system with tablet control.

Capabilities

One application, from schedule to sign-off

Functions that would otherwise be split across a cycler front end, a spreadsheet and a separate lab system.

Test controlMulti-channel scheduling and per-channel protocols
Method editorCurrent, voltage and power steps with loops and cut-offs
LIMSSample registration, test assignment and results
BMS communicationSMBus, CAN and CAN-FD with DBC import
Sampling10 / 100 / 1000 Hz, selectable
Audit trailOperator and timestamp on record changes
AnalysisCapacity, efficiency and cycle-life views
ExportPDF, CSV and XLSX reports; raw data export

Typical configuration

What a BTS 9.1 install looks like

Bench R&D

One workstation, a rack of cell-test channels and BTS 9.1 — schedules, live curves and cycle-life views on a single PC.

Production line

BTS 9.1 driving 512-channel formation cabinets, with auto-generated grading results and LIMS hand-off as cells move down the line.

Regulated lab

Role-based access, append-only audit trail and linked electronic records, configured with your QA team around an existing SOP.

Data integrity

Audit trail, roles and records

Built for labs that have to show who did what, when, and with which instrument.

BTS 9.1 records test activity against the instrument, the channel and the signed-in operator. Method edits, starts, pauses and manual interventions are written to an audit trail rather than overwritten.

Access is role-based, so an operator can run a schedule without editing methods or deleting records. Electronic records are retained with the test and can be reviewed alongside the raw channel data.

The workflow is designed to support labs working toward 21 CFR Part 11 expectations. It is a software control, not a certification: validation and SOP fit remain with your quality team.

Audit trailTime-stamped, append-only change history
Access controlRole-based user permissions
Electronic recordsLinked to sample, method and instrument
Regulatory fit21 CFR Part 11 friendly
Export formatsPDF, CSV, XLSX
RetentionConfigurable per site policy

BTS 9.1 in your system landscape

Data leaves the instrument once and is consumed by the systems that already own sample identity and reporting.

BTS 9.1 integration paths
System Direction Typical payload Notes
LIMSTwo-waySample ID, test assignment, result, statusBuilt-in LIMS workflow; third-party LIMS scope agreed at quotation.
MESOutboundSerial number, grade, pass/fail, timestampUsed on formation and grading lines; interface specification per project.
ERPOutboundBatch summary, yield, rework countsAggregated at batch level rather than per raw sample.
Analytics / data lakeOutboundCSV, XLSX or raw channel exportFile-based by default; API options depend on version and licence.

Integration paths are illustrative. Protocols, API availability and validation responsibility are confirmed at quotation.

From install to validated workflow

A software install is a project. These are the four steps we plan with your team.

  1. Install and qualify

    Workstation, database and instrument links installed and checked against the agreed configuration.

  2. Map methods

    Your protocols are translated into BTS 9.1 methods; limits, cut-offs and sampling rates are reviewed together.

  3. Set roles

    Users, permissions and review responsibilities are configured with QA, including audit-trail review practice.

  4. Support validation

    We provide the configuration record and test evidence your team needs for IQ/OQ; sign-off stays with your quality function.

Instrument to report, without a gap

Each step keeps the sample identity attached, so a result can be traced back to the channel and the raw sample record.

1 · InstrumentCycler or chamber writes raw channel data
2 · BTS 9.1Schedules, logs, applies limits and audit trail
3 · LIMSHolds sample identity and result status
4 · ReportPDF, CSV or XLSX for review and archive

Exact interfaces and export formats are confirmed at quotation.

What BTS 9.1 does not do

Software boundaries matter as much as feature lists. These are the ones that come up in validation reviews.

  • It is not the instrument firmware. The control loop and protection live on the tester; BTS 9.1 schedules, logs and reports.
  • It does not replace your LIMS master data. Sample identity and retention policy stay in the system that owns them.
  • It does not validate your method. Method suitability and acceptance criteria remain with your laboratory and QA team.
  • It does not provide a hosted cloud service by default. Deployment is on a local workstation or your own server infrastructure.
  • It does not certify 21 CFR Part 11 compliance. It provides the controls; validated use is a property of your workflow.
  • It does not interpret results for you. Capacity, efficiency and cycle-life views are calculations on recorded data, not engineering conclusions.

Software documentation

BTS 9.1 manuals, release notes and validation-support documents are supplied with the licence. The shared instrument datasheets are in the resources centre.

Questions we get before a trial

Can I export to CSV or XLSX?

Yes. BTS 9.1 exports report-grade PDF and tabular CSV or XLSX files for downstream analysis. The supported set depends on the version and licence, so we confirm it against your workflow at quotation.

Does it integrate with our LIMS, MES or ERP?

BTS 9.1 includes LIMS functions for sample registration, test assignment and results. MES and ERP integration is scoped per project through a documented interface. Where you already run a third-party system, the interface, direction of data flow and validation are specified at quotation.

Is there an API?

API availability depends on the BTS 9.1 version and licence. For most labs, file-based export is enough; where a live interface is required, the protocol and payload are agreed during project scoping rather than assumed.

Is the system 21 CFR Part 11 compliant?

The software is 21 CFR Part 11 friendly: audit trail, role-based access and retained electronic records are built in. Compliance is a property of your validated workflow, so we support your qualification instead of claiming it for you.

Can we read BMS data during a test?

Yes. SMBus, CAN and CAN-FD are supported, and DBC files map the CAN signals into named channels alongside voltage, current and temperature. Available buses vary by model and are confirmed at quotation.

What sampling rate should we run?

10 / 100 / 1000 Hz is selectable. Use 1000 Hz for pulse and fast-charge work where transient response matters, and a lower rate for long cycle-life runs where file size and review time dominate.

Put BTS 9.1 in front of your method

Send us a protocol and the instruments it has to run. We map it to BTS 9.1, confirm the interface set and quote the licence — typically within one business day.

Talk to an engineer

Request a quote