Product structure
Equipment, boards, PCBs and stackups, with the quantity of each child element.
For hardware teams
Product lifecycle management suites are built for large manufacturers: they bring purchasing, costing, planning and months of rollout. Most electronics teams look at them, work out what getting in costs, and stay with the shared folders for another year.
XKEMA covers only the engineering strip: what the product contains, in which version, with which documentation and what was approved. You start with a real product on day one.
The design tool knows the design that is open. The management system knows items and orders. Between the two sits the whole product —its structure, its revisions and why they were approved— and that is where there is almost always a shared folder.
Equipment, boards, PCBs and stackups, with the quantity of each child element.
Bills of materials, power tables, requirements and interfaces, each with its own version.
PDF, Gerber and drill files tied to their element, and a frozen version with who signed it.
A concrete example
In the screenshot, a sample equipment with its board inside and the quantity it carries. That relationship is a fact in the system: you do not have to infer it from a folder name or ask anyone.
From there you go down to the board's frozen version, and from it hangs the bill of materials that was actually bought for that batch.
XKEMA is developed and operated from Spain. The email the site generates goes out through infrastructure in the European Union.
What you will not read here is that your data is guaranteed to stay inside the European Union, or that there is a data protection certification: the application is not open to the public yet, and the privacy policy says exactly which providers may process data outside the European Economic Area. It is written there, and it is not dressed up here.
XKEMA is invitation-only: there is no public sign-up and no automatic trial yet. There is a demo with a person and a waiting list with no card required.