PRIHIR Product Information Message for Hire Working

Transcription

1 PRIHIR Product Information Message for Hire Working Subset for application in the European Steel Industry only for hire working activities Version May 1995 Corporate Factory Ph. D. Sarraute EDIFER WORKING GROUP - Message development

2 PRODUCT INFORMATION MESSAGE FOR HIRE WORKING (Table of Contents) 0. INTRODUCTION 2 1. DATA MODEL Data Model Format Data Model Diagram Data Model Entities Data Model Relationships Data Model Attributes SCOPE Functional Definition Field of Application Principles Message Usage MESSAGE DEFINITION Message Structure Mapping of the Data Model to the Message Branching Diagram of the Segments used by Eurofer General Description of the Message - Subset of Eurofer Detailed Description of the Message - Subset of Eurofer EXAMPLES Example of a Product Information message of Basic Products from 60 EKO Stahl to Krupp Hoesch Stahl 1

3 PRODUCT INFORMATION MESSAGE FOR HIRE WORKING 0. INTRODUCTION This document provides the definition of the EUROFER subset of the PRODUCT INFORMATION message to be used for hire working activities between steel producers. This message can be used to inform about the actual specifications of the basic products, including the parts of the product (sub-entities), the information about defects and welds. This message can also be used to given the actual specifications of the final products including sub-entities, and information on defects and welds. The decision, to use the same message for both types of products, has been taken by the EDIFER working group "Hire working activities" based on the data models of the basic product information message and the final product information message. Those data models are presented in the document " An EDI concept for hire working activities ". Therefore this message can be used for giving information about : - the actual specifications of basic products from the service requester to the service provider - the actual specifications of final products from the service provider to the service requester Consequently, therefore the wording "Basic product" and "Final product" have been replaced by "B / F product" in the document, meaning "Basic or Final product". The subset is based on the UN standard QALITY message of the UN/EDIFACT directory D93.A. This subset has been created by the EDIFER "Hire working activities" working group. The message is to be used in Electronic Data Interchange (EDI) between partners involved in the steel industry. The manual has been structured in the following format: - A Data Model definition describes the data entities, attributes and their relationships. - The scope describes the field of application, principles and message usage. - The message definition covers the structure, the entity/attribute mapping and how the data described in the data model relate to the message. - The message definition outlines the general structure of the message and specifies the use of each segment group and, or segment. - Based on the branching diagram of the original EDIFACT message "QALITY", the segments used are indicated. This is followed by a detailed segment description of the segments used by Eurofer. - Examples of Eurofer messages of some Product information sheets in a hire working relationship between steel producers are provided to clarify the understanding of the message description. 2

4 1. DATA MODEL 1.1 Data Model Format The data model of this Product information message has been created based on the global data model for hire working and is based on the information requested by the European Steel industry for the specifications of basic products or final products in hire working activities. The data model has been created, to make it possible for the potential users to understand the Eurofer subset for the Product information message for hire working. This data model gives the following information : - contents of the information (data elements) that can occur in the message, - relationships between the different data elements, - grouping of the data elements in data entities, - and the relationship between data entities. To simplify the understanding of the data model, the model is defined at a summary level, specifying when necessary a group of data elements instead of each data element. The data model consists of data entities, the relationships between those data entities and the attributes (data elements) in each data entity. An entity specifies an object against which information is held, it has a name, a description and attributes. An attribute describes a unique characteristic (information which can appear on the order sheet), it has a name, a description and a value. The relationships of the data entities within the data model are reflected in the structure of the diagram in chapter

5 1.2 Data Model Diagram B / F product Information message 1 Relates to 1,N 1 B / F product unit 1 1 Has Consist of Has 0,N Order Attribution 0,1 Refers to 1,N B / F product Sub-entity N Refers to 0,N B / F product Defect/Weld 1 Has 0,1 Ordering 0,1 Basic product unit 0,N B / F product Defect/Weld Remark B / F product = Basic or Final product Reference to Reference to Reference to Reference to Hire working Other Rules & Customer's Partner Company Agreements Order 4

6 In this diagram, the rectangles represent a data entity and the ovals show us the relationship between two data entities. How often a relationship can exist between two data entities is given in both direction and specified as 0, 1, N. - 0 means that there is no relationship between the entities. - 1 means that there is one and only one relationship between the entities. - N means that there are many relationships between the two entities. - 0,1 means that there can be no or one relationship between the two entities. - 1,N means that there can be one or many relationships between the entities. - 0,N means that there can be no or many (one or more) relationships between the two entities. Example relationship between B / F product unit and B / F product Defect/Weld 1. In the direction from B / F product unit to B / F product Defect/Weld. A B / F product unit can have no, one or more B / F product Defects or Welds. 2. In the direction from B / F product Defect/Weld to B / F product unit. A B / F product Defect/Weld always belongs to one B / F product unit. 5

