Why unique?
Protect what the customer or technical requirement genuinely needs. Make the supply consequence visible.
00 · The short version
Custom product. Repeatable decisions.
DTO should stay flexible where it creates customer value. The sourcing approach should not have to start from zero around every variation.
What role?
Primary source, second source, capacity support, development source or not suitable. A supplier name is not a strategy.
What should the commercial setup absorb?
Use price, delivery cadence, lead time and capacity commitments to absorb uncertainty rather than move it into stock.
What carries forward?
Reuse what is already proven: component, interface, qualification, evidence or commercial terms.
The product can stay custom.
The supply model should not restart from zero.
The supply model should not restart from zero.
That is the one idea I wanted to add after our conversation.
01 · Public context behind my thinking
Public contextBased on published NOVENCO material
NOVENCO is already using external subassembly to support production capacity.
NOVENCO's 2025 annual report makes the growth context more concrete than the job ad alone. The factory relocation was fully in place in the second half of 2024 and had a positive full-year effect in 2025. NOVENCO also focused on optimising internal processes and production, while an overseas subassembly cooperation has been active since mid-2025 to strengthen production capacity and mitigate Europe-U.S. trade barriers.
External subassembly adds sourcing questions.When an external partner carries subassembly work, I would want capability, capacity and handoff treated as part of the sourcing decision, not only as supplier performance metrics.
Trade exposure can change the trade-off.Cost, lead time, localisation, documentation and resilience can move together, not separately.
Qualification has to hold up in execution.Process, validation, evidence, data and handoff matter if a source is expected to carry real production responsibility.
My read: when an external source carries subassembly responsibility, supplier capability has a direct effect on capacity, resilience and execution. That is why I see this role as more than supplier selection: it is also about understanding which capabilities can be relied on and reused as NOVENCO scales.
Why this fits the roleThe current DTO brief asks for early supplier involvement, modular thinking, framework agreements and pricing structures for volatile demand, supplier segmentation, commonality and a scalable supplier base. Other current NOVENCO roles also mention increasing project complexity, scalable production and the balance between standard functionality and customisation. I would not assume these roles are part of one programme. I only take them as supporting context.
Sometimes a supplier choice affects the product trade-off.
Motors and drives are a simple public example. NOVENCO's technical documentation shows motor configurations from Nidec, Domel and Lafert together with defined Danfoss drive configurations. When a component can affect system performance, integration, validation effort and supply exposure, supplier choice belongs in the trade-off early. I would keep the technical decision with Engineering and use Sourcing to make capability, commercial and supply consequences visible while there is still room to choose.
02 · Three pieces of proof
How I already work.
Three short examples. No CV repetition.
I used the commercial setup to manage uncertainty.
Variable demand did not justify buying the whole forecast.
Recurring demand was variable. I used historical consumption, current production needs, stock, expected demand, supplier capability and lead time to shape the purchase. Negotiation covered price, quantity, cadence, lead time and conditions. Staged call-offs supported availability without taking the full forecast into stock.
Support availability without buying the full forecast.
I improved the process, not only the incident.
Recurring issues needed a better process between the two companies, not repeated expediting.
With a surface-treatment supplier, quality, documentation and reference misunderstandings kept returning. I created a more consistent contact route, clearer requirement checks and repeatable follow-up between the companies.
Relationship + process, not escalation alone.
I challenged with data, then supported the decision.
I can disagree, make the risk visible, respect the decision and still own the follow-through.
On a steel order, I checked market and production information, made the risk visible and gave my recommendation. My manager made the final call. I respected it and kept monitoring the risk afterward.
Challenge with facts. Keep authority clear. Own the follow-through.
Two smaller signals:Incomplete origin / conformity evidence meant stop, not “probably fine”. When commercial data did not reconcile, a wider check exposed 100+ affected items before a major quotation.
Negotiate firmly without losing the relationship.Commercial pressure and supplier trust have to coexist.
Challenge the value chain when the facts justify it.Not change for its own sake.
Stay with the decision after the meeting.The sourcing decision only matters if it holds up in execution.
03 · The step-up
Useful on day one. More independent as trust is earned.
From our conversation, I understood that the paper profile is not the whole decision. What matters too is trust, ability to learn, whether we can work well together and whether I can grow with the organisation.
Can I work upstream, not only operationally?
Yes. The core logic is familiar. The formal Global Sourcing scale is the step-up. My Planning, Quality and ERP exposure is useful because I understand the downstream consequences of a sourcing decision. The headline remains sourcing: supplier choice, commercial setup, development and risk.
Can I challenge without overstepping?
Yes. In my previous scope, Engineering owned technical approval and Quality owned final technical disposition. My role was to make supplier, commercial and supply consequences visible, own the follow-through within my scope, and escalate major commitments with analysis and recommendation.
What is new for me at NOVENCO?
That is where the step-up sits. The company-specific depth I would need to learn is NOVENCO's product range, how supplier segmentation and modular architecture are applied here, the IFS environment, NOVENCO's contract structures and Global Sourcing governance.
My aim is simple: be useful from day one.
Learn quickly, ask early where NOVENCO is new to me, and earn more ownership through the work.
Surface issues early.
Escalate with the decision point clear.
Escalate with the decision point clear.
If I come to you, I want the problem defined, the business impact visible, the facts checked, my recommendation ready and the decision I need from you clear.
Think beyond the supplier.Commercial choices have to work for Engineering, Quality, Planning and Production too.
Challenge with facts. Keep it constructive.The objective is a better business decision, not winning the argument.
Once aligned, execute.I can disagree, respect the decision and still own the follow-through.
Understand before changing.Learn the product, people and system before deciding what needs improvement.
04 · One useful first output
One way I would structure the decision.
A short view that makes the trade-off clear enough for the affected functions to choose a route, owner and next action.
DTO Supplier Decision BriefQuestion → evidence → route → owner
01 · Value
Why unique?
What customer, technical or regulatory value would be lost by simplifying?
02 · Source
What role + what proof?
Primary source, second source, capacity support or development source, backed by capability, capacity, quality and validation evidence.
03 · Commit
What fits the uncertainty?
Price / TCO, call-off structure, lead time, capacity commitment, allocation and escalation.
04 · Reuse
What carries forward?
Component, interface, tooling, qualification, evidence, supplier data or commercial terms.
Before execution: approved revision · supplier / item data · required Quality evidence · Planning assumption · clear owner.
KeepReuseDevelopSplit selectivelySimplifyReplace