x

Application Of Odette / EDIFACT

Technical annexe to the frame agreement for deliveries to Volvo Car Corporation
2001-05-02 Volvo Car Corporation Dept 53340 405 31 GOTHENBURG

Technical Annexe Contents

1.0 Preface.................................................................................................................................................................................2 1.1 General............................................................................................................................................................................2 1.2 Contact Persons.............................................................................................................................................................2 1.3 Explanation of codes used in the segment-description ..........................................................................................3 2.0 General Arrangement .......................................................................................................................................................4 2.1 Stage 1 COMMUNICATION.....................................................................................................................................4 2.2 Stage 2 APPLICATIONS............................................................................................................................................5 3.0 Communication .................................................................................................................................................................6 3.1 Specifications ................................................................................................................................................................6 3.2 Agreement regarding communication.......................................................................................................................7 4.0 Application of ISO/ EDIFACT and OFTP....................................................................................................................9 4.1 General............................................................................................................................................................................9 4.2 Service segment ..........................................................................................................................................................10 4.3 Separators .....................................................................................................................................................................10 4.4 Character sets ..............................................................................................................................................................10 4.5 Identification of partners ...........................................................................................................................................10 4.6 UNB...............................................................................................................................................................................12 4.6 UNZ...............................................................................................................................................................................14 5.0 Instructions for Implementation ...................................................................................................................................15 5.1 Instructions for implementation ...............................................................................................................................15 5.2 Signing agreements ....................................................................................................................................................15 5.3 Volvo transmits to the supplier.................................................................................................................................15 5.4 The supplier evaluates the received EDI file..........................................................................................................15 5.5 The supplier transmits to Volvo ...............................................................................................................................15 5.6 Volvo evaluate the received file ...............................................................................................................................15 5.7 Step 4 and 5 will be repeated until the information flows without any interruptions.....................................15

Technical Annexe 1.0 Preface

1.1 General
This document describes Volvos application of the ODETTE subsets of the EDIFACT standard messages. The name Volvo refers throughout the document to: Volvo Car Corporation and all companies owned by this company.

This document covers all information for the EDI messages that Volvo uses. The intention is that information in this document is to form the basis for practical application by suppliers and Volvo. This annexe refer to the guidelines of following messages: EDIFACT ver 4.0, based on d96a DESADV DELFOR DELJIT INVOIC ORDERS Odette Messages ver 3.2 DELINS CALL-OFF AVIEXP SYNCRO INVOIC ENGDAT

This annexe refers also to the communication- and application agreement and also the appendix 1 to 6. Volvos suppliers can use the document to obtain the following detailed information: Setting-up of COMMUNICATION Application of ISO/EDIFACT SYNTAX Implementation

Additional information and amendments will be distributed whenever necessary.

1.2 Contact Persons

Information regarding EDI contact persons at Volvo Car see: www.it.volvo.se/edi

Technical Annexe
1.3 Explanation of codes used in the segment-description
In the detailed applications in this documentation we use M, R, D and N to describe which segments and data elements that are mandatory, required, dependent or not used. Each data elements length and representation is also described. Base Attributes, are in accordance with the Edifact specification and User Attributes are in accordance with Volvos demand. See example below. M Mandatory mandatory according to the Odette or International Edifact Standard R Required mandatory according to Volvos demands D Dependent always clarified by Conditions N Not Used not used by Volvo

Example: Data Element Summary Data Component Base User Element Element Name Attributes Attributes C002 DOCUMENT/MESSAGE NAME C R Identification of a type of document/message by code or name. Code preferred. 1001 Document/message name, coded C an..3 R Document/message identifier expressed in code. 351 Despatch advice Document/message by means of which the seller or consignor informs the consignee about the despatch of goods.

Technical Annexe 2.0 General Arrangement

Volvo intends to implement EDI communication in accordance with the Edifact standard with their suppliers, and between the various companies within Volvo. The technology will be progressively introduced and will basically apply to all suppliers and companies within Volvo. Establishment of computer-to-computer communication will take place in two stages: 1. 2. Establishment of communication. Implementation of the Odette Subsets of Edifact messages.

2.1 Stage 1 COMMUNICATION

Volvo communicates via Volvo IT. Before this communication test takes place, a number of identities and parameters must be finalised and documented. Detailed information is given under section 3. When the technical preparations for EDI communication have been completed and the agreed information has been registered in each system, a communication test will be performed. The test consists of: Communication tests. Test files are transmitted or received for formal checks of both syntax and agreed message content. The relevant company within Volvo will test for approval before activation (operational use) starts.