7 1.3. Data Model Entities Because the data entities Hire working Partner, Other Company, Rules & Agreements and Customer's Order are not really basic information in this message, they have been put outside the data model and they are treated as related data entities.this has been done to simplify and not to overload the data model, so that the data model is easier to understand. The entities are regrouped in two groups. The first group includes all the basic data entities and the second the related data entities. The following entities are contained within the data model. The basic data entities B / F PRODUCT INFORMATION MESSAGE B / F PRODUCT UNIT B / F PRODUCT SUB-ENTITY B / F PRODUCT ORDER ATTRIBUTION B / F DEFECT/WELD B / F DEFECT/WELD REMARK The related application area ORDERING The related data entities HIRE WORKING PARTNER OTHER COMPANY RULES & AGREEMENTS CUSTOMER's ORDER B / F PRODUCT This entity contains the general information about a message INFORMATION reporting on B / F products. MESSAGE B / F PRODUCT UNIT B / F PRODUCT SUB-ENTITY This entity contains the general production information about a basic or final product, such as material number, serial number, production date, size, weights, etc... This entity contains the production information of each part consisting of a B / F product unit. For example a colled rolled coil having two different parts. 6

8 B / F PRODUCT ORDER ATTRIBUTION B / F PRODUCT DEFECT/WELD B / F PRODUCT DEFECT/WELD REMARK this entitiy gives information about the quantity of the B / F product unit that is attributed to a certain order or order item for the production of the final product (order). This entity gives the defect type, value, size and the location of the defect on the B / F product. This entity is also used to give information about the weld, dividing the sub-entities of the B / F product unit. This entity is used to give the description of a defect or a weld on the B / F product unit. HIRE WORKING This entity contains the name, address and contact persons of the PARTNER partners involved in the hire working activities. This can be the service requester and the service provider. OTHER COMPANY RULES & AGREEMENTS CUSTOMER's ORDER Another organisation with whom we deal for whatever purpose. This can be the buyer, the selling agency, inspection authority and so on. This entity contains all the rules and agreements that are valid for the production of steel products in function of a hire working contact. For example despatch limitations, restrictions of a production line. The entity contains the information about the final products ordered by the customer to the steel plant acting as the service requester. The related Application area : ORDERING A basic or final product unit can be attributed to an order, an order item or to an order itemproduction schedule detail. That means that the basic and final product unit relates to the ordering area. Further information about the entities of the application area Ordering and their relationship between the entities can be found in the document " An EDI concept for hire working activities". 7

9 1.4. Data Model Relationship B / F PRODUCT INFORMATION MESSAGE - B / F PRODUCT UNIT (relation : relates to - 1/1,N) - Direction from B / F product information message to B / F product unit. A B / F product information message can relate to one or more B / F product units. - Direction from B / F product unit to B / F product information message. A B / F product unit always belongs to one B / F product information message. B / F PRODUCT UNIT - B / F PRODUCT SUB-ENTITY (relation : consists of - 1/1,N) - Direction from B / F product unit to B / F product sub-entity. A B / F product unit consists of one or more B / F product sub-entities. - Direction from B / F product sub-entity to B / F product unit. A B / F product sub-entity belongs only to one B / F product unit. B / F PRODUCT UNIT - B / F PRODUCT ORDER ATTRIBUTION (relation : has - 1/0,N) - Direction from B / F product unit to B / F product order attribution. A B / F product unit can have no B / F product order attribution, or can have one or several B / F product order attribution (orders or order item for a certain tonnage). - Direction from B / F product order attribution to a B / F product unit. A B / F product order attribution can only be related to one B / F product unit. (Remark : A final product unit can not be attributed to more than one order attribution. For final product units the relation is 1/0,1 ) B / F PRODUCT ORDER ATTRIBUTION - ORDERING (relation : reference to - 0,1/0,1) - Direction from B / F product order attribution to Ordering. A B / F product order attribution can only refer to one Ordering. This attribution can be at the level of the Order, Order item or Production schedule detail. - Direction from Ordering to B / F product order attribution. An Ordering (Order, Order item or Production schedule detail) cannot have a B / F product order attribution or can have one or more B / F product order attribution. 8

10 B / F PRODUCT UNIT - B / F PRODUCT DEFECT/WELD (relation : has - 1/0,N) - Direction from B / F product unit to B / F product Defect/Weld. A B / F product unit can have no or one or more B / F product Defects or Welds. - Direction from B / F product Defect/Weld to B / F product unit. A B / F product Defect/Weld always belongs to one B / F product unit. B / F PRODUCT DEFECT/WELD - B / F PRODUCT DEFECT/WELD REMARK (relation : has - 1/0,N) - Direction from B / F product Defect/Weld to B / F product Defect/Weld remark; For a B / F product Defect/Weld we can have no remarks, or one or more B / F product Defect/Weld remarks. - Direction from B / F product Defect/Weld remark to B / F product Defect/Weld. A B / F product Defect/Weld remark belongs always to one B / F product Defect/Weld. 9

11 1.5. Data Model Attributes For each entity specified under point 1.3. Data model entities, a list of attributes and a description is given. ENTITY : B / F PRODUCT INFORMATION MESSAGE product information message number Unique number to identify the product information message. product information message date/time Date when the product information was issued. ENTITY : B / F PRODUCT UNIT material number of the basic or final product Unique number given by the producer to a basic or final product. serial number of the basic or final product Unique number given to a basic or final product unit (as mentioned on the transport label). cast number of the basic or final product Unique number identifying the cast of which the basic or final product unit was produced. production date of the basic or final product Date when the basic or final product unit was produced. net weight of the basic or final product Net weight of the basic or final product unit. gross weight of the basic or final product Gross weight of the basic or final product unit. outside diameter of the basic or final product Outside diameter of the basic or final product unit. inside diameter of the basic or final product Inside diameter of the basic or final product unit. dimensions of the basic or final product Length, width and thickness of the basic or final product unit. product information of the basic or final product Informations as chemical, mechanical and physical properties, material numbers and so on. 10

