|
|
Application module:
Product concept identification |
ISO/TS 10303-1060:2004(E)
© ISO
|
This clause specifies the information requirements for the
Product concept identification
application module. The information requirements are specified as the
Application Reference Model (ARM) of this application module.
NOTE 1 A graphical representation of the information
requirements is given in
Annex C.
NOTE 2 The mapping specification is specified in
5.1. It shows how
the information requirements are met by using common resources and
constructs defined or imported in the MIM schema of this application
module.
The following EXPRESS specification begins the
Product concept identification schema.
EXPRESS specification:
*)
SCHEMA Product_concept_identification_arm;
(*
This subclause specifies the ARM entities for this
module. Each ARM application entity is an atomic element that
embodies a unique application concept and contains attributes
specifying the data elements of the entity. The ARM
entities and definitions are specified below.
A Market is the identification of a marketing segment for products.
EXPRESS specification:
*)
ENTITY Market;
name : STRING;
market_segment_type :
OPTIONAL
STRING;
END_ENTITY;
(*
Attribute definitions:
name:
the words by which the market is known.
market_segment_type:
the
text that identifies a marketing category of products.
EXAMPLE
'Luxury automobiles', 'laptop personal computers', and 'budget personal stereos' are examples of
market segment types.
The value of this attribute need not be specified.
A Product_concept is the identification of a set of similar products that were, are or will be proposed to customers.
NOTE 1
The definition of product concepts is driven by market and customer requirements and
forecasting. A Product_concept often corresponds to the highest level item(s) manufactured by an organization
for customers.
EXAMPLE 1
In an organization which manufactures cars and engines for cars, the car models will be represented by instances of Product_concept.
NOTE 2
The entity data type Product_concept enables to represent customer-oriented identification of products that are to be delivered to customers,
while the entity data type Product enables to identify and to track the history of items that are designed and manufactured,
as a tangible solution, or component of the solution, for a product concept.
NOTE 3
A product concept may be characterized by a set of product features identified by the customers or derived from
customers' needs.
NOTE 4
Depending on the kind of industry and products, a product concept might be offered to the customers in
one or many different configurations.
EXPRESS specification:
*)
ENTITY Product_concept;
id : STRING;
name : STRING;
description :
OPTIONAL
STRING;
target_market :
OPTIONAL
Market;
UNIQUE
UR1: id;
END_ENTITY;
(*
Attribute definitions:
id:
the
identifier for the Product_concept.
EXAMPLE 2
The id may be a sales model number.
name:
the words by which the Product_concept is known.
description:
the
text that provides further information about the Product_concept.
The value of the attribute need not be specified.
target_market:
the Market
for which the Product_concept
is intended. The value of the attribute need not be specified.
NOTE 5
In the MIM schema, the corresponding attribute is mandatory and refers to the entity data type product_concept_context. If target_market is not specified,
empty strings shall be assigned to the attributes name and market_segment_type of the instance of product_concept_context.
Formal propositions:
UR1:
there shall not be, in the data set, another instance of Product_concept with the same id.
Informal propositions:
IP1:
id and name shall not be both no-word strings.
*)
END_SCHEMA; -- Product_concept_identification_arm
(*
© ISO 2004 — All rights reserved
