862 Pull Loop System

Transcription

1 NEXTEER Supplier Information Packet 862 Pull Loop System Revised Date: March, 2010 Supplier Pull Loop System

2 TABLE OF CONTENTS Page I. Introduction... 1 II. System Flow... 2 III. Bar Code Label Requirements & Layout IV. EDI Guidelines Transaction Set Example of Multiple Parts and Due Dates ST Segment BSS Segment DTM Segment N1 Segment LIN Segment UIT Segment PO4 Segment PKG Segment REF Segment FST Segment CTT Segment SE Segment... 19

3 Supplier Pull Loop System Page 1 I. INTRODUCTION This packet is to provide information to Nexteer and SteeringMex Suppliers on the Nexteer Supplier Pull Loop System. The purpose of the Supplier Loop System is to electronically communicate replenishment requirements to Nexteer and SteeringMex direct material suppliers. The system formats requirements into pull signals (AIAG 862) and transmits them to the suppliers via EDS*ELIT (formerly GMNET). An overview of the process is provided, followed by barcode label requirements found at under Supplier Standards, under Supplier Label Specification North America - AIAG 862 Transaction format.

4 Supplier Pull Loop System Page 2 II. SYSTEM FLOW To get a better understanding of what steps are involved in the Supplier Loop, follow the cycle through once. Assume that Nexteer has just received parts from the supplier. A summary of the steps involved in receiving and consuming pull signals as well as sending requirements to the supplier are as follows: PLANT RECEIVES PARTS -- Parts will continue to be received at the dock. Barcode label information is entered into our system one of two ways: 1) RF EQUIPMENT -- Barcode labels will be scanned with RF Equipment, and then downloaded into our mainframe system. 2) LABEL REMOVED FROM CONTAINER -- When parts are received, one of two identical barcode labels is removed from the container. LABEL PLACED IN COLLECTION BOX -- Once the label is removed from the container, it is placed in a collection box. All of the labels in the collection boxes are gathered by the system coordinator at predetermined intervals. CARDS READ INTO SYSTEM -- The labels are entered into the mainframe system by using a wedge connected to the terminal. The information may also be manually entered into the system using the keyboard. Both mark the parts as consumed and in need of replenishment. If a label is damaged and cannot be scanned, the information must be entered using the keyboard. REQUIREMENTS SENT VIA EDS*ELIT (formerly GMNET) --The requirements are sent to the supplier via the network. The supplier dials up the network to retrieve Pull Signals from their mailbox. SUPPLIER BAR CODES CONTAINERS -- The supplier packs the parts into containers and attaches two bar coded labels to the outside of the container, unless otherwise instructed by the plant. SUPPLIER SHIPS CONTAINER -- The supplier ships the containers of parts to the appropriate Nexteer plant. Nexteer receives the parts and the process begins again.

5 Supplier Pull Loop System Page 6 IV. EDI GUIDELINES TRANSACTION SET The 862 transaction set is the EDI standard transaction set used for Kanban or pull signal information. Each transaction set contains information such as which parts are being ordered, the quantity, the ship date, etc. The following section provides an interpretation of each segment of the 862 transaction set that will be sent by Nexteer. The 862 transactions from Nexteer will be sent to the supplier in the EDS*ELIT file named EDI862SHPS or EDI862SSG. Nexteer will send the file with a default blocking size of 512 bytes. It is possible to have the file sent with a blocking size of 80 bytes. If this alternate is desired, the supplier must notify Nexteer prior to implementation. The ASC X12 Version/Release/Industry Standard for this transaction set is GM.

