edi supplier guide -...

EDI Supplier GuideVersion 1.1

January 12, 2000

EDI Supplier Guide

Version 1.0 of 28 January 1, 2000 2

Dura Automotive Systems, Inc.

Table of Contents1 INTRODUCTION................................................................................................................................ 4

1.1 EDI PROGRAM OVERVIEW ................................................................................................................. 41.2 EDI REFERENCE DOCUMENTS............................................................................................................ 41.3 VERSIONS OF THIS DOCUMENT............................................................................................................ 52.1 IMPLEMENTATION STEPS .................................................................................................................... 62.2 EDI PROCESSING OPTIONS................................................................................................................. 62.3 REQUESTING AN EXEMPTION FROM EDI ............................................................................................ 72.3 USE OF D-U-N-S NUMBERS ............................................................................................................. 8

2.3.1 Organizational and Mailbox Identification............................................................................... 82.3.2 How to Verify or Order a DUNS Numbers ............................................................................... 8

2.4 VAN COMMUNICATIONS.................................................................................................................... 82.3.1 Dura’s VAN Requirement ......................................................................................................... 82.3.2 VAN Costs and Dura/Supplier Split .......................................................................................... 82.3.3 Approaches for Selecting a VAN............................................................................................... 92.3.4 Establish VAN Communications ............................................................................................... 9

3 EDI PRACTICES OVERVIEW ....................................................................................................... 12

3.1 EDI TRANSACTION SUMARY............................................................................................................ 123.2 ORGANIZATIONAL IDENTIFIERS (DUNS).......................................................................................... 123.3 PURCHASE ORDER PRACTICES.......................................................................................................... 13

3.3.1 Summary Purchase Order Types ............................................................................................ 133.3.2 Standard Practice in the Use of Different Order Types .......................................................... 133.3.3 Exception Conditions with Concurrent Orders....................................................................... 143.3.4 Supplier Responsibility Relative to Spot Orders ..................................................................... 14

3.4 MATERIAL ACQUISITION PRACTICES................................................................................................ 163.4.1 Cum Management ................................................................................................................... 163.4.2 Open Requirements and Intransit Material ............................................................................ 163.4.3 Engineering Change Incorporation ........................................................................................ 163.4.4 Lot Control.............................................................................................................................. 173.4.5 Consignee Supplier Shipments................................................................................................ 173.4.6 Direct Delivery to Non-Dura Location ................................................................................... 173.4.7 Part Balance Out .................................................................................................................... 173.4.8 Release / Schedule Cancellation ............................................................................................. 183.4.9 Returnable Container Tracking .............................................................................................. 183.4.10 Shipment Authorization ...................................................................................................... 183.4.11 Shipment Based Schedules.................................................................................................. 183.4.12 Shipment Date Determination ............................................................................................ 183.4.13 Shipping Documentation and Identification Numbers........................................................ 19

3.5 MATERIAL RELEASE (830) CHARACTERISTICS ................................................................................. 203.5.1 Material Release Attributes..................................................................................................... 203.5.2 Material Release Processing................................................................................................... 213.5.3 Annual Cum Reset................................................................................................................... 21

3.6 ADVANCED SHIP NOTICE (856) ........................................................................................................ 223.6.1 ASN Attributes......................................................................................................................... 22

4 TRANSACTION GUIDELINES ...................................................................................................... 23

4.1 GENERAL TRANSACTION INFORMATION........................................................................................... 234.1.1 Formal ANSI X12 Guidelines and AIAG Documents.............................................................. 234.1.2 Conformance with AIAG Recommendations........................................................................... 234.1.3 Functional Acknowledgments ................................................................................................. 244.1.4 Transaction Versions .............................................................................................................. 254.1.5 Segment Terminators/Element Separators.............................................................................. 25

EDI Supplier Guide



4.2 DURA TRANSACTION CHANGES: 003020 TO 004010....................................................................... 264.3 DURA TRANSACTION CHANGES: 003060 TO 004010....................................................................... 284.4 DURA VERSION 004010 TRANSACTION GUIDELINES........................................................................ 284.5 TRANSACTION EXAMPLES ................................................................................................................ 28

EDI Supplier Guide



1 INTRODUCTION

1.1 EDI PROGRAM OVERVIEW The EDI program of Dura Automotive Systems applies to all production material suppliersshipping to a Dura North American operation. The program contains common specifications forall Dura Divisions and is composed of two components:

EDI transactions - The communication of ANSI X12 Version 004010 EDI transactions isconducted by subscribing to or interconnecting with the IBM Global Network. The Duraprogram includes the following EDI transactions (with directions from Dura perspective):

• 830 (out) Material Release

• 856 (in) Advanced Ship Notice

• 997 (in/out) Functional Acknowledgements

Web/EDI - A low cost, Web based, alternative to EDI called WEB EC must be used by anysupplier who does not implement formal EDI communications. WEB EC allows suppliers toaccess 830 Material Releases, print shipping labels and enter ASNs. WEB EC is fully compliantwith Dura standards. It is suitable for low volume suppliers or suppliers who need additionaltime to achieve certification with Dura EDI transactions and shipping labels.

1.2 EDI REFERENCE DOCUMENTSDocuments related to EDI can be referenced on the Supplier ExtraNet.

ExtraNet Document Document Content

Transaction Guidelines Go to the <Key Information/Publications> section to accessand print EDI transaction set guidelines

EDI Control Record Settings Go to <Key Information/Reference Material> section andaccess this document to obtain EDI Control Record settingsfor each Dura facility. This document also provides theimplementation status of each Dura facility.

Frequently Asked Questions(FAQs)

Go to the <Key Information/FAQs> section and reference theFAQs on EDI and WEB EC for clarifications on programrequirements and options.

