corporation - iconnecticonnect-corp.com/specs/vendors/intermet/foundry/... · the intermet...

Corporation

IMPLEMENTATION GUIDELINE FOR EDI CONVERSION

ADVANCE SHIPMENT NOTICE TRANSACTION(856)

ANSI X12 VERSION 4010

Published: February 2004

Version 001

Carolyn Hines

Intermet MIS Dept.

1000 Brookstone Centre Pkwy.

Columbus, GA 31904

(706) 649-7604

Intermet Corporation Conventions Advance Shipment Notice(856)

Intermet Corporation of 35 February 2004

INTRODUCTION

The purpose of the Ship Notice/Manifest transaction, also known as the "Advanced Ship Notice (ASN)", is to convey the contents of and key reference numbers related to a shipment of material, e.g. Shipment Identification, Carrier PRO, Bill of Lading, Packing Slip, etc., placed in transit to a Intermet facility. Ship quantities and due dates used in the 856 for parts shipped to manufacturing locations are dictated by an 830 transaction (Planning Schedule with Release Capability). The data transmitted in the 856 is used by Intermet to facilitate the on-line computer receipt of material, shipment tracking, and payment of supplier invoices. The Shipment Identification Number (SID) is the primary reference used by Intermet in all of these processes. In addition to ship quantities and due dates, other data elements to be included in the 856, e.g. Purchase Order Number, Item Number, Ship-to Location Code, etc. are conveyed to the supplier via the EDI 830 transaction as applicable; the 856 should echo back these elements when material is shipped, ideally from an integrated system which precludes the need for data entry. This requires that the data received from Intermet be stored in the supplier's system and retrieved when the 856 is generated.

An EDI 856 transmission (ISA through IEA segment) can consist of multiple transaction sets, one transaction set (ST through SE segment) per shipment. Each 856 transaction set will consist of three levels (shipment, item, and summary.) Segments in the shipment level convey reference numbers, etc. which pertain to the shipment as a whole while segments at the item level describe a single part number within the shipment. Summary level segments are used to validate the transaction (see CTT and SE segments). Generally, the order in which they are presented within each level is not significant provided that all segments required by Freightliner are included; similarly, Freightliner does not desire the inclusion of segments not required per this section of the EDI User's Manual, i.e. send only the segments, elements, and values requested. The appropriate EDI Coordinator must be advised if one or more segments required by Freightliner cannot be included in the transaction and/or segment(s) not required cannot be excluded; all discrepancies will be addressed on a case by case basis and must be authorized prior to implementation of the transaction.

Example:

MFG Example



ST+856+0020. BSN+00+5253+19990727+2155. DTM+011+19990727+2155. HL+1++S. MEA+PD+G+10800+LB. TD1+RCK58+8. TD5+B+2+PRO +M. TD3+TL++409. REF+BM+5253. REF+PK+5253. REF+CN+PDX-075374-9. N1+ST+TMP+92+001. N1+SU+MFG Company+92+MFG. HL+2+1+I. LIN+001+BP+A18-29879-004. SN1++8+EA. PRF+A02121+++19990727+026. REF+PK+5253. CTT+2+8. SE+20+0020

This document is intended to serve as a guide to Electronic Data Interchange (EDI) for

suppliers of the Intermet Corporation. The Intermet Corporation makes no warranties,

express or implied regarding the use of this document. In no event, will the Intermet

Corporation, it’s employees or agents, be liable for any consequential, incidental, or

indirect damages (including damages for loss of business profits, business interruption,

loss of business information, and the like) arising from the use or inability to use this

document.



TABLE OF CONTENTS:

INTRODUCTION............................................................................................................. 2

TABLE OF CONTENTS: ................................................................................................ 5

IMPLEMENTATION PROCEDURE GUIDE .............................................................. 6

EDI Trading Partner Implementation .................................................................................................. 6

ISA/IEA FUNCTIONAL GROUP CONTROL REQUIREMENTS ........................... 7

SEGMENT ISA – Interchange Control Header .................................................................................. 7

TRANSACTION SET: ALL TRANSACTION SETS .................................................. 8

SEGMENT - IEA Interchange Control Trailer .................................................................................... 8

SEGMENT – GS Functional Group Header ........................................................................................ 9

SEGMENT – GE Functional Group Trailer ...................................................................................... 10

TABLE 1: DATA SEGMENT SEQUENCE FOR HEADING AREA ...................... 11

