Engineering, IT & Data
Clean parts data before you migrate
A migration moves your part master and BOMs as they are, and a portal shows them to your customers. We link eBOM, mBOM and service BOM per serial number, merge duplicate parts and classify them first.
What we usually find
01
Three BOMs
Each team keeps its own BOM, and none shows the machine as built.
02
Duplicate parts
The same screw sits in the part master five times, with five stock levels.
03
No standard classes
Free-text descriptions make search, comparison and a parts shop fail.
04
A migration date
S/4HANA, Teamcenter or Windchill is coming, and nobody wants the mess moved.
Measured before and after
We score your data before we start and again at handover. Acceptance of the sprint is tied to the score.
- Quality score per object: parts, BOMs, customers
- Rules your team can keep running
- A part master ready for migration or a parts portal
Example with made-up numbers. Your scores come from the sprint.
What we work on
BOM harmonisation
eBOM, mBOM and service BOM connected, with an as-built and as-maintained view per serial number.
Part classification
eCl@ss, ETIM or UNSPSC, normalised attributes, and descriptions in several languages under one part number.
Deduplication & rationalisation
Duplicate and near-duplicate parts found, obsolete parts flagged, part numbers consolidated.
Supersession & interchangeability
Part-to-part replacement chains and cross-references to aftermarket equivalents.
Customer & account master
Clean hierarchies linking end customers, dealers and distributors.
Migration & portal readiness
Data prepared for S/4HANA, Teamcenter, Windchill or a customer parts portal.
Data Foundation Sprint
6–8 weeks depending on data volume, fixed scope and price. You get clean data and the rules to keep it clean.
What you get
- Data-quality score before and after
- Linked eBOM, mBOM and sBOM for your key machine types
- Deduplicated, classified part master
- One part number per part, with descriptions in every language you need
- Supersession chains for service parts
- Data-quality rules and a migration-ready export
What we need from you
- Part master and BOM exports from ERP and PLM
- Machine sales with serial numbers
- A data owner from engineering and one from service
- Someone who knows the history of your part numbering
Weeks 1–2
Profile
We measure data quality and agree priorities.
Weeks 3–6
Clean & link
Deduplication, classification and BOM linking, with your team reviewing as we go.
Weeks 7–8
Hand over
Clean data, rules and an export ready for your target system.
After
Keep it clean
Optional Managed Data Governance, with monthly quality reports.
Questions we often get
Do you replace our PLM or ERP?
No. We hand the clean data over as files, and your team or your integrator loads it into the systems you use.
Our S/4HANA project already has an integrator.
We clean and link the master data before it moves. The integrator runs the migration.
Which classification standard?
It depends on your customers and systems. eCl@ss is common in German-speaking markets and ETIM for electrical parts. We can map to both.
How does the data stay clean?
We leave rules and checks your team can run. Managed Data Governance runs them monthly if you prefer.
Who decides which BOM is right?
We propose the rules, your data owners decide, and every decision is logged.
How do you use AI?
Software proposes duplicate matches and classes. Your engineers and our team review them, and you get the rules and the review log.
Do we need a part number per language?
No. We keep one part number per part and store the description in each language you need. A new number per language multiplies the part master.
Send us a part master export
In a 30-minute call we tell you how clean it is.