Contact & Facility Directory Reference Corporate section for SPS Commerce contactnumber. Reference Division sections for InformationTechnology and Scheduling contacts.

EDI Software ProvidersSupporting Dura

Go to <Key Information/Reference Material> section andaccess this document for a list of software suppliers whosesoftware is (logged as being) in use by other Dura suppliers.

Supplier should contact his software provider to verify thatthey support the particular operating system and integrate to

EDI Supplier Guide



the particular ERP system used by supplier.

1.3 VERSIONS OF THIS DOCUMENT

Version 1.0: Released January 1, 2000This is the initial release of (corporate wide) Dura EDI specifications based on ANSI x12 version004010. This release supercedes prior ‘division’ specifications issued at ANSI X12 versions003020 and 003060. Three version 004010 transactions are included with Version 1.0:

• 830 Material Release

• 856 Ship Notice/Manifest

• 997 Functional Acknowledgment

Version 1.1: Released January 12, 2000Version 1.1 introduces two significant corrections.

• In Version 1.1 of the 830 transaction, the Release Number is designated to be in BFR02(rather than BRF03).

• In Version 1.1 of the 856 transaction guideline, the looping structure diagram is clarifiedto show that the Item Hierarchical Level is within the Order Hierarchical Level. Thisimplies that Item Level segments for a part will immediately follow the part’s order levelsegments.

The above changes retain guideline consistency with the draft guidelines issued in 1999 to pilotsuppliers. They were posted to the ExtraNet as of January 12, 2000. Other changes in version1.1 are essentially clarifications or cosmetic. They were posted to the ExtraNet on January 18,2000.

• A section highlighting deviations between Dura versions 003060 and 004010 was addedto this document.

• Transaction guidelines for the 830 and 856 have additional explanatory notes. Loop‘repeat’ values and segment ‘max use’ values are changed to reflect Dura’s actual usage.

• Control record guidelines (ISA, IEA, GS and GE) have been removed from thisdocument and are now posted separately on the ExtraNet.

EDI Supplier Guide



• Initiating EDI with Dura

2.1 IMPLEMENTATION STEPSThe following steps summarize the process necessary to begin transmitting EDI documents withDura Automotive System, Inc. More detail is provided in the remainder of this section.

1. Review this EDI Supplier Guide and EDI Transaction Guidelines.

2. Initiate any changes needed to your software systems to accommodate Dura EDI transactions.If you are using packaged software, contact both your EDI Software provider and your(MRP/ERP) manufacturing application provider and initiate the necessary steps. Anyrequired software modifications are the supplier’s responsibility. SPS Commerce personnel(Reference the Contact & Facility Directory).are available to answer questions.

3. Determine how EDI transactions will be processed with Dura. Refer to the next sectionwhich describes EDI processing options. Briefly, the primary options are to conduct formalEDI or a web forms based alternative referred to as WEB EC.

5. Identify (or obtain) DUNS numbers for each location shipping to Dura. You can request aDUNS number by accessing the Dun and Bradsteet site at www.dnb.com. If the address ischanged in the future, refer to the ExtraNet logon page, which links to D&B’s current siteaddress.

6. Establish communications by subscribing to or interconnecting with the IBM Global Network(an EDI Value Added Network/VAN). Reference the Corporate section of the Contact &Facility Directory for IBM contact information.

7. Conduct transaction testing with SPS Commerce. SPS will notify Dura after you havesuccessfully passed certification testing. Suppliers who fail to pass certification testing willbe subscribed to WEB EC.

Suppliers will be contacted by SPS Commerce to initiate the certification process.Alternatively, the supplier can contact SPS. In either case, there is a 30 day testing periodprovided for the supplier to certify EDI transactions. If a supplier fails to certify, he is tosubscribe to WEB EC or, for a nominal fee, he can arrange with SPS Commerce for anadditional certification period of 3 weeks.

Direct questions to SPS Commerce Client Services (refer to EDI Certification in theCorporate Contact & Facility Directory).

8. Conduct parallel operation. After a supplier is certified, individual Dura Divisions willcontact the supplier to commerce EDI (or WEB EC) implementation. Parallel testing with beconducted with each Dura facility that you ship to (‘parallel’ implies the distribution of paperdocuments continues with EDI transmissions). Part of the implementation will be to switchsupplier’s receiving ‘delivery based’ schedules to ‘ship based’ schedules.

9. Commence paperless operation. The issuing of paper documents, e.g. material releases, willbe stopped when successful electronic operation is established. The decision and timing tostop paper is made independently for each supplier shipping location.

2.2 EDI PROCESSING OPTIONSDura has partnered with an outside service provider, SPS Commerce, to facilitate the

EDI Supplier Guide



implementation and to provide alternatives to formal EDI formats and communications. Thefollowing options are available to satisfy Dura’s EDI requirement:

Option A: Implement formal VAN based EDI using translation software.

Suppliers choosing this option must test with and be certified by SPS Commerce. AnyEDI software can be used, including software products available from SPS Commerce.Suppliers must subscribe with or interconnect to the IBM Global Network.

After being contacted by SPS Commerce, suppliers will be given 30 days to completeEDI certification testing. Any supplier who fails to certify by the end of the test periodmust subscribe to WEB EC (see Option B).

Option B: Implement the web-based alternative to EDI.

Suppliers choosing this option will subscribe to SPS Commerce’s WEB EC product toexchange the 830 and 856 documents with Dura using the Internet and web forms. WEBEC supports Dura specific EDI transactions and can also be used to create Dura shippinglabels.

Monthly charges for using WEB EC are volume based and will typically be no more than$50 for a supplier shipping to four or fewer Dura facilities. Subscription options will beexplained when you are contacted by SPS. A supplier using WEB EC can change toformal EDI at a future time by scheduling a new test period with SPS Commerce andpassing transaction certification tests.

Option C: Implement proprietary application interfaces.

