DELFOR Delivery Schedule Message Subset for Application in the European Steel Industry

DELFOR Delivery Schedule Message Subset for Application in the European Steel Industry Version December 1998 Corporate Factory Ph. D. Sarraute EDIFER WORKING GROUP - Message development

DELIVERY SCHEDULE MESSAGE (Table of Contents) 0. INTRODUCTION 2 1. BACKGROUND INFORMATION 3 1.1 General information 3 1.2 The different types of the message 4 1.3 The level of commitment 5 1.4 Synchronisation of the information received 6 2. DATA MODEL 7 2.1 Data Model Format 7 2.2 Data Model Diagram 8 2.3 Data Model Entities 9 2.4 Data Model Relationships 10 2.5 Data Model Attributes 12 3. SCOPE 17 3.1 Functional Definition 17 3.2 Field of Application 17 3.3 Principles 17 3.4 Message Usage 17 4. MESSAGE DEFINITION 18 4.1 Message Structure 18 4.2 Mapping of the Data Model to the Message 19 4.3 Branching Diagram of the Segments used by Eurofer 27 4.4 General Description of the Message - Subset of Eurofer 31 4.5 Detailed Description of the Message - Subset of Eurofer 37 5. EXAMPLES 79 5.1 Example of a delivery schedule (forecast only) of Scania 80 5.2 Example of a delivery schedule (firm delivery only) of Scania 83 Page 1

DELIVERY SCHEDULE MESSAGE 0. INTRODUCTION This document provides the definition of the EUROFER subset of the Delivery schedule message based on the UN standard DELFOR message of the UN/EDIFACT directory D97A. This message has been created by the EDIFER "Message development" 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: - Background information describing the use of the Delivery schedule message. - 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 relates 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 DELFOR, the segments used are indicated. This is followed by a detailed description of the segments used by Eurofer. - Examples of some Delivery schedules are provided to clarify the understanding of the message description Page 2

1. BACKGROUND INFORMATION 1.1. General information In the steel industry the Delivery schedule message is sent by the customer to a supplier to give details on short, medium and long term material requirements in line with the conditions set out in the purchase contract or order. Delivery schedule messages are used to synchronise a continuous material flow (e.g. repeat business) between supplier and customer, when the delivery specifications are not completely defined in the contract or order. The delivery schedule message is intended to : - specify requirements based on the delivery conditions, - define the aspects that guarantee synchronisation between the customer and the supplier, - provide information allowing the supplier to plan future requirements, to purchase raw material, to fabricate and to plan the delivery of goods in line with the delivery instructions, specified in the delivery schedule. The customer and the seller must agree on the commercial conditions prior to starting up the use of the delivery schedule. A contract or an order must be issued by the customer defining the product specifications, and the commercial conditions, such as delivery conditions, payment conditions, price agreement, etc A Delivery schedule message can be issued in any frequency (e.g. once per month, week), and may cover fixed or variable time periods (e.g. week, month, quarter, six months, a year). Medium and long term delivery schedules issued each month, can be altered by short-term delivery schedules issued each week. Guidelines for the understanding of the Delivery schedule are to be provided by the customer to the supplier with the aim of clarifying the use of the message in practice. Without guidance there is a risk of misinterpretation due to the degree of complexity of the message. However, it is the responsibility of the trading partners to determine the conditions for use of the message. All products (articles) specified in the Delivery schedule should be uniquely identified by an order item number, an article number or a part number. The identification number can be defined by either the customer or the supplier. The conditions for use of the unique identification number must be agreed between the partners. The deliveries requested in the Delivery schedule can be directed to a precise location within the customer s premises or to an external warehouse or consignment warehouse. Direct deliveries to a precise location within the customer s premises is an important requirement, having impact on the delivery process and the labelling of the goods to be delivered. This can be done using the consignee s information as follows : Page 3

- The consignee s identification number or the Consignee s name and address identify the company or the business unit to which the despatch is consigned. If the address clearly identifies the delivery point for the specified delivery, no further information is required. - The place of discharge is required wherever there is more than one place of discharge at the consignee s premises. - The place of destination can be used to provide details of the ultimate destination at the request of the consignee. This can either be a place of destination at the assembly line or a place of destination at the warehouse. - If a scheduled article in a delivery schedule should be delivered to several places of discharge and, or places of destination, the same scheduled article has to be repeated for each combination of place of discharge and, or destination to provide the scheduling information. 1.2. The different types of the message The DELFOR message can be used in three different ways based on the agreement between the partners involved. The circumstances in which the types of message are used need to be clearly defined between the customer and the supplier (seller). The difference is made based on the level of commitment, specified in point 1.3. in the following way : - A firm delivery covers only the commitment for firm order, allowing the supplier to deliver goods according to the delivery plan given in the message. - A forecast delivery covers not only the planning/forecast, but also the commitment to manufacture the goods or to buy the raw material needed for the manufacturing of the goods. The different functions are : Forecast Delivery schedule When the message covers only the forecast information, the message covers a longer period of time (e.g. from one month to one year) and is used to give the supplier a basis for planning his own production. Forecast information can be updated by sending a new forecast information, but it can never be used to order the delivery of the goods. The delivery of the goods can be requested by a DELFOR message having the function firm delivery or by a DELJIT message requesting a delivery just-in-time. Firm Delivery schedule When the DELFOR is used only to transmit the firm delivery information, the message covers a short period of time (e.g. one day to one month) and is the instruction to move the goods. Being used for a firm order, delivery quantities and dates given in the message should not be changed by another Delivery schedule message. Page 4

