PCB Library
Every board the group has built leaves something behind: a footprint that turned out correct, a power stage that passed EMC, a part that was available when its alternative was not. The PCB library is that memory, held as verified symbols, footprints, reference blocks and an approved manufacturer list.
Inside the platform
Verified footprints & symbols
Library parts proven on a manufactured board, not drawn from a datasheet and hoped for.
Reference blocks
Power stages, protection, comms interfaces and sensor front-ends reused across designs instead of redrawn.
Approved parts & alternates
An AML with qualified second sources — the practical answer to a supply chain that keeps moving.
Design rules by class
Stack-up and clearance rules by product class, from commercial to airborne.
The shape of the work
An eight-layer stack-up, decided before anything is routed
Which layer a signal lives on is not a routing convenience — it is what sets its impedance, its return path and how much it radiates. Choosing the stack-up after routing means re-doing the routing, so the class of the product fixes it on day one.
Used across the group
- Every hardware programme in the group
Ownership
A shared platform. It has no natural home in any single unit, so the group funds it centrally and the shared engineering bench maintains it. Every company and division draws on the same version.
How we decide what is sharedOther platforms
Firmware SDK
The common embedded foundation — hardware abstraction, drivers, secure boot and update, with timing you can reason about.
Read moreDevice Management
Fleet identity, provisioning and health — knowing what is deployed, where, running what.
Read moreOTA Platform
Staged, reversible firmware campaigns across a fleet — the return path designed at the same time as the forward one.
Read moreBuilding something that needs PCB Library?
Tell us the constraints and we will come back with how this platform would carry them — or say plainly if it would not.