This option is a custom priced service provided by SPS Commerce for exchanging EDIinformation. Supplier defined interface files can be used to integrate Material Releasedata into a spreadsheet or application system. Supplier generated files with ASN data aresent to SPS Commerce, formatted into X12 ASNs and forwarded to Dura.

Direct questions to SPS Commerce Client Services (refer to EDI Certification in the CorporateContact & Facility Directory).

2.3 REQUESTING AN EXEMPTION FROM EDIWEB EC (Web/EDI) is an option to formal EDI for a low volume shipper. WEB EC can also beused for an interim period until EDI software has been implemented. All suppliers are expectedto conduct electronic communications with Dura, using either formal EDI or WEB EC.

Exemption from electronic communication will be granted in limited circumstances (for example,if a supplier is being “de-sourced”). To request an exemption to Dura’s electroniccommunications requirement refer to EC Exemption Request form on the ExtraNet.

EDI Supplier Guide



2.3 USE OF D-U-N-S NUMBERS

2.3.1 Organizational and Mailbox IdentificationThe Dun & Bradstreet D-U-N-S number (DUNS number) is used to identify both Dura andsupplier locations in EDI transactions. In GS and N1 segments, the Identification Code Qualifieris set to “01” (DUNS Number) and the Identification Code is the DUNS number.3.1.1.1 DUNS number with a “S” suffix is used to identify Dura mailboxes on the IBM Global Network.Mailboxes are identified in the ISA segment of EDI transactions. Set the Interchange IDQualifier to “14” (DUNS Plus Suffix) and the Receiver ID to the DUNS based mailbox identifier(format “nnnnnnnnnS”).

The EDI Control Record Settings document on the ExtraNet contains the DUNS number andIBM mailbox for each Dura facility. Also provided is the EDI implementation status of thefacility.

2.3.2 How to Verify or Order a DUNS NumbersThe supplier can use the Dun & Bradstreet web site to validate his location DUNS numbers. If aDUNS number is needed, it can be ordered by telephone (1-800-333-0505). The web site canalso be used to order a DUNS number:

• Access the address www.dnb.com.

• Open the D&B D-U-N-S Numbers hyperlink and follow menus. Select <How do I getthe> in the pull down list.

• To verify your DUNS, enter company information in the selection form and a list oflocation addresses and their DUNS number will be provided.

• If your shipping location does not have a DUNS number, you can obtain one by clickingon the <Get Listed> button and submitting the <D&B D-U-N-S® Number Request> form.A response will be sent via email in approximately three weeks.

2.4 VAN COMMUNICATIONS

2.3.1 Dura’s VAN RequirementIn order to conduct EDI with Dura, it is necessary to establish an account with a Value AddedNetwork (VAN). While Dura uses the IBM Global Network, you have the option of using anyVAN of your choice by establishing an interconnect between VANs. Note that most VANs havemonthly interconnect fees.

2.3.2 VAN Costs and Dura/Supplier SplitBased on VAN evaluations conducted by Dura in the spring of 1999, it is estimated thatminimum annual VAN charges will be in the range of $500 to $800. This is due to the minimummonthly charge commonly employed by VANs. As the number of “ship-from/ship-to” trading

EDI Supplier Guide



partner relationships increase, the incremental cost per relationship will quickly drop below $100per year.

Van communication charges are based on a (typical) 50/50 split. When establishingcommunications, VAN accounts should be set up for the sender of a document to pay for chargesto the VAN and from the VAN to the Receiver.

2.3.3 Approaches for Selecting a VANIf you do not have an account with a VAN, one will need to be established to conduct formalEDI. Several approaches are offered.

• If you already have a VAN, establish an interconnect between it and the IBM GlobalNetwork.

• If Dura is the only customer asking you to implement EDI and you want to avoid anevaluation project, use the IBM Global Network. Other major public VANS includeAT&T, GEIS, Harbinger and Sterling, to name a few.

• If you anticipate doing EDI with multiple customers, select that VAN that is mostcommonly used by your major customers. This will minimize the additionalcommunications time and charges for VAN interconnects.

• Conduct a detailed evaluation. The time and cost to conduct an evaluation is warranted ifyou have near term plans to become a ‘hub’ to a significant number of suppliers. Theavailability and cost of implementation services is then a major consideration (as opposedto the network communications, which is basically a commodity item).

2.3.4 Establish VAN CommunicationsAfter selecting the VAN to be used with Dura, communications must be established. Dependingon your VAN selection, one of the steps below is followed.

3.1.1.2 If Using an Existing IBM Network AccountIf you are a current subscriber of the IBM Network, verify that the DUNS number for eachlocation shipping to Dura is in the global alias table.

3.1.1.3 If Interconnecting to the IBM NetworkTo use a VAN other than the IBM Global Network, contact your VAN (or set up an account withthe desired VAN) and ask them to establish an interconnect with the IBM Global Network. Theywill need the ISA Receiver ID and Qualifier of each Dura facility you ship to. Reference the EDIControl Record Settings on Dura’s supplier extranet.

3.1.1.4 If Establishing a new VAN AccountIf your do not use an interconnect, then an account must be established on the IBM GlobalNetwork. While the steps below are for the IBM Global Network, they are representative of the

EDI Supplier Guide



setup processed that would be conducted with any VAN. If any phone numbers above becomeinvalid, reference the Corporate Contact & Facility Directory on the ExtraNet.

Step 1 - Contact the Network

Call IBM at 1-800-655-8865 and ask for the “EDI Marketing. Be prepared to provide thefollowing information:

• Company Name

• Name and telephone number of two contact individuals who will be authorized to makeaccount changes.

• The type of information to be transferred (i.e. EDI transactions).

• The name of your EDI software package.

• Communications protocol to be used, e.g. Async, FTP, TCP/IP, etc.