Technical Annexe

2.2 Stage 2 APPLICATIONS

The Odette messages implemented at Volvo are currently: DELINS/DELFOR AVIEXP/DESADV INVOIC/INVOIC SYNCRO/DELJIT ENGDAT ORDER Delivery schedule Despatch advice Commercial invoice Sequence/direct delivery Engineering data Order Message

When the first contact is made, it is a good idea to pass on information about and discuss the messages, which are going to be implemented between the parties. At this time, the sender and recipient should make a note of details such as: File names, if used Versions handled in each message

In normal circumstances, ENGDAT is implemented first, if applicable, followed by DELINS/DELFOR, AVIEXP/DESADV and INVOIC. If applicable, also SYNCRO/DELJIT or ORDER

Engineering data ENGDAT Implementation of the ENGDAT message shall be done in an early stage of a project Delivery schedule DELINS/DELFOR Delivery schedule is primarily aimed at ensuring that data from Volvo can directly update the suppliers order system via computer-to-computer communication. Despatch advice AVIEXP/DESADV Despatch advice shall be sent within one hour after the goods have been despatched. Implementation of the AVIEXP/DESADV message is done once the delivery schedule is in operational use. Commercial invoice INVOIC Implementation of the INVOIC message is done once delivery schedule DELINS/DELFOR and despatch note AVIEXP/DESADV has been put into operational use. Sequence/direct delivery SYNCRO/DELJIT This message is only implemented after special agreement. The message is implemented in parallel with the DELINS/DELFOR message. Sequence/direct delivery ORDERS This message is only implemented after special agreement.

Technical Annexe 3.0 Communication

3.1 Specifications
Network service and protocol Volvo communicates point-to-point using the public switched network service based on X.25 or, ISDN networks. As file transfer protocol, OFTP will be used (Odette ref.: ODG04SP9213 and ODG04OR95044). Asynchronous access (X28) may be used in exceptional cases. The suppliers client within Volvo should approve this. If a partner prefers to use a third party, e.g. a clearing centre or a VAN, he may do so but the partner must then accept sole responsibility for his relationship with the third party. Volvo stipulates however, that the third party must communicate to Volvo using X.25 or ISDN and OFTP, i.e. the same principles, which govern direct communications. To the commercial agreement between the supplier and Volvo is appended a part, which specifies that the supplier takes the total cost within the VAN. File names Volvo does not normally use predefined virtual filenames. File format Volvo supports different file formats. The standard format is undefined (U) format, but those partners who wish to use another format may choose among: Fixed (F) record format of arbitrary length. Variable (V) record format of arbitrary length. Each record should contain one segment.

Code representation
Volvo supports both ASCII and EBCDIC standards. ASCII is the standard option, so those partners who wish to use EBCDIC have to stipulate this.

Technical Annexe
3.2 Agreement regarding communication
The communication agreements, are distributed separately, is intended as a basis for an agreement relating to communication. Suppliers wishing to initiate Odette communication with Volvo are requested to fill in the form and return it to: Volvo Car Corporation "Communication Agreement" Dept. 53340 S - 405 31 GOTHENBURG SWEDEN E-mail: Send to a contact person listed at http://www.it.volvo.se/edi/ We will then contact the supplier and arrange for a communication test. Volvo has chosen to co-ordinate all communication through Volvo Data. Therefore it is enough to return only one communication agreement, irrespective of how many Volvo companies a supplier wants to communicate with. Comments regarding the form: Physical address or SSID Odettes implementation group has developed recommendations for so-called physical addressing. Each country works out its own addresses based on these recommendations. In Sweden, where the physical address is based on the tax authoritys company code, it looks like: PHYSICAL ADDRESS O094200009999999999XXXXXX Where O = Qualifier for Odette. 0942 = Number for the Swedish Tax Board company code. 00009999999999 = The Swedish Tax Board company code. XXXXXX = Internal code per company. This syntax for the physical address must be used. If necessary, ask your software supplier for help. For other countries, please contact your national Odette organisation.

Technical Annexe
Network address This is the users subscription number in the X.25 or ISDN network. For X.25 the layout is defined in the X.121 standard by CCITT. The first four digits is a network identifier (DNIC), e.g. the Swedish Datapak 2 has 2403. The DNIC is followed by the network terminal number (NTN) with a maximum length of 10, subaddress included. Stand-by The stand-by is the hours that the communication system is available. Volvo has a 24-hour stand-by, and if possible, we want the partner to have the same. If not, it is important that a stand-by is agreed upon with Volvo. For instance, the partner might be available every night between 1700-0700. Files shall not be queued up for several days at Volvo. Password For communication using OFTP there are two passwords defined, one for each partner. These are alphanumeric with a maximum length of 8 characters. On the form Volvos send password is already filled in. The partner shall fill in his password in the corresponding space. 3 Security Volvo is generally not using any security methods, like digital signatures or encryption, for the EDI service.

