Electrical Product Catalogue Management

BC-1940 Level 1 Electrical Components & Equipment 2 providers 3 API surfaces

Saleable product structure for electrical products — variants, configurator rules, jurisdictional SKUs, phase-in and phase-out, datasheets and marketing collateral.

Electrical Product Catalogue Management (BC-1940) is a level-1 business capability in the Electrical Components & Equipment model. The catalog holds 3 API surface(s) from 2 provider(s) that can perform some part of it. 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

Saleable Product Master Management BC-1940.10

Maintenance of saleable product master records and family hierarchies.

1 provider, 1 API surface

Product Variant & Option Management BC-1940.20

Management of voltage, frequency, protection, protocol, and accessory variants.

no catalog coverage

Product Configurator Rule Management BC-1940.30

Authoring and validation of configure-to-order rules.

no catalog coverage

Jurisdictional SKU Management BC-1940.40

Management of jurisdiction-specific SKUs, plug standards, and language variants.

no catalog coverage

Product Phase-In & Phase-Out Management BC-1940.50

Catalogue activation, replacement mapping, end-of-sale, and last-buy windows.

no catalog coverage

Product Documentation & Datasheet Management BC-1940.60

Authoring and maintenance of datasheets, manuals, and marketing collateral linked to SKUs.

1 provider, 1 API surface

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.

Developing 1 Usable, with meaningful gaps to close
RenesasProduct Part1 API43.4
Thin 1 Limited public surface area
HYPERLABSAdminDatasheetsProducts2 APIs28.3
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 Electrical Product Catalogue 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 →