6 Supplier Pull Loop System Page 7 Example of Multiple Parts and Due Dates ST*862*0001 BSS*00* *980315*KB*980318*980315*01****A DTM*097*980315*0300*ET N1*SI**1* N1*SU**1* LIN**BP* UIT*PC PO4*110 PKG*X*67*AI*11Z*W23B5678 PKG*X*67*AI*12Z*06 PKG*X*67*AI*13Z*NEXTEER - PLANT # PKG*X*67*AI*14Z*NEXTEER - STREET ADDRESS PKG*X*67*AI*15Z*NEXTEER - CITY STATE ZIP PKG*X*67*AI*17Z*INNER TIE REF*KB* REF*KE* REF*DK*06 FST*600*C*D*980315**068*0800 LIN**BP* UIT*PC PO4*100 PKG*X*67*AI*11Z*W23B5678 PKG*X*67*AI*12Z*07 PKG*X*67*AI*13Z*NEXTEER - PLANT # PKG*X*67*AI*14Z*NEXTEER - STREET ADDRESS PKG*X*67*AI*15Z*NEXTEER - CITY STATE ZIP PKG*X*67*AI*17Z*INNER TIE REF*KB* REF*KE* REF*DK*07 FST*200*C*D*980315**068*0800 CTT*3*1130 SE*37*0001

7 Supplier Pull Loop System Page 8 ST Segment Heading The ST Segment is the Transaction Set Header ST*862* This is the Transaction Set - AIAG ELEMENT #143. Nexteer will send 862 to identify this transaction set as a Shipping Schedule (Supplier Pull Signal). 3. This is a Transaction Set Control Number - AIAG ELEMENT #329. This will be a unique number that will not be repeated within the calendar year.

8 Supplier Pull Loop System Page 9 BSS Segment Heading The BSS Segment is the beginning segment for the Shipping Schedule - Transaction Set It is used to indicate the beginning of a shipping schedule transaction set BSS*00* *980315*KB*980316*980316*01****A 2. This is the Transaction Set Purpose Code - AIAG ELEMENT #353. Nexteer will send 00 to indicate an original document. 3. This is the Reference Number - AIAG ELEMENT #127. This element is a reference number assigned to a Pull Signal Shipping Schedule by Nexteer. This sequence number will be incremented by 1 each time Nexteer sends Shipping Schedules. It is a 9 position numeric field. (Note that since each supplier may not receive pull signals each time Nexteer transmits, this number may have gaps from transmission to transmission for any one supplier.) 4. This is a Date field - AIAG ELEMENT #373. This is the creation date of the Pull Signal Shipping Schedule. The date will be in YYMMDD format. 5. This is the Schedule Type Qualifier - AIAG ELEMENT #675. Steering SSC will send KB in this field to identify a Kanban Shipping Schedule. 6. This is a Date field - AIAG ELEMENT #373. This is the schedule horizon start date. The date will be in YYMMDD format. 7. This is a Date field - AIAG ELEMENT #373. This is the schedule horizon end date. The date will be in YYMMDD format. 8. This is a release number - AIAG ELEMENT #328. Nexteer will send a 01 in this field. *Note the four asterisks between 8 and 9. This means Nexteer is not using data elements 127, 376, and 324. If used, these elements would follow element 328 and appear before element This is the Schedule Quantity Qualifier - AIAG ELEMENT #676. Nexteer will send an A in this field to indicate the quantities in this schedule are Actual Discreet Quantities. Supplier Pull Loop System Page 10

9 DTM Segment Heading The DTM Segment is the Date/Time Reference segment. It is used here to identify the transaction create time DTM*097*980315*0300*ET 2. This is the Date/Time Qualifier - AIAG ELEMENT #374. Nexteer will send code 097 to indicate Transaction Creation Date. 3. This is a Date field - AIAG ELEMENT #373. Nexteer will use this as the transaction create date. The date will be in YYMMDD format. 4. This is a Time field - AIAG ELEMENT #337. Nexteer will use this as the transaction create time. It will be in an HHMM format based on a 24-hour clock. 5. This is the Time Qualifier - AIAG ELEMENT #623. Nexteer will send ET. *Note dates and times are based on Eastern Standard Time.

