|
EXTENSION SPECIFICS TECHNICAL CHARACTERISTICS v. 2.0.2 |
|
|
|
|
|
Business Opportunity and Business Needs |
|
|
Technical Data alignment between partners
of the supply chain (salesmen, buyers and logistic actors) is an essential
condition in the automation of the administrative treatments.
This alignment crosses the sending and
receiving of fact sheets containing, besides basic data and those relative to
the hierarchy of products, specific technical characteristics in finished or
semi finished products, allowing the specific item information needs of buyers
and salesmen to be met.
This basic information and the hierarchy is
already organized and structured.
The
objective of these works is to allow the standardization and the structuring of
the spBcific technical characteristics of items.
These fact sheets allow the sending of the
technical characteristics on behalf of the manufacturer without being seized
again by the distributor.
It allows to look for products with regard
to a range, or a feature, to use this information for an internal custom (i.e.
commercial, after sale services, etc.), or an external usage: (i.e. spread the
information with the partners and the end users).
The information is thus right, precise and
up to date; the risk of error is reduced and the adaptation of the data allows
an automation of the updates and the data processing.
Today, these technical characteristics are
sent in EDI by using the group of segments CCI-CAV-MEA of the message PRODAT.
The users want to exchange this information in XML. |
|
|
Business Intention |
|
|
The purpose of this message is to exchange
specific technical characteristics which are not listed in the GDD. Those
specific technical characteristics are coded by an agency, e.g. code 65
identifies GS1 FRANCE
(but any other MO can codify technical characteristics to respond to their
members’ needs).
This allows exchanging specific information
on products, information which does not exist in the GDD, and which are not
intended to be added into the GDD. The intention is not to add information
already existing in GDD. |
|
|
Business Justification |
|
|
If this extension for specific technical
characteristics does not exist, it means that a retailer will have to key in
the information, and a manufacturer will have to send different format of
specific technical characteristics to their clients with a large possibility to
have different ways to express the same information, as it has not been agreed
previously. (e.g. : maximum speed in mph or in km/h, etc…)
|
|
|
Audience |
|
|
Every
manufacturer, retailer or trader involved in the manufacture, the sale or the
referencing of products with the need to spread or to receive specific
technical information. Today, the
concerned sectors are the do-it-yourself, construction, household equipment (large
domestic appliance and consumer electronics, furniture), the textile (textile
industry) and the wines and the spirit, disc and soon automotive with the MRO
and others.
Example of
sector concerned: Building and construction sector wants to use it as a
Dictionary for the whole sector. |
|
|
Business Context |
|
|
Industry:
All
Geopolitical:
All
Product:
All
Process: Align Item Technical Characteristics
System
Capabilities:
EAN.UCC
Official
Constraints: None |
|
|
In Scope |
|
|
GS1 standards allows to exchange
information while using the GS1 standards, but it is mainly generic
information about products, like their weight, length, identification, and so
on.
The purpose of this Change Request is to
exchange more specific and more technical information about products
using GS1 standards, and without re-keying in the information because
it is not
possible to send the information using GS1 standards.
|
|
|
Immediate Phase |
|
|
There is only one phase: to create the
possible “fields” or extensions that will allow the transmission of specific
technical characteristics using GS1 standards. |
|
|
Subsequent Phases
|
|
|
No subsequent phase |
|
|
Out of Scope
|
|
|
It is not in the scope to transmit any
other information in this extension, which would already have been defined in GS1 standards. |
|
|
General Definition |
|
|
Initial Challenges |
|
|
The specifics technical characteristics are
extensions to be used with the core GS1 XML standards, these extensions are
conditional. |
|
|
Assumptions |
|
|
First the trading partners have to agree on
aligning their data.
To be successful, users have to support and
respect the GS1 rules and recommendations (e.g. When do I need to create a
new GTIN?). The users also have to agree to use the extensions for specific
technical Characteristics and to use GS1 XML recommendations. |
|
|
Dependencies |
|
|
Users are willing to use and respect the GS1 recommendations. They are also willing to align their data. Technical
characteristics have to be coded by a Member Organisation before being sent in
XML. |
|
|
Business Rules and Requirements
Analysis |
|
|
Business Requirements |
|
|
|
Number
|
Business Requirement
|
Rationale
|
|
1
|
ProductCharacteristics class with the following attributes and their
respective requirements is mandatory within the extension.
|
|
|
1.1
|
Class Name: ProductCharacteristics
Attribute Name: characteristicsCode
Cardinality: M
Multiple Occurrences: N
Type:
String
Size:
1..17
Definition: Code
assigned to a technical characteristic.
Example: “000006” for the characteristic
“Main Feature”
Business Rules: A code can be
used several times for different item, as long as the meaning of the
characteristic stays the same. Example: revolution per minute can be used for
washing machine and drill.
Validation Rules: Each
characteristic code has to be related to a CharacteristicsValue,
CharacteristicsMeasurement or CharacteristicsDescription.
External Code List Name GS1
recognised maintenance agency, as defined by
“categoryAgencyCode”
External Code List Source: GS1 recognised maintenance agency, as
identified in “categoryAgencyCode”
|
|
|
1.2
|
Class Name: ProductCharacteristics
Attribute Name: characteristicsCategoryCode
Cardinality: M
Multiple Occurrences: N
Type:
string
Size:
1..17
Definition: Code
assigned to a category of product.
Example: “13G” for DIY
Business Rules: Each code would be applied with the same
value across all sectors and verticals.
Validation Rules: The technical
characteristics are supposed to be reused in the same sector or verticals.
The characteristic code has to be taken as a whole to get its meaning.
External Code List Name GS1
recognised maintenance agency, as defined by
“categoryAgencyCode”
External Code List Source: GS1 recognised maintenance agency, as
identified in “categoryAgencyCode”
|
|
|
1.3
|
Class Name: ProductCharacteristics
Attribute Name: categoryAgencyCode
Cardinality: M
Multiple Occurrences: N
Type:
String
Size:
1..3
Definition: Code assigned to a categoryAgencyCode.
This is a string.
Example: “65“ for GENCOD EAN FRANCE
Business Rules: None
Validation Rules: None
External Code List Name 3055
External Code List Source: UN/CEFACT
|
|
|
2
|
Characteristic Value class
with and their respective requirements is a choice within the extension
|
|
|
2.1
|
Class Name: CharacteristicsValue
Attribute Name: characteristicsValueCode
Cardinality: M
Multiple Occurrences: Y
Type:
String
Size:
1..17
Definition: Value code of
a technical characteristics selected in the pre defined value list. Only the
characteristicsValueCode appears
Examples: “001” for Yes or “002” for No
Business Rules: A closed list
of possible values can have multiple occurrences. For example, to describe a
product it is possible to have to make reference one or more times to a
closed list of possible values : “Sound type” for a TV set can be 01 mono and
02 Stereo, and 03 Dolby Surround, etc… Only experts can provide this kind of
information in a working group.
Validation Rules: Each
characteristicValue has to be picked up from a predefined closed list of
values.
External Code List Name GS1
recognised maintenance agency, as defined by
“categoryAgencyCode”
External Code List Source: GS1 recognised maintenance agency, as
identified in “categoryAgencyCode”
|
|
|
|
|
Example
of application of the extension for a drill and its technical characteristics
(1 + 2) :
65
(identifying the Maintenance Agency here GENCOD EAN FRANCE)
13G
(identifying the characteristicsCategoryCode here : DIY)
00000109
(identifying the characteristic : here « Type of chunk »)
003 (identifying the value of the
characteristic : here « SDS ») *
004
(identifying the value of the characteristic : here « SDS+ »)*
005
(identifying the value of the characteristic : here « SDS
max »)*
* For a
drill we may have those three possible values for the type of chunk. |
|
|
|
3
|
CharacteristicsMeasurement class with the following attributes and
their respective requirements is a choice within the extension
|
|
|
3.1
|
Class Name: MeasurementValue
Attribute Name: unitOfMeasure
|
4
|
CharacteristicsDescription
class with and their respective requirements is a choice within the extension
|
|
|
4.1
|
Class Name: CharacteristicsDescription
Attribute Name: characteristicsDescriptionText
Cardinality: M
Multiple Occurrences: Y
Type:
String
Size:
1..70
Definition: Free
text of at least 70 characters
Example: For the characteristics 00006
“Main Feature” : “Best drill in the world with this new laser technology…
etc…”
Business Rules: A code can be
used several times for different product descriptions, as long as the meaning
of the characteristic stay the same
Validation Rules: None
External Code List Name : N/A
External Code List Source: N/A
|
|
Cardinality: M
Role:
characteristicsMeasurement
Multiple Occurrences: N
Type:
String
Size:
1..3
Definition: Measuring unit
abbreviation used in UN/ECE recommendation 20
Example: “RPM” for the
measuring unit : Revolution Per Minute
Business Rules: Each time a
measuring unit is needed to enable the product description, the measuring
unit has to be taken from the list of code UN/ECE recommendation 20
Validation Rules: Each
characteristic code using a measuring unit has to have one.
External Code List Name: recommendation 20
External Code List Source: UN/ECE
|
|
|
3.2
|
Class Name: MeasurementValue
Attribute Name: measurementValue
Cardinality: M
Role:
characteristicsMeasurement
Multiple Occurrences: N
Type:
Float
Size:
1..15
Definition: Value affected
to the characteristic. (e.g. : “10”)
Example: “10 000” for 10 000 Watt
Business Rules: As a
measurement is supposed to be fixed, it cannot have several occurrences for
the same code, or it would mean that there should be multiple possible
values, which implicitly means that there can be a minimum and a maximum for
example.
Validation Rules: None
External Code List Name : N/A
External Code List Source: N/A
|
|
|
|
|
Example
of application of the extension for a drill and its technical characteristics
(1 + 3) :
65
(identifying the Maintenance Agency here GENCOD EAN FRANCE)
13G
(identifying the characteristicsCategoryCode here : DIY)
00011627
(identifying the characteristic : here «Maximum Number of round per
minute »)
2000
(value float) |
|
|
|
4
|
CharacteristicsDescription
class with and their respective requirements is a choice within the extension
|
|
|
4.1
|
Class Name: CharacteristicsDescription
Attribute Name: characteristicsDescriptionText
Cardinality: M
Multiple Occurrences: Y
Type:
String
Size:
1..70
Definition: Free
text of at least 70 characters
Example: For the characteristics 00006
“Main Feature” : “Best drill in the world with this new laser technology…
etc…”
Business Rules: A code can be
used several times for different product descriptions, as long as the meaning
of the characteristic stay the same
Validation Rules: None
External Code List Name : N/A
External Code List Source: N/A
|
|
|
|
|
Example
of application of the extension for a drill and its technical characteristics
(1 + 4) :
65
(identifying the Maintenance Agency here GENCOD EAN FRANCE)
13G
(identifying the characteristicsCategoryCode here : DIY)
0000006
(identifying the characteristic : here «Main feature »)
“Best
drill in the world with this new laser technology… etc…” (value text) |
|
|
Business Process Analysis |
|
|
Business Process Participants
Descriptions |
|
|
For business process description see core item BMS |
|
|
Business Scenario Overview |
|
|
Current Business Scenario |
|
|
For business process description see core item BMS |
|
|
Proposed Business Scenario |
|
|
For business process description see core item BMS |
|
|
Structured Business Scenarios |
|
|
Structured Business
Scenario for Specifics Technical Characteristics |
|
|
For business process description see core item BMS |
|
|
Test Data |
|
|
|
Attribute
|
Value
|
|
categoryAgencyCode
|
65
|
|
characteristicsCategory
|
13G
|
|
characteristicsCode
|
000006
|
|
characteristicsDescription
|
Best drill in the world with this new laser
technology
|
|
|
|
|
|
|
TOP
|
|
|
|
|
