Two levels of data
Enter static, family-level information once per battery model (product family), then register one passport per physical battery with its serial number and any unit-specific details.
This matches common industry practice (model code + serialised units) and EU passport expectations under Annex IV.
Two layers at a glance
Enter once per product family
attribute_value
holder = MODEL
Per physical battery
Chemistry, BOM, and recycled metal shares live on the model; each passport carries its serial identity, hazardous substance list, lifecycle status, and (when connected) live performance readings.
Main record types
| Record | What it represents | You know it by |
|---|---|---|
| Organization (workspace) | Your company or partner account. All batteries and models belong to one workspace. | Legal name shown in the top bar |
| Battery model | Product family — one datasheet for many physical units. | Model code, optional LMT reference |
| Passport | One manufactured battery with its own serial and QR. | Public ID, serial number |
| Bill of materials | Structured parts list with masses, linked to the model. | Model → Bill of materials |
Regulatory fields (catalogue-driven)
Annex IV and related rules define many individual data points (chemistry, recycled %, labels, etc.). The app stores them in a flexible catalogue so new legal fields can be added without rebuilding the database.
Shared on the model (typical examples):
- Battery chemistry, cathode/anode, critical raw materials
- Recycled content percentages and several circularity fields
- Carbon footprint declaration
Per passport (typical examples):
- Hazardous substances list
- Some label and circularity details specific to the unit
- Live performance / state of health after BMS connection
See Materials & composition for the full split and screen names.
LMT reference catalogue
The LMT reference catalogue is tenant-agnostic reference data (28 demo e-bike packs locally).
A model may optionally provision from a catalogue entry via reference_code when creating
or importing a model — copying baseline attributes without re-keying the datasheet.
In the app: LMT reference catalogue
(manufacturer workspace). Model CSV import can set reference_code to link a row to catalogue data.
Carbon & bill of materials
- Carbon footprint — declared on the model (class, kg CO₂e/kWh, lifecycle stages). Passports display the model declaration automatically.
- Bill of materials — one primary BOM per model with optional parent/child rows, material codes, and mass balance checks. Passport views read from the model BOM.
- Production details — production date and plant information on each passport where required.
Live performance data
State of health, cycle counts, and telematics readings belong to each passport, not the product family. They update over time while the battery is in service.
What you see on a passport
Tabs such as Materials and Circularity combine model data with anything entered for that serial number. Shared fields show an “inherited from model” note and a link to edit the family once instead of retyping on every unit.
Completeness and Compliance use the same logic — for example recycled content declared on the model counts for every passport under that model.
Where to work in the application
| What you are editing | Holder / entity | Route in this app |
|---|---|---|
| Register product family | BatteryModel |
/app/models/new |
| Import vendor datasheet (CSV) | MODEL attributes + model row | /app/models → Import CSV |
| Materials & chemistry (shared) | Model | Models → Materials · Help: materials guide |
| Hazardous substances (per unit) | Passport | Registry → passport → Materials → Edit |
| Circularity & recycled content (shared) | MODEL attribute_value |
/app/models/{id}/circularity/edit |
| Bill of materials | Model | Models → Bill of materials |
| Carbon declaration | Model metadata_json |
Model detail / carbon form (from models list) |
| Register physical unit | Passport |
/app/passports/new |
| Bulk serial units (CSV) | Passport rows only | /app/passports → Import (columns: public_id, model_code, serial_number) |
| Passport detail (read inherited + unit data) | Effective MODEL ∪ PASSPORT | /app/passports/{id} |
| Unit static data override | PASSPORT | /app/passports/{id}/edit |
| Public QR / Art. 77 surface | Passport public_id |
/p/{publicId} (anonymous) |
| LMT catalogue browse | Reference data | /app/catalog/lmt-batteries |
Routes under /app/... require a signed-in manufacturer (or appropriate partner) session.
Help pages are public at /help/**.
Recommended manufacturer workflow
- Create or import a battery model (and optionally link LMT reference code).
- Complete model-level materials, circularity, carbon, and BOM once.
- Create passports (form or CSV) with serial numbers pointing at that model code.
- Fill unit-specific fields and dynamic data per passport; use passport detail for lifecycle, NB audit, and market placement.
Related help
- Materials, BOM & composition — step-by-step for manufacturers.
- Workflows & regulation — WF-01 through WF-12.