NEXUM®-CTR-Client watches your production line, works out what is ready to register, and submits it to Volkswagen's Component Repository in the right order. No manual step, and nothing goes out that you have not approved.
Volkswagen's CTR (Component Repository, in German the Bauteilrepository) only accepts a parent assembly after every one of its subcomponents is already registered on its own. On the shop floor, scans arrive in whatever order the parts move, and a component's subcomponents are often scanned on a completely different production line than the parent itself.
Submit a module before its cells and the registration is rejected.
A component and the parent's data land at different moments.
Two components can share a part type yet need different attributes registered — the wrong match means
the wrong data goes to VW.
Someone has to remember what is still missing, and revisit it, for every part, every shift.
Each component requires its own registration. The parent can only be successfully registered once its children are acknowledged as usable by VW's CTR.
Each production line keeps its own database. NEXUM®-CTR-Client watches them all and registers every component with Volkswagen's CTR, in order.
Each scan writes one P-Key — a single reading, like a serial number or a parent link — to that line's own database. The client only watches; it never changes how scanning works.
NEXUM®-CTR-Client doesn't care how a scan got there — direct integration is enough. If you're setting up a new line, VW-supplier plants typically run one of two concepts for that layer, and NEXUM®-BDE Executer V3 covers both.
NEXUM®-BDE Executer V3 is a separate NEXUM® product — it pairs well with NEXUM®-CTR-Client, but neither one needs the other to work. Learn more about NEXUM®-BDE Executer
The client owns every stage, from the first scan to VW's acknowledgement, with tracked results and automatic retries.
Every scan on your line is noticed the moment it is written, without touching how scanning works today.
Works out which real component the scan is, and quietly sets aside scans that are just more data for a known part.
Confirms everything needed is present, including that every subcomponent is already registered.
Builds the exact registration data your approved contract describes, then validates it against the contract's own XSD schema.
Sends it to Volkswagen's CTR and tracks the result. Not ready yet? It waits, then tries again automatically.
The part now exists in CTR, and its parent can move forward.
Set it up once in the browser, then let it run.
A part type can have more than one contract — each still describes exactly what you send to
VW. Test it, approve it, and it is the only definition the line uses.
Map each P-Key your plant scans to the attribute its contract needs — the link between your
line's raw data and what VW expects. An overview of the scan keys shows what is covered.
Each production line has its own configuration, queues and active revision, all managed from the same interface.
Start, stop and inspect the arrival and submission queues per line. A stop is clean, and a restart picks up where it left off.
See what is new, waiting, submitted or failed as it happens. If the live feed drops, the screen falls back to polling on its own.
Test the connection to a plant's scan data step by step. If something is wrong, the page says which step failed and why.
Automation is only useful if you trust it. Approval is a decision made here, by you, and the line only ever follows what was approved.
part typeA contract is approved by an explicit action and validated again on the server. No import or edit can approve one by accident.
An approved contract cannot be edited until you revoke its approval, so nothing changes silently on the next restart.
Before the queue starts, every contract is checked. Broken ones refuse the start, with the reason on screen.
A change that triggers a restart never brings it back up invalid — if validation fails, it just stays down and says why.
Scans keep queuing while the processor is down. Unapproved parts are set aside and marked, never deleted.
Changes to mappings, part types and line links are limited to administrators.
A small footprint that fits how plants already work.
A single Windows executable, installed as a service and managed like any other on the server.
State lives in the database you already operate, next to the plant's own scan data.
Live updates with automatic fallback to polling and reconnection, so a screen is never quietly stale.
The management UI is available in English, German and Spanish.
Your configuration is versioned as revisions. Prepare the next one on the side while the current one keeps running.
Book a short demo and we will walk through your line, your part types and what it would take to get them
registered
automatically.
info@atonmexico.com