Firm and Forecast delivery schedule In this case the Delivery schedule message covers the forecast information, with the different levels of commitment (planning/forecast, material, manufacturing), and the firm delivery information. Depending on the specified delivery period in the message, the information provided can replace partly or completely the information provided in the previous DELFOR message. To clarify the difference between a partial or a complete replacement of the delivery information given in a DELFOR message, the following two examples have been added. If the DELFOR message is only replacing partial the previously sent information the period for which the replacement is valid shall be given in the message. 1. Complete replacement At the beginning of each week the customer sends a firm delivery DELFOR message to specify the delivery instructions from the second and subsequent four weeks. E.g. the previously sent DELFOR message has specified the deliveries for the first week of 1998 up to the fourth week of 1998. The next DELFOR message specifies the deliveries from the second week of 1998 up to the fifth week of 1998. In this case the information provided for the second week up to the fourth week in the previous message is overruled with the specification given in the second DELFOR message. 2. Partial replacement As an example the previously sent DELFOR message specifies the delivery period from 01.01.1998 up to 31.01.98, the second message specifies deliveries only valid from 15.01.1998 up to 22.01.1998). In this case the delivery information provided in the first message is updated with the information provided in the second message for the period 15.01 up to 22.01.1998. The rest of the deliveries specified in the previously message is still valid. 1.3. The level of commitment The responsibility between the customer and the supplier concerning the information provided and the delivery of the goods is indicated by means of the level of commitment. The following levels of commitment can be specified : Firm : The supplier may deliver the goods according to the schedule. No further confirmation or notification is needed and there are no changes to the quantity or delivery time. Forecast : Commitment for manufacturing : The supplier may start producing according the schedule. Commitment for material : The supplier may buy raw material according to the schedule. Planning/Forecast : The supplier can use the information according the schedule as a forecast information for his own planning system. Page 5

1.4. Synchronisation of the information received The DELFOR message allows the customer to define the aspects that guarantee the synchronisation between the supplying and receiving parties. This information allows the supplier to plan the resources necessary to fulfil the customers requirements, taking into account the despatches received and used to calculate the revised needs of the customer. The trading partners may agree to use one of the two following possibilities : No synchronisation data is provided. In this case it is very difficult to align the new requests for delivery and forecast with the goods delivered, underway and received. Firm agreements between the parties are required about the previous despatched goods taken into account for the calculation of the new delivery schedule, otherwise this can lead to short or over deliveries. Synchronisation data is provided. The message allows the synchronisation of data in different ways : The following data must always provided : - Delivery calculation date/time (date/time on which the requested delivery quantities are calculated), - Actual cumulative quantity received. To simplify the synchronisation at the supplier side, the customer can provide some supplementary information, such as - the start date when the cumulative quantity was set to zero, - the cumulative quantity given in the previous delivery schedule - the cumulative quantity scheduled. To inform the supplier of the latest received goods, the customer can specify up to a certain number the last received goods by providing the following information : - Quantities received or despatched - Despatch advice number or goods receipt reference number. Page 6

2. DATA MODEL 2.1 Data Model Format The data model has been created to make it possible for potential users to understand the Eurofer subset of the Delivery schedule message. 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 within the data entities, - and the relationship between data entities. To simplify the understanding of the data model, the model is defined at a summary level, description 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 delivery schedule); 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 2.2. Page 7

2.2 Data Model Diagram Delivery schedule 1 Relates to 1,N Consignee 1 Relates to Synchronisation infomation 0,N Has 1,N 1 1 Order item Has 0,1 Delivery variance restrictions 1 1 1 Has 0,N 1,N Has 0,N Delivery schedule details Has 0,1 Received - despatched quantities Labelling - Package information Reference to Reference to Company Message / Document Page 8

In these diagrams, the rectangles represent data entities 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 directions and is 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 entities. - 0,1 means that there can be no or one relationship between the 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 entities. Example relationship between Consignee and Order item 1. In the direction from Consignee to Order item. A Consignee can have one or more Order items. 2. In the direction from Order item to Consignee. An Order item can only belong to one Consignee. 2.3. Data model entities Because the data entities Company and Message / Document are not really basic information in this message and can be referenced at different levels, they have been put outside the data model and 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 DELIVERY SCHEDULE CONSIGNEE ORDER ITEM DELIVERY SCHEDULE DETAILS SYNCHRONISATION INFORMATION RECEIVED - DESPATCHED QUANTITIES DELIVERY VARIANCE RESTRICTIONS LABELLING AND PACKAGING INFORMATION The related data entities COMPANY MESSAGE/DOCUMENT DELIVERY SCHEDULE CONSIGNEE This entity contains the general information about a delivery schedule such as the type of schedule, its number and date, the period/date covered in the delivery schedule. This entity contains information about the party to which goods are to be consigned. Page 9

