Product Lifecycle Management

BC-820 Level 1 Cross-Industry 22 providers 54 API surfaces 7 rated strong or better

End-to-end management of products from concept to retirement.

Product Lifecycle Management (BC-820) is a level-1 business capability in the Cross-Industry model. The catalog holds 54 API surface(s) from 22 provider(s) that can perform some part of it, 7 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 Concept Management BC-820.10

Concept development, ideation, market validation.

no catalog coverage

Product Design Management BC-820.20

Product design, engineering, design reviews.

1 provider, 5 API surfaces

Product Specification Management BC-820.30

Product specifications, requirements, BOM definition.

6 providers, 8 API surfaces

Product Configuration & Variant Management BC-820.40

Configurations, variants, options, bundles.

12 providers, 26 API surfaces

Product Release & Launch Management BC-820.50

Release planning, launch execution, ramp-up.

2 providers, 2 API surfaces

Product Performance & Feedback Management BC-820.60

In-life performance, customer feedback, product analytics.

no catalog coverage

Product End-of-Life Management BC-820.70

EOL planning, sunset, replacement strategies.

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.

Workflows that realise this capability

Arazzo workflows whose own sourceDescriptions call APIs that carry this capability. The link is derived, not asserted: each workflow declares x-realizes-capability-ids with the spec and confidence behind it.

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 Lifecycle 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 →