corporation - iconnect · the intermet corporation only uses one mailbox address for testing and...

Corporation

IMPLEMENTATION GUIDELINE FOR EDI CONVERSION

MATERIAL RELEASE TRANSACTION SET (830)

ANSI X12 VERSION 4010

Published: April 8, 2004

Version 003

Carolyn Hines

Intermet MIS Dept.

1000 Brookstone Centre Pkwy.

Columbus, GA 31909

(706) 649-7604

Intermet Corporation Conventions Material Release (830)

Intermet Corporation of 38 April 8, 2004

INTRODUCTION

This document provides the format and establishes the data contents of a planning schedule

with release capability EDI transaction set. This transaction set provides for customary and

established business practice relative to the transfer of forecasting / material release

information between the Intermet Corporation and it’s suppliers.

Intermet use the releases, as a buyer’s authorization for the seller to commit to resources,

such as labor or material, period-to-date and ship/delivery patterns requirements that have

been represented in ‘buckets,’ as daily or weekly quantities.

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: ................................................................................................ 3

IMPLEMENTATION PROCEDURE GUIDE .............................................................. 4

EDI Trading Partner Implementation .................................................................................................. 4

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

SEGMENT ISA – Interchange Control Header .................................................................................. 5

TRANSACTION SET: ALL TRANSACTION SETS .................................................. 6

SEGMENT - IEA Interchange Control Trailer .................................................................................... 6

SEGMENT – GS Functional Group Header ........................................................................................ 7

SEGMENT – GS Functional Group Trailer ........................................................................................ 8

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

TRANSACTION SEGMENTS ........................................................................................ 9

SEGMENT: ST - TRANSACTION SET HEADER ............................................................................ 9

SEGMENT: BFR - Beginning Segment (Forecast/Material Release) ............................................. 10

SEGMENT: BFR - Beginning Segment (Forecast/Material Release - continued) .......................... 12

SEGMENT: PID - Product/Item Description .................................................................................... 13

SEGMENT: N1 – Name ..................................................................................................................... 14

SEGMENT: N2 – Name ..................................................................................................................... 15

SEGMENT: N3 – Name ..................................................................................................................... 16

SEGMENT: N4 – Name ..................................................................................................................... 17

SEGMENT: TD5 - Carrier Header (Routing Sequence/transit Time) ............................................. 18

SEGMENT: TD5 - Carrier Header (continued) ................................................................................ 19

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

SEGMENT: LIN - Item Identification Detail .................................................................................... 21

SEGMENT: UIT - Unit Detail ........................................................................................................... 22

SEGMENT: UIT - Unit Detail (Continued) ...................................................................................... 23

SEGMENT: PER – Administrative Contact ...................................................................................... 24

SEGMENT: MEA – Measurements ................................................................................................... 25

SEGMENT: PID - Product/Item Description .................................................................................... 26

SEGMENT: REF - Reference Number ............................................................................................. 27

SEGMENT: SDP - Ship/Delivery Pattern ......................................................................................... 28

SEGMENT: FST - Forecast Schedule ............................................................................................... 29

SEGMENT: FST - Forecast Schedule (continued) ........................................................................... 30

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

SEGMENT: CTT - Transaction Totals .............................................................................................. 32

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

INTERMET CORPORATION FACILITY DUNS NUMBERS ................................ 34

ATTACHMENTS: .......................................................................................................... 35

ELECTRONIC DATA INTERCHANGE TRADING PARTNER AGREEMENT ............................ 35



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 5 through 8, 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: EXAMPLES: ISA *00* 01*12345678901* 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 34, “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*PS*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 34, “Intermet Corporation Facility DUNS Numbers”



SEGMENT – GS 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: GS*15*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 Des. use Repeat Use ST Transaction Set Header M 1 YES

BFR Beginning Planning Schedule M 1 YES

XPO Pre-assign Purchase Order Number O >1 YES

CUR Currency O 1 NO

REF Reference Identification O 12 NO

