EDI Supplier Guide. Version 1.1 January 12, 2000

Transcription

1 Version 1.1 January 12, 2000

2 Table of Contents 1 INTRODUCTION EDI PROGRAM OVERVIEW EDI REFERENCE DOCUMENTS VERSIONS OF THIS DOCUMENT IMPLEMENTATION STEPS EDI PROCESSING OPTIONS REQUESTING AN EXEMPTION FROM EDI USE OF D-U-N-S NUMBERS Organizational and Mailbox Identification How to Verify or Order a DUNS Numbers VAN COMMUNICATIONS Dura s VAN Requirement VAN Costs and Dura/Supplier Split Approaches for Selecting a VAN Establish VAN Communications EDI PRACTICES OVERVIEW EDI TRANSACTION SUMARY ORGANIZATIONAL IDENTIFIERS (DUNS) PURCHASE ORDER PRACTICES Summary Purchase Order Types Standard Practice in the Use of Different Order Types Exception Conditions with Concurrent Orders Supplier Responsibility Relative to Spot Orders MATERIAL ACQUISITION PRACTICES Cum Management Open Requirements and Intransit Material Engineering Change Incorporation Lot Control Consignee Supplier Shipments Direct Delivery to Non-Dura Location Part Balance Out Release / Schedule Cancellation Returnable Container Tracking Shipment Authorization Shipment Based Schedules Shipment Date Determination Shipping Documentation and Identification Numbers MATERIAL RELEASE (830) CHARACTERISTICS Material Release Attributes Material Release Processing Annual Cum Reset ADVANCED SHIP NOTICE (856) ASN Attributes TRANSACTION GUIDELINES GENERAL TRANSACTION INFORMATION Formal ANSI X12 Guidelines and AIAG Documents Conformance with AIAG Recommendations Functional Acknowledgments Transaction Versions Segment Terminators/Element Separators Version 1.0 Page 2 of 28 January 1,

3 4.2 DURA TRANSACTION CHANGES: TO DURA TRANSACTION CHANGES: TO DURA VERSION TRANSACTION GUIDELINES TRANSACTION EXAMPLES Version 1.0 Page 3 of 28 January 1,

4 1 INTRODUCTION 1.1 EDI PROGRAM OVERVIEW The EDI program of Dura Automotive Systems applies to all production material suppliers shipping to a Dura North American operation. The program contains common specifications for all Dura Divisions and is composed of two components: EDI transactions - The communication of ANSI X12 Version EDI transactions is conducted by subscribing to or interconnecting with the IBM Global Network. The Dura program 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 any supplier who does not implement formal EDI communications. WEB EC allows suppliers to access 830 Material Releases, print shipping labels and enter ASNs. WEB EC is fully compliant with Dura standards. It is suitable for low volume suppliers or suppliers who need additional time to achieve certification with Dura EDI transactions and shipping labels. 1.2 EDI REFERENCE DOCUMENTS Documents related to EDI can be referenced on the Supplier ExtraNet. ExtraNet Document Document Content Transaction Guidelines Go to the <Key Information/Publications> section to access and print EDI transaction set guidelines EDI Control Record Settings Go to <Key Information/Reference Material> section and access this document to obtain EDI Control Record settings for each Dura facility. This document also provides the implementation status of each Dura facility. Frequently Asked Questions (FAQs) Contact & Facility Directory EDI Software Providers Supporting Dura Go to the <Key Information/FAQs> section and reference the FAQs on EDI and WEB EC for clarifications on program requirements and options. Reference Corporate section for SPS Commerce contact number. Reference Division sections for Information Technology and Scheduling contacts. Go to <Key Information/Reference Material> section and access this document for a list of software suppliers whose software is (logged as being) in use by other Dura suppliers. Supplier should contact his software provider to verify that they support the particular operating system and integrate to Version 1.0 Page 4 of 28 January 1,

