← Back to catalogue
Published

Product, Offering and Roadmap

EM-PRD-01 · em-prd-01

The product as a managed outcome for a consumer, offering variants, prices and development intents. The physical instance, the software and the actual delivery have separate boundaries.

Enterprise profiles Enterprise subject EnterprisePRD

Bundle → Layer → Finding → Questions Filled

3 bundles · 3 layers · 4 findings · 9 questions

Product identity The product as a managed outcome for a consumer.

Product and family

What a product is and when an edition stays the same product.

Product boundary

The outcome the product delivers and to whom.

  1. Which consumer outcome does this product deliver, and who manages it?
  2. Is this product software, a physical device, a service or internal, and does that change its profile?
  3. Does this edition continue an existing product or form a new one?
Offering and price How the product is offered to markets and priced.

Offering

Variants offered in a market and period.

Market and period

Each offering with its market and validity.

  1. Which market and period does this offering cover?
  2. Did a pricing change alter the product, or only the offering?

Price plan

Prices with currency and unit.

  1. Which currency and unit of measure does this price use?
  2. Does the price plan impose a model, such as a subscription, that does not fit the product?
Roadmap Intended development, kept apart from commitments and facts.

Roadmap item

An intent with status, not proof of a feature.

Intent versus commitment

Roadmap items compared with contracts and releases.

  1. Is this roadmap item a plan, or has it been promised in a contract?
  2. Does the feature exist in a released version, according to delivery records?

Classifiers Filled

Family
Enterprise profiles
Category
Enterprise subject
Entry kind
subject
Domain
EnterprisePRD
Industry
Cross-industry
Tags
EM-PRD-01W1subjectProductProductFamilyOfferingPricePlanRoadmapItem

What it is Filled

The product as a managed outcome for a consumer, offering variants, prices and development intents. The physical instance, the software and the actual delivery have separate boundaries.

Why it exists Filled

The product as a managed outcome for a consumer, offering variants, prices and development intents. The physical instance, the software and the actual delivery have separate boundaries.

Distinguishing features Filled

  • A product is a managed outcome for a consumer; its physical units, software and deliveries are separate records.
  • An offering always has a market and a period, and a price has a currency and a unit.
  • A roadmap item states an intent and never proves that a feature exists.
  • Distinct from services and requirements, which describe provision terms and expected behaviour.

What robots and AI may and may not do Filled

Must not

  • Create a new software product because one pricing change was made.
  • Present a roadmap item to customers as an existing feature.
  • Treat a roadmap intent as a contractual obligation, or the reverse, without checking the contract.
  • Apply a subscription profile to a physical device by default.
  • Change a published price without recording its period.

Only with a human decision

  • Launching or retiring a product or offering.
  • Making roadmap commitments to a named customer.

May

  • List offerings of a product per market and period.
  • Compare roadmap items with released versions and contractual commitments.
  • Flag prices that lack a currency or unit.

Moral aspects Filled

  • Overstating roadmap items can mislead customers into purchase decisions.
  • Inconsistent prices and terms can cause financial harm and unfair treatment of customers.

Who is affected

  • Customers and users
  • Sales and support teams
  • Product teams

Owners Filled

Steward

The head of product who answers for the product definition and its catalogue entries.

Master systems

  • Product catalogue
  • Product discovery tool
  • Product lifecycle management system

Links to other meta-models Filled

neighbor

  • EM-COM-02
  • EM-COM-03
  • EM-FAC-02
  • EM-FIN-01
  • EM-FIN-05
  • EM-PEO-02
  • EM-PRD-02
  • EM-PRD-03
  • EM-RSK-01
  • EM-WRK-05

references

  • WM-ECO-021 - conceptual-candidate
  • WM-ACT-008 - conceptual-candidate

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Identified by a product identifier within the catalogue, with offerings identified by product, market and period.

Direct properties not applicable Not applicable

Not applicable

Enterprise record contour: physical properties belong to referenced world models.

Recognition optional Filled

  • A record names a consumer outcome, a product family, offerings and roadmap items.
  • Often confused with a SKU, a software repository or a service.

Capabilities and actions required Filled

  • Describe software, devices and internal products on one foundation.
  • Trace prices and offerings over time by market.

Hazards and failure modes required Filled

  • Product records multiplied by pricing or packaging changes.
  • Roadmap plans published as facts.

Standards and interfaces required Filled

  • TM Forum Information Framework (SID) for product, service and resource.
  • GS1 Global Trade Item Number for traded items.
  • Schema.org Product and Offer for published product data.
  • ISO 4217 currency codes.

Context of use required Filled

  • Used in catalogues, pricing, sales enablement and portfolio planning.
  • Consumer protection and advertising rules apply to published claims.

Sources Filled

  1. TM Forum SID: product/service/resource and commercial roles
  2. IDTA AAS: physical assets and composite descriptions
  3. Product management and engineering configuration; compare selected PLM and software practices
  4. United Nations Convention on Contracts for the International Sale of Goods - Carried over from the published world model wm-eco-021-offer-quote; checked live (HTTP 200) on 2026-10-09.
  5. UNIDROIT Principles of International Commercial Contracts 2016 - Carried over from the published world model wm-eco-021-offer-quote; checked live (HTTP 200) on 2026-10-09.
  6. Universal Business Language Version 2.3 - Carried over from the published world model wm-eco-021-offer-quote; checked live (HTTP 200) on 2026-10-09.

Open questions

  • When does an edition continue a product, and when does it form a new one?
  • How is a roadmap promise separated from a contractual obligation?
  • How are a free, an internal and a physical product described on one foundation?
  • Установить границу и решение reuse/extend/new по действующим спецификациям.
  • Подтвердить semantic crosswalk, права и source mastership.
  • Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.

Machine files

Provenance

enterprise research programme · published-partial

Built from: enterprise/models/em-prd-01/brief.json, ver-cy/world-models/card-supplements/em-prd-01.json

Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.