Case study
Device Identity & Traceability
How an automotive BLE module manufacturer made duplicate MAC addresses impossible — without buying an MES

At a glance
- Client: a Pune-based automotive electronics manufacturer assembling BLE modules for a leading automotive Tier-1 supplier’s tyre-pressure monitoring systems.
- Industry: automotive electronics / EMS (Tier-2).
- Challenge: MAC addresses calculated from a running counter and recorded in Excel could be duplicated by a miscount or batch re-run, with no reliable audit evidence.
- Solution: a factory-floor allocation server, supervisor console, customer trace portal and programming-station toolkit.
- Outcomes: structurally impossible duplicate addresses; approximately 4,000 legacy records imported; 22 of 22 allocations completed during an internet outage; three disconnected tools plus Excel replaced by one system.
The stakes
Every BLE module carries a globally unique MAC address that the vehicle’s systems depend on. Two modules with the same address can interfere in the field, creating a potential field failure, containment exercise, customer audit and risk to the contract.
The Tier-1 customer operates under IATF 16949, with traceability obligations flowing down to its suppliers. The manufacturer needed to show every unit an address had been written to and prove that no address was issued twice, on demand and with evidence.
The breaking point
Previously, each address was calculated from a spreadsheet counter and never read back from the device. Records were scattered across the chip vendor’s programming tool, two test applications and Excel files that did not communicate.
A miscount, re-run or stale spreadsheet could silently issue the same address twice. There was no single source of truth or reliable proof for an auditor.
A full Manufacturing Execution System could mean ₹7–30 crore and a year of integration for an SME line. MES-lite products handled work orders and inventory rather than device identity. The manufacturer needed a focused alternative.
The solution: identity managed like a ticket book
MetaDesign treated the company’s purchased IEEE block of 16.7 million addresses like a ticket book: issue exclusive blocks, never reissue a used address, and verify every identity before shipment.
The database itself makes duplicates impossible
The database refuses overlapping address blocks at the deepest level of the system. Attempts to add a conflicting range are rejected with the exact conflict identified, rather than relying on an operator or procedure to catch it.
Used addresses never come back
Consumed blocks, and blocks with uncertain status, never return to the available pool. Approximately 4,000 legacy Excel records were imported as already consumed, preventing addresses from the old process from being reissued.
Every unit is verified twice
Before programming, the assigned address is bound to the module’s scanned QR code. After programming, the station reads the address back from the actual device and the server checks it. Only a confirmed match passes.
Ambiguous units are held, not shipped
A mismatch, duplicate, wrong-block address or unknown result places the unit in a hold queue. Clearing a hold requires a written reason and an explicit recorded decision: resolved, quarantined, scrapped or reprocessed. The system never fabricates a pass.
The customer can see their own trail
A cloud portal lets the Tier-1 customer or an auditor trace their modules by station, batch and address block, with a complete event timeline. Strict isolation means partners see only their own production.
An append-only, tamper-evident audit log makes alterations detectable on screen. When an auditor asks for proof that no address was issued twice, the answer is a login rather than a week of spreadsheet archaeology.
The floor does not depend on the internet
The allocation server runs on the factory LAN. Production continues when the cloud connection fails: records buffer locally and synchronise on reconnect, without loss or duplication. If synchronisation silently breaks, administrators receive SMS alerts.
Built for the client’s own workflow
MetaDesign delivered the server, database, supervisor web console, reports and a Python SDK with a handful of simple functions for the client’s station software. A reconciliation report highlights unaccounted-for addresses, and five standard reports export to CSV, Excel and PDF.
The results
The system runs on one box on the factory LAN plus an optional cloud portal, rather than requiring a full MES project.
- Duplicate MAC addresses are structurally impossible through database enforcement.
- Approximately 4,000 historical records were imported so old addresses cannot be reissued.
- A 16.7-million-address IEEE block is managed centrally, with exclusive site allocations, a visual address map and automatic refusal of company-wide overlaps.
- During a live cloud outage, all 22 of 22 allocations succeeded with zero loss and synchronised cleanly on reconnect.
- Three disconnected tools plus Excel were replaced by one system.
- Every allocation, verification and hold decision has a tamper-evident record that the customer can inspect directly.
What this means for you
If your production line ships devices with MAC addresses, IMEIs or serial numbers and keeps its records in spreadsheets, you face the same identity and audit risks.
A focused identity layer can provide exclusive allocation, read-back verification, holds instead of silent failures, and trustworthy customer traceability. It is an engagement measured in months rather than an enterprise programme measured in years.
Where the platform goes next
The foundation supports the following capabilities in follow-on engagements; these are extensions, not claims about the delivered scope.
- Panel and lot genealogy linking raw panels, receipts, modules and positions.
- Functional-test records and yield dashboards by station, jig and firmware.
- Serial-number and IMEI allocation for smart meters, trackers and other devices.
- One-click recall audit packs covering affected units, batches and shipments.
- Label printing at binding, keeping label and database identities consistent.
- Key and certificate provisioning, on the roadmap.
Why MetaDesign
MetaDesign builds focused, production-grade systems for problems too critical for spreadsheets and too specific for off-the-shelf software. We define a clear scope, demonstrate it end to end and hand over a system your team can run: standard containers on commodity hardware, with your data in an open database you own.
The complete system can be demonstrated on a single laptop, with no hardware required. Contact Pradeep CK to see it live.