5 the particular ERP system used by supplier. 1.3 VERSIONS OF THIS DOCUMENT Version 1.0: Released January 1, 2000 This is the initial release of (corporate wide) Dura EDI specifications based on ANSI x12 version This release supercedes prior division specifications issued at ANSI X12 versions and Three version transactions are included with Version 1.0: 830 Material Release 856 Ship Notice/Manifest 997 Functional Acknowledgment Version 1.1: Released January 12, 2000 Version 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 clarified to show that the Item Hierarchical Level is within the Order Hierarchical Level. This implies that Item Level segments for a part will immediately follow the part s order level segments. The above changes retain guideline consistency with the draft guidelines issued in 1999 to pilot suppliers. They were posted to the ExtraNet as of January 12, Other changes in version 1.1 are essentially clarifications or cosmetic. They were posted to the ExtraNet on January 18, A section highlighting deviations between Dura versions and was added to 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 this document and are now posted separately on the ExtraNet. Version 1.0 Page 5 of 28 January 1,

6 Initiating EDI with Dura 2.1 IMPLEMENTATION STEPS The following steps summarize the process necessary to begin transmitting EDI documents with Dura Automotive System, Inc. More detail is provided in the remainder of this section. 1. Review this 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. Any required 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 section which describes EDI processing options. Briefly, the primary options are to conduct formal EDI 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 a DUNS number by accessing the Dun and Bradsteet site at If the address is changed in the future, refer to the ExtraNet logon page, which links to D&B s current site address. 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 have successfully passed certification testing. Suppliers who fail to pass certification testing will be 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 period provided for the supplier to certify EDI transactions. If a supplier fails to certify, he is to subscribe to WEB EC or, for a nominal fee, he can arrange with SPS Commerce for an additional certification period of 3 weeks. Direct questions to SPS Commerce Client Services (refer to EDI Certification in the Corporate Contact & Facility Directory). 8. Conduct parallel operation. After a supplier is certified, individual Dura Divisions will contact the supplier to commerce EDI (or WEB EC) implementation. Parallel testing with be conducted with each Dura facility that you ship to ( parallel implies the distribution of paper documents continues with EDI transmissions). Part of the implementation will be to switch supplier s receiving delivery based schedules to ship based schedules. 9. Commence paperless operation. The issuing of paper documents, e.g. material releases, will be stopped when successful electronic operation is established. The decision and timing to stop paper is made independently for each supplier shipping location. 2.2 EDI PROCESSING OPTIONS Dura has partnered with an outside service provider, SPS Commerce, to facilitate the Version 1.0 Page 6 of 28 January 1,

7 implementation and to provide alternatives to formal EDI formats and communications. The following 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. Any EDI 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 complete EDI certification testing. Any supplier who fails to certify by the end of the test period must 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 to exchange the 830 and 856 documents with Dura using the Internet and web forms. WEB EC supports Dura specific EDI transactions and can also be used to create Dura shipping labels. 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 be explained when you are contacted by SPS. A supplier using WEB EC can change to formal EDI at a future time by scheduling a new test period with SPS Commerce and passing transaction certification tests. Option C: Implement proprietary application interfaces. This option is a custom priced service provided by SPS Commerce for exchanging EDI information. Supplier defined interface files can be used to integrate Material Release data into a spreadsheet or application system. Supplier generated files with ASN data are sent to SPS Commerce, formatted into X12 ASNs and forwarded to Dura. Direct questions to SPS Commerce Client Services (refer to EDI Certification in the Corporate Contact & Facility Directory). 2.3 REQUESTING AN EXEMPTION FROM EDI WEB EC (Web/EDI) is an option to formal EDI for a low volume shipper. WEB EC can also be used for an interim period until EDI software has been implemented. All suppliers are expected to 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 electronic communications requirement refer to EC Exemption Request form on the ExtraNet. Version 1.0 Page 7 of 28 January 1,

8 2.3 USE OF D-U-N-S NUMBERS Organizational and Mailbox Identification The Dun & Bradstreet D-U-N-S number (DUNS number) is used to identify both Dura and supplier locations in EDI transactions. In GS and N1 segments, the Identification Code Qualifier is set to 01 (DUNS Number) and the Identification Code is the DUNS number 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 ID Qualifier 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 and IBM mailbox for each Dura facility. Also provided is the EDI implementation status of the facility How to Verify or Order a DUNS Numbers The supplier can use the Dun & Bradstreet web site to validate his location DUNS numbers. If a DUNS number is needed, it can be ordered by telephone ( ). The web site can also be used to order a DUNS number: Access the address Open the D&B D-U-N-S Numbers hyperlink and follow menus. Select <How do I get the> in the pull down list. To verify your DUNS, enter company information in the selection form and a list of location addresses and their DUNS number will be provided. If your shipping location does not have a DUNS number, you can obtain one by clicking on the <Get Listed> button and submitting the <D&B D-U-N-S Number Request> form. A response will be sent via in approximately three weeks. 2.4 VAN COMMUNICATIONS Dura s VAN Requirement In order to conduct EDI with Dura, it is necessary to establish an account with a Value Added Network (VAN). While Dura uses the IBM Global Network, you have the option of using any VAN of your choice by establishing an interconnect between VANs. Note that most VANs have monthly interconnect fees VAN Costs and Dura/Supplier Split Based on VAN evaluations conducted by Dura in the spring of 1999, it is estimated that minimum annual VAN charges will be in the range of $500 to $800. This is due to the minimum monthly charge commonly employed by VANs. As the number of ship-from/ship-to trading Version 1.0 Page 8 of 28 January 1,

