the component record
With manufacturer, part number, package and the properties of its type.
What XKEMA does
The whole product, connected in one system.
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.
Projects
Product structure
You pull up its bill of materials
Components
Documents
Revisions
Viewers
Teams
Sharing
Engineering tables
01 · Projects
The usual starting point.
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.
- Hardware technical documentation, inside the project — XKEMA
- Per-object permissions, granted to one person or to the whole team.
- No artificial project limit to get started.
02 · Product structure
The real structure of the hardware, inside the system.
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.
- Stackup with layers, materials and thicknesses.
- Several boards per unit, several revisions per board.
ORION CONTROL UNIT
-
Main Control Board
Rev C
- PCB ·
- You pull up its bill of materials ·
- Power Supply Board
- Power budget ·
Sample data.
03–04 · Example bill of materials.
every line points at a component
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 |
- Manufacturer
- STMicroelectronics
- Class
- Microcontroller
- Package
- LQFP-100
- stm32f407-datasheet.pdf Datasheet
Materials and substances
They belong to the same library, but with the specific fields each type needs.
The knowledge travels with the part
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
Documentation keeps its place and its history.
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.
- Viewers for PDF, Gerber, stackup, components, BOM and engineering tables.
- Versioning for documents, BOMs and engineering tables, with author and date.
- Every upload is checked by its actual content, not by its extension.
XKEMA does not compare revisions line by line. It keeps which version each one was and the order they came in, so that years later the history is still clear.
08–10 · Teams, sharing and engineering tables
It belongs to the team, not to a person
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.
Teams
What is created in XKEMA belongs to the team and can still be used even when the people working on the project change.
- Permissions on each object.
- To one named person or to the whole team.
Sharing outside
Share a specific document through a read-only link that expires.
- Whoever receives it needs no account.
- The link gives no access to the rest of the project.
Engineering tables
Power, requirements and interfaces, inside the product and versioned.
- With their own viewer.
- Without depending on yet another spreadsheet lost outside the project.
How far XKEMA goes today
It doesn't draw schematics or PCBs, it doesn't integrate with any ECAD tool, it doesn't query distributor stock, price or obsolescence, it doesn't diff revisions line by line, and there is no “where is this component used” screen. We'd rather say it here than let you discover it in the demo.