12 ENTITY : B / F PRODUCT SUB-ENTITY product sub-entity identification Number attributed to a part of a basic product unit or final product unit coming from different production units. For example a hot roll produced out of two slabs. product sub-entity location Starting- and end position of the sub-entity in the basic product unit or final product unit. product sub-entity marking type Code identifying the way how the start- and end position of the sub-entity is marked. Product information of the product sub-entity Information as chemical, mechanical and physical properties, material numbers (such as cast number, hot roll number) can also be present in this entity. ENTITY : B / F PRODUCT ORDER ATTRIBUTION order attribution code Code identifying the level on which the basic product unit or final product unit is attributed. This can be at the level of the order, order item or production schedule detail. quantity affected The quantity affected of the basic product unit to the order, order item or production schedule detail. ENTITY : B / F PRODUCT DEFECT/WELD defect/weld type Code indicating a defect or a weld. defect/weld location Information about the starting- and ending position of a defect or the position of a weld in the B / F product unit.the defect can be located in three dimensions and on the upper- or lower side. 11

13 ENTITY : B / F PRODUCT DEFECT/WELD REMARK defect/weld remark subject qualifier Code specifying the subject of the response remark, for example on defect specification or weld specification. defect/weld remark A remark can be given as a code or as a clear text. defect value The value of the defect mentioned by the defect/weld remark. 12

14 2. SCOPE 2.1. Functional Definition This message is used by the service requester to inform the service provider about the actual specifications of the basic product units. The same message is also used by the service provider to inform the service requester about the specifications of the final product units. The message is not limited to the actual specifications of the product, but allows also to transmit the welds or the detected defects of each product. If the message is used to specify all detailed information on the final product, the message allows also to give the relation between the final product unit (sub-entity) and the basic product unit(s) Field of Application This message provides the definition of the Eurofer Basic or Final product information message to be used in Electronic Data Exchange between European steel companies within a hire working relationship Principles The Product information message in a hire working relationship has been created as a subset of the UNSM QALITY message of EDIFACT. This message allows to transmit the specification of the basic or final product units, but does not allow to transmit the quality data information or the test results obtained by testing on samples. To transmit quality data information use the Eurofer subset of the Quality data message (User implementation guide QALITY). When the message is used to give the specifications of each basic product unit, the detailed information of each sub-entitiy, and the order attribution are established by using the subline technique. When the message is used to give the specifications of each final product unit, the detailed information of each sub-entity with the relation to the basic product unit can be given by using the sub-line technique. To give detailed information on the product specifications and the defects or welds, the segments CCI (Characteristic) and MEA Measurements) are used. 13

15 2.4. Message Usage The Product information message can be used to convey the information about the specifications of the basic or final products. This message can be sent together with the despatch advice message or can be sent before or after the despatch advice message. Normally for basic products, the information will be given before or together with the despatch advice message. This allows the service provider to check if the basic products can be used to realise the requested specifications given in the order message. When the basic product units are fulfilling the needs, it allows the service provider to generate his global production planning. But for final product units, in most of the cases the information on the final product units will be given before the despatch of the final products to the consignee, specified by the service requester. This approach allows the service requester to control if the final product produced by the service provider meets the specifications, specified by the customer, and if necessary allows the service requester to request supplementary samples. 14

16 3. MESSAGE DEFINITION 3.1 Message Structure The Quality Data message of UN/EDIFACT is structured in two sections, a Heading Section and a Detail Section Message structure - Heading section The heading section is used to give the general information relating to the whole message. Examples of this kind of information are Document number, date of the document, Type of document and Originator of the document. The heading section can also be used to give information which has the same content for each line of the detail section. Examples of this kind of information are description of the product, buyer's order number, despatch advice number, despatch advice date and so on Message structure - Detail section The detail section is controlled by the segment group 5 with the mandatory segment LIN and the message can have a maximum of 200 segments groups. Each line in the detail section provides information about the relevant product information for the product identified in the LIN segment. The detail line can be used to specify the product specifications of the basic / final product units but can also be used to specify the relevant specifications for the product sub-entities. To satisfy this requirement sub-lining in the LIN segment is used. Detailed information at the product sub-entity level can only be given by using for each product sub-entity a sub-line in the LIN segment group. The dependent segments and segment groups of the LIN segment are used to give the relevant information about product, references, chemical, mechanical and physical properties of the product unit or product sub-entity. By the use of the sub-line in the LIN segment it is possible to create a product information message, which can represent the product hierarchy in different ways. The possible ways are: a. all the product specifications are reported on the product unit level and no information is given on the product sub-entity level (sub-line in the LIN segment not used) ; b. some of the product specifications are reported on the product unit level and other specifications are reported on the product sub-entity level (e.g. a cold rolled final product unit was produced out of two hot rolled basic product units, subline in the LIN segment used for the product sub-entities), 15

