For OEMs
Know which variants a change affects
You build customer-specific variants on a shared base. Verca shows what a change to the base actually affects.
Variant register
4 customer variants
PX-200-A
Nordwind AB
PX-200-B
Halden Marine
PX-200-C
Vestbo Energi
PX-200-D
Sundal Teknikk
One component swap, four variants
A component is discontinued and swapped in the base BOM, but only reaches the variants that inherit it.
Design change
Relay module RY-12Relay module RY-12B
Reason · Discontinued by the supplier
PX-200-A
Nordwind AB
EMC report and EU declaration no longer cover it
PX-200-B
Halden Marine
EMC report no longer covers it
PX-200-C
Vestbo Energi
Unaffected by the change
PX-200-D
Sundal Teknikk
Unaffected by the change
Spread through the variant tree
2 of 4 variants affected · 3 documents no longer cover
Responsibility shifts per variant
Whoever sells under their own name or trademark is regarded as the manufacturer. That may be you for one variant and the customer for the next.
- 01
Establish the role
For each variant, determine who sells under their own name. That decides who is the manufacturer in the regulatory sense.
- 02
Scope the variant
Define what separates the variant from the base platform: items, configuration and intended use.
- 03
Derive the requirements
Establish which legal acts and requirements follow from the deviation, and which are already covered by the base.
- 04
Connect the evidence
Inherit what applies to the base platform and produce what the variant needs on its own.
- 05
Handle the change
Judge whether a component swap is substantial and reassess the evidence it affects.
A structure that holds variants
The variant inherits the base platform's evidence and the variant-specific is marked. On a swap, Verca points out which variants are affected.
- Every variant linked to its base and its deviations
- Affected variants identified at every component swap
- Reassessments and customer sharing kept per variant
Change record
PX-200 · relay module swapped
Change
RY-12 replaced by RY-12B
Affected variants
2 of 4 identified
Reassessed evidence
EMC report and EU declaration
Inherited evidence
9 documents unchanged
Customer sharing
New evidence shared with 2 customers
History
Every variant keeps its own version
Built for customer-specific variants
BOM structure, requirements, documentation, change handling, sharing and monitoring, per variant. The base is inherited, the variant-specific is marked.
Verca structures, you decide
The platform holds variants, items and evidence together and shows what a change affects. The judgement on whether the variant still conforms stays with you.
Verca
Holds the variants together
- Structures base platform, variants and items
- Shows what is inherited and what is variant-specific
- Traces changes, reassessments and sharing
Your team
Owns the judgement
- Determines which role you hold for each variant
- Judges whether a change is substantial
- Decides whether the variant still conforms
Start with one variant family
Bring one base platform and the variants you have built on it. We will show you how inheritance, deviations and changes can connect in Verca.