TRANSACTION SEGMENTS ...................................................................................... 12

SEGMENT: ST - TRANSACTION SET HEADER 12 SEGMENT: BSN - Beginning Segment (Ship Notice) 13 SEGMENT: DTM – Date/Time Reference 14 SEGMENT: HL – Hieracrhy Level 15 SEGMENT: MEA – Measurement 16 SEGMENT: TD1 – Carrier Detail(Quantity and Weigeh 17 SEGMENT: TD5 – Caririer Detail(Routing Sequence/transit time) 18 SEGMENT: TD3 - Carrier Detailr (Equipment) 20 SEGMENT: REF - Reference 21

SEGMENT: N1 – Name ...................................................................................................................... 22

TABLE 2: DATA SEGMENT SEQUENCE FOR DETAIL AREA .......................... 23

SEGMENT: HL – Hieracrhy Level 24 SEGMENT: LIN - Item Identification Detail 25 SEGMENT: SN1- Item Detail(shipment) 26 SEGMENT: PRF – Purchase Order Number 27 SEGMENT: REF – Reference 28

TABLE 3: DATA SEGMENT SEQUENCE FOR SUMMARY AREA .................... 29

SEGMENT: CTT - Transaction Totals .............................................................................................. 30

SEGMENT: SE - Transaction Set Trailer ......................................................................................... 31

INTERMET CORPORATION FACILITY DUNS NUMBERS ................................ 32

ATTACHMENTS: .......................................................................................................... 33

ELECTRONIC DATA INTERCHANGE TRADING PARTNER AGREEMENT ............................ 33



Implementation Procedure Guide

EDI Trading Partner Implementation

The Intermet Corporation will set up the trading partner relationship based on the information supplied on the Trading Partner Survey filled out by our Suppliers. The Intermet Corporation uses the General Electric Information System (GEIS) network for exchanging EDI transactions. Intermet Corporation Trading Partners are not limited to this VAN, as Advantis, Ordernet, and the many other major VANs offer interconnects to exchange EDI documents between networks. The Intermet Corporation only uses one mailbox address for testing and production. The cost of receiving the transactions is distributed by the VAN, fifty-fifty (50/50) between the Intermet Corporation and The Trading partner. An important part of the EDI communications between the Intermet Corporation and its Trading Partner, is documented on pages 6 through 9, detail Intermet guidelines of the ISA and GS enveloping segments.



ISA/IEA FUNCTIONAL GROUP CONTROL REQUIREMENTS

SEGMENT ISA – Interchange Control Header LEVEL N/A MAX USAGE/LOOPS 1/None PURPOSE: To start and identify an interchange of one or more functional groups and interchange related control segments. GENERAL None INFORMATION: EXAMPLE: ISA *00* ZZ*123456789*01* 987654321 9004110930*U*00200*000000001*0**P**N/L

ELEM ELEM ANSI

ID # NAME FEATURE COMMENTS

ISA01 744 Authorizing Information M ID 02/02 Use ‘00’ (zeros)

Qualifier

ISA02 745 Authorizing Information M AN 10/10 Use 10 spaces

ISA03 746 Security Information M ID 02/02 Use ‘00’ (zeros)

Qualifier

ISA04 747 Security Information M AN 10/10 Use 10 spaces

ISA05 704 Interchange ID Qualifier M ID 02/02 Use ‘01’

ISA06 705 Interchange Sender ID M ID 15/15 Intermet DUNS Number1

ISA07 704 Interchange ID Qualifier M ID/0202 Use ‘ZZ’

ISA08 706 Interchange Receiver ID M ID 15/15 Assigned supplier code

ISA09 373 Date M DT 06/06 Use date of trans-

mission ‘YYMMDD’

ISA10 337 Time M TM 04/04 Use time of trans-

mission ‘HHMM’ 24hr.

ISA11 726 Interchange Standards ID M ID 01/01 Use ‘U’ for USA

ISA12 703 Interchange Version ID M ID 05/05 Use ‘00400’

ISA13 709 Interchange Control Number M NO 09/09 Must be the same num-

ber as in IEA02.

Sequential number

starting with 1 and

incremented by 1 for

each ISA between

sender and receiver.

ISA14 749 Acknowledgement Request M ID 01/01 Use ‘1’997 required

ISA15 748 Test Indicator M ID 01/01 Use ‘P’ for Production

ISA16 701 Sub-element Separator M AN 01/01 Must be different than

Element separator

Reference page 32, “Intermet Corporation Facility DUNS Numbers”



Transaction Set: All Transaction Sets

SEGMENT - IEA Interchange Control Trailer LEVEL N/A MAX USAGE/LOOPS 1/None PURPOSE: To define the end of an interchange of one or more functional groups and interchange related control segments. GENERAL The interchange control number in this trailer must match the INFORMATION: value in the ISA segment. ISA13 date element. EXAMPLE: IEA*3000000001 N/L

ELEM ELEM ANSI


IEA01 405 Number of Included Groups M NO 01/05 Number of GS segments

included between ISA

and this IEA.

IEA02 709 Interchange Control Number M NO 09/09 Must match ISA13



SEGMENT – GS Functional Group Header LEVEL N/A MAX USAGE/LOOPS 1/As required PURPOSE: To start and identify a group of related transaction sets and provide control and application identification information. GENERAL Strict compliance and agreement on content by trading INFORMATION: partners is required. EXAMPLE: GS*ST*01000*0400*900205*20*X*002002 N/L

ELEM ELEM ANSI


GS01 479 Functional ID M ID 02/02 For ‘830’ use ‘PS’

GS02 142 Application Sender Code M ID 02/12 This element contains

the Intermet DUNS Number2

GS03 124 Application Receiver Code M ID 02/12 This element contains

your assigned supplier

code

GS04 029 Data Interchange Date M DT 06/06 Date of transmission

‘YYMMDD’

GS05 030 Data Interchange Time M TM 04/04 Time of transmission

‘HHMM’ – 24 hour clock

GS06 028 Data Interchange Number M NO 01/09 Must be the same as the

number in GE02

GS07 455 Responsible Agency M ID 01/02 Use ‘X’ for X12

GS08 480 Version M ID 01/12 ANSI Version and Release

number. Use ‘004010’

Reference page 32, “Intermet Corporation Facility DUNS Numbers”



SEGMENT – GE Functional Group Trailer LEVEL N/A MAX USAGE/LOOPS 1/As required PURPOSE: To define the end of a functional group of related transaction sets. GENERAL The data interchange control number (GE02) in trailer must INFORMATION: be identical to the same data element in the associated functional group header (GS) EXAMPLE: GE*1*20 N/L

ELEM ELEM ANSI


GE01 097 Number of Included M NO 01/06 The total number of

Transaction Sets ST/SE pairs within

the functional group.

GE02 028 Data Interchange Control M NO 01/09 Must be identical to the

Number same data element in the

associated group header

(GS06).



TABLE 1:DATA SEGMENT SEQUENCE FOR HEADING AREA

Seg Req. Max. Loop Intermet

ID Name Dec. use Repeat Use ST Transaction Set Header M 1 YES

BSN Beginning Shipment M 1 YES

DTM Date/Time Shipment M 2 YES

HL Hierarchy Level M 1 YES

MEA Measurements M 1 YES

TD1 Carrier Detail(Qty & Weight) M 1 YES

TD5 Carrier Detail(Routing) M 1 YES

TD3 Carrier Detail(Equipment) M 1 YES

REF Reference(BOL/packing list) M 2 YES

N1 Name M 2 N1/200 YES



TRANSACTION SEGMENTS

SEGMENT: ST - TRANSACTION SET HEADER

LEVEL: Heading MAX USAGE/LOOPS: 1/None PURPOSE: To indicate the beginning of a transaction set and to assign a control number. GENERAL INFORMATION: The transaction set control number (ST02) and the header must match the transaction set control number (SE02) in the transaction set trailer (SE). EXAMPLES: ST*856*000000001

AIAG/

ELEM ELEM INTERMET INTERMET

ID # NAME FEATURE USE COMMENTS

ST01 143 Transaction Id Set code M ID 03/03 YES Use ‘856’ for

---------- Advance Shipment

Notice

ST02 329 Transaction Set Control M ID 04/09 YES Intermet Use:

---------- a unique control

M ID 09/09 number.

(same as SE02)

SEGMENT: BSN - Beginning Segment (Begin Ship Notice)

LEVEL: Heading MAX USAGE/LOOPS: 1/None



PURPOSE: To indicate the beginning of a advance shipment transaction set and it BOL number, date/time created . GENERAL INFORMATION: Element BSN02 must be a unique shipper ID Not being used in the last 12 months. EXAMPLES: BSN*00*00000414*20040205*1110

AIAG/



BSN01 353 Transaction Purpose M ID 02/02 YES Intermet use

Code ---------- 00 = original

01 = delete

05 = replace

BSN02 369 Shipment Identification M AN 01/30 YES BOL Number

----------

M AN 01/08

BSN03 373 Date M DT 08/08 YES CCYYMMDD

----------

BSN04 337 Time M ID 02/02 YES HHMM

----------



SEGMENT: DTM – (Date/Time References) LEVEL: Heading MAX USAGE/LOOPS: 1/None PURPOSE: To specify pertinent dates and times . EXAMPLES: DTM*011*20040205*1110*ET DTM*017*20040206*1110*ET

AIAG/



DTM01 374 Date/Time qualifier M AN 03/03 YES 011 = shipped

---------- 017 = delivery

DTM02 373 Date M DT 08/08 YES The bill of

Shipment/Delivery ---------- lading created

CCYYMMDD

DTM03 337 Time M TM 04/04 YES HHMM

Shipment/Delivery ----------

DTM04 623 Time Code O ID 02/02 YES Intermet use

---------- ‘ET’ eastern

standard



SEGMENT: HL – (Hierarchial Level) LEVEL: Detail - Shipment MAX USAGE/LOOPS: 1 PURPOSE: To identify dependencies among and the content of Hierarchically related groups of data segments. GENERAL INFORMATION: The HL This segment has a specific hierachy which can be displayed here. EXAMPLES: HL*1**S AIAG/



HL01 628 Heirarchical ID Number M AN 01/12 YES A unique number

---------- assigned by

M AN 01/01 sender must

start with ‘1’

HL02 734 Hierarchical Parent ID C AN 01/01 NO

----------

HL03 735 Hierarchical level code M ID 01/01 YES Code Values

---------- S=Shipment

I=Item

HL04 736 ID Code C ID 01/01 NO

----------

SEGMENT: MEA – (Measurements) LEVEL: Detail – (Shipment Hierarchical Level)



MAX USAGE/LOOPS: 1 PURPOSE: To identify dependencies among and the content of Hierarchically related groups of data segments. GENERAL INFORMATION: The HL This segment has a specific hierachy which can be displayed here. EXAMPLES: HL*1**S AIAG/



MEA01 737 Measurement Reference M ID 02/02 YES General use

ID Code PD=physical

dimension

MEA02 738 Measurement Dimension M ID 01/03 YES Intermet use

Qualifier ---------- G= Gross weight

M ID 01/02 N= Net weight

MEA03 739 Measurement Value M R 01/10 YES Value qualified

By MEA02

MEA04 355 Unit of Measure M ID 02/02 YES

MEA05 740 Range Minimum C R 01/10 NO

MEA06 741 Range Maximum C R 01/10 NO

SGMENT: TD1- Carrier Detail (Quantity and Weight) LEVEL: Detail Shipment



MAX USAGE/LOOPS: 1/NONE PURPOSE: To specify the transportation details relative to Commodity, weight and quantity. GENERAL INFORMATION: provide a total lading quantity for the entire Shipment. EXAMPLES: TD1*TUB90*20~

AIAG/



TD101 103 Packaging code M ID 03/05 YES Container

---------- code

TD102 80 Lading Quantity M ID 01/07 YES Number of

---------- containers of

the lading

commodity

TD103 23 Commodity code qualfier O ID 01/30 NO

----------

TD104 22 Commodity code O ID 01/30 NO

----------

TD105 79 Lading Description O ID 01/50 NO

----------

TD106 187 Weight Qualifier O ID 01/02 NO

----------

TD107 81 Weight O R 01/10 NO

----------

TD108 355 Unit of Measurement O ID 02/02 NO

----------

TD109 387 Volume C AN 01/08 NO

----------

TD110 368 Unit of muasurement O ID 02/02 NO

----------



SGMENT: TD5 - Carrier Detail (Routing Sequence/transit Time) LEVEL: Header MAX USAGE/LOOPS: 1/NONE PURPOSE: To specify the carrier and sequence of routing and to provide transit time information. GENERAL INFORMATION: Used to distinguish parts by name or free form comments. EXAMPLES: TD5*B*2*XXXX*M N/L (MOTOR)

AIAG/



TD501 133 Routing Sequence code O ID 01/02 YES Intermet use:

---------- 'B'= Originat-

M ID 01/02 ing Carrier

TD502 066 ID Code Qualifier C ID 01/02 YES Intermet use:

---------- '2'= Standard

M ID 01/02 carrier alpha-

betic (SCAC

code).

TD503 067 ID Code C ID 02/17 YES For TD502. Use

---------- carrier SCAC

M ID 02/04 code.

TD504 091 Transportation Method C ID 01/02 YES Intermet use:

Mode ---------- AC=Air carrier

M ID 01/02 AE=Air express

PD=parcel

delivery (UPS,

Federal Express

etc.)

R=Rail

M=Motor

TD505 387 Routing C AN 01/35 NO

----------

TD506 368 Shipment/Order status O ID 02/02 NO

Code ----------



SEGMENT: TD5 - Carrier Detail (continued)

AIAG/



TD507 309 Location Qualifier O ID 01/02 YES 'PP'=Pool

---------- point (for con-

solidation

shipments).

TD508 310 Location Identifier C AN 01/25 YES If TD507 ='PP'

---------- use pool point

C AN 01/07 location.

TD509 731 Transit Direction Code O ID 02/02 NO

----------

TD510 732 Transit Time Direction O ID 01/02 NO

Qualifier ----------

TD511 733 Transit Time O R 01/04 NO

----------

TD512 284 Service Level Code C ID 02/02 NO






SGMENT: TD1- Carrier Detail (Equipment) LEVEL: Detail Shipment MAX USAGE/LOOPS: 1/NONE PURPOSE: To specify the transportation details relative to The equipment used by the carrier. GENERAL INFORMATION: provide to identify the serial number of the trailer EXAMPLES: TD1*TL*1234567890~

AIAG/



TD301 40 Equipment Description M ID 02/02 YES Code identifing

---------- type of equipment

TD302 206 Equipment Initial N AN 01/04 NO

TD302 207 Equipment number M ID 01/10 YES Serial number of

---------- equipment. Must be

Numberic 0 thru 9

TD304 187 Commodity code O ID 01/02 NO

TD305 81 Weight O R 01/10 NO

TD306 355 Unit of Measeure O ID 01/02 NO

TD307 102 Ownership Code O ID 01/01 NO

TD308 407 Seal Status Code O ID 02/02 NO

TD309 225 Seal Number O AN 02/15 NO

TD310 24 Equipment Type O ID 04/04 NO



SEGMENT: N1 – Name LEVEL: Header MAX USAGE/LOOPS: 1/N1/200 PURPOSE: To identify a party by type of organization, name and code. GENERAL INFORMATION: The N1 loop in the heading area is used to identify the release issuer and the supplier EXAMPLES: N1*ST**01*609120753 N/L N1*SU**01*123456789 N/L

AIAG/



N101 98 Origination identity M ID 02/02 YES Intermet use:

---------- 'SU' = Release

supplier

N102 93 Name C AN 01/35 NO

----------

N103 66 ID Code Qualifier C ID 01/02 YES Intermet use:

---------- '92' = Intermet

M ID 02/02 assigned vendor

code

N104 67 ID Code C ID 02/17 YES If N101=SU this

---------- element would

M ID 02/17 contain the

supplier vendor

code. If

N101=ST then

this element

would contain

Intermet DUNS

number.



SEGMENT: REF- Reference Number

LEVEL: Detail MAX USAGE/LOOPS: 12/N1 PURPOSE: To transmit identifying numbers associated with the name party. GENERAL INFORMATION: This segment is used to identify the receiving dock of ship-to-location. EXAMPLES: REF*PK*01234567~ N/L

AIAG/



REF01 128 Reference Number M ID 02/02 YES Intermet Use:

Qualifier ---------- PK=Dock code

BM=Bill of Lading

AW=Air Waybill

REF02 127 Reference Number C AN 01/30 YES Shipment info

---------- based on the re-

M AN 01/08 ference qual

REF03 352 Description C AN 01/80 NO



TABLE 2: DATA SEGMENT SEQUENCE FOR DETAIL AREA

Seg. Req. Max. Loop Intermet

ID ID Name Des. use Repeat Use HL Hierarchical Level M 1 1/LIN YES

LIN Item Information M 1 1000 YES

SN1 Item Detail-Shipment M 1 YES

PRF Purchase Order Reference M 1 YES

REF Additional Item Detail O 1 YES



SEGMENT: HL – (Heirarchical Level) LEVEL: Detail - Shipment MAX USAGE/LOOPS: 1/LIN PURPOSE: To identify dependencies among and the content of Hierarchically related groups of data segments. GENERAL INFORMATION: The HL This segment has a specific hierachy for which can be displayed here. EXAMPLES: HL*2**S AIAG/



HL01 628 Heirarchical ID Number M AN 01/12 YES This number is

---------- incremented from

M AN 01/01 the first HL no

HL02 734 Hierarchical Parent ID C AN 01/01 NO

----------

HL03 735 Hierarchical level code M ID 01/01 YES Code Values

---------- S=Shipment

I=Item

HL04 736 ID Code C ID 01/01 NO

----------



SEGMENT: LIN - Item Identification Detail LEVEL: Detail MAX USAGE/LOOPS: 1/LIN/10,000

PURPOSE: To specify basic item identification data. GENERAL INFORMATION: This segment is used for part number information. EXAMPLES: LIN**BP*05003670*VN*P5912740

AIAG/



LIN01 350 Assign Identification O AN 01/06 NO

LIN02 235 Product ID Qualifier M ID 02/02 YES Intermet use:

‘BP’=Part Number

LIN03 234 Product ID M AN 01/30 YES Intermet's Part Number

LIN04 235 Product Qualifier M ID 02/02 YES Intermet use:

VN = Vendor part number

LIN05 234 Product ID M AN 01/30 YES Vendor part number

LIN06 Through LIN31

Note: LIN06 through LIN31 provide 13 additional pairs of

Product/service ID Qualifiers (235) and Product/service

ID (234).



SEGMENT: SN1 – Item Detail(shipment) LEVEL: Detail MAX USAGE/LOOPS: 1/LIN PURPOSE: To specify item detail relative to a shipment. GENERAL INFORMATION: This segment indicates the quantity for each line item. EXAMPLES: SN1**300*EA N/L (General Use)

AIAG/



SN101 0350 Item Description type O ID 01/20 NO

SN102 0382 Number of Units M R 01/10 YES

SN103 0355 Unit of Measure M ID 02/02 YES

SN104 0646 Qty Shipped to date O R 01/15 NO

SN105 0330 Quantity Ordered O R 01/15 NO

SN106 0355 Unit of measure O ID 02/02 NO

SN107 0728 Returnable Container O ID 01/02 NO

SN108 0668 Line Item Code O ID 02/02 NO

SEGMENT: PRF- Purchase Order Reference



LEVEL: DETAIL MAX USAGE/LOOPS: 1/HL PURPOSE: To provide reference to a specific purchase order. GENERAL INFORMATION: This segment is display Intermet Purchase Order Number and is required at this order level EXAMPLES: PER*0123456789*011111111111**013104 N/L

AIAG/



PRF01 324 Purchase order Number M ID 01/22 YES Intermet

P O

PRF02 328 Release Number O AN 01/35 YES Intermet

Release

PRF03 327 Change order O ID 02/02 NO

Sequence number

PRF04 337 Purchase Order Date M AN 08/08 YES CCYYMMDD

PRF05 350 Assigned Identification O AN 01/45 NO

SEGMENT: REF- Reference Number

LEVEL: Detail MAX USAGE/LOOPS: 5/LIN PURPOSE: To transmit identifying numbers associated with the name party. GENERAL INFORMATION: This segment is used to identify the receiving dock of ship-to-location.



EXAMPLES: REF*DK*ASLK1 N/L

AIAG/



REF01 128 Reference Number M ID 02/02 YES Intermet Use:

Qualifier ---------- DK=Dock code

REF02 127 Reference Number C AN 01/30 YES The Intermet

---------- assigned name

M AN 01/08

REF03 352 Description C AN 01/80 NO



TABLE 3: DATA SEGMENT SEQUENCE FOR SUMMARY AREA

Seg. Req. Max. loop Intermet

ID Name Des. use Repeat Use

CTT Transaction Totals M 1 YES

SE Transaction set Trailer M 1 YES

Note 1: Number of line items (CTT01) is the accumulation of LIN segments. If used, hash total (CTT02) is the sum of the values of the quantities (SN102) for each SN1 segment.



SEGMENT: CTT - Transaction Totals LEVEL: Summary MAX USAGE/LOOPS: 1/None PURPOSE: To transmit hash totals for 'LIN' segments and for quantity appearing in element 'FST01' within the this transaction set. GENERAL INFORMATION: This segment allows the receiver to perform checks for completeness and corrections of this transaction set. EXAMPLES: CTT*5*2679 N/L CTT*1*1500 N/L (Primary Metals)

AIAG/



CTT01 354 Number of Lines Items M NO 01/06 YES Total number

---------- of 'HL'

segment.

CTT02 347 Hash Total O R 01/10 YES General use:

---------- The hash total

of all quanti-

ties ON THE

(SN102).

Primary Metals

Use:

If Purchase by

weight, this

is the actual

weight total

(sum of SN102

quantities).

CTT03 81 weight O R 01/08 NO

----------

CTT04 355 Unit of measure code C ID 02/02 NO

----------

CTT05 183 Volume O R 01/08 NO

----------

CTT06 355 unit of measure code C ID 02/02 NO

----------

CTT07 352 Description C AN 01/80 NO



SEGMENT: SE - Transaction Set Trailer

LEVEL: Summary MAX USAGE/LOOPS: 1/None PURPOSE: To indicate the end of the transaction set and provide the count of transmitted segments including the beginning 'ST' and ending 'SE' segments. GENERAL INFORMATION: The transaction set control number value must must match the transaction set control number (ST02) in the transaction set header (ST). EXAMPLES: SE*100*000000001 N/L

AIAG/



SE01 96 Number of Included M ID 01/06 YES The total of

Segments ---------- all segment in

in the trans-

action set,

including the

'ST' and "SE'

segments.

SE02 329 Transaction Set Control M ID 04/09 YES Same as 'ST02'

Number ----------

M ID 09/09



Intermet Corporation Facility DUNS Numbers

DUNS NUMBER FACILITY

005163282 INTERMET DECATUR FOUNDRY

948511704 INTERMET COLUMBUS MACHINING

054202916 INTERMET COLUMBUS FOUNDRY INC.

148508120 INTERMET HIBBING CASTING CORPORATION

157702515 INTERMET NEW RIVER CASTINGS COMPANY INC.

809942147 INTERMET ARCHER CREEK FOUNDRY

607588183 INTERMET HAVANA FOUNDRY



ATTACHMENTS:

ELECTRONIC DATA INTERCHANGE TRADING PARTNER AGREEMENT

THIS ELECTRONIC DATA INTERCHANGE (EDI) TRADING PARTNER AGREEMENT (The “Agreement”) is made as of ________________, 2000 by and between the Intermet Corporation with offices at 5445 Corporate Drive, Troy, Michigan and ___________________________________________________________ (“Supplier”), a ________________________________________________ corporation with offices at _________________________________________________________________________.

RECITALS The Intermet Corporation and Supplier desire to facilitate purchase and sale transactions (“Transactions”) by electronic transmitting and receiving data in agreed formats in substitution for conventional paper documents and to assure that such transactions are not legally invalid or unenforceable as a result of the use of available electronic technologies for the mutual benefit of the parties. NOW THEREFORE, the parties, intending to be legally bound, agree as follows: Section 1. Prerequisites. 1.1 Documents: Standards. Each party may electronically transmit to or receive from

the other party any of the transaction sets listed in Appendix A, entitled “Transaction Sets”, and other transaction sets which the parties, by written agreement, add to Appendix A, (collectively “Documents”). All documents shall be transmitted in accordance with the standards set forth in the most current ANSI X12, 4010 Standard Guidelines as modified from time to time. Documents may be transmitted between Intermet Corporation locations and the locations of the Supplier, which have been tested and approved by the Intermet Corporation for EDI in accordance with the applicable Intermet Corporation implementation guideline.

1.2 Third Party Service Providers: Documents will be transmitted electronically to each party

either directly or through a third party service provider (“Provider”). Unless otherwise agreed to in writing, each party shall be responsible for the costs of any Provider with which it contracts. Either party may modify its election to use or not to use a Provider upon 30 days prior written notice.

1.3 System Operations: Each party is responsible for ensuring that it can effectively and

reliably transmit and receive documents. 1.4 Security Procedures: Each party shall properly use those security procedures, including

any specified as an attachment to this Agreement, to prevent unauthorized transmissions and protect all Documents from improper access, modification, interception or retrieval.

1.5 Signatures: If either party transmit a Document using any network access device or

password of such party, such Document will be deemed “signed” and “executed” by such party. Each party waives any defense to the enforceability of any contract formed as a result of the transmission of such Document on the ground that it was not “signed” or “executed” by the party.



Section 2. Transmissions. 2.1 Proper Delivery: Documents shall be deemed properly delivered by the sender when

transmitted to the receiving party’s designated receipt terminal, Provider or electronic mailbox whichever shall occur first.

2.2 Proper Receipt: Documents shall be deemed properly received by the receiving party

when accessible at such party’s designated receipt terminal, Provider, or electronic mailbox. The receiving party is required to transmit a control message in return

2.3 Acceptance: If the parties agree in writing that notification of acceptance of the terms of

a Document is required, any such Document even though properly received, shall not give rise to any obligation unless and until the party receiving such Document has properly delivered in return of an acceptance Document or application acknowledgement.

2.4 Garbled Transmissions: If any properly delivered Document is received in an

unintelligible or garbled form (i.e. one which can not be completely translated ) the receiving party shall promptly notify the originating party (if identifiable from the received Document) in a reasonable manner. In the absence of such a notice, the originating party’s records of the contents of such Document shall control.

Section 3. Transaction Terms. 3.1 Terms and Conditions: Any Transaction made pursuant to this Agreement shall be

subject to terms and conditions in Intermet Corporation Standard Purchase Order Terms and Conditions. The terms of the agreement shall prevail in the event of any conflict with any other terms and conditions applicable to any Transaction made pursuant to this agreement.

3.2 Validity and Enforceability: This agreement has been signed by the parties to evidence

their mutual intent to create binding obligations pursuant to the electronic transmissions and receipt of Documents which contain some or all of the terms of such obligations. Any Document properly transmitted pursuant to this Agreement shall be considered to be a “writing” or “in writing”.

3.3 International Transactions: International Transactions made pursuant to this Agreement

shall also be subject to the terms and conditions the Intermet Corporation Standard Purchase Order Terms and Conditions. In addition, such transactions shall be governed by and construed according to the laws of the State of Michigan as such laws are applied to contracts between residents of the State of Michigan to be performed entirely within such state , specifically excluding application of the U.N. Convention Contracts for International Sale Of Goods and the uniform Rules of Conduct for interchange of Trade Data by Teletransmission (UNCID).



Section 4. Miscellaneous. 4.1 Termination: This agreement shall remain in effect until terminated by either party with

not less than ten(10) days prior written notice, which notice shall specify the effective date of termination; provided, however, that any termination shall not affect the respective obligations or rights of the parties arising under any written agreement or the terms and conditions referred to in Section 3.1, or any Documents under this Agreement prior to the effective date of termination.

4.2 Severabilitv: Any provision of this Agreement which is determined to be invalid or

unenforceable will be ineffective to the extent of such determination without invalidating the remaining provisions of this Agreement or affecting the validity or enforceability of such remaining provisions.

4.3 Entire Agreement: This Agreement, including any appendix, attachment, or supplement

and any other written agreements referenced in this Agreement, each of which is incorporated herein, constitutes the complete statement of an agreement between the parties relating to the electronic transmission of Documents and supercede all prior representations or agreements, whether oral or written, with respect to such matters. This agreement is for the benefit of, and shall be binding upon, the parties and their respective successors and assigns.

4.4 Governing Law: This Agreement shall be governed by and interpreted in accordance

with the laws, other than choice of law rules, of the State of Michigan. 4.5 No Buy/Sell Commitment: Nothing in this Agreement shall be deemed to create any

commitment on the part of either party to buy or sell any specific goods. This Agreement is simply and solely intended to facilitate the electronic handling of Documents between the parties. Neither party shall be entitled to or required to do any certain amount of business with the other, nor shall either party be required to do business with the other for a certain period of time. Commitments are made only by the Documents transmitted pursuant to the Agreement.

Each party has caused this Agreement to be properly executed on its behalf as of the date first above written.

Intermet Corporation Supplier

BY___________________________________BY_____________________________________ (Signature) (Signature) NAME_______________________________ NAME__________________________________ (Type or print) (Type or print) TITLE________________________________TITLE___________________________________ DATE________________________________ DATE___________________________________ Mail Signed Copy to: Carolyn Hines 1000 Brookstone Centre Parkway Columbus, GA 31904-2955