10 Supplier Pull Loop System Page 11 N1 Segment Heading The N1 Segment is used to identify a party by type of organization, name and code N1*SI**1* or N1*SI**92*06 N1*SU**1* This is the Entity Identifier Code - AIAG ELEMENT #98. Nexteer will send SI to identify the Pull Signal Shipping Schedule issuer and SU to identify the Supplier who received the schedules. Note the two asterisks between 2 and 3. This means that Nexteer will not use the optional element #93 between element #98 and element # This is an ID Code Qualifier - AIAG ELEMENT #66. Nexteer will use 1 to indicate a DUNS # will be present in the ID code. Nexteer will use 92 to indicate that a GM standard code will be present in the ID code, such as plant number. 4. This is an ID Code - AIAG ELEMENT #67. An ID code identifies the parties in the transaction. If SI is used in the Entity Identifier Code, Nexteer DUNS # will be represented in this field. Otherwise, it will be the Supplier s DUNS #. It is defined as a 9-position numeric field. 5. Nexteer will send at least 2 iterations of the N1 loop. The SI and SU codes are mandatory.

11 Supplier Pull Loop System Page 12 LIN Segment Detail The LIN Segment is used to specify basic item identification data LIN**BP* Note the two asterisks between 1 and 2. This means that Nexteer is not using the optional element #350 between the segment identifier and element # This is the Product/Service ID Qualifier - AIAG ELEMENT #235. This code identifies the Type/Source of the descriptive number used in the Product ID. Nexteer will send BP which identifies the Buyer s Part Number. 3. This is the Product/Service ID - AIAG ELEMENT #234. The Buyer s Part Number will be present in this field. It will be 8-position numeric. Note that Nexteer will not use data elements #235, #234 and the repeating sets of #235 and #234 in this segment. If present, they would follow element #234 (#3 in this example).

12 Supplier Pull Loop System Page 13 UIT Segment Detail The UIT Segment is used to specify item unit data. 1 2 UIT*PC 2. This is the Unit of Measure Code - AIAG ELEMENT #355. This code identifies the unit of measure which applies to the part number. 3. Nexteer may send the following codes: AY BR CF CN DA GA JR LB MI PD RD SI TH BA BU CG CO DR GR KE MO PK RE SM TO BD BX CH CQ DZ GS KG LF MR PL RL SO BF CA CI CT EA HR KM LO OZ PR RM ST WK BG CB CL CW EV HU KT LT PA PT SF SV YD BO CE CM CY FT IN LA LY PC QT SH SY YR

13 Supplier Pull Loop System Page 14 PO4 Segment Detail The PO4 Segment is used to specify the physical qualities, packaging, weights and dimensions relating to the item. 1 2 PO4* This is the Standard Pack - AIAG ELEMENT #356. Nexteer will send the standard pack quantity in this field. This is a numeric field, minimum length 1, and maximum length 8. Note that Nexteer will not use data elements #357, #355, #103, #187, #384, #355, #385, #355, #82, #189, #67 or #355. If used, these elements would follow element 356.

14 Supplier Pull Loop System Page 15 PKG Segment Detail The PKG Segment is used to provide for Nexteer specified information the supplier must print on the shipping label PKG*X*67*AI*11Z*W23B5678 PKG*X*67*AI*12Z*07 PKG*X*67*AI*13Z*NEXTEER - PLANT # PKG*X*67*AI*14Z*NEXTEER - STREET ADDRESS PKG*X*67*AI*15Z*NEXTEER - CITY STATE ZIP PKG*X*67*AI*17Z*BOOT, RACK 2. This is the Item Description Type - AIAG ELEMENT #349. Nexteer will send X to indicate the information is semi-structured. 3. This is the Packaging Characteristic Code - AIAG ELEMENT #753. Nexteer will send a 67 in this field to indicate label information. 4. This is an Item Description Qualifier - AIAG ELEMENT #348. Nexteer will send an AI which indicates AIAG is the agency responsible for the code used. 5. This is the Packaging Description Code - AIAG ELEMENT #754. Nexteer will send 11Z, 12Z 13Z, 14Z, 15Z and 17Z. This field indicates the line on the label the information will appear. See label specifications at 6. This is a Description - AIAG ELEMENT #352. In this field, Nexteer will send the information which must be printed on the Shipping Label. If the Packaging Description Code is 11Z, then this data element will be an 8 character maximum field and will contain the Delivery Location (DLOC). If the Packaging Description Code is 12Z, then this data element will be a 7 character maximum field and will contain the Plant/Dock code. If the Packaging Description is 12Z 15Z, then this data element will be a 30 character maximum field and will contain the shipping information. If the Packaging Description Code is 17Z, then