9 partner relationships increase, the incremental cost per relationship will quickly drop below $100 per year. Van communication charges are based on a (typical) 50/50 split. When establishing communications, VAN accounts should be set up for the sender of a document to pay for charges to the VAN and from the VAN to the Receiver Approaches for Selecting a VAN If you do not have an account with a VAN, one will need to be established to conduct formal EDI. Several approaches are offered. If you already have a VAN, establish an interconnect between it and the IBM Global Network. If Dura is the only customer asking you to implement EDI and you want to avoid an evaluation project, use the IBM Global Network. Other major public VANS include AT&T, GEIS, Harbinger and Sterling, to name a few. If you anticipate doing EDI with multiple customers, select that VAN that is most commonly used by your major customers. This will minimize the additional communications time and charges for VAN interconnects. Conduct a detailed evaluation. The time and cost to conduct an evaluation is warranted if you have near term plans to become a hub to a significant number of suppliers. The availability and cost of implementation services is then a major consideration (as opposed to the network communications, which is basically a commodity item) Establish VAN Communications After selecting the VAN to be used with Dura, communications must be established. Depending on your VAN selection, one of the steps below is followed If Using an Existing IBM Network Account If you are a current subscriber of the IBM Network, verify that the DUNS number for each location shipping to Dura is in the global alias table If Interconnecting to the IBM Network To use a VAN other than the IBM Global Network, contact your VAN (or set up an account with the desired VAN) and ask them to establish an interconnect with the IBM Global Network. They will need the ISA Receiver ID and Qualifier of each Dura facility you ship to. Reference the EDI Control Record Settings on Dura s supplier extranet If Establishing a new VAN Account If your do not use an interconnect, then an account must be established on the IBM Global Network. While the steps below are for the IBM Global Network, they are representative of the Version 1.0 Page 9 of 28 January 1,

