the component record
With manufacturer, part number, package and the properties of its type.
What XKEMA does
Projects, equipment, boards, PCBs, bills of materials, components, documents, revisions and technical data. Everything has its place and, above all, stays connected to the rest.
01 · Projects
A project holds everything about a product: its folders, its documents, its equipment and its boards. It belongs to the team rather than to whoever created it, so when someone changes roles the context doesn't leave with them.
02 · Product structure
Equipment holds boards. A board has its PCB, its stackup and its revisions. Its bill of materials and its documents hang off that. In XKEMA the hierarchy is the data structure itself, not a folder-naming convention every engineer reads differently.
Sample data.
03–04 · Example bill of materials.
A bill of materials is not just part numbers typed into cells. Each line can point to a record in the central library, with its manufacturer, properties and documentation. A component is created once and then reused wherever it appears.
| Ref | MPN | Manufacturer | Qty |
|---|---|---|---|
| U1 | STM32F407VGT6 | STMicroelectronics | 1 |
| U4 | TPS62130RGTR | Texas Instruments | 2 |
| C12–C18 | GRM188R71H104KA93D | Murata | 7 |
| J1 | 1734035-2 | TE Connectivity | 1 |
With manufacturer, part number, package and the properties of its type.
They belong to the same library, but with the specific fields each type needs.
Datasheets and documents stay tied to the component and are available from any design that uses it.
Sample data.
05–07 · Documents, versions and viewers
Each file is linked to the item it documents. When a new version appears, the previous one stays available and both are part of the same history. And when you need to consult them, you can do it directly in XKEMA.
As well as keeping which version each one was and the order they came in, XKEMA compares two revisions of the supported artefacts: the rows of a BOM, the pages of a PDF and the geometry of a Gerber.
08–10 · Teams, sharing and engineering tables
XKEMA is built so that technical information ends up belonging to the company: shared within the team, shown outside in a controlled way, and always tied to the product it belongs to.
What is created in XKEMA belongs to the team and can still be used even when the people working on the project change.
Share a specific document through a read-only link that expires.
Power, requirements and interfaces, inside the product and versioned.
XKEMA does not draw schematics or PCBs and does not yet integrate directly with ECAD tools. It does not query manufacturer or distributor stock, prices or obsolescence either, and there is no dedicated “where is this component used” view. It does compare BOM, PDF and Gerber geometry revisions, but it does not open your ECAD's native project or compare its internal files. We'd rather you knew exactly what the product does before you start using it.