Component library
A component gets entered once
The same microcontroller shows up in four projects written four different ways, each with its own copy of the datasheet and none with the properties filled in. XKEMA's central library exists so that record gets written once and everyone uses it.
- Manufacturer
- STMicroelectronics
- MPN
- STM32F407VGT6
- Class
- Microcontroller
- Package
- LQFP-100
- Supply
- 1,8 – 3,6 V
- Temperature
- −40 °C … 85 °C
- stm32f407-datasheet.pdfDatasheet
- an4488-getting-started.pdfApplication note
- errata-rev8.pdfErrata
Sample data.
What a record holds
Properties that depend on the type
A capacitor and a connector aren't described by the same fields, and forcing them to share a form ends in half-empty records. In XKEMA each component type has its own properties, so what gets filled in is what actually matters for that part.
- Electronic components — with manufacturer, part number and package.
- Materials and substances — in the same catalogue, not in another tool.
- Documents per component — datasheet, application notes, errata.
When someone finally uploads the right datasheet, it appears in every design that uses the part — not only in the project of whoever uploaded it.
From catalogue to board
The same record, followed from either end.
- Central librarythe component record
- BOM lineuses it, with a quantity
- BOMthe complete list
- Boardthe list belongs to it
- Productwhat gets built
Said plainly
There is no “where is this component used” screen and no automatic distributor lookup: XKEMA doesn't know whether a part has been discontinued. What it gives you is a single catalogue properly tied to the BOMs, which is the part that's usually missing.