Product, Offering and Roadmap
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.
Research draft, second pass
A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.
Bundle → Layer → Finding → Questions Missing, in the backlog
Not described yet. This gap is in the card backlog.
Note: Research contour: bundles not designed yet; questions are listed as open questions.
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 Derived, awaiting review
- An offering has a market and a period
- A price has a currency and a unit
- A roadmap item does not prove the existence of a feature
What robots and AI may and may not do Derived, awaiting review
Must not
- Negative case: A single pricing change creates a new software product.
Note: Negative case of the research brief, not yet a rule for agents.
Moral aspects Missing, in the backlog
Not described yet. This gap is in the card backlog.
Owners Filled
Steward
Руководитель продукта
Master systems
- Каталог продуктов
- discovery
- PLM
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 Incomplete
Identity and identifiers required Derived, awaiting review
- Product
- ProductFamily
- Offering
- PricePlan
- RoadmapItem
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Capabilities and actions required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Hazards and failure modes required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Standards and interfaces required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Context of use required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Sources Filled
- TM Forum SID: product/service/resource and commercial roles
- IDTA AAS: physical assets and composite descriptions
- Product management and engineering configuration; compare selected PLM and software practices
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
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.