You will be sent an information package with network service descriptions, pricing schedules anda network agreement contract form (fax is an option to mail).

Step 2 - Complete the Service AgreementThe service agreement must be signed and mailed to IBM. By default, IBM will provide twomailboxes with a new account. Additional mailboxes (User IDs) can be requested at this point orlater (it takes 24 to 48 hours to have new mailboxes established).

Return the services agreement to IBM (fax is an option to mail):

IBM Global ServicesCustomer Enabling Support3405 West Dr. MLK, Jr. Bldv.Parkside Building, mail drop PK101Tampa, Florida 33607

IBM will fax you an Account ID within two or three days after receiving a signed serviceagreement. Allow an additional 5 days if you have an AS400 with async communications.

Step 3 - Establish Communications InterfaceSet up your Account and User ID Profiles: Call IBM at 1-800-655-8865 and ask for “EDIEnablement”. A consultant will review the default account profile settings assigned to youraccount. Verify that payment level settings are for a 50/50 split with with Dura (“As a sender” ofa message, set both Pay for Sending and Pay for Receiving to YES and “as a receiver” set both ofthese fields to NO).

Set up DUNS number aliases. For each of your shipping locations, have IBM create mailboxaliases based on the location’s DUNS number. If a mailbox identifier other than DUNS numberis used, it must be similarly set up in an alias table.

Establish communications: Typically, communications scripts will already be available fromyour EDI Software provider. In any case, EDI Enablement will work with you to establish andtest communications.

EDI Supplier Guide