ORDER ITEM DELIVERY SCHEDULE DETAILS The entity contains the information about the goods ordered to allow reference to the correct order item specified in the order message as agreed between the customer and the supplier (seller). This entity provides the information about a requested delivery, such as the quantity, the date/time/period, and the level of commitment. SYNCHRONISATION INFORMATION This entity provides the cumulative quantities taken into account for the calculation of the revised delivery schedule details. RECEIVED - DESPATCHED QUANTITIES DELIVERY VARIANCE RESTRICTIONS LABELLING PACKAGING INFORMATION COMPANY MESSAGE & DOCUMENT This entity gives information about the previous received and/or despatched quantities taken into account for the calculation of the delivery schedule details of the order item. This entity contains a set of data defining the maximum and minimum quantities for delivery during a specific period or per type of subperiod. For example the minimum and maximum quantity to be delivered during any week of a specific period. This entity is used to describe either the handling unit or a package type and can be used to specify the labelling information. This entity identifies the parties with associated information, such as name and address, contact details and communication types and numbers. This can be the customer, supplier, consignor, consignee, manufacturer, etc.... This entity contains all the references to another message or document. For example contract, order, previous delivery schedule. 2.4. Data model relationships DELIVERY SCHEDULE - CONSIGNEE (relation : relates to - 1/1,N) - Direction from Delivery schedule to Consignee. A Delivery schedule can relate to one or more Consignees. - Direction from Consignee to Delivery schedule. The information concerning the delivery request of a Consignee belongs to one Delivery schedule. Page 10

CONSIGNEE - ORDER ITEM (relation : relates to - 1/1,N) - Direction from Consignee to Order item. A Consignee relates to one or more Order items. - Direction from Order item to Consignee. An Order item belongs to one Consignee. ORDER ITEM - DELIVERY SCHEDULE DETAILS (relation : has - 1/1,N) - Direction from Order item to Delivery schedule details. An Order item can have one or more Delivery schedule details. - Direction from Delivery schedule details to Order item. A Delivery schedule details belongs to one Order item. ORDER ITEM - SYNCHRONISATION INFORMATION (relation : has - 1/0,N) - Direction from Order item to Synchronisation information. An Order item can have no, one or more Synchronisation information. - Direction from Synchronisation information to Order item. A Synchronisation information belongs to one Order item. ORDER ITEM - RECEIVED-DESPATCHED QUANTITIES (relation : has - 1/0,N) - Direction from Order item to Received-despatched quantities. An Order item can have no, one or more Received-despatched quantities. - Direction from Received-despatched quantities to Order item. A Received-despatched quantities belongs to one Order item. Page 11

ORDER ITEM - DELIVERY VARIANCE RESTRICTIONS (relation : has - 1/0,1) - Direction from Order item to Delivery variance restrictions. An Order item can have no or one Delivery variance restrictions. - Direction from Delivery variance restrictions to Order item. A Delivery variance restrictions belongs to one Order item. ORDER ITEM - LABELLING-PACKAGE INFORMATION (relation : has - 1/0,1) - Direction from Order item to Labelling-package information. A Order item can give details on no or one Labelling-package information. - Direction from Labelling-package information to Order item. A Labelling-package information belongs to one Order item. 2.5. Data model attributes For each entity specified under point 2.3. Data model entities, a list of attributes and a description is given. ENTITY : DELIVERY SCHEDULE document/message type Document/message type expressed in code specifying the message function (e.g. Delivery schedule, forecast, firm delivery). document/message number Reference number assigned to the document/message by the issuer (e.g. delivery schedule number). document/message date/time Date and if necessary the time when the document/message was issued. validity period Start date/time and end date/time of the validity period of the delivery schedule. release type code Clarification about the meaning of the date/time/period given in the delivery schedule details (e.g. its the delivery date/time requested, shipment date/time request, availability date/time or the production/manufacture date). Page 12

schedule release frequency The frequency of transmission of the delivery schedule (e.g. daily, weekly or monthly). ENTITY : CONSIGNEE company code, name and address Code and if necessary the name and address, contact persons and communication channels of the consignee. ENTITY : ORDER ITEM order number buyer Unique number given by the buyer to identify an order. order date buyer Date when the order was issued by the buyer. order item number Unique number given to an order item for identification. seller s article number Seller s reference identifying an article or product. buyer s article number Buyer s reference identifying an article or product. part number Buyer s identification number attributed to the article. drawing/revision number (Design revision number) Reference number identifying a revision of a drawing of the article. drawing/revision date (Design revision date) Date assigned to the drawing revision. engineering change number Reference number assigned an engineering change. engineering change date Date assigned to the engineering change. place of discharge The place within the consignee premises where goods are (to be) unloaded (e.g. Dock and gate). Page 13