PER Administrative Communications O 3 YES

TAX Tax Reference O 3 NO

FOB F.O.B. related instructions O 1 NO

CTP Pricing Information O 25 NO

SAC Allowance or Charge Information O 25 NO

CSH Sales Requirements O 1 NO

ITD Terms of Sales O 2 NO

DTM Date/Time Reference O 10 NO

PID Item Description/Comments O 200 YES

MEA Measurements O 40 NO

PWK Paperwork O 25 NO

PKG Marking, Packaging, Loading O 25 NO

TD1 Carrier Details(Qty. & Weight) O 2 NO

TD5 Carrier Details (Routing) O 12 YES

TD3 Carrier Details (equipment) O 12 NO

TD4 Carrier Detail(special handling) O 5 NO

MAN Marks and Numbers O 10 NO

N1 Name O 1 N1/200 YES

N2 Additional Name Information O 2 YES

N3 Address Information O 2 YES

N4 Geographic Location O 1 YES


PER Administrative communication O 3 NO

FOB F.O.B. Related instruction O 1 NO

LM Code Source Information O 1 >1

LQ Industry Code M 100

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*830*000000001

AIAG/

ELEM ELEM INTERMET INTERMET

ID # NAME FEATURE USE COMMENTS

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

---------- Planning Schedule

with release

capability

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

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

M ID 09/09 number.

(same as SE02)

SEGMENT: BFR - Beginning Segment (Forecast/Material Release)

LEVEL: Heading MAX USAGE/LOOPS: 1/None PURPOSE: To indicate the beginning of a planning schedule transaction set and related forecast dates. GENERAL



INFORMATION: Element BFR04 indicates whether the planning schedule is shipment or delivery based. EXAMPLES: BFR*05**994-5*SH*A*20000414*20000613*20000826

AIAG/



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

Code ---------- 05 = Replace

BFR02 127 Forecast Order Number C AN 01/30 No

----------

BFR03 328 Release Number M AN 01/30 YES Intermet Release

Code ---------- Number

M AN 11/11

BFR04 675 Forecast Type Qualifier M ID 02/02 YES Intermet use

---------- SH = shipment

base

DL = delivery

base

BFR05 676 Forecast Quantity M ID 01/01 Yes Intermet use

Qualifier ---------- 'A' = actual

discrete qty.

BFR06 373 Forecast Horizon Start M DT 08/08 Yes the date when

---------- the forecast

begins ccyymmdd



SEGMENT: BFR - Beginning Segment (Forecast/Material Release - continued)

AIAG/



BFR07 373 Forecast Horizon End M DT 08/08 YES date when the

---------- forecast horizon

ends ccyymmdd

BFR08 373 Forecast Generation M DT 08/08 YES the forecast

Date ---------- issue date

ccyymmdd

BFR09 373 Forecast Update Date C DT 08/08 NO

Code ----------

BFR10 367 Contact Number O ID 01/30 NO

----------

BFR11 324 Purchase Order Number O ID 01/22

Qualifier ---------- NO



SEGMENT: PID - Product/Item Description LEVEL: Header MAX USAGE/LOOPS: 1/PID/200 PURPOSE: To describe a product or item by name or free form general information. GENERAL INFORMATION: Used to distinguish parts by name or free form comments. EXAMPLES: PID*F*DES**SCRAP IRON N/L PID*F*GEN**THIS IS THE HEADER COMMENT AREA N/L

AIAG/



PID01 349 Item Description Type M ID 01/01 YES Intermet use:

---------- F = free form.

PID02 750 Product characteristic O ID 02/03 YES Intermet infor-

---------- mation, use:

GEN=general

information.

DES=part des-

cription.

PID03 348 Item Description O ID 02/02 NO

Qualifier ----------

PID04 751 Contact Number C ID 01/07 NO

----------

PID05 352 Description/Comment M AN 01/80 YES Description/

---------- Comments

PID06 752 Surface/Layer Position O ID 02/02 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*INTERMET NEW RIVER FOUNDRY*01*609120753 N/L N1*SU**92*1234567NA N/L