Step 4 - Establish Administrative FunctionsWork with the EDI Enablement consultant to define your account administrators and passwordaccess (use of extended security options is not typical). Verify that your Web browser can accessIBM’s administrative web site (http://ieas.services.ibm.com). Change your password (to beoperational, IBM requires the initially assigned password to be changed).

Once in production, administrative functions can be conducted by IBM Customer Assistance (1-800-727-2222).

Network DocumentationNetwork documentation will not be sent to you. Documentation manuals can be printed off theInternet: Go to http://edi.services.ibm.com/edi. Click on library. Click on desired manuals toprint a copy.

• If you intend to directly conduct administrative tasks, refer to the Information ExchangeAdministrative Services User Guide.

• If you are programming the network interface, refer to the Information ExchangeInterface Programming Guide.

IBM Global Network - Contact PointsContact points for the IBM Global Network:

• For establishing and setting up an account: 1-800-655-8865

• For assistance after account set up: 1-800-727-2222

EDI Supplier Guide



3 EDI PRACTICES OVERVIEW

3.1 EDI TRANSACTION SUMARYDura EDI transactions are summarized below. Also indicated for each EDI transaction arethe alternative delivery media available for sending or receiving document information (e.g.Web Server access, E-mail or Fax).

EDI Transaction Direction Version WebAccess

E-mail Fax

830 Material Release Outbound 004010 Yes No No

856 Advance Ship Notice Inbound 004010 Yes No No

997 Functional Acknowledgement In/Out 004010 No No No

As noted in Section I, all EDI communications with Dura will be through IBM GlobalNetwork, a Value Added Network.

3.2 ORGANIZATIONAL IDENTIFIERS (DUNS)All supplier and Dura facilities will be identified using their DUNS number. The organizationalidentifiers below are common to all EDI Transaction Sets.

• Material Issuer (MI) The Dura facility (plant) issuing the EDI document.

• Ship-To (ST) The facility to which parts are shipped. Typically the same asthe MI.

• Supplier (SU) The supplier location responsible for part delivery. Typically asupplier manufacturing plant.

• Ship-From (SF) The supplier shipping location. Typically the same as thesupplier manufacturing plant.

No other supplier or Dura locations (such as Bill-to organization) are currently used. Thisinformation is provided on the contract order. Any changes would typically becommunicated off system, e.g. through mail.

EDI Supplier Guide



3.3 PURCHASE ORDER PRACTICES

3.3.1 Summary Purchase Order TypesProduction material acquisition practices are discussed by distinguishing two types ofpurchase orders, spot orders and contract orders. In summary and relative to each Duraship-to facility:

• A Spot Order refers to a one-time purchase agreement to deliver material.

• A Contract Order refers to long term purchase agreement used to establish a“vendor scheduling” acquisition environment. Once a contract order is establishedfor a part, acquisition management will utilize Material Releases, Cumulativequantities, and shipment schedules or pulls signals.

3.3.2 Standard Practice in the Use of Different Order TypesFor each Dura manufacturing facility, Dura practice is to have no more than one order ofany purchase order type (spot or contract) effective at one point in time for a specificproduction material part number. Dura order type relative to a part’s life cycle is describedbelow:

I. A spot order may be used to acquire material prior to prototype or pilot build.

a. Delivery schedule is stated on the spot order.

b. The spot order represents the authorization to ship.

II. A contract order is established to acquire material in support of volumeproduction.

a. Separate Contract Orders will be established between a Dura ship-toplant and a supplier ship from location. A Contract Order may beissued for each part. A Contract Order may be issued with multipleparts. A contract order may be effective for multiple years.

b. A contract order may be established prior to launch of volumeproduction.

c. Once a contract order is established and open, spot orders usage for thepart will be restricted to exception situations described in the subsectionbelow.

d. Dura practice is that multiple contract orders can be concurrently openfor a production material part number. This implies that materialreleases for one part number may include multiple LIN loops (one foreach open contract order).

e. Material Releases are periodically issued to forecast deliveryrequirements.

f. Material Releases will authorize shipment for parts which are notimplemented on the Dura Pull System (with the Ship-to plant involved).

EDI Supplier Guide



Parts under Pull System control will be shipped based on the manuallyissued pull signal documents (not EDI transactions).

g. Price changes are reflected through amendment to the existing contractorder or with a new contract order.

III. A part with both production and service requirements is managed with one

contract order.

IV. Once a part’s demand is restricted to supporting service requirements, it may bemanaged using either a contract order or spot order, but not both concurrently.

a. A contract order is used when Dura desires to manage acquisition usingservice forecasts of demand in the planning system.

b. After the open contract order for a part has been closed, spot orders areissued for subsequent service requirements.

3.3.3 Exception Conditions with Concurrent OrdersOn an exception basis, a given production material part number managed with a contractorder may have spot orders concurrently open. Listed below are circumstances for which aconcurrent spot order may be issued.

• A spot order is used when the ultimate delivery destination is to a location otherthan a Dura manufacturing facility. This could include either Dura or non-Duradelivery locations, such as Dura Engineering or a vehicle dealer.

• A spot order is used to procure 'unplanned' supplemental quantities of a part thatexists on a contract order. For example, a spot order will be issued for when a partis to be used as a temporary substitute for a different part.

• A spot order is used for retro-billing. Retro-billing is conducted with a special

purpose spot order that denotes the items and date ranges approved for retroactivebilling. Retro-billing does not impact planning schedules or deliveryauthorizations.

3.3.4 Supplier Responsibility Relative to Spot OrdersBeyond requiring exception processing by Dura manufacturing facilities, the creation ofspot orders for productive material may also require exception processing by the supplier.

• Spot Order requirements will not appear on Material Releases and do not impactrelease management; i.e. cumulative quantities do not reflect quantities on the spotorder. Spot order delivery requirements must be considered supplemental demandto the Material Release for planning purposes.

• Shipment authorization for the substitute part will not be provided by a MaterialRelease nor will Pull Signals be issued. Spot order quantities must be considered asupplemental delivery requirement.

EDI Supplier Guide



• The Packing Slip must reflect which specific spot orders are included in the shipment. Ifthe spot order is shipped with other production materials, a separate Packing Slip shouldbe used to segregate it from shipment of parts under release control.

• Inclusion of spot ordered items are not required on the ASN. If they are included in theshipment's ASN, the spot order quantity must be placed on a separate item loopreferencing the spot Purchase Order number.

• If a new part number is created, the supplier may need to establish this "new partnumber” in all business systems. For example, a new part number will be issued on aspot order when special processing on an existing part is needed to allow substitution foranother part.

EDI Supplier Guide



3.4 MATERIAL ACQUISITION PRACTICES

3.4.1 Cum ManagementCumulative quantities are used in the 830 and 856 transactions. The bullets belowsummarize cum management as used by Dura.

• Cum management is used for part numbers issued on contract orders.

• Cum quantities are defined for each part number/contract order combination foreach supplier location (SU) to a Dura (MI) location. Cum quantities are noteffected by changes to a part's engineering revision level.

• Cum quantities are reset effective to January 1st of each year for all Dura facilities.Cums are based on material received on or after January 1st.

• Cumulative quantity for raw and fab authorizations are based on the cum received(as identified in the 830 Material Release). Note that raw and fab authorizationsmight not be sent in the Material Release by all plants. If not sent, authorizationpositions can be determined from data in the Material Release and contract termsfor the item.

• Cum received is not reduced for rejected or returned materials.

• Spot Orders issued for a part under release control do not affect the part’s cums.Spot orders may be issued under exceptional circumstances, such as for a partsubstitution.

The supplier is to immediately resolve/contact his Dura material analyst to reconcile anydiscrepancy conditions:

• The Dura cum received is greater than the supplier cum shipped.

• The Dura cum received equals the supplier cum shipped but intransit materialexists (cums are equal, but not relative to the last received shipment).

• The Dura cum received is less than the supplier cum shipped and intransit materialis less than the difference.

3.4.2 Open Requirements and Intransit MaterialOpen requirements in the 830 Material Release are based on cum received and will thereforeinclude requirements for any intransit material. Intransit material is determined by comparing thesupplier cum shipped to Dura's cum received and determining whether any shipments have beenmade since the last shipment referenced in the 830 SHP segment. Note that there are no suppliercalculations relative to PQ (prior cum) authorization quantities.

3.4.3 Engineering Change IncorporationEngineering Revision Level changes are managed manually by Dura MaterialsManagement.

EDI Supplier Guide



• Supplier is notified of engineering revisions level changes and their effectivity byamendment to an existing contract order or by issuing a new contract order.

• If the existing contract order is amended, the schedule on the Material Releaserepresents the combined requirements for all engineering revisions. The MaterialRelease will provide the current effective Engineering Revision until the effectivedate of the engineering change is reached (at which point, that new revision will bereferenced on the Release).

• If a new contract order is issued, the Material Release will include separate LINloops for each engineering revision of the part (since a separate LIN loop will bepresent for each part/contract order combination).

• ASNs are to reference the engineering revision of each part shipped. The cumshipped for a part will vary based whether or not a new contract was created:

• If engineering revisions are issued on the existing contract, the cum shippedmust reflect all shipments of the part, regardless of engineering revision.

• If Engineering revisions are issued on a new contract, the cum shipped mustreflect shipments for each part / engineering revision combination.

3.4.4 Lot ControlLot Tracking is not required in any Dura EDI transaction, e.g. 856 Ship Notice/Manifest.

3.4.5 Consignee Supplier ShipmentsNote that in Release 2 of this EDI Supplier Guide, EDI transaction processing does notdistinguish drop shipments (parts shipped to consignee who subsequently ships to Dura) fromparts shipped directly to a Dura location. The consignee supplier is not identified and no uniqueEDI processing is conducted relative to consignee shipments.

Consignee conditions are identified on the purchase agreement and must be handled "outside" ofthe system.

3.4.6 Direct Delivery to Non-Dura LocationParts that are repetitively shipped to a non-Dura location will be placed on a contract order and,from an EDI perspective, handling will be identical to consignee shipments. Periodic orexception shipments will be place on a spot purchase order.

3.4.7 Part Balance OutBalance out management is not typically required. Should a balance out conditions arise, itwill be managed directly (i.e. manually) by Dura Materials Management. A "Balance Out"status is not issued in a PRS segment of the Material Release.

EDI Supplier Guide



3.4.8 Release / Schedule CancellationPart cancellation processing:

• A contract order amendment will be issued notifying supplier of part cancellation.

• One 830 Material Release will be issued with a "zero" schedule (FST segments with zeroquantities). No additional Material Releases will be issued for the cancelled part. A"Cancelled" status is not issued in the PRS segment of the Material Release.

• If the part is under Pull System control, no further pull signals will be issued. Those pullsignals previously received are to be shipped unless Dura has issued instructions to thecontrary.

3.4.9 Returnable Container TrackingReturnable Containers used with a shipment are to be included on 856 Ship Notice in the LINsegment using the "RC" qualifier. The LIN segment for each production part number ("BP"qualifier) is to identify the returnable container in which it is shipped. There is no 'electronic'notification when returnable containers are shipped back to the supplier. Returnable containersare not included on Material Releases.

3.4.10 Shipment AuthorizationThe 830 authorizes shipment for parts not under pull system control. Parts under pull systemcontrol have shipment authorized with manually generated pull signals. A single supplierlocation could have shipment authorized by both 830s and pull signals depending on theparticular parts shipped.

3.4.11 Shipment Based SchedulesCurrently, schedules in manually issued Material Releases may be shipment based or deliverybased. This varies by individual Dura manufacturing facility. When EDI base Material Releasesare issued, schedules will be 'shipment based'.

3.4.12 Shipment Date DeterminationDifferent levels of sophistication exist in the different manufacturing planning systems used inDura. As such, an established shipment routing takes precedent over shipment dates in theMaterial Release.

3.4.12.1 Material Release Authorizes ShipmentOpen deliveries with a Material Release ship date that does not coincide with establishedtransportation routings should be shipped on the prior scheduled shipment. For example, ifshipments are made each Monday and Thursday, an open delivery with a Wednesday ship date inthe Material Release should be shipped on the prior Monday.

Open requirements for shipments authorized by the Material Release must reflect intransitmaterial:

EDI Supplier Guide



• If there is no intransit material, the first FST quantity is the open deliveryrequirement.

• If there is intransit material, FST requirements in the Material Release should bereduced.

3.4.12.2 Pull Signal Authorizes ShipmentPull Signals do not typically indicate a ship date. While Pull Signals may arrive daily, actualshipment is based on established practice with the Dura receiving facility. For example, withsome Dura facilities shipment is to be immediate (or next day). With other facilities delivery iswith the next scheduled shipment (e.g. if shipments are made each Thursday, all pull signalsreceived on the days leading up to Thursday are accumulated until that shipment).

Note that shipments authorized by Pull Signals do not reference the Material Release, nor arethere any intransit considerations.

3.4.13 Shipping Documentation and Identification NumbersAll documents associated with a shipment are to include a Shipment Identification Number (SID).The SID is assigned in data element BSN02 of the ASN). The SID is a unique number whichmust not be repeated (with an original shipment) for at least two years. The SID, Bill of Lading,Invoice and (if possible) Packing Slip numbers should all be the same.