additional internal address (place of destination) An internal location within the consignee premises, where goods are moved to after they have been unloaded (e.g. an assembly line, a warehouse). order item remarks A remark related to the order item. ENTITY : DELIVERY SCHEDULE DETAILS level of commitment Code indicating the level of commitment of a delivery instruction. delivery date/time or period Date and time or period of the requested delivery. delivery date/time first Earliest date/time of the requested delivery. delivery date/time last Latest date/time of the requested delivery. quantity to be delivered The quantity scheduled for the requested delivery. reference of the delivery Reference number given to a specific requested consignment. ENTITY : SYNCHRONISATION INFORMATION level of commitment Code indicating the level of commitment of the synchronisation information. delivery calculation date/time Date and time on which the requested delivery quantities are calculated. quantities accumulation start date Date and time on which the accumulation of quantities started. actual cumulative quantity received Actual quantity received by the consignee, starting from the accumulation start date. cumulative quantity since accumulative start date The quantity scheduled for delivery of a specific order item since the quantities accumulation start date. cumulative quantity previously scheduled The quantity scheduled for delivery of a specific order item by the previous delivery schedule. Page 14

actual cumulative quantity scheduled The actual cumulative quantity scheduled in the delivery schedule message by the buyer. delivery quantity balance The difference between the cumulative quantity scheduled in the previous delivery schedule and the cumulative quantity received from the accumulation start date. For positive values, the quantity scheduled is greater than the quantity received. ENTITY : RECEIVED - DESPATCHED QUANTITIES quantity received The quantity received by the consignee. goods receipt reference Unique identification given to the receipt of goods. reception date The date/time when the goods were received by the consignee. quantity despatched The quantity despatched by the seller to the consignee. despatch advice number Unique identification number of a despatch. despatch advice date The date/time of the despatch advice message/document ENTITY : DELIVERY VARIANCE RESTRICTIONS date/time/period of the delivery variance restrictions The start date and the end date of the period, or the period valid for the delivery variance restrictions. number of working days within the referenced period Number of working days included in the referenced period date/time/period of the delivery variance restrictions. daily average quantity within the referenced period Average quantity scheduled for each working day of the referenced period. period maximum quantity Maximum quantity which may be called-off during the referenced period. period minimum quantity Minimum quantity which may be called-off during the referenced period. Page 15

ENTITY : LABELLING - PACKAGING INFORMATION type of package Type of package (e.g. Bundles, coils) dimensions of the package Length, width, height, inside diameter and outside diameter of the package. number of pieces per package Number of pieces requested per package unit marks and numbers These are all the kinds of information that must be printed on the transport label of the package units. marking label number Number(s) requested to be put on the label of the package unit(s). THE RELATED DATA ENTITY ENTITY : COMPANY company code, name and address Code and if necessary the name and address, contact persons and communication channels of the partners involved. Examples are : buyer, supplier, manufacturer, delivery party, invoicee. ENTITY : MESSAGE / DOCUMENT message / document type Code identifying a referenced message or document (e.g. previous delivery schedule message, order, contract document). message / document number Identification number of a referenced message or document. message /document date The date/time of the referenced message or document. Page 16

3. SCOPE 3.1. Functional definition This message is used in the steel industry to provide information from a party who is planning the use or consumption of products (customer) to a party who has to plan for the supply of the products (supplier). The message gives the requirements regarding details for short term delivery and/or medium to long term scheduling for products. The scheduling can be used to authorise manufacturing and/or the provision of basic materials for the production. 3.2. Field of application This message provides the definition of the Eurofer delivery schedule message to be used in Electronic Data Interchange between trading partners. 3.3. Principles The Delivery schedule message shall be used to : - specify forecast production requirements, either for planning/forecast, commitment for material and commitment for manufacturing and material. - specify firm delivery dates and the quantities scheduled, - define the aspects that guarantee the synchronisation between the supplying and receiving parties, thus allowing the supplier to plan for the resources necessary to fulfill customer requirements. The EDIFACT - Delivery schedule message provides the option to use one of the two scheduling methods. Method 1 : Delivery point driven This is when for a given delivery point a number of different products are to be delivered. This means that the address of the consignee triggers the product information. Method 2 : Product driven This is when a given product is to be delivered to a number of different delivery points. This means that the product information triggers the delivery address information. Eurofer has decided to use only the Delivery point driven method. 3.4. Message usage The Delivery schedule message can be used in three different ways based on the agreement between the partners involved. The different functions of the message are explained in chapter 1.2. Page 17

4. MESSAGE DEFINITION 4.1 Message Structure The Delivery schedule message of UN/EDIFACT is structured in two sections, a Heading Section and a Detail Section. 4.1.1. 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 the references to the initial contract, or information about the customer and the supplier, references and contacts relevant for the whole message. 4.1.2. Message structure - Detail section The detail section is controlled by the segment group 6 (with trigger segment GIS). The trigger segment GIS provides the information if the delivery schedule is location or product driven. Based on the decision taken by Eurofer, the GIS segment will indicate that the location driven approach is used. This means that the segment group 7 (triggered by the segment NAD) is used to give details about the consignee, such as the delivery address and references, documents and contacts relevant for the consignee. The segment group 12 (trigger segment LIN) provides details on each individual item regarding the product identification, references, the specific location of discharge and destination, package and labelling information, scheduling information and synchronisation data to interpret the scheduling information. Page 18