AIAG/



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

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

supplier

N102 93 Name C AN 01/35 YES If N101 = ‘ST’

----------

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: N2 – Name LEVEL: Header MAX USAGE/LOOPS: 2/N1 PURPOSE: To identify additional names or those longer than 35 characters. GENERAL INFORMATION: The N2 segment may be used to convey full names of ship-to-location. EXAMPLES: N2*SCRAP&IRON-SPECIAL ACCOUNTS N/L

AIAG/



N201 93 Name M ID 01/35 Yes Supplier Name

----------

N202 93 Name O AN 01/35 NO

----------



SEGMENT: N3 – Name LEVEL: Detail MAX USAGE/LOOPS: 2/N1 PURPOSE: To specify the location of the named party GENERAL INFORMATION: The N3 segment may be used to convey full address of ship-to location. EXAMPLES: N3*PO BOX 2716 N/L

AIAG/



N301 166 Address C ID 01/35 YES

----------

N302 166 Address C ON 01/35 NO

----------



SEGMENT: N4 – Name LEVEL: Header MAX USAGE/LOOPS: 1/N1 PURPOSE: To specify the geographic place of the named party GENERAL INFORMATION: The N4 segment is used to convey the city and state information for the ship-To location. EXAMPLES: N4*COLUMBUS*GA*31904 N/L

AIAG/



N401 19 City name C ID 01/19 YES

N402 156 State/Province Code C ID 02/02 YES

N403 116 Postal Code O ID 05/09 YES

N404 26 County Code O ID 02/02 YES Only use if located

outside of the

United States

N405 309 Location Qualifier O ID 01/02 NO

N406 310 Location identification C AN 01/25 NO



SEGMENT: TD5 - Carrier Header (Routing Sequence/transit Time) LEVEL: Header MAX USAGE/LOOPS: 1/TD5/12 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 66 ID Code Qualifier C ID 01/02 YES Intermet use:

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

M ID 01/02 carrier alpha-

betic (SCAC

code).

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

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

M ID 02/04 code.