The SID number and/or supplier location DUNS number must be clearly identified on allshipping documents calling for them.

• Advanced Ship Notice

• Bill of Lading

• Packing Slip

• Barcode Shipping Labels

• Pull Card Labels

EDI Supplier Guide



3.5 MATERIAL RELEASE (830) CHARACTERISTICS

3.5.1 Material Release AttributesAttribute DescriptionRelease Function Release function will vary by part:

• For suppliers receiving shipment authorization via PullSignals, Material Releases are issued as forecasts only.All schedule quantities are classified as 'planned'.

• For suppliers who do not receive shipment authorizationvia Pull Signals, Material Releases are issued as bothforecasts and authorization to ship. Scheduled quantitieswill include both "firm" and 'planned' requirements.

Material ReleaseDefinition

A unique Material Release is defined by a "MaterialIssuer/Supplier/Part Number/Contract Order" combination. Allschedules and cumulative quantities are defined for thiscombination.

Transaction Scope Material Releases are issued periodically for each production partwith demand within the Release horizon. All Releases from aDura Material Issuer (MI) location to a supplier (SU) locationwill be included in one 830 transaction, i.e. one header withmultiple LIN loops.

TransactionIdentification

Release identification (release number) formats vary by Duradivision. Release identifiers end with an increasing, but notnecessarily sequential, number.

ReplacementReleases

Releases totally replace the prior Material Release. In otherwords, the supplier should discard the entire schedule from aprior release and use the new release.

Schedule Basis Material Releases issued via EDI are "shipment based. Referencethe 'Shipment Date' topic in prior section.

Authorizations Raw and fab authorization commitments are defined in thecontract order. Based on capabilities of applications in each Durafacility, authorization quantities may or may not be sent inMaterial Releases.

If authorizations are not sent in the Material Release, they can bedetermined using authorization horizons defined in a part'scontract order. The authorization quantity is the YTD cumreceived quantity in the Material Release plus scheduledquantities in FST segments over the authorization horizon.

Schedule Segment Part schedules (FST segments) in the Material Release have the

EDI Supplier Guide



Attribute Descriptionfollowing characteristics

• Schedule quantities are discrete values (rather thancumulative).

• When the Material Release is used for both planning andshipment authorization, discrete days will be included inthe near term schedule. In particular, Ship/DeliveryPatterns are not used to identify shipment dates.

• Forecast buckets are restricted to weekly periods. Thestart date for weekly periods will always be a 'Monday'.