15 this data element will be a 10 character maximum field and will contain the Part Description. *Note that if no DLOC information exists, 11Z will show nothing leave blank on the label.

16 Supplier Pull Loop System Page 16 REF Segment Detail REF*KB* REF*KE* REF*DK*06 2. This is a Reference Number Qualifier - AIAG ELEMENT #128. Nexteer will send KB to indicate the beginning Pull Signal Number, KE to indicate the ending Pull Signal Number, and DK to indicate which Nexteer plant the parts should be delivered to. 3. This is a Reference Number - AIAG ELEMENT #127. This is a reference number as specified by the reference number qualifier. The beginning ( KB ) and ending ( KE ) Pull Signal Numbers will reflect zeroes. The PO is required on the Bar Code Labels when Kanban number zeroes are sent on the 862. There may be Kanban numbers in the future, so supplier should not remove this code but allow all zeroes to process in their system but use PO (Purchase Order) from the Release. Note Nexteer does not use the optional element #352. If used, element #352 would follow element #127.

17 Supplier Pull Loop System Page 17 FST Segment Detail The FST Segment is used to specify the forecasted dates and quantities FST*330*C*D*980315**068* This is a Quantity Field - AIAG ELEMENT #380. Nexteer will send the quantity authorized to be shipped. This is a numeric field, minimum length 1, and maximum length This is a Forecast Qualifier - AIAG ELEMENT #680. This is a code specifying the sender s confidence level of the forecast data. Nexteer will send a C to indicate a firm quantity. 4. This is the Forecast Timing Qualifier - AIAG ELEMENT #681. Nexteer will send a D to indicate a discrete quantity. 5. This is a Date field - AIAG ELEMENT #373. Nexteer will send the Ship Date in this field (ship based). This is the date which the parts are to be shipped to the appropriate Nexteer plant. The format is YYMMDD. *Note the two asterisks between 5 and 6. This means that Nexteer is not using optional element #373 between element #373 (#5 in this example) and element # This is a Date/Time Qualifier - AIAG ELEMENT #374. Nexteer will send 068 to indicate the current ship date and time. 7. This is a Time field - AIAG ELEMENT #337. Nexteer will send the time the shipment is ship (ship based). It will be in an HHMM format based on a 24-hour Eastern Time clock. *Note Nexteer does not use data elements #128 and #127. If used, they would follow #337.

18 Supplier Pull Loop System Page 18 CTT Segment Summary CTT*1* This is the Number of Line Items - AIAG ELEMENT #354. Nexteer will send the total number of line items (LIN segments) in the transaction set. It is a numeric field, minimum length 1, maximum length This is a Hash Total - AIAG ELEMENT #347. Nexteer will send the hash total of all of the quantities authorized to be shipped (AIAG ELEMENT #380) in the FST segments. This is a numeric field, minimum length 1, maximum length 10. *Note Nexteer is not using data elements #81, #355, #183, #352. If used, these elements would follow #347.

19 Supplier Pull Loop System Page 19 SE Segment Summary SE*17* This is the Number of Included Segments - AIAG ELEMENT #96. Nexteer will send the total number of segments included in this transaction set including the ST and SE segments. It is a numeric field, minimum length 1, and maximum length This is a Transaction Set Control Number - AIAG ELEMENT #329. This will be the same number as contained in #3 of the ST-Transaction Set Header segment.