Technical Annexe 4.0 Application of ISO/ EDIFACT and OFTP

4.1 General
At the end of 1987, the ISO (International Standardisation Organisation) adopted a general set of rules for the construction of standardised data messages between the industrial, commercial and transport sectors. The rules and syntax were presented in ISO/EDIFACT DIS 9735. Odette has decided to apply certain ISO/EDIFACT recommendations. This application is presented in the document entitled Odette application of ISO/EDIFACT - June 1988 Version 3 . Among the cornerstones of the syntax we find the following: Service segment (UNB, UNH, UNT, UNZ etc.) Separators Character sets (abc, ABC) Partner Identification

For further information, we recommend you to study the ISO/EDIFACT specification.

Technical Annexe
4.2 Service segment
UNB and UNH and the corresponding final trailer segments UNT and UNZ are used. If the UNOC, Syntax identifier, is used, UNA must be inserted. For a better understanding of the details below, please refer to ISO/EDIFACT 9735 or Odettes implementation of ISO/EDIFACT.

4.3 Separators
The following characters are reserved for special use in ISO/EDIFACT: + Segment tag and data element separator : Component data element separator Segment terminator ? Release character

4.4 Character sets

Volvo supports level A, B and level C. UNOA: As defined in ISO 646 (with the exception of letters, lower case a to z) UNOB: As defined in ISO 646 UNOC: As defined in ISO 8859-1 Latin alphabet no. 1. UNA segment is required. I.e. UNA:+.? '

The character sets are specified in section 5 in ISO/EDIFACT. Volvo recommends the use of level A wherever possible.

4.5 Identification of partners

ODETTE has tried to use existing code systems for identification of partners. This applies to both physical and logical addresses. However, the various data messages make use of current methods of identifying partners. This means for instance, that each supplier receives a supplier number from each customer and that it is the responsibility of the supplier to keep track of this number. As regards to physical and logical addressing, the rules defined for each country participating in Odette are to be applied. For Sweden, the Mechanical engineering Association has defined the following structures, one for the Physical and two for the Logical Address. Physical address, SSID O094200009999999999XXXXXX Where, O = (letter O) for Odette 0942 = Code for the Swedish National Tax Board 00009999999999 = National Tax Board company code XXXXXX = Internal code/company (The Physical Address is used in the OFTP software)

10

Technical Annexe
Logical address (UNB 0004/0010) Together with the qualifier, these data elements produce a unique global identity for the sender or recipient. It is important that the logical address is based on the recommendations specified by the national Odette organisation. Qualifier (UNB 0007) Refers to the logical address (0004/0010). A level of significance is given to the logical address, depending on the value allocated to the qualifier. A value of OD or 30 shows that Odettes rules apply to the logical address. Logical addresses with the qualifier OD are in accordance with the former rules for the logical address. Qualifier 30 replaces this qualifier when the software or the network restricts the use of the qualifier to 30; in this case a special agreement has to be established. Volvo will support both qualifiers for new installations.