4.2. Mapping of the Data model to the message To understand the mapping process, completed by the EDIFER working group, it is necessary to have knowledge about the structure of the official UNSM DELFOR message and the functionality of the segment groups and segments as defined by the EDIFACT message development group EEG1 - Trade. To have the complete information about the official version we recommend the use of the official document published by UNITED NATIONS - EDIFACT directory D97.A. In the 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 To identify the type of Delivery schedule Mandatory. message and its number. DTM To specify general date/time/period related to Must be used at least once to identify the whole message. the date of the Delivery schedule. FTX Free text information. Not recommended by Eurofer. GROUP 1 RFF DTM To specify referencing documents and their date, related to the whole message. For referencing documents related to the whole DELFOR message. To specify the date/time of the reference. GROUP 2 GROUP 3 GROUP 4 GROUP 5 NAD RFF DTM CTA COM TDT DTM To identify the parties (companies) relevant to the whole message. Function, name and address of the party. To specify referencing documents and their date related to the party. To identify the reference related to the party. To specify the date/time of the reference. To give contact details of the party. To identify to whom communication should be directed. To identify communication type and numbers. To specify details of the mode and means of transport relating to the whole message To specify the carriage, mode and means of transport. Date/time/period relating to the TDT segment. Must be used to specify at least the supplier and the customer. Not used Not used Page 19

SEGMENT GROUP SEGMENT FUNCTION DETAIL SECTION COMMENTS GROUP 6 GROUP 7 (GIS, SG.7 SG.12) NAD LOC To provide details on delivery points and products and related information using the one of both scheduling methods. To identify the delivery point and its attached information when the delivery point driven approach is used. To identify the consignee. To identify specific location at the consignee address to which the product should be delivered. FTX Free text information. Not used. GIS segment indicates that the delivery point driven approach is used. Not used, (see group 12). GROUP 8 To give references relevant to the consignee. Not used. RFF To give references related to the consignee. DTM Date/time/period of the reference. GROUP 9 DOC DTM To provide information relating to documents required for the consignee. To describe the documents required for the specified consignee. Date/time/period of the document required. Not used. GROUP 10 CTA COM To give contact details of the consignee. To identify to whom communication should be directed. To identify communication type and numbers. GROUP 11 TDT DTM To specify details of the mode and means of transport relating to the specified delivery point. To specify carriage, and the mode and means of transport. Date/time/period of departure or arrival relating to the TDT segment. Not used. GROUP 12 LIN PIA IMD MEA ALI GIN GIR To provide detailed information, on each line of the delivery schedule. To identify the line item by the line number and additionally, identifying the product. To provide additional identification to the product specified in the LIN segment. To describe the product. To specify physical measurements of the item to be delivered. To indicate that the line item is subject to special conditions due to origin, customs reference, embargo regulations or commercial factors. To provide identity number to be applied to the Not used. goods to be delivered. To provide related identification numbers for the Not used. line item specified in the LIN segment. Page 20

SEGMENT GROUP SEGMENT FUNCTION COMMENTS LOC To identify specific location to which products, as specified in the LIN segment, should be placed after delivery (e.g. dock, gate, point of destination). DTM To specify date/time/period details relating to the line item only. FTX Free text information. Not recommended by Eurofer. GROUP 13 RFF DTM To give references and where necessary, their dates, relating to the line item. To identify the referenced document. To specify the date/time of the referenced document. GROUP 14 TDT DTM To specify details of the mode and means of transport and date/time/period related to the specified transport details. To specify carriage, and the mode and means of transport. To indicate the date/time/period details relating to the TDT segment. Not used. GROUP 15 To specify quantities and associated date not related to schedules and when relevant the references. QTY To specify quantities for synchronisation, received - despatched quantities not related to schedules. DTM Date/time/period relating to the quantity. GROUP 16 GROUP 17 GROUP 18 GROUP 19 GROUP 20 RFF DTM SCC QTY DTM RFF DTM PAC To give references related to the quantities and when necessary their date. To identify references related to the quantity. Date/time/period of the reference. To specify the schedule information. To specify the level of commitment. To specify product quantities and associated dates. To specify scheduled quantities. Date/time/period relating to the given quantity. To specify references associated with the given scheduled quantity. To identify references related to the quantity (e.g. Kanban card number). Date/time/period of the reference. To identify the packaging, physical dimensions and marks and numbers for the goods specified in the line item. To specify the number and type of packages. Page 21

