Product Lifecycle Management › Product Configuration & Variant Management
Product Configuration & Variant Management
BC-820.40
Level 2
Cross-Industry
24 providers
42 API surfaces
11 rated strong or better
Configurations, variants, options, bundles.
Product Configuration & Variant Management (BC-820.40) is a level-2 business capability under Product Lifecycle Management in the Cross-Industry model. The catalog holds 42 API surface(s) from 24 provider(s) that can perform some part of it, 11 of them rated strong or better. Reach is the vendor surface that lands on this capability — it is not a claim about what any particular organisation has deployed.
Where this capability definition comes from.
This capability is part of a published business-architecture model that API Evangelist
did not author. It is redistributed here under
CC-BY-4.0.
Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0
Changes: Consolidated from 333 per-L1 YAML files into one JSON; English only (upstream i18n/ omitted); descriptions whitespace-normalised. No capability was added, removed, renamed or re-parented.
Source repository · NOTICE and third-party framework attributions
Sub-capabilities
Product Configuration Modelling BC-820.40.10
Configuration models, options, and rules.
no catalog coverage
Variant Management BC-820.40.20
Management of product variants and platforms.
no catalog coverage
Bundle and Solution Definition BC-820.40.30
Definition of bundles, kits, and combined solutions.
no catalog coverage
Providers that reach this capability
Ordered by rating band. Reach means a provider publishes an API surface that can perform
some part of this capability — it is not a claim that any particular
organisation has deployed it.
Exemplar
7
Complete, well-documented, and agent-ready
Strong
4
Solid coverage with minor gaps
Developing
9
Usable, with meaningful gaps to close
Thin
4
Limited public surface area
This page carries no rating. Capabilities are not rated. A capability is a description of what a business does, not a thing a company publishes, so a Kin Score would have nothing to measure.
The edge table is a Pro feature.
This page shows
which providers and tags reach Product Configuration & Variant Management. The underlying
tag → capability edges — each with the quoted fragment of the provider's own
OpenAPI that evidences it, a calibrated confidence score, and the contract-provenance gate
it passed — are available through the API, along with company-level capability maps.
Only edges at confidence ≥ 0.7 with evidence found verbatim in
the source contract are published at all.
See plans →
·
How the edges are graded →