• Intransit material is reflected as open requirements inMaterial Release schedules based on the last shipmentreceived at the Dura plant.

• The supplier must reduce open requirements in theMaterial Release to reflect any intransit shipmentsrelative to the last shipment received (as designated in theMaterial Release).

• The Supplier does not calculate ahead/behind conditions(using Prior Cum authorization quantity).

3.5.2 Material Release ProcessingCharacteristic DescriptionRelease Issuer Releases are issued independently by individual Dura plants to

individual supplier locations.

Issue Frequency A weekly frequency is targeted. Actual frequency and date ofissuing will vary by Dura plant. All active production parts willhave releases issued.

Exception Releases Releases for a subset of production parts may be issued at anytime to meet (exceptional) near term schedule changes.Typically, these exception releases would only be necessary forparts for which the Material Release provides ship authorization.

Such exception releases will be issued with the "05" PurposeCode (Replacement) and not highlighted with the moreappropriate "04" Purpose Code (Change).

3.5.3 Annual Cum ResetAll Dura facilities will reset cums effective January 1 of each year. YTD cum received quantityis based on shipments received in the new year. In other words, a December 30th shipmentreceived on January 2nd will be included in the new years cum received quantity.

EDI Supplier Guide



3.6 ADVANCED SHIP NOTICE (856)

3.6.1 ASN AttributesAttribute DescriptionASN Function An ASN provides data on a shipment from a Supplier location to

a Dura location.

Transaction Scope An ASN is required for production parts on contract orders.Returnable containers used in the shipment are to be included inthe ASN.

If the shipment of production parts includes items from spotorders, they can be (optionally) included on the ASN.

TransactionIdentification

Each ASN is identified with a Ship Identification number (SID).The SID should be the same number as the Bill of Lading,Invoice and Packing Slip numbers.

LIN Loops A separate LIN loop is required for each part/purchase order(contract or spot) combination. Cum quantity shipped is based oneach part/contract order combination.

Container Data For each part shipped, the ASN is to include

• Number of containers and pieces per container

• Bar-code label serial numbers for each container

EDI Supplier Guide



4 TRANSACTION GUIDELINES

4.1 GENERAL TRANSACTION INFORMATION

4.1.1 Formal ANSI X12 Guidelines and AIAG DocumentsEDI Guidelines for Dura transactions are provided in to following sections. Dura guidelinesdocument the segments used by Dura and are not intend to replace formal X12 transaction setdocumentation. These guidelines are intended to clarify Dura specific use of transactions.

The formal ANSI X12 guidelines are available from the Data Interchange Standards Association(DISA). Rather than ordering formal guideline documentation, it is suggested that the supplierorder the following documents from the Automotive Industry Action Group (Southfield,Michigan):

• AIAG Implementation Guidelines-Version 004010 AIAG

• AIAG M-3, Recommended Business Practices for EDI Implementation for Requirements(Push) Based EDI.

• AIAG M-5, Recommended Business Practices for EDI Implementation for Requirements(Pull) Based EDI.

4.1.2 Conformance with AIAG RecommendationsThe AIAG “recommended practice” refers to the M-3 and M-5 publications. Thepublication AIAG Implementation Guideline for Electronic Data Interchange versions004010AIAG provides for a more extensive EDI implementation and is interpreted as"allowed practice” for addressing business conditions not supported in the M-3 and M-5publications.

Dura conformance with AIAG recommendations and allowed practice is discussed insections below.

4.1.2.1 AIAG Conformance – Control RecordsOther than noted below, Dura's ISA and GS control records are consistent withrecommended practice.

• Dura sender and receiver identifier in the ISA Segment will be a suffixed DUNS number(format nnnnnnnnnS) with a qualifier of “14” (DUNS plus suffix).

4.1.2.2 AIAG Conformance – 830 Material ReleaseOther than noted below, Dura's Material Release is consistent with recommended practices forthe subset of segments used.

• Release Status segment (PRS) is not sent to flag conditions such as Release cancellationsor part balance out. Refer to document subsections on Balance-Out and Cancellations inthe Materials EDI Overview section.

EDI Supplier Guide



• The 04"change" purpose code is not sent to highlight a partial release (i.e. when atransaction only includes a subset of items under release control). All MaterialReleases are issued with a 05 "replacement" purpose code. Only the schedules forthose items present in the transaction are to be replaced; and the schedules for anyother items are not affected.

• Raw and Fab authorizations (ATH segment) are optional. Some Dura plants will includeauthorizations in the Material Release and other plants will not. When authorizations arenot provided, the supplier can determine authorized quantities from informationcontained in the Material Release and the authorization horizons designated in the item'sPurchase Order.

• Prior Cum quantity (ATH segment) is not sent. The schedule contains all Durarequirements based on the last received shipment referenced in the release. Thesupplier’s open shipping requirement must reflect any ‘intransit’ shipments notreceived by Dura at the time of release generation.

• Item description may be provided in an optional PID segment. Some Dura plantswill include item descriptions for supplier reference on printed reports of EDItransactions.

4.1.2.3 AIAG Conformance – 856 Advanced Ship NoticeOther than noted below, Dura's Advanced Ship Notice is consistent with recommended practicesfor the subset of segments used.

• The Carrier PRO/Invoice number is to be returned in the ASN. PRO number is neither anAIAG Recommended or Allowed field.

4.1.2.4 AIAG Conformance - Record DefinitionWhile within AIAG recommended practice, it is important to realize a unique release is definedfor each Item - Purchase Order combination. This means that multiple LIN loops will be issuedfor the same part if there is more than one open Purchase Order. The schedule in each LIN loopmust only replace the prior schedule for the designated PO. The total schedule requirement for anitem is the sum of the “by PO” schedules present in each LIN loop.

