Skip to content

How it works

From the empty project to the revision that gets manufactured

XKEMA does not ask you to migrate anything before you start. You open it with a real product, build its structure the way it actually exists, and hang the information where it belongs as you need it. This is what happens at each step, and also what does not.

Step 1

You create the project and go into the library

The central library is where everything reusable lives: stackups, PCBs, boards and equipment on one side, and the component families on the other —passives, discretes, integrated circuits, connectors, optoelectronics, electromechanics, materials and substances—.

You do not have to load it all before you start. You enter what shows up in the product you are building, and from then on it is available for the next ones.

XKEMA's central library with a component search box and the categories stackups, PCB, board, equipment, passives, discretes, integrated circuits, connectors, optoelectronics, electromechanics, materials and substances.
XKEMA's “Add New Element” dialog with the options components, materials, substances, stackups, PCB, board and equipment.

Step 2

You build the product structure

Equipment contains boards; a board has its PCB; a PCB has its stackup. The structure is declared the way it really exists in the product, with the quantity of each child element.

That hierarchy is not decoration: it is what turns “the power supply” into something you can look up. The product configuration comes out of it.

Configuration management, in detail

Step 3

The bill of materials hangs from the board

The BOM is created inside the element it belongs to, not as a file named after the product. Each line points to a record in the library —manufacturer, part number, properties, datasheet— instead of to text that every person types their own way.

And the BOM has its own version. Changing it does not renumber the board, and changing the board does not renumber the BOM.

BOM management, in detail

XKEMA's stackup viewer with a PCB's layers, their materials and their thicknesses.
The engineering tables —stackup, power, requirements, interfaces— open the same way the BOM does, inside the browser.
XKEMA's Gerber viewer showing a PCB's manufacturing layers in the browser.

Step 4

You connect the documentation to the element it describes

Schematics in PDF, Gerbers, drill files, IBIS and SPICE models, footprints and symbols. Each document is tied to the element it actually describes, and opens in the browser without downloading it.

This is where XKEMA meets your design tool, and where it parts company with it: XKEMA does not draw schematics and does not route boards. It stores, relates and versions what comes out of the design.

Technical documentation, in detail

Step 5

You freeze the revision that gets manufactured

Up to here everything is editable, which is how it has to be while you are designing. The last step is saying “this is the one”. The freeze is requested, whoever has to sign signs, and the version is closed with a fingerprint of its approved content.

It does not reopen

A frozen version is not corrected. What comes next is a new version linked to it.

It can be compared

Two versions are placed side by side: the BOM row by row, the PDF page by page and the Gerber by its geometry.

It can be verified

The fingerprint is recalculated whenever you want and compared with the one stored on the day of approval.

What XKEMA does not do

It does not replace your design tool: it does not draw schematics, does not route boards, and does not open the ECAD's native project. It does not raise purchase or manufacturing orders. It does not look up distributor prices or stock, so it will not warn you when a component goes obsolete either. And it does not track unit by unit with serial numbers.

So where does it fit, between ECAD and ERP