Hardware operations
Your ERP Knows What You Bought. Does It Know Why It Is in the Design?
Two different questions, two different systems, and the gap between them.
Ask an ERP system what you bought last quarter and it will tell you precisely: quantities, suppliers, prices, delivery dates, stock on hand. That is a real capability and a hard one to build.
Ask it why a particular capacitor is in the design and it has nothing to say, because it was never asked to know.
The position. Transactional business data and engineering context are different concerns, served well by different systems. An ERP is excellent at the first. The gap is not a deficiency in ERP software; it is a category that most tool landscapes leave empty.
Two questions that look similar
| Question | Who answers it well | Why |
|---|---|---|
| How many of this part did we buy, and at what price? | ERP | It is a transaction record |
| Which supplier delivers it, and in what lead time? | ERP | It is a supplier relationship |
| How much stock do we hold? | ERP | It is inventory |
| Which products use it, at which released revision? | Neither, usually | It is an engineering relationship |
| Why was it chosen over the cheaper alternative? | Nobody | It is a design decision |
| What breaks if we replace it? | Engineering, slowly | It requires design context |
The first three rows are solved problems. The last three are the ones that cost a week during a shortage.
Why ERP does not cover the bottom half
Not because ERP vendors overlooked it. Because the data models answer different questions:
- An ERP item is a thing you transact. Its identity is commercial: it has
a cost, a supplier, a stock level, a unit of measure.
- An engineering component is a thing you design with. Its identity is
technical: it has behaviour, constraints, a footprint, approved alternatives, and a reason for being in a particular circuit.
- A BOM in an ERP is usually a manufacturing BOM, structured for
purchasing and production. An engineering BOM is structured for the design and carries designators, variants and rationale.
Both are correct. They are not the same list, which is why teams maintain both and reconcile them by hand.
The gap, named precisely
Between the tool where the design is captured and the tool where the business transacts, there is a set of facts that belongs to neither:
- Which product versions are released, and which are drafts.
- Which board revision each BOM belongs to.
- Which components have approved alternatives, approved by whom, with what
scope.
- Which documents describe which version of which object.
- Why a design decision was made.
In most companies these live in a shared drive and in people. That is the layer this note is about.
What a good hardware team should know
- Do not ask the ERP to be a design system. It will technically accept
the data and it will not answer the engineering questions.
- Do not ask the ECAD tool to be a product record. It knows this design,
not your product portfolio across versions.
- Reconciliation effort is a measurement. The hours spent making the
engineering and manufacturing views agree are the size of the gap.
- Name an owner for released state. Whoever that is, the role has to
exist.
Where structured engineering data helps
XKEMA is neither an ECAD tool nor an ERP, and it does not replace either. It organises the engineering context between them: components, products, boards, BOMs, versions and released state, with documents attached to the objects they describe.
The result is that the bottom three rows of the table above have a place to live, and the top three stay where they already work.
Sources
- NASA Systems Engineering Handbook Rev 2, section 6.5 — configuration management as a discipline distinct from, and complementary to, business and logistics processes.
- NIST AI Risk Management Framework 1.0 (NIST AI 100-1) — why the context a system was designed for determines what its outputs mean.