17 c. some of the product specifications are reported at a higher level than the product unit level and the other specifications are given at the product unit level (e.g. four slabs as basic product units produced from the same heat. The chemical analysis are given at the heat level and the other specifications are reported at the product unit level (subline in the LIN segment is used for the product units). By using the segment group 12 (CCI segment group) it is possible to report on : - the product specifications - the order attribution of a basic product unit to several order items - the defect/weld type, location, value and remarks. Some of the product specifications, as dimensions, diameters and weight can be provided in the MEA segment of the LIN segment group without using the segment group 12 (CCI segment group). The usage of the LIN segment group and the sub-lining To use one of the possibilities, must always be a mutual agreement between the partners involved in the transaction. a. The results are reported only at the product unit level In this case the possibility of sub-lining is not used in the LIN segment. This means that all the product information (chemical, mechanical or physical properties) are given on the level of each product unit (detail line), even when they are informations related to the sub-entity level of the product unit. By referencing to other final product units (detail lines), for chemical, mechanical or physical properties, it is possible to associate the relevant information to one or more final product units. If the technique of backward referencing in the message is used, handling of the received information is difficult without special agreement of the partners involved. It may be more convenient for trading partners to duplicate the data at each detail line. b. Some product specifications are reported on the product unit level and others are reported at the product sub-entity level In this case the possibility of sub-lining is used in the LIN segment. This means that in the detail section, the message starts at the basic or final product unit for which there is relevant information (chemical, mechanical or physical properties) to be given. This first LIN segment group is followed by additional LIN segment groups with sub-lines for the specifications of each product sub-entity. In each sub-line of the LIN segment group information can be given of the semi-finished products for which the basic or final product unit has been produced. 16

18 To make it more understandable, we have provided the following example ; - a cold rolled coil (final product unit) with product information - this cold rolled coil is produced out of two hot rolled coils (basic product units), for each coil solution : - cold roll coil 1st LIN segment Cold rolled number, no sub-line - first sub-entity 2nd LIN segment Hot rolled number, sub-line = 1 (from the first hot rolled coil) Location of the hot rolled material in the cold rolled coil - second sub-entity 3rd LIN segment Hot roll number, sub-line = 1 (from the second hot rolled coil) Location of the hot rolled material in the cold rolled coil c. Some of the product specifications are reported at a higher level than the product unit level In this case the possibility of sub-lining is used in the LIN segment. This means that in the detail section, the message starts at the highest level with the primary product unit for which there is relevant information (chemical, mechanical or physical properties) to be given. Followed with lower level information for basic product units or final product units. To make it more understandable, we have provided the following example ; - a heat with chemical analysis, - three hot rolled coils, as basic product units, are produced from the heat solution : - heat 1st LIN segment Heat number, no sub-line - first hot rolled coil 2nd LIN segment Hot rolled number, sub-line = 1 - second hot rolled coil 3rd LIN segment Hot rolled number, sub-line = 1 - third hot rolled coil 4rd LIN segment Hot rolled number, sub-line = 1 17

19 The usage of the CCI segment group - Product specifications To report on the product specifications the segment CCI of group 12 and the segment MEA of group 14 is to be used. The segment CCI can be used to identify the type of properties ( chemical, mechanical, physical) and the measurement data are given in the segment MEA, by specifying the element and the value. If the specification (element) is not foreseen in the code list of data element 6313 (measurement dimension, coded) of segment MEA, it is necessary to use the segment CCI to specify the product detail. In this case the segment CCI must specify the product detail by using the code list PDS (Product detail specifications) of Eurofer. The value for this product detail is to be given in the segment MEA. - Order attribution of a basic product unit to several order item To give the necessary information on the order attribution of a basic product unit to more than one order item it is necessary to use the segment CCI of segment group 12, the segment MEA of segment group 14 and the segment RFF of segment group 15. In the segment CCI the specification detail "Order attribution" is given by using the code list PDS of Eurofer. In the segment MEA the quantity attributed to the order item is specified. The segment RFF is used to identify the order item. - The defect/weld type, location, value and remarks To give the relevant informations on the defects or welds, it is necessary to use also the segment groups 12 and 14. In the segment CCI the defect/weld type is to be specified by using the code list PDS of Eurofer. The segment FTX is used to give the remarks either in a structured- or free text format. The segment MEA is in this case used to give the location (ending and starting position) and if necessary also the value of the defect. 18

20 3.2. Mapping of the Data Model to the Message For the understanding of the mapping process, done by the EDIFER working group, it is necessary to have the knowledge about the structure of the official UNSM QALITY message and the functionality of the segment groups and segments as defined by the EDIFACT message development group MD1 - Trade. To have the complete information about the official version we recommend the use of the official document published by UNITED NATIONS - EDIFACT directory D93.A. In following table a short overview is given about the meaning and the functionality of the segment groups and segments in the message. The information given covers : - the segment group - the segment - the description of the meaning and the functionality - the comments of the EDIFER working group SEGMENT GROUP SEGMENT FUNCTION HEADING SECTION COMMENTS BGM DTM IMD MEA To identify the Product information message by his number. To specify general date/time/period related to the whole message To describe the product involved, when it is relevant for all the items of the message. To allow physical measurements and dimensions to be stated, where it is required for identification of the product. Mandatory. FTX Free text information Not used. Must be used at least once to identify the Date of the product information message. Only to be used if the information is relevant for all the items. Not used. GROUP 1 RFF DTM To specify referencing documents and their date, related to the whole message. To identify the referenced document To specify the date time of the referenced document. Only to be used if the information is relevant for all the items. GROUP 2 GROUP 3 GROUP 4 To identify the parties (companies) relevant to the whole message. Only to be used if the information is relevant for all the items. NAD Function, name and address of the company LOC To indicate locations related to the company Not used. (RFF, To specify referencing documents and their date Not used. DTM) related to the company (CTA, To give contact details of the company Not used. COM) 19

21 SEGMENT GROUP SEGMENT FUNCTION DETAIL SECTION COMMENTS GROUP 5 To provide the relevant product information data Must be used at least once. for the specified product. LIN To identify the line item by its number and additionally, identifying the product involved by a product identification number. PIA To provide additional product identification of the product involved. IMD To describe the product involved. MEA To allow physical measurements and dimensions to be stated, where it is required for identification of the product. PSD To define the physical sample parameters, Not used. associated with a test. SPS To define the sampling parameters associated Not used. with summary statistics. DTM To specify date/time details to the line item QTY To specify quantity information. Not used. FTX Free text information Not used. GROUP 6 RFF DTM To specify referencing documents and their date, relating to the line item.. To identify the referenced document To specify the date time of the referenced document. GROUP 7 GROUP 8 GROUP 9 GROUP 10 GROUP 11 To identify the parties (companies) relevant to the line item only. NAD Function, name and address of the company LOC To indicate locations related to the company Not used. (RFF, To specify referencing documents and their date Not used. DTM) related to the company (CTA, To give contact details of the company Not used. COM) TEM MEA To provide details of the test methods, employed including any circumstances, test devices, references and dates. To describe the nature of test performed. To provide the necessary values of the circumstances related to the tests. Not used. Not used. DTM To specify the date/time of an activity. Not used. (RFF, To specify referencing documents and their date, Not used. DTM) relating to the test method. 20

22 SEGMENT GROUP SEGMENT FUNCTION COMMENTS GROUP 12 GROUP 13 GROUP 14 GROUP 15 GROUP 16 (including GROUP 17) GROUP 18 GROUP 19 To define a class of properties, the individual properties within that class CCI To specify the general, class and/or the Gives the possibility to split up the individual properties on which the product product informations in the chemical, information is being reported. mechanical or physical properties. PSD To define the physical sample parameters, Not used. associated with a test, the values only apply to data within the same analysis group. SPS To define the sampling parameters associated Not used. with summary statistics, the values only apply to data within the same analysis group. DTM To specify the date/time of an activity. Not used. FTX Free text information Used for Defect/Weld remarks. (RFF, To specify referencing documents and their date Not used. DTM) relating to the analysis group. To allow measurement values or specification values to be specified along with their associated references and dates. MEA To specify discrete values, other measurement results or specification values. DTM To specify the date/time of an activity. Not used. (RFF, To specify referencing documents and their date Used for order attribution. DTM) relating to the specifications and the values. (STA, To provide the necessary information for Not used. DTM) summary statistics with any related references (RFF,DTM) and dates. To provide details of the test methods, employed including any circumstances, test devices, references and dates. TEM To describe the nature of test performed. MEA To provide the necessary values of the circumstances related to the tests. DTM To specify the date/time of an activity. Not used. (RFF, DTM) To specify referencing documents and their date, relating to the test method. Not used. GROUP 20 (including GROUP 21, GROUP 22) (GIN, DTM) (RFF,DTM) To enable to specify batch related quality data information. Group 22 has the same structure as group 12. Not used. 21

23 SEGMENT GROUP SEGMENT FUNCTION COMMENTS GROUP 30 GROUP 31 GROUP 32 GROUP 33 GROUP 34 GROUP 35 GROUP 36 (including GROUP 37) GROUP 38 GROUP 39 To allow to specify process related product Not used. information. PRC To specify a process/ sub-process to which Not used. quality data is related. (NAD, To indentify names, addresses and locations Not used. LOC) relevant to the process. To define a class of properties, the individual Not used. properties within that class, related to the process/sub-process. CCI To specify the general class and/or the Not used. individual properties on which the product information is being reported. PSD To define the physical sample parameters, Not used. associated with a test, the values only apply to data within the same analysis group. SPS To define the sampling parameters associated Not used. with summary statistics, the values only apply to data within the same analysis group. DTM To specify the date/time of an activity. Not used. FTX Free text information Not used. (RFF, To specify referencing documents and their date Not used. DTM) relating to the process/sub-process and to the analysis group. To allow measurement values or specification values to be specified along with their associated references and dates. MEA To specify discrete values, other measurement results or specification values. DTM To specify the date/time of an activity. Not used. (RFF, To specify referencing documents and their date Not used. DTM) (STA, DTM) (RFF,DTM) relating to the specifications and the values. To provide the necessary information for summary statistics with any related references and dates. To provide details of the test methods, employed including any circumstances, test devices, references and dates. Not used. TEM To describe the nature of test performed. MEA To provide the necessary values of the circumstances related to the tests. DTM To specify the date/time of an activity. Not used. (RFF, DTM) To specify referencing documents and their date, relating to the test method. Not used. 22

24 The mapping is done starting from the entities, relationships and attributes of the data model to the EDIFACT message. This mapping is presented as a table containing the entities of the following information ; - the attributes - the segment group number - the segment by his tag - the Edifact data element - remarks about the usage. ATTRIBUTE SEGMENT GROUP SEGMENT TDID - Data element REMARKS Entity : PRODUCT INFORMATION MESSAGE Product information message number BGM 1004 Product information message date/time DTM 2380 DTM segment in the header, following BGM. Entity : B / F PRODUCT UNIT Material number of the basic or final product Serial number of the basic or final product Cast number of the basic or final product Production date of the basic or final product Net weight of the basic or final product Outside diameter of the basic or final product Inside diameter of the basic or final product Dimensions of the basic or final product Product information Group 12 Group 14 Group 05 LIN or PIA 7140 Use the relevant code for element Group 05 LIN or PIA 7140 Use the relevant code for element Group 05 PIA 7140 Use the relevant code for element Group 05 DTM 2380 Use the relevant code for element Group 05 MEA 6314 Use the relevant code for Group 05 MEA 6314 Use the relevant code for Group 05 MEA 6314 Use the relevant code for Group 05 MEA 6314 Use the relevant code for CCI MEA 7059, Use the Eurofer code list PDS. Use the relevant code for Entity : B / F PRODUCT SUB- ENTITY Product sub-entity identification Group 05 LIN 7140 Use the relevant code for element Product sub-entity location Group 12 Group 14 CCI MEA 7059, Use the Eurofer code list PDS. Use the relevant code for Product sub-entity marking type Group 12 CCI 7059, 7037 Use the Eurofer code list PDS. Product information of the product sub-entity Group 14 Group 12 Group 14 MEA CCI MEA , Use the relevant code for Use the Eurofer code list PDS. Use the relevant code for

25 ATTRIBUTE SEGMENT GROUP SEGMENT TDID - Data element REMARKS Entity : B / F PRODUCT ORDER ATTRIBUTION Order attribution code Group 15 RFF 1153, 1154 Use the relevant code for element Quantity affected Group 14 MEA 6314 Use the relevant code for element Entity : B / F PRODUCT DEFECT/WELD Defect/weld type Group 12 CCI 7059, 7037 Use the Eurofer code list PDS. Defect/weld location Group 12 Group 14 CCI MEA 7059, 7037 Use the Eurofer code list PDS. Use the relevant code for Entity : B / F PRODUCT DEFECT/WELD REMARK Defect/weld remark subject qualifier Group 12 FTX 4451 Defect/weld remark Group 12 FTX 4441 or 4440 Code form or clear form can be used. Defect value Group 14 MEA 6314 Use the relevant code for Entity : HIRE WORKING PARTNER Service requester Group 2 NAD 3039 or C058 Service provider Group 2 NAD 3039 or C058 Code form or clear form can be used. Eurofer recommends to use the code form and the code of Eurofer. Code form or clear form can be used. Eurofer recommends to use the code form and the code of Eurofer. Entity : OTHER COMPANY Partners involved by service requester or service provider : Examples are buyer, consignee, sales office, etc... Group 2 or Group 7 NAD 3039 or C058 Code form or clear form can be used. Entity : CUSTOMER's ORDER Customer's order number Group 01 RFF 1154 Use the relevant code in or Group 7 element Customer's order date Group 01 or Group 7 DTM 2380 DTM segment following the RFF in the segment group. Part number Group 05 PIA 7140 Use the relevant code in element

26 3.3 Branching Diagram of the Segments used by Eurofer QALITY Quality Data message version D93A Message to enable the transmission of the results of tests performed to satisfy a specified product or process requirement. The codes used for the usage indicator (USG. IND.) for the segments. R for REQUIRED - Should always be used in the message O for OPTIONAL - May be used by trading partners if required. X for EXCLUDED - Not used in the message. Heading Section USG.IND. PAGE NUM. TAG NAME STATUS REPEATS GROUP REPEATS R 36 UNH Message header M 1 R 37 BGM Beginning of message M 1 R 38 DTM Date/time/period M 10 O 39 IMD Item description C 10 X MEA Measurements C 10 X FTX Free text C 5 O SEGMENT GROUP 1 C 10 R 40 RFF Reference M 1 O 41 DTM Date/time/period C 2 R SEGMENT GROUP 2 C 10 R 42 NAD Name and address M 1 X LOC Place/location identification C 5 SEGMENT GROUP 3 C 10 X RFF Reference M 1 X DTM Date/time/period C 2 SEGMENT GROUP 4 C 5 X CTA Contact information M 1 X CO M Communication contact C 5 Detail Section USG.IND. PAGE NUM. TAG NAME STATUS REPEATS GROUP REPEATS SEGMENT GROUP 5 C 200 R 44 LIN Line item M 1 O 45 PIA Additional product id C 10 O 47 IMD Item description C 10 O 48 MEA Measurements C 10 X PSD Physical sample description C 1 X SPS Sample parameters for summary stat C 1 O 49 DTM Date/time/period C 10 X QTY Quantity C 10 X FTX Free text C 5 25

27 USG.IND. PAGE NUM. TAG NAME STATUS REPEATS GROUP REPEATS O SEGMENT GROUP 6 C 10 R 50 RFF Reference M 1 O 51 DTM Date/time/period C 2 O SEGMENT GROUP 7 C 10 R 52 NAD Name and address M 1 X LOC Place/location identification C 5 SEGMENT GROUP 8 C 10 X RFF Reference M 1 X DTM Date/time/period C 2 SEGMENT GROUP 9 C 5 X CTA Contact information M 1 X CO M Communication contact C 5 X SEGMENT GROUP 10 C 100 X TEM Test method M 1 X MEA Measurements C 10 X DTM Date/time/period C 10 SEGMENT GROUP 11 C 10 X RFF Reference M 1 X DTM Date/time/period C 2 R SEGMENT GROUP 12 C 200 R 54 CCI Characteristic/class id M 1 X PSD Physical sample description C 10 X SPS Sample parameters for summary stat C 10 X DTM Date/time/period C 10 O 55 FTX Free text C 10 SEGMENT GROUP 13 C 10 X RFF Reference M 1 X DTM Date/time/period C 2 O SEGMENT GROUP 14 C 100 R 56 MEA Measurement M 1 X DTM Date/time/period C 10 O SEGMENT GROUP 15 C 10 R 58 RFF Reference M 1 X DTM Date/time/period C 2 SEGMENT GROUP 16 C 100 X STA Statistics M 1 X DTM Date/time/period C 10 SEGMENT GROUP 17 C 10 X RFF Reference M 1 X DTM Date/time/period C 2 X SEGMENT GROUP 18 C 100 X TEM Test method M 1 X MEA Measurements C 10 X DTM Date/time/period C 10 SEGMENT GROUP 19 C 10 X RFF Reference M 1 X DTM Date/time/period C 2 26

28 USG.IND. PAGE NUM. TAG NAME STATUS REPEATS GROUP REPEATS SEGMENT GROUP 20 C 100 X GIN Goods identity number M 1 X DTM Date/time/period C 10 SEGMENT GROUP 21 C 10 X RFF Reference M 1 X DTM Date/time/period C 2 SEGMENT GROUP 22 C 200 X CCI Characteristic/class id M 1 X PSD Physical sample description C 10 X SPS Sample parameters for summary stat C 10 X DTM Date/time/period C 10 X FTX Free text C 10 SEGMENT GROUP 23 C 10 X RFF Reference M 1 X DTM Date/time/period C 2 SEGMENT GROUP 24 C 100 X MEA Measurement M 1 X DTM Date/time/period C 10 SEGMENT GROUP 25 C 10 X RFF Reference M 1 X DTM Date/time/period C 2 SEGMENT GROUP 26 C 100 X STA Statistics M 1 X DTM Date/time/period C 10 SEGMENT GROUP 27 C 10 X RFF Reference M 1 X DTM Date/time/period C 2 SEGMENT GROUP 28 C 100 X TEM Test method M 1 X MEA Measurements C 10 X DTM Date/time/period C 10 SEGMENT GROUP 29 C 10 X RFF Reference M 1 X DTM Date/time/period C 2 X SEGMENT GROUP 30 C 100 X PRC Proces identification M 1 SEGMENT GROUP 31 C 10 X NAD Name and address M 1 X LOC Place/location identification C 5 X SEGMENT GROUP 32 C 200 X CCI Characteristic/class id M 1 X PSD Physical sample description C 10 X SPS Sample parameters for summary stat C 10 X DTM Date/time/period C 10 X FTX Free text C 10 27

29 USG.IND. PAGE NUM. TAG NAME STATUS REPEATS GROUP REPEATS SEGMENT GROUP 33 C 10 X RFF Reference M 1 X DTM Date/time/period C 2 X SEGMENT GROUP 34 C 100 X MEA Measurement M 1 X DTM Date/time/period C 10 SEGMENT GROUP 35 C 10 X RFF Reference M 1 X DTM Date/time/period C 2 SEGMENT GROUP 36 C 100 X STA Statistics M 1 X DTM Date/time/period C 10 SEGMENT GROUP 37 C 10 X RFF Reference M 1 X DTM Date/time/period C 2 X SEGMENT GROUP 38 C 100 X TEM Test method M 1 X MEA Measurements C 10 X DTM Date/time/period C 10 SEGMENT GROUP 39 C 10 X RFF Reference M 1 X DTM Date/time/period C 2 R 59 UNT Trailer M 1 28

30 29

31 3.4 General description of the message - subset of Eurofer Message definition and segment clarification This section is provided to give clarification and futher explanation to the usage of the segment within the message defined by Eurofer. The message is constructed from two sections, a heading section and a detail section. The heading section is representing the commercial details, the corresponding references and the parties involved. Some detail information which applies or relates to all the line items of the detail section can also be given in the heading section. This section should be read in conjuction with the segment usage and the branching diagram (chapter 3.3.) which indicate the required (R) and optional (O) segments and segments groups. The following guidelines and principles applies to the whole message of Eurofer and are intended to falicitate the understanding and the implementation of the message. All the specified data/times (segment DTM) should be in the format 'CCYYMMDD'/'hhmm' unless all parties involved in the transaction agree that there is a functional requirement for an alternative format. Periods should be specified as whole numbers representing the required period as indicated in the format qualifier (weeks, month, etc) Where a choice of code or text is given, only the code element should be used if possible. Optional (conditional) data that is not required in the message should not be included. Care must be taken out that the segment qualifier in dependent segments do not conflict with the segment qualifier of the trigger segment of the group. 30

32 3.4.2 Message description - Heading section Information to be provided in the heading section of the message. Segment UNH, Message Header A service segment starting and uniquely identifying a message. The message code for the EUROFER Product information message is "QALITY". Note : Product information messages conforming to this document must contain the following data in the segment UNH composite data element S009 with data elements ; QALITY D A EF PRIHIR Segment BGM, Beginning of message A segment by which the sender uniquely identifies the Product information message by means of its type and number. Segment DTM, Date/time/period A segment specifying general dates and/or when relevant dates/times/periods related to the whole message. This segment must exist at least once to identify the date of issue of the product information message. Segment IMD, Item description A segment for describing the basic product unit or final product unit, when it is relevant for all the line items of the whole message. For the Iron and Steel industry, this segment can be used to give the general description of the product group or a very detailed description. Item description given at the heading section are related to all the items given in the detail section. Segment group 1 : RFF-DTM A segment group for referencing documents and where necessary, their dates, relating to the whole message, e.g. Buyers order, despatch advice. Segment RFF, Reference A segment identifying the referenced document, message or information by its number and where appropriate, a line number within the document. Segment DTM, Date/time/period A segment specifying the date/time of the referenced document, message or information. 31

33 Segment group 2 : NAD-LOC-SG3-SG4 A group of segments identifying the parties relevant to the whole Product information message. Eurofer has decided to use only the segment NAD of this group. The other segments for giving associated information should not be used. Segment NAD, Name and address A segment identifying name and address of parties and their function relevant to the whole Product information message. The name and address can be given in a coded or clear form. Identification of the sender (service requester - provider) and the receiver party (service provider - requester) is mandatory for the Product information message. They are to be given in the NAD segment Message description - Detail section Information to be provided in the detail section of the message. Segment group 5 : LIN-PIA-IMD-MEA-DTM-SG6-SG7-SG12 A group of segments providing the relevant Product information for a product unit. Eurofer has decided to use only the segments LIN, PIA, IMD, MEA, DTM, and the segments groups SG6, SG7 and SG12. Segment LIN, Line item A segment identifying the line item by its unique line number and additionally, identifying the product or material by its identification number (e.g. serial number). Segment PIA, Additional product identification A segment providing additional product identification to the product or material specified in the LIN segment, e.g. Buyer's product identification number, Buyer's product group, Buyer's test number, Buyer's part number, etc. Segment IMD, Item description A segment for describing the product or material involved. This segment should be used for products that cannot be identified by a product code or a material number. In the Steel and Iron industry this segment can be used to give a detailed description of the material, the steel grade, or a general description of the product group. Segment MEA, Measurements A segment to allow physical measurements and dimensions to be stated, where it is required for identification of the product or material. For example this segment can be used to specify the dimensions or the net weight and gross weight of the product or material. Segment DTM, Date/time/period A segment specifying date/time/period details to the line item only. For example this segment can be used for the production date. 32

34 Segment group 6 : RFF-DTM A segment group for referencing documents relating to the line item and when necessary their dates. Segment RFF, Reference A segment identifying the referenced document, message or information by its number and where appropriate, a line number within that document. Segment DTM, Date/time/period A segment specifying the date/time of the referenced document, message or information. Segment group 7 : NAD-LOC-SG8-SG9 A group of segments identifying the parties, relevant to the line item only. Eurofer has decided to use only the segment NAD of this group. The other segments and segment groups for giving associated information should not be used. Segment NAD, Name and address A segment identifying name and address of the parties and their function relevant to the line item. The name and address can be given in a coded or clear form. Segment group 12 : CCI-PSD-SPS-DTM-FTX-SG13-SG14-SG16-SG18 A group of segments to be used to define a class of properties, the individual properties within that class and the related data (e.g. discrete values, measured values, target values, test methods).when this segment group is used, the data is directly related to the product specified by the line segment. Eurofer has decided to use only the segments CCI, FTX and the segment group SG14. The other segments and segment groups for giving associated information should not be used. Segment CCI, Characteristic/class id A segment to specify the general class and/or the individual properties on which the quality data is being reported. Note : Within the CCI segment the data element Property Class (7059) or composite data element Measurement Details (C502) or composite data element C240 Product Characteristic (C240) must be presented. Segment FTX, Free text A segment with free text information to give further clarification within the segment group 12. This segment is used to give the Defect/weld remarks. Segment group 14 : MEA-DTM-SG15 A group of segments to allow measurement values or specification values to be specified along with their associated references and dates. The data element Measurement Application Qualifier (6311) indicates the type of the values. Eurofer has decided to use only the segment MEA. The other segment and segment groups for giving associated information should not be used. 33