4.1.3 Functional AcknowledgmentsIn addition to Interchange acknowledgements, Functional Acknowledgments (X.12 997) arerequired for transaction sets as shown in the following table.

EDI Transaction Acknowledgment Sender

830 Outbound YES Supplier

856 Inbound YES Dura

862 Outbound YES Supplier

EDI Supplier Guide



4.1.4 Transaction VersionsAs of release 2 of Dura's EDI Supplier Guide, all current transaction versions are 004010.Release 1 transaction versions for the 830 and 856 were at 003020.

EDI Transaction X.12 Version

830 Outbound 004010

856 Inbound 004010

997 (Inbound and Outbound) 004010

4.1.5 Segment Terminators/Element SeparatorsExamples in this document display the Element Separator with an asterisk “*” and the SegmentTerminator as N/L. The transaction defines actual values of the Segment Terminator and ElementSeparator sender in the data interchange envelope (ISA). The preferred values are:

PrintableCharacter EBCDIC HEX ASCII HEX

Segment Terminator: 1C 1CElement Separator: ~ A1 7ESub-element Separator: > 3E

Note that the data Element Separator is define by the value of the fourth character position in theISA and the Segment Terminator is defined by the value of the last character position (one byteafter the data element ISA16).

EDI Supplier Guide



4.2 DURA TRANSACTION CHANGES: 003020 TO 004010The tables below summarize version 004010 EDI transaction deviations for the 830 and 856transactions defined at X12 version 003020. Version 003020 transactions have only beenimplemented by plants of the former Excel Industries.

ISA and GS Control Record Changes

Deviation Area Description

DUNS numbers introduced Telephone numbers were used as control record identifiers inversion 003020.

With version 004010, either telephone and DUNS numbers willbe used for Sender and Receiver Identifiers. Particular usage willvary by Dura organization

ISA and GS identifiers. ISA and GS identifiers in version 003020 were the same andalways referenced a specific plant.

With version 004010, The ISA may contain a Division identifierand the GS a plant identifier. Particular usage will vary by Duraorganization. Identifier usage will not be retroactively changed.

830 Material Release Changes

Deviation Area Description (deviation from 003020)

Transaction Purpose Code Transaction purpose code (BFR01) is '05' rather than '00' (i.e.replace rather than original).

Release Number Release number format will vary by Division. There should be nosupplier processing that requires parsing of release numbers.

Release Definition In version 004010, a unique release is defined for eachitem/purchase order combination. This implies that multipleconcurrent releases may be issued for the same item?

Horizon Start In version 004010, the Horizon Start Date (BRF06) is no longerdefined as the Purchase Order creation date. Depending on theissuing plant, the Horizon start date will be the Monday of theschedule generation week or the schedule generation date.

Schedule Definition Schedules (FST dates) are Ship Based rather than Delivery Based(BRF04).

FST schedules will use discrete days and/or weekly periods.Weekly periods start on Mondays. SDP codes will not be used.

EDI Supplier Guide




Purchase OrderIdentification

In version 004010, all Purchase Order numbers are identified inthe LIN segment (even if one PO applies to all LIN loops). ThePRF segment in the LIN loop is not used. BRF11 is not used.

Organization Identifiers The Dura facility issuing the Material Release is identified in N1Loop with the MI rather than BY identification code.

Cum Management Cumulative Received quantity is sent in the SHP loop.

Segment Usage Version 004010 looping structure/segments are changed toconform with AIAG recommendations. FST segments will beunder the LIN loop rather than the SDP loop.

856 ASN Changes


Purpose Code The '05' Replacement Purpose Code (BSN01) is not used.

Changing an issued ASN is accomplished by canceling the initialASN and sending a new original ASN with the corrections.

Returnable Containers Returnable Container items are required to be designated in anLIN loop.

The LIN segment for production parts are to indicate theReturnable Container in which they are shipped.

Cum Management Cumulative quantity shipped is returned (SN104).

Pull Signals The REF segment under CLD loop has the Customer Referencenumbers (CR) added for designation of pull signal numbers. PullSignal numbers are only returned when shipping parts under Durapull system control.

Excess Transportation ETD segment added.

Segment Usage Looping structure/segments changed to conform with AIAGrecommendations.

• The "Order" hierarchical level is added. The LIN and SN1segments are moved out of the "Item" level to the "Order"level.

• The PRF segment is not used to indicate Purchase Ordernumber. Purchase Order number is designated in the LINsegment

EDI Supplier Guide



4.3 DURA TRANSACTION CHANGES: 003060 TO 004010The tables below summarize version 004010 EDI transaction deviations for 830 transactionsdefined at X12 version 003060. Version 003060 transactions have only been implemented inDura’s Stratford, Ontario and Milan, Tennessee facilities.

830 Deviation Area Description (deviation from 003060)

Release Number In version 004010 the release number is in BFR02 rather thanBFR03.

Release Definition In version 004010, a unique release is defined for eachitem/purchase order combination. This implies that multipleconcurrent releases may be issued for the same item?

NTE Segment The NTE segment is not used.

N1 Loop DUNS numbers are used exclusively. Use proprietaryidentification codes is discontinued.

The N3 and N4 segments are not sent.

PID Segment PID segment is sent to provide a free form part description.

PER Segment PER segments are not sent.

ATH Segment PQ cumulative quantity is not sent. MT and FI authorizationswill still be sent.

Schedule Representation Version 004010 looping structure/segments are changed toconform with AIAG recommendations. FST segments will beunder the LIN loop rather than the SDP loop.

FST segments may be sent with discrete days (as well as weeks).

4.4 DURA VERSION 004010 TRANSACTION GUIDELINESAccess and print EDI Transaction Guidelines from section <Key Information/Publications>.

4.5 TRANSACTION EXAMPLESReference ExtraNet under <Key Information/Publications>.