SEGMENT GROUP SEGMENT FUNCTION MEA To specify physical measurement of the packages described in the PAC segment. QTY To specify the quantity per package described in the PAC segment. DTM To specify date/time/period details relating to the physical units (packages) described in the PAC COMMENTS Not used. GROUP 21 PCI GIN To specify markings, labels and packing. To specify markings and, or labels used on individual physical units (packages) described in the PAC segment. To provide identity numbers to be applied to the packages. GROUP 22 NAD-LOC- FTX-SG23- SG24- SG25- SG27-SG30 To provide details of the individual delivery points for the given product, when the product driven approach is used. Not used. Page 22

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 its tag - the Edifact data element - remarks about the usage. ATTRIBUTE SEGMENT GROUP SEGMENT TDID - Data element REMARKS Entity : DELIVERY SCHEDULE Document/message type BGM 1001 Document/message number BGM 1004 Document/message date/time DTM 2380 DTM segment in the header, following BGM. Use code 137 in element 2005. Validity period DTM 2380 DTM segment in the header, following BGM. Use code 273 or 157 in element 2005. Release type code DTM 2005 DTM segment in the header, following BGM. Use code 2, 10, 44 or 94 in element 2005. Schedule release frequency DTM 2379 DTM segment in the header, following BGM, with code 264 in element 2005. Entity : CONSIGNEE Company code, name and address of the consignee Group 7 NAD 3039 or C058, C080, Contact information Group 10 CTA 3412 or 3413 Communication contact Group 10 COM 3148 or 3155 Code form, structured or clear form can be used. C059, 3164, 3229, 3521, 3207 Entity : ORDER ITEM Order number buyer Group 13 RFF 1154 Use the code ON in element 1153. Order date buyer Group 13 DTM 2380 Use the code 137 or 171 in element 2005. Order item number Group 13 or Group 12 RFF LIN 1154 7140 Use the relevant code for 1153. Use the code IN in element 7143. Seller s article number Group 12 LIN or 7140 Use the code SA in element PIA Buyer s article number Group 12 LIN or PIA 7143. 7140 Use the code IN in element 7143. Page 23

ATTRIBUTE SEGMENT GROUP SEGMENT TDID - Data element REMARKS Entity : ORDER ITEM Part number Group 12 LIN or PIA 7140 Use the code IN in element 7143. Drawing/revision number Group 12 PIA 7140 Use the code DR in element 7143. Drawing/revision date Group 12 DTM 2380 Use the code 380 in element 2005. Engineering change number Group 12 PIA 7140 Use the code EC in element 7143. Engineering change date Group 12 DTM 2380 Use the code 60 in element 2005. Place of discharge Group 12 LOC 3225 or 3224 Additional internal address (Place of destination) Group 12 LOC 3225 or 3224 Order item remarks Group 12 FTX 4440 Use the code 11 for element 3227. Use the code 159 for element 3227. Entity : DELIVERY SCHEDULE DETAILS Level of commitment Group 17 SCC 4017 Use the relevant code. Delivery date/time or period Group 18 DTM 2380 Use code 2 in element 2005 Delivery date/time first Group 18 DTM 2380 Use code 64 in element 2005. Delivery date/time last Group 18 DTM 2380 Use code 63 in element 2005. Quantity to be delivered Group 18 QTY 6060 Use the relevant code in 6063. Reference of the delivery Group 19 RFF 1153 Use the relevant code in 1154. Entity : SYNCHRONISATION INFORMATION Level of commitment Group 17 SCC 4017 Use the relevant code. Delivery calculation date/time Group 12 DTM 2380 Use code 257 in element 2005. Quantities accumulation start date Group 12 DTM 2380 Use code 51 in element 2005. Actual cumulative quantity received Group 15 or 18 QTY 6060 Use code 70 in element 6063. Cumulative quantity since Group 15 QTY 6060 Use code 186 in element 6063. accumulative start date or 18 Cumulative quantity previously Group 15 QTY 6060 Use code 79 in element 6063. scheduled or 18 Actual cumulative quantity scheduled Group 15 QTY 6060 Use code 78 in element 6063. or 18 Delivery quantity balance Group 15 or 18 QTY 6060 Use code 73 in element 6063. Entity : RECEIVED- DESPATCHED QUANTITIES Quantity received Group 15 QTY 6060 Use code 48 in element 6063. Goods receipt reference number Group 16 RFF 1154 Use code SI in element 1153. Reception date Group 15 DTM 2380 Use code 310 in element 2005. Quantity despatched Group 15 QTY 6060 Use code 12 in element 6063. Despatch advice number Group 16 RFF 1154 Use code AAK in element 1153. Despatch advice date Group 16 DTM 2380 Use code 171 in element 2005. Page 24

ATTRIBUTE SEGMENT GROUP SEGMENT TDID - Data element REMARKS Entity : DELIVERY VARIANCE RESTRICTIONS Date/time/period of the delivery Group 15 DTM 2380 Use code 206 in element 2005. variance restrictions Number of working days within the Group 15 QTY 6060 Use code 77 in element 6063. referenced period Daily average quantity within the Group 15 QTY 6060 Use code 1 in element 6063. referenced period Period maximum quantity Group 15 QTY 6060 Use code 54 in element 6063. Period minimum quantity Group 15 QTY 6060 Use code 53 in element 6063. Entity : LABELLING- PACKAGING INFORMATION Type of package Group 20 PAC 7065 Dimensions of the package Group 20 MEA 6314 Use the relevant code for element 6314. Number of pieces Group 20 QTY 6060 Use the code 52 in element 6063. Marks and numbers Group 21 PCI 7102 Marking label number Group 21 GIN 7402 Use the code ML in element 7405. Entity : COMPANY Company code, name and address Group 2 NAD 3039 or C058, C080, Contact information Group 4 CTA 3412 or 3413 Communication contact Group 4 COM 3148 or 3155 Code form, structured or clear form can be used. C059, 3164, 3229, 3521, 3207 Entity : MESSAGE / DOCUMENT Message / document type Group 1 or Group 13 Message / document number Group 1 or Group 13 Message / document date Group 1 or Group 13 RFF 1153 RFF 1153 RFF 1154 and RFF 1156 DTM 2380 Use the code 171 in element 2005 Page 25