TD504 91 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 Header (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






TABLE 2: DATA SEGMENT SEQUENCE FOR DETAIL AREA

Seg. Req. Max. Loop Intermet

ID ID Name Des. use Repeat Use LIN Item Identification M 1 YES

UIT Unit Detail O 1 YES

DTM Date/Time Reference O 10 NO

CUR Currency O 1 NO

PO3 Additional Item Detail O 25 NO

CTP Pricing Information O 25 YES

PID Item Description/Comments O 1000 YES

MEA Measurements O 40 NO

PWK Paperwork O 25 NO

PKG Marking, Packaging, Loading O 25 NO

PO4 Item Physical Details O 25 NO

PRS Part Release Status O 1 NO


PER Administration Contact O 3 NO

SAC Service, Allowance or Charger O 25 NO

ITD Terms of Sales O 2 NO

TAX Tax Reference O 3 NO

FOB F.O.B. related instructions O 1 NO

LDT LEAD Time O 12 NO

QTY Quantity O >1 NO

TD1 Carrier Details(Qty. & Weight) O 2 NO

TD5 Carrier Details (Routing) O 12 NO

TD3 Carrier Details (equipment) O 12 NO

TD4 Carrier Detail(special handling) O 5 NO

MAN Marks and Numbers O 10 NO

N1 Name O 1 N1/200 NO

N2 Additional Name Information O 2 NO

N3 Address Information O 2 NO

N4 Geographic Location O 1 NO

REF Reference Identification O 12 YES

PER Administrative communication O 3 YES

FOB F.O.B. Related instruction O 1 NO

SDP Ship/Delivery Pattern O 1 YES

LM Code Source Information O 1 >1 NO

LQ Industry Code M 100 NO

FST Forecast Schedule O 1 >1 YES

QTY Quantity O >1 YES

SDQ Destination Quantity 0 50 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*PO*P5912740

AIAG/



LIN01 350 Assign Identification O AN 01/06 YES Will be used for part

number if part Number

not available

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

‘BP’=Part Number if not

‘VP’=Vendor Part Number

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

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

PO = Intermet Purchase

Order Number

LIN05 234 Product ID M AN 01/30 YES Intermet's

Purchase Order

Number

LIN06 Through LIN31

Note: LIN06 through LIN31 provide 13 additional pairs of

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

ID (234).



SEGMENT: UIT - Unit Detail LEVEL: Detail MAX USAGE/LOOPS: 1/LIN PURPOSE: To specify item unit data. GENERAL INFORMATION: This segment indicates the unit of measure for all quantities relating to the line item. EXAMPLES: UIT*EA N/L (General Use)

AIAG/



UIT0101 355 Unit of Measure Code M ID 02/02 General use:

'EA'=Each

Primary Metals

'01'=Pounds

'24'=Theoratica

UIT0102 1018 Exponent O R 01/15 NO

UIT0103 649 Multiplier O R 01/10 NO

UIT0104 355 Unit or Basis for O R 02/02 NO

Measurement Code




Measurement Code




Measurement Code




Measurement Code



SEGMENT: UIT - Unit Detail (Continued) AIAG/






Measurement Code

UIT02 212 Unit Price O R 01/14 YES Price per unit

of product,

service, etc.

UIT03 639 Basis of Unit Price O ID 02/02 NO

Code



SEGMENT: PER – Administrative Contact LEVEL: DETAIL MAX USAGE/LOOPS: 1/LIN/1000 PURPOSE: To describe a product or item by name or free form general information. GENERAL INFORMATION: Used to distinguish parts by name or free form comments. EXAMPLES: PID*F*DES**SCRAP IRON N/L PID*F*GEN**THIS IS THE HEADER COMMENT AREA N/L

AIAG/


ID # NAME FEATURE USE COMMENTS PID01 349 Item Description Type M ID 01/01 YES Intermet use:

F = free form.

PID02 750 Product characteristic O AN 02/03 YES Intermet infor-

mation, use:

GEN=general

information.

DES=part des-

cription.

PID03 348 Item Description O ID 02/02 NO

Qualifier

PID04 751 Contact Number O ID 01/07 NO

PID05 352 Description/Comment M AN 01/80 YES Description/

Comments

PID06 752 Surface/Layer Position O ID 02/02 NO



SEGMENT: MEA – Measurements LEVEL: DETAIL MAX USAGE/LOOPS: 40/LIN PURPOSE: To specify physical measurements including dimensions, tolerances, weights and counts. GENERAL INFORMATION: Primary Metals Use ONLY. Comments. EXAMPLES: MEA*PD*TH*.13370*IN N/L MEA*LC*WT**LB**06000 N/L

AIAG/



MEA01 737 Measurement Reference M ID 02/02 YES 'PD'=Physical

ID Code ---------- Dimension

'LC'=Limited

weight/Size

Coil.

MEA02 738 Measurement Qualifier M ID 01/03 YES If MEA01='PD'

---------- 'TH'= thickness

'WD'=Width

'LN'=Length

(blank only)

If MEA01='LC'

'ID'=Inside

Diameter of coil

'OD'=Outside

Diameter of coil

'WT'=Maximum

Weight of Coil.

MEA03 739 Measurement Value C R 01/10 YES Not used if

Qualifier ---------- MEA03='WT'

MEA04 355 Unit of Measure Code M ID 02/02 YES 'IN'=Inches

---------- 'LB'=Pounds

MEA05 740 Range Minimum C R 01/10 No

----------

MEA06 741 Range Maximum C ID 01/10 YES If MEA01='LC'

---------- and MEA02='WT'

this is the

maximum coil

weight.



SEGMENT: PID - Product/Item Description LEVEL: DETAIL MAX USAGE/LOOPS: 3/LIN PURPOSE: To identify a person or officer to whom administrative communications should be directed. GENERAL INFORMATION: This segment is used to convey information about the contact person. EXAMPLES: PER*EX*DAN BIRD*TE*7066492121 N/L

AIAG/



PER01 366 Contact Function Code M ID 02/02 YES Intermet use:

---------- 'EX'=Expeditor

PER02 93 Name O AN 01/35 YES Intermet Use:

---------- Name of contact

M AN 01/35 person

PER03 365 Communication Number O ID 02/02 YES Intermet Use:

Qualifier ---------- 'TE'=Telephone

M ID 02/02 number

PER04 365 Communication Number C AN 07/21 YES Intermet Use:

---------- The telephone

M AN 10/10 of the contact

person

PER05 326 Request Reference O AN 01/45 NO

----------



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*DK*MAIN 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



SEGMENT: SDP - Ship/Delivery Pattern LEVEL: Detail MAX USAGE/LOOPS: 1/SDP/260/LIN PURPOSE: To identify specific ship/delivery requirements GENERAL INFORMATION: This segment specifies what day of the week and/or a time frame during the day that a shipment is to be made. EXAMPLES: SDP*Y*Y N/L (no pattern) SDP*1*G N/L (ship once a month = 1st week, any shift) SDP*D*G N/L (ship weekly - Monday, any shift)

AIAG/



SDP01 678 Ship/Delivery Pattern M ID 01/02 YES Intermet corp.

code ---------- ship code is

converted to

to the appropri-

ate ANSI/X12

code for this

element.

If no specific

ship/Deliver

pattern infor-

mation is to be

conveyed code

of 'y'=none

will be used.

See the ANSI/X12

Dictionary.

SDP02 679 ship/delivery Pattern C ID 01/01 YES Intermet Use:

'G'=Any shift.

This code is

used only when

specific ship/

delivery infor-

mation is being

passed.

If SDP01='Y',

SDP02 will also

contain a 'Y'=

None.



SEGMENT: FST - Forecast Schedule

LEVEL: DETAIL MAX USAGE/LOOPS: 260/LIN PURPOSE: To specify the forecasted dates and quantities. GENERAL INFORMATION: This segment is mandatory and, although it allows for time to be specified in addition to date. EXAMPLES: FST*1366*C*W*20000124 N/L FST*12100*C*F*20000201*20000210 N/L FST*12100*C*F*20000201*20000212 N/L

AIAG/



FST01 380 Quantity M R 01/08 YES The actual

---------- discrete

quantity

FST02 680 Forecast Qualifier M ID 01/01 YES Intermet use:

---------- 'A'=Immediate

'C'=Firm

'D'=Planning.

FST03 681 Forecast Timing M ID 01/01 YES Intermet Use:

Qualifier 'W'=Weekly

'D'=Discrete

'F'=Flexible

'M'=Monthly.

FST04 373 Date M DT 08/08 YES General Use

---------- YYMMDD format:

If FST02='A' the date

material is to

be shipped.

If FST03='D'

the date the quantity

is due.

If FST03='M' the first

Monday date of the

month the quantity is

due.

If FST03='W' the Monday

date of the week the

quantity is due.



SEGMENT: FST - Forecast Schedule (continued)

AIAG/



FST05 373 Date O DT 08/08 YES Service & Part Direct

---------- use.

If FST02 = 'A'

can be shipped

in YYMMDD

format.

Primary Metals

use:

If FS03='F',

last day of

the order

period in

YYMMDD format

FST06 374 Date/Time Qualifier O ID 03/03 No

----------

FST07 337 Time O ID 03/03 No

----------

FST08 128 Reference Number C ID 02/02 YES Primary metals

Qualifier ---------- use:

'RE' = Release

Number

FST09 127 Reference Number C ID 11/11 YES Primary metals

---------- use:

Release Number



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 (FST01) for each FST 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 'LIN'

segment.

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

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

of all quanti-

ties released

(FST01).

Primary Metals

Use:

If Purchase by

weight, this

is the actual

weight total

(sum of FST01

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