Internal code per company (UNB 0008(0014) Can be used to address a unit/business process within a company. Examples of logical addresses: LOGICAL ADDRESS UNB 0004/0010 094200009999999999YYYYYY Where, 0942 = Code for the Swedish National Tax Board 00009999999999 = National Tax Board company code YYYYYY = Internal code per company

LOGICAL ADDRESS UNB 0004/0010 using qualifier OD in UNB 007 094200009999999999YYYYYY:OD Where, 0942 = Code for the Swedish National Tax Board 00009999999999 = National Tax Board company code YYYYYY = Internal code per company OD = Qualifier

LOGICAL ADDRESS UNB 0004/0010 using qualifier 30 in UNB 0007 and internal routing in UNB 008/0014 094200009999999999:30: YYYYYY Where, 0942 = Code for the Swedish National Tax Board 00009999999999 = National Tax Board company code 30 = Qualifier YYYYYY = Internal code per company

11

Technical Annexe
4.6 UNB
Segment: Position: Group: Level: Usage: Max Use: Purpose: Dependency Notes: Comments: Notes:

UNB Interchange Header

0 Mandatory 1 To start, identify and specify an interchange

Example: UNB+UNOA:2+000123456789+000987654321+010403:1608+31' Data Element Summary

Data Component Element Element Name S001 0001

Base Attributes

Volvo Car Attributes

0002

S002 0004 0007 0008

S003 0010 0007 0014

S004 0017 0019 0020

SYNTAX IDENTIFIER M M Identification of the agency controlling the syntax and indication of syntax level SYNTAX IDENTIFIER M a4 M Coded identification of the agency controlling a syntax and syntax level in an interchange. Format UNOA, UNOB or UNOC. Syntax version number M n1 M Version number of the syntax identified in the syntax identifier (0001) 1 Version INTERCHANG SENDER M M Identification of the sender of the interchange Sender identification M an..35 M Name or coded representation of the sender of a data interchange. Partner Identification M an..4 M an..2 Qualifier referring to the source of codes for the identifiers of interchanging partners Address for reverse routing C an..14 C Address specified by the sender of an interchange to be included by the recipient in the response interchanges to facilitate internal routing. INTERCHANG RECIPIENT M M Identification of the recipient of the interchange. Recipient identification M an..35 M Name or coded representation of the recipient of a data interchange. Partner Identification M an..4 M an..2 Qualifier referring to the source of codes for the identifiers of interchanging partners Address for reverse routing C an..14 C Address specified by the recipient of an interchange to be included by the sender and used by the recipient for routing of received interchanges inside his organisation. DATE AND TIME OF PREPARATION M M Date and time of preparation of the interchange. Date of preparation M n6 M Local date when an interchange or a functional group was prepared. Time of preparation M n4 M Local time of day when an interchange or a functional group was prepared. INTERCHANGE CONTROL REFERENCE M an..14 M Unique reference assigned by the sender to an interchange. 12

Technical Annexe
0026 APPLICATION REFERENCE C an..14 C Identification of the application area assigned by the sender, to which the messages in the interchange relate e.g. the message identifier if all the messages in the interchange are of the same type. Insert TEST during the test period.

13

Technical Annexe
4.6 UNZ
Segment: Position: Group: Level: Usage: Max Use: Purpose: Dependency Notes: Comments: Notes:

UNZ Interchange Trailer

0 Mandatory 1 To end and check the completeness of an interchange.

Example: UNZ+1+31' Data Element Summary

Data Component Element Element Name 0036

Base Attributes

Volvo Car Attributes

0020

INTERCHANGE CONTROL COUNT M n..6 M Count either of the number of messages or, if used, of the number of functional groups in an interchange. INTERCHANGE CONTROL REFERENCE M an..14 M Unique reference assigned by the sender to an interchange. Shall be identical to 0020 in UNB

14

Technical Annexe 5.0 Instructions for Implementation

5.1 Instructions for implementation
The test is divided into seven steps: 1. 2. 3. 4. 5. 6. 7. Signing the agreements Set up communication Volvo transmits to the supplier The supplier evaluates the received file The supplier transmits to Volvo Volvo evaluates the file End of test phase

Below you will find a detailed description of each step in the test.

5.2 Signing agreements

The supplier fills out the forms EDI, Application Of EDIFACT, Data Sheet or EDI, Application Of Odette 3.2, Data Sheet and Specification of CAD/CAM Parameters, if applicable, and returns the forms to Volvo The person responsible for implementation at Volvo, contacts the supplier, in order to reach an agreement on the date for starting the implementation. At this occasion, parameters not included in the agreements above will be exchanged.

5.3 Volvo transmits to the supplier

Volvo sends the EDI message according to the agreements

5.4 The supplier evaluates the received EDI file.

The supplier converts the EDI message and analyses the syntax, as well as the logical content of the file. The supplier checks the file for: * Loss of information * Incorrect information

5.5 The supplier transmits to Volvo

The supplier contacts Volvo to settle a date for the tests. On this occasion, parameters not included in the agreements will be exchanged. The suppliers create an EDI message of their own. The supplier transmits the EDI, to Volvo as agreed.

5.6 Volvo evaluate the received file

Volvo analyses the syntax of the EDI message. If any violation of the syntax rules occurs, Volvo contacts the supplier. Volvo analyses the content in the ENGDAT message, if applicable, and the CAD files. If the CAD files can not be further processed, in accordance with the ENGDAT message, Volvo contacts the supplier for feedback.

5.7 Step 4 and 5 will be repeated until the information flows without any interruptions.
Closing up the test phase Volvo updates the supplier to production status and the responsible part at Volvo will be the receiving unit. 15