10 setup processed that would be conducted with any VAN. If any phone numbers above become invalid, reference the Corporate Contact & Facility Directory on the ExtraNet. Step 1 - Contact the Network Call IBM at and ask for the EDI Marketing. Be prepared to provide the following information: Company Name Name and telephone number of two contact individuals who will be authorized to make account 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 and a network agreement contract form (fax is an option to mail). Step 2 - Complete the Service Agreement The service agreement must be signed and mailed to IBM. By default, IBM will provide two mailboxes with a new account. Additional mailboxes (User IDs) can be requested at this point or later (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 Services Customer Enabling Support 3405 West Dr. MLK, Jr. Bldv. Parkside Building, mail drop PK101 Tampa, Florida IBM will fax you an Account ID within two or three days after receiving a signed service agreement. Allow an additional 5 days if you have an AS400 with async communications. Step 3 - Establish Communications Interface Set up your Account and User ID Profiles: Call IBM at and ask for EDI Enablement. A consultant will review the default account profile settings assigned to your account. Verify that payment level settings are for a 50/50 split with with Dura ( As a sender of a message, set both Pay for Sending and Pay for Receiving to YES and as a receiver set both of these fields to NO). Set up DUNS number aliases. For each of your shipping locations, have IBM create mailbox aliases based on the location s DUNS number. If a mailbox identifier other than DUNS number is used, it must be similarly set up in an alias table. Establish communications: Typically, communications scripts will already be available from your EDI Software provider. In any case, EDI Enablement will work with you to establish and test communications. Version 1.0 Page 10 of 28 January 1,

11 Step 4 - Establish Administrative Functions Work with the EDI Enablement consultant to define your account administrators and password access (use of extended security options is not typical). Verify that your Web browser can access IBM s administrative web site ( Change your password (to be operational, IBM requires the initially assigned password to be changed). Once in production, administrative functions can be conducted by IBM Customer Assistance ( ). Network Documentation Network documentation will not be sent to you. Documentation manuals can be printed off the Internet: Go to Click on library. Click on desired manuals to print a copy. If you intend to directly conduct administrative tasks, refer to the Information Exchange Administrative Services User Guide. If you are programming the network interface, refer to the Information Exchange Interface Programming Guide. IBM Global Network - Contact Points Contact points for the IBM Global Network: For establishing and setting up an account: For assistance after account set up: Version 1.0 Page 11 of 28 January 1,

12 3 EDI PRACTICES OVERVIEW 3.1 EDI TRANSACTION SUMARY Dura EDI transactions are summarized below. Also indicated for each EDI transaction are the alternative delivery media available for sending or receiving document information (e.g. Web Server access, or Fax). EDI Transaction Direction Version Web Access Fax 830 Material Release Outbound Yes No No 856 Advance Ship Notice Inbound Yes No No 997 Functional Acknowledgement In/Out No No No As noted in Section I, all EDI communications with Dura will be through IBM Global Network, a Value Added Network. 3.2 ORGANIZATIONAL IDENTIFIERS (DUNS) All supplier and Dura facilities will be identified using their DUNS number. The organizational identifiers 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 as the MI. Supplier (SU) The supplier location responsible for part delivery. Typically a supplier manufacturing plant. Ship-From (SF) The supplier shipping location. Typically the same as the supplier manufacturing plant. No other supplier or Dura locations (such as Bill-to organization) are currently used. This information is provided on the contract order. Any changes would typically be communicated off system, e.g. through mail. Version 1.0 Page 12 of 28 January 1,

13 3.3 PURCHASE ORDER PRACTICES Summary Purchase Order Types Production material acquisition practices are discussed by distinguishing two types of purchase orders, spot orders and contract orders. In summary and relative to each Dura ship-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 established for a part, acquisition management will utilize Material Releases, Cumulative quantities, and shipment schedules or pulls signals Standard Practice in the Use of Different Order Types For each Dura manufacturing facility, Dura practice is to have no more than one order of any purchase order type (spot or contract) effective at one point in time for a specific production material part number. Dura order type relative to a part s life cycle is described below: 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 volume production. a. Separate Contract Orders will be established between a Dura ship-to plant and a supplier ship from location. A Contract Order may be issued for each part. A Contract Order may be issued with multiple parts. A contract order may be effective for multiple years. b. A contract order may be established prior to launch of volume production. c. Once a contract order is established and open, spot orders usage for the part will be restricted to exception situations described in the subsection below. d. Dura practice is that multiple contract orders can be concurrently open for a production material part number. This implies that material releases for one part number may include multiple LIN loops (one for each open contract order). e. Material Releases are periodically issued to forecast delivery requirements. f. Material Releases will authorize shipment for parts which are not implemented on the Dura Pull System (with the Ship-to plant involved). Version 1.0 Page 13 of 28 January 1,

14 Parts under Pull System control will be shipped based on the manually issued pull signal documents (not EDI transactions). g. Price changes are reflected through amendment to the existing contract order or with a new contract order. III. IV. A part with both production and service requirements is managed with one contract order. Once a part s demand is restricted to supporting service requirements, it may be managed using either a contract order or spot order, but not both concurrently. a. A contract order is used when Dura desires to manage acquisition using service forecasts of demand in the planning system. b. After the open contract order for a part has been closed, spot orders are issued for subsequent service requirements Exception Conditions with Concurrent Orders On an exception basis, a given production material part number managed with a contract order may have spot orders concurrently open. Listed below are circumstances for which a concurrent spot order may be issued. A spot order is used when the ultimate delivery destination is to a location other than a Dura manufacturing facility. This could include either Dura or non-dura delivery locations, such as Dura Engineering or a vehicle dealer. A spot order is used to procure 'unplanned' supplemental quantities of a part that exists on a contract order. For example, a spot order will be issued for when a part is 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 retroactive billing. Retro-billing does not impact planning schedules or delivery authorizations Supplier Responsibility Relative to Spot Orders Beyond requiring exception processing by Dura manufacturing facilities, the creation of spot orders for productive material may also require exception processing by the supplier. Spot Order requirements will not appear on Material Releases and do not impact release management; i.e. cumulative quantities do not reflect quantities on the spot order. Spot order delivery requirements must be considered supplemental demand to the Material Release for planning purposes. Shipment authorization for the substitute part will not be provided by a Material Release nor will Pull Signals be issued. Spot order quantities must be considered a supplemental delivery requirement. Version 1.0 Page 14 of 28 January 1,

15 The Packing Slip must reflect which specific spot orders are included in the shipment. If the spot order is shipped with other production materials, a separate Packing Slip should be 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 the shipment's ASN, the spot order quantity must be placed on a separate item loop referencing the spot Purchase Order number. If a new part number is created, the supplier may need to establish this "new part number in all business systems. For example, a new part number will be issued on a spot order when special processing on an existing part is needed to allow substitution for another part. Version 1.0 Page 15 of 28 January 1,

16 3.4 MATERIAL ACQUISITION PRACTICES Cum Management Cumulative quantities are used in the 830 and 856 transactions. The bullets below summarize 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 for each supplier location (SU) to a Dura (MI) location. Cum quantities are not effected by changes to a part's engineering revision level. Cum quantities are reset effective to January 1 st of each year for all Dura facilities. Cums are based on material received on or after January 1 st. 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 authorizations might not be sent in the Material Release by all plants. If not sent, authorization positions can be determined from data in the Material Release and contract terms for 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 part substitution. The supplier is to immediately resolve/contact his Dura material analyst to reconcile any discrepancy conditions: The Dura cum received is greater than the supplier cum shipped. The Dura cum received equals the supplier cum shipped but intransit material exists (cums are equal, but not relative to the last received shipment). The Dura cum received is less than the supplier cum shipped and intransit material is less than the difference Open Requirements and Intransit Material Open requirements in the 830 Material Release are based on cum received and will therefore include requirements for any intransit material. Intransit material is determined by comparing the supplier cum shipped to Dura's cum received and determining whether any shipments have been made since the last shipment referenced in the 830 SHP segment. Note that there are no supplier calculations relative to PQ (prior cum) authorization quantities Engineering Change Incorporation Engineering Revision Level changes are managed manually by Dura Materials Management. Version 1.0 Page 16 of 28 January 1,

17 Supplier is notified of engineering revisions level changes and their effectivity by amendment to an existing contract order or by issuing a new contract order. If the existing contract order is amended, the schedule on the Material Release represents the combined requirements for all engineering revisions. The Material Release will provide the current effective Engineering Revision until the effective date of the engineering change is reached (at which point, that new revision will be referenced on the Release). If a new contract order is issued, the Material Release will include separate LIN loops for each engineering revision of the part (since a separate LIN loop will be present for each part/contract order combination). ASNs are to reference the engineering revision of each part shipped. The cum shipped 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 shipped must reflect all shipments of the part, regardless of engineering revision. If Engineering revisions are issued on a new contract, the cum shipped must reflect shipments for each part / engineering revision combination Lot Control Lot Tracking is not required in any Dura EDI transaction, e.g. 856 Ship Notice/Manifest Consignee Supplier Shipments Note that in Release 2 of this, EDI transaction processing does not distinguish drop shipments (parts shipped to consignee who subsequently ships to Dura) from parts shipped directly to a Dura location. The consignee supplier is not identified and no unique EDI processing is conducted relative to consignee shipments. Consignee conditions are identified on the purchase agreement and must be handled "outside" of the system Direct Delivery to Non-Dura Location Parts 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 or exception shipments will be place on a spot purchase order Part Balance Out Balance out management is not typically required. Should a balance out conditions arise, it will 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. Version 1.0 Page 17 of 28 January 1,

18 3.4.8 Release / Schedule Cancellation Part 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 zero quantities). 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 pull signals previously received are to be shipped unless Dura has issued instructions to the contrary Returnable Container Tracking Returnable Containers used with a shipment are to be included on 856 Ship Notice in the LIN segment 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 containers are not included on Material Releases Shipment Authorization The 830 authorizes shipment for parts not under pull system control. Parts under pull system control have shipment authorized with manually generated pull signals. A single supplier location could have shipment authorized by both 830s and pull signals depending on the particular parts shipped Shipment Based Schedules Currently, schedules in manually issued Material Releases may be shipment based or delivery based. This varies by individual Dura manufacturing facility. When EDI base Material Releases are issued, schedules will be 'shipment based' Shipment Date Determination Different levels of sophistication exist in the different manufacturing planning systems used in Dura. As such, an established shipment routing takes precedent over shipment dates in the Material Release Material Release Authorizes Shipment Open deliveries with a Material Release ship date that does not coincide with established transportation routings should be shipped on the prior scheduled shipment. For example, if shipments are made each Monday and Thursday, an open delivery with a Wednesday ship date in the Material Release should be shipped on the prior Monday. Open requirements for shipments authorized by the Material Release must reflect intransit material: Version 1.0 Page 18 of 28 January 1,

19 If there is no intransit material, the first FST quantity is the open delivery requirement. If there is intransit material, FST requirements in the Material Release should be reduced Pull Signal Authorizes Shipment Pull Signals do not typically indicate a ship date. While Pull Signals may arrive daily, actual shipment is based on established practice with the Dura receiving facility. For example, with some Dura facilities shipment is to be immediate (or next day). With other facilities delivery is with the next scheduled shipment (e.g. if shipments are made each Thursday, all pull signals received 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 are there any intransit considerations Shipping Documentation and Identification Numbers All 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 which must 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 all shipping documents calling for them. Advanced Ship Notice Bill of Lading Packing Slip Barcode Shipping Labels Pull Card Labels Version 1.0 Page 19 of 28 January 1,

20 3.5 MATERIAL RELEASE (830) CHARACTERISTICS Material Release Attributes Attribute Release Function Description Release function will vary by part: For suppliers receiving shipment authorization via Pull Signals, Material Releases are issued as forecasts only. All schedule quantities are classified as 'planned'. For suppliers who do not receive shipment authorization via Pull Signals, Material Releases are issued as both forecasts and authorization to ship. Scheduled quantities will include both "firm" and 'planned' requirements. Material Release Definition Transaction Scope Transaction Identification Replacement Releases Schedule Basis Authorizations A unique Material Release is defined by a "Material Issuer/Supplier/Part Number/Contract Order" combination. All schedules and cumulative quantities are defined for this combination. Material Releases are issued periodically for each production part with demand within the Release horizon. All Releases from a Dura Material Issuer (MI) location to a supplier (SU) location will be included in one 830 transaction, i.e. one header with multiple LIN loops. Release identification (release number) formats vary by Dura division. Release identifiers end with an increasing, but not necessarily sequential, number. Releases totally replace the prior Material Release. In other words, the supplier should discard the entire schedule from a prior release and use the new release. Material Releases issued via EDI are "shipment based. Reference the 'Shipment Date' topic in prior section. Raw and fab authorization commitments are defined in the contract order. Based on capabilities of applications in each Dura facility, authorization quantities may or may not be sent in Material Releases. If authorizations are not sent in the Material Release, they can be determined using authorization horizons defined in a part's contract order. The authorization quantity is the YTD cum received quantity in the Material Release plus scheduled quantities in FST segments over the authorization horizon. Schedule Segment Part schedules (FST segments) in the Material Release have the Version 1.0 Page 20 of 28 January 1,

21 Attribute Description following characteristics Schedule quantities are discrete values (rather than cumulative). When the Material Release is used for both planning and shipment authorization, discrete days will be included in the near term schedule. In particular, Ship/Delivery Patterns are not used to identify shipment dates. Forecast buckets are restricted to weekly periods. The start date for weekly periods will always be a 'Monday'. Intransit material is reflected as open requirements in Material Release schedules based on the last shipment received at the Dura plant. The supplier must reduce open requirements in the Material Release to reflect any intransit shipments relative to the last shipment received (as designated in the Material Release). The Supplier does not calculate ahead/behind conditions (using Prior Cum authorization quantity) Material Release Processing Characteristic Release Issuer Issue Frequency Exception Releases Description Releases are issued independently by individual Dura plants to individual supplier locations. A weekly frequency is targeted. Actual frequency and date of issuing will vary by Dura plant. All active production parts will have releases issued. Releases for a subset of production parts may be issued at any time to meet (exceptional) near term schedule changes. Typically, these exception releases would only be necessary for parts for which the Material Release provides ship authorization. Such exception releases will be issued with the "05" Purpose Code (Replacement) and not highlighted with the more appropriate "04" Purpose Code (Change) Annual Cum Reset All Dura facilities will reset cums effective January 1 of each year. YTD cum received quantity is based on shipments received in the new year. In other words, a December 30 th shipment received on January 2 nd will be included in the new years cum received quantity. Version 1.0 Page 21 of 28 January 1,

22 3.6 ADVANCED SHIP NOTICE (856) ASN Attributes Attribute ASN Function Transaction Scope Transaction Identification LIN Loops Description An ASN provides data on a shipment from a Supplier location to a Dura location. An ASN is required for production parts on contract orders. Returnable containers used in the shipment are to be included in the ASN. If the shipment of production parts includes items from spot orders, they can be (optionally) included on the ASN. 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. A separate LIN loop is required for each part/purchase order (contract or spot) combination. Cum quantity shipped is based on each 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 Version 1.0 Page 22 of 28 January 1,

23 4 TRANSACTION GUIDELINES 4.1 GENERAL TRANSACTION INFORMATION Formal ANSI X12 Guidelines and AIAG Documents EDI Guidelines for Dura transactions are provided in to following sections. Dura guidelines document the segments used by Dura and are not intend to replace formal X12 transaction set documentation. 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 supplier order the following documents from the Automotive Industry Action Group (Southfield, Michigan): AIAG Implementation Guidelines-Version 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 Conformance with AIAG Recommendations The AIAG recommended practice refers to the M-3 and M-5 publications. The publication AIAG Implementation Guideline for Electronic Data Interchange versions AIAG 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-5 publications. Dura conformance with AIAG recommendations and allowed practice is discussed in sections below AIAG Conformance Control Records Other than noted below, Dura's ISA and GS control records are consistent with recommended 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) AIAG Conformance 830 Material Release Other than noted below, Dura's Material Release is consistent with recommended practices for the subset of segments used. Release Status segment (PRS) is not sent to flag conditions such as Release cancellations or part balance out. Refer to document subsections on Balance-Out and Cancellations in the Materials EDI Overview section. Version 1.0 Page 23 of 28 January 1,

24 The 04"change" purpose code is not sent to highlight a partial release (i.e. when a transaction only includes a subset of items under release control). All Material Releases are issued with a 05 "replacement" purpose code. Only the schedules for those items present in the transaction are to be replaced; and the schedules for any other items are not affected. Raw and Fab authorizations (ATH segment) are optional. Some Dura plants will include authorizations in the Material Release and other plants will not. When authorizations are not provided, the supplier can determine authorized quantities from information contained in the Material Release and the authorization horizons designated in the item's Purchase Order. Prior Cum quantity (ATH segment) is not sent. The schedule contains all Dura requirements based on the last received shipment referenced in the release. The supplier s open shipping requirement must reflect any intransit shipments not received by Dura at the time of release generation. Item description may be provided in an optional PID segment. Some Dura plants will include item descriptions for supplier reference on printed reports of EDI transactions AIAG Conformance 856 Advanced Ship Notice Other than noted below, Dura's Advanced Ship Notice is consistent with recommended practices for the subset of segments used. The Carrier PRO/Invoice number is to be returned in the ASN. PRO number is neither an AIAG Recommended or Allowed field AIAG Conformance - Record Definition While within AIAG recommended practice, it is important to realize a unique release is defined for each Item - Purchase Order combination. This means that multiple LIN loops will be issued for the same part if there is more than one open Purchase Order. The schedule in each LIN loop must only replace the prior schedule for the designated PO. The total schedule requirement for an item is the sum of the by PO schedules present in each LIN loop Functional Acknowledgments In addition to Interchange acknowledgements, Functional Acknowledgments (X ) are required 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 Version 1.0 Page 24 of 28 January 1,

25 4.1.4 Transaction Versions As of release 2 of Dura's, all current transaction versions are Release 1 transaction versions for the 830 and 856 were at EDI Transaction X.12 Version 830 Outbound Inbound (Inbound and Outbound) Segment Terminators/Element Separators Examples in this document display the Element Separator with an asterisk * and the Segment Terminator as N/L. The transaction defines actual values of the Segment Terminator and Element Separator sender in the data interchange envelope (ISA). The preferred values are: Printable Character EBCDIC HEX ASCII HEX Segment Terminator: 1C 1C Element Separator: ~ A1 7E Sub-element Separator: > 3E Note that the data Element Separator is define by the value of the fourth character position in the ISA and the Segment Terminator is defined by the value of the last character position (one byte after the data element ISA16). Version 1.0 Page 25 of 28 January 1,

26 4.2 DURA TRANSACTION CHANGES: TO The tables below summarize version EDI transaction deviations for the 830 and 856 transactions defined at X12 version Version transactions have only been implemented by plants of the former Excel Industries. ISA and GS Control Record Changes Deviation Area DUNS numbers introduced Description Telephone numbers were used as control record identifiers in version With version , either telephone and DUNS numbers will be used for Sender and Receiver Identifiers. Particular usage will vary by Dura organization ISA and GS identifiers. ISA and GS identifiers in version were the same and always referenced a specific plant. With version , The ISA may contain a Division identifier and the GS a plant identifier. Particular usage will vary by Dura organization. Identifier usage will not be retroactively changed. 830 Material Release Changes Deviation Area Description (deviation from ) Transaction Purpose Code Release Number Release Definition Horizon Start Schedule Definition Transaction purpose code (BFR01) is '05' rather than '00' (i.e. replace rather than original). Release number format will vary by Division. There should be no supplier processing that requires parsing of release numbers. In version , a unique release is defined for each item/purchase order combination. This implies that multiple concurrent releases may be issued for the same item? In version , the Horizon Start Date (BRF06) is no longer defined as the Purchase Order creation date. Depending on the issuing plant, the Horizon start date will be the Monday of the schedule generation week or the schedule generation date. 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. Version 1.0 Page 26 of 28 January 1,

27 Deviation Area Description (deviation from ) Purchase Order Identification Organization Identifiers In version , all Purchase Order numbers are identified in the LIN segment (even if one PO applies to all LIN loops). The PRF segment in the LIN loop is not used. BRF11 is not used. The Dura facility issuing the Material Release is identified in N1 Loop with the MI rather than BY identification code. Cum Management Segment Usage Cumulative Received quantity is sent in the SHP loop. Version looping structure/segments are changed to conform with AIAG recommendations. FST segments will be under the LIN loop rather than the SDP loop. 856 ASN Changes Deviation Area Description (deviation from ) Purpose Code Returnable Containers Cum Management Pull Signals Excess Transportation Segment Usage The '05' Replacement Purpose Code (BSN01) is not used. Changing an issued ASN is accomplished by canceling the initial ASN and sending a new original ASN with the corrections. Returnable Container items are required to be designated in an LIN loop. The LIN segment for production parts are to indicate the Returnable Container in which they are shipped. Cumulative quantity shipped is returned (SN104). The REF segment under CLD loop has the Customer Reference numbers (CR) added for designation of pull signal numbers. Pull Signal numbers are only returned when shipping parts under Dura pull system control. ETD segment added. Looping structure/segments changed to conform with AIAG recommendations. The "Order" hierarchical level is added. The LIN and SN1 segments are moved out of the "Item" level to the "Order" level. The PRF segment is not used to indicate Purchase Order number. Purchase Order number is designated in the LIN segment Version 1.0 Page 27 of 28 January 1,

28 4.3 DURA TRANSACTION CHANGES: TO The tables below summarize version EDI transaction deviations for 830 transactions defined at X12 version Version transactions have only been implemented in Dura s Stratford, Ontario and Milan, Tennessee facilities. 830 Deviation Area Description (deviation from ) Release Number In version the release number is in BFR02 rather than BFR03. Release Definition NTE Segment N1 Loop PID Segment PER Segment ATH Segment Schedule Representation In version , a unique release is defined for each item/purchase order combination. This implies that multiple concurrent releases may be issued for the same item? The NTE segment is not used. DUNS numbers are used exclusively. Use proprietary identification codes is discontinued. The N3 and N4 segments are not sent. PID segment is sent to provide a free form part description. PER segments are not sent. PQ cumulative quantity is not sent. MT and FI authorizations will still be sent. Version looping structure/segments are changed to conform with AIAG recommendations. FST segments will be under the LIN loop rather than the SDP loop. FST segments may be sent with discrete days (as well as weeks). 4.4 DURA VERSION TRANSACTION GUIDELINES Access and print EDI Transaction Guidelines from section <Key Information/Publications>. 4.5 TRANSACTION EXAMPLES Reference ExtraNet under <Key Information/Publications>. Version 1.0 Page 28 of 28 January 1,