The use of the segments groups 15 and 17 The difficulty when implementing the DELFOR message is the use of the segment group 15 (triggered by quantity) and segment group 17 (triggered by SCC) at the line item. This is due to the fact that the two segment groups were designed to transmit any kind of quantity related to the line item. These quantities are specified in the following entities : - Delivery schedule details - Synchronisation information - Received -despatched quantities - Delivery variance restrictions. In the data model and the DELFOR message, there are four main types of quantities to be transmitted in one of the two groups : 1. Delivery schedule details This quantity information is transmitted by using the segment group 17. - In the segment SCC the level of commitment is given and if necessary a delivery pattern. - The segment QTY is used to specify the requested delivery quantity. - The segment DTM specifies the requested delivery date/time/period. - The segment RFF can be used to refer to a part consignment number. 2. Synchronisation data Only when the synchronisation data is provided at the global level, then the segment group 15 shall be used. - The segment QTY is used to specify the type of cumulative quantity and the value. - The segment DTM is used to specify the related date and time. When the synchronisation data is provided at the level of commitment, then the segment group 17 shall be used. - The segment SCC is used to give the level of commitment applicable to the synchronisation data. - The segment QTY is used to specify the type of cumulative quantity and the value. - The segment DTM is used to specify the related date and time. 3. Received-despatched quantities This information is transmitted by using the segment group 15. - The segment QTY is used to specify the received or the despatched quantity. - The segment DTM is used to give goods receipt date/time. - The segment group 16, triggered by the segment RFF is used to give reference to the Despatch advice number or Shipper s ID number for shipment and the despatch date/time. 4. Delivery variance restrictions This information is transmitted by using the segment group 15. - The segment QTY is used to specify the delivery variance restrictions, such as number of working days, daily average quantity, minimum and maximum quantity. - The segment DTM is used to specify the related date/time/period. Page 26

4.3 Branching Diagram of the Segments used by Eurofer DELFOR Delivery schedule message version D97A Message to enable the transmission of the requirements regarding details for short term delivery and/or medium to long scheduling for products. 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 38 UNH Message header M 1 R 39 BGM Beginning of message M 1 R 40 DTM Date/time/period M 10 O 41 FTX Free text C 5 O SEGMENT GROUP 1 C 10 R 42 RFF Reference M 1 O 43 DTM Date/time/period C 1 R SEGMENT GROUP 2 C 99 R 44 NAD Name and address M 1 X SEGMENT GROUP 3 C 10 X RFF Reference M 1 X DTM Date/time/period C 1 O SEGMENT GROUP 4 C 5 R 46 CTA Contact information M 1 O 47 COM Communication contact C 5 X SEGMENT GROUP 5 C 10 X TDT Details of transport M 1 X DTM Date/time/period C 5 Page 27

Detail Section USG.IND. PAGE NUM. TAG NAME STATUS REPEATS GROUP REPEATS R SEGMENT GROUP 6 C 9999 R 48 GIS General indicator M 1 R SEGMENT GROUP 7 C 1 R 49 NAD Name and address M 1 X LOC Place/location identification C 10 X FTX Free text C 5 X SEGMENT GROUP 8 C 10 X RFF Reference M 1 X DTM Date/time/period C 1 X SEGMENT GROUP 9 C 10 X DOC Document/message details M 1 X DTM Date/time/period C 10 O SEGMENT GROUP 10 C 5 R 51 CTA Contact information M 1 O 52 COM Communication contact C 5 X SEGMENT GROUP 11 C 10 X TDT Details of transport M 1 X DTM Date/time/period C 5 R SEGMENT GROUP 12 C 9999 R 53 LIN Line item M 1 O 54 PIA Additional product id C 10 O 56 IMD Item description C 10 O 57 MEA Measurements C 5 O 58 ALI Additional information C 5 X GIN Goods identity numbers C 999 X GIR Related identification numbers C 999 O 59 LOC Place/location identification C 999 O 60 DTM Date/time/period C 5 O 61 FTX Free text C 5 O SEGMENT GROUP 13 C 10 R 62 RFF Reference M 1 O 63 DTM Date/time/period C 1 X SEGMENT GROUP 14 C 10 X TDT Details of transport M 1 X DTM Date/time/period C 5 O SEGMENT GROUP 15 C 10 R 64 QTY Quantity M 1 O 65 DTM Date/time/period C 2 O SEGMENT GROUP 16 C 10 R 66 RFF Reference M 1 O 67 DTM Date/time/period C 1 Page 28

O SEGMENT GROUP 17 C 999 R 68 SCC Scheduling conditions M 1 O SEGMENT GROUP 18 C 999 R 69 QTY Quantity M 1 O 70 DTM Date/time/period C 2 O SEGMENT GROUP 19 C 10 R 71 RFF Reference M 1 O 72 DTM Date/time/period C 1 O SEGMENT GROUP 20 C 99 R 73 PAC Package M 1 O 74 MEA Measurements C 10 O 75 QTY Quantity C 5 X DTM Date/time/period C 5 O SEGMENT GROUP 21 C 10 R 76 PCI Package identification M 1 O 77 GIN Goods identity numbers C 10 X SEGMENT GROUP 22 C 999 X NAD Name and address M 1 X LOC Place/location identification C 10 X FTX Free text C 5 X SEGMENT GROUP 23 C 10 X DOC Document/message details M 1 X DTM Date/time/period C 1 X SEGMENT GROUP 24 C 5 X CTA Contact information M 1 X COM Communication contact C 5 X SEGMENT GROUP 25 C 10 X QTY Quantity M 1 X DTM Date/time/period C 2 X SEGMENT GROUP 26 C 10 X RFF Reference M 1 X DTM Date/time/period C 1 X SEGMENT GROUP 27 C 999 X SCC Scheduling conditions M 1 X SEGMENT GROUP 28 C 999 X QTY Quantity M 1 X DTM Date/time/period C 2 X SEGMENT GROUP 29 C 10 X RFF Reference M 1 X DTM Date/time/period C 1 X SEGMENT GROUP 30 C 10 X TDT Details of transport M 1 X DTM Date/time/period C 5 R 78 UNT Message trailer M 1 Page 29

EUROFER DELFOR DELIVERY SCHEDULE MESSAGE VERSION - DECEMBER 1998 UN/EDIFACT DIRECTORY : D97.A Level 00 UNH M 1 BGM M 1 UNT M 1 G01 G02 G06 C 10 C 99 C 9999 01 DTM M 10 FTX C 5 RFF M 1 NAD M 1 GIS M 1 G04 G07 G12 02 DTM C 5 CTA C 1 NAD C 9999 LIN C 1 M 1 M 1 M 1 G10 03 COM C 5 C 5 CTA M 1 PIA C 10 IMD MEA ALI C 10 C 5 C 5 LOC C 999 DTM C 5 FTX C 5 See page 2 04 COM C 5 Branching Diagram Page 1 EUROFER DELFOR DELIVERY SCHEDULE MESSAGE VERSION - DECEMBER 1998 UN/EDIFACT DIRECTORY : D97.A Level 03 See page 1 G13 C 10 RFF G15 C 10 QTY G17 C 999 SCC G20 C 99 PAC M 1 M 1 M 1 M 1 G16 G18 G21 C 10 C 999 C 10 04 DTM C 1 DTM C 1 RFF M 1 QTY M 1 MEA C 10 QTY C 5 PCI M 1 G19 C 10 04 DTM DTM RFF GIN C 1 C 2 M 1 C 10 05 DTM C 1 06 Branching Diagram Page 2 Page 30

4.4 General description of the message - subset of Eurofer 4.4.1 Message definition and segment clarification This section is provided to give clarification and further explanation to the usage of the segments within the message defined by Eurofer. The message consists of two sections, a heading section and a detail section. The heading section is representing 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 conjunction with the segment usage and the branching diagram (chapter 4.3.) which indicates the required (R) and optional (O) segments and segment groups. The following guidelines and principles apply to the whole message of Eurofer and are intended to facilitate 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 are not required in the message should not be included. Care must be taken that the segment qualifier in dependent segments do not conflict with the segment qualifier of the trigger segment of the group. 4.4.2 Message description - Heading section Information to be or which can be provided in the heading section of the message. Segment UNH, Message Header A service segment starting and uniquely identifying a message. The message type code for the Delivery schedule message is DELFOR. Note: Delivery schedule messages conforming to this document must contain the following data in segment UNH, composite data element S009 : Data elements ; - 0065 DELFOR - 0052 D - 0054 97A - 0051 UN Page 31

Segment BGM, Beginning of message A segment for unique identification of the Delivery schedule message by means of its type (e.g. firm, forecast, delivery schedule), its number and its function (original, replacement). Segment DTM, Date/time/period The DTM segment shall be specified at least once to identify the Delivery schedule message date. This segment can be included to indicate the beginning and the end date of the schedule. Segment FTX, Free text A segment with free text in coded or clear form to give further clarification when required. In computer to computer exchanges such text will normally require the receiver to process this segment manually. Eurofer recommends not to use this segment. Segment group 1: RFF-DTM A group of segments giving references and where necessary, their dates relating to the whole message, e.g. contract number. Segment RFF, Reference A segment for giving references to the whole Delivery schedule message, e.g. contract, original message number, previous message number. Segment DTM, Date/time/period Date or time, or date and time of the reference. Segment group 2: NAD-SG3-SG4 A group of segments identifying parties by their names, addresses, references and contacts relevant to the whole Delivery schedule message. Eurofer has decided not to use the segment group 3 for giving references related to the party specified in the NAD segment. Page 32