IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS SHIPPING SCHEDULE (862) TRANSACTION SET

Transcription

1 IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS SHIPPING SCHEDULE (862) TRANSACTION SET FCA US INFORMATION & COMMUNICATION TECHNOLOGY MANAGEMENT ANSI ASC X12 VERSION/RELEASE CHRY

2 FCA US - Shipping Schedule 862 Shipping Schedule Functional Group ID=SS Introduction: This standard provides the format and establishes the data contents of a shipping schedule transaction set within the context of an electronic data interchange (EDI) environment. The shipping schedule transaction set provides the ability for a customer to convey precise shipping schedule requirements to a supplier, and is intended to supplement the planning schedule transaction set (830). The shipping schedule transaction set will supersede certain shipping and delivery information transmitted in a previous planning schedule transaction, but it does not replace the 830 transaction set. The shipping schedule transaction set shall not be used to authorize labor, materials or other resources. The use of this transaction set will facilitate the practice of Just In Time (JIT) manufacturing by providing the customer with a mechanism to issue precise shipping schedule requirements on a more frequent basis than with the issuance of a planning schedule transaction, e.g.daily shipping schedules versus weekly planning schedules. The shipping schedule transaction also provides the ability for a customer location to issue shipping requirements independent of other customer locations when planning schedule transactions are issued by a consolidated scheduling organization. Notes: With the launch of Common Ship/Delivery Schedule (CSDS), plants may establish ship and delivery windows which do not necessarily differ by total transit time. In addition, window times within each day and by day of the week may differ. FCA has changed the 862 format to provide transportation suppliers with both shipment based information and delivery based information to facilitate smooth, on-time delivery to its plants. Please refer to Example 7 - Common SDS. The supplier or carrier should be aware of the following things when programming for this implementation guide - The date (FST04) and time (FST07) indicated in the FST segment represent when the supplier should SHIP the parts, not when the supplier should deliver the parts to FCA. - The elements BSS05 and BSS06 represent the horizon start and horizon end dates with a 30 calendar day schedule. - The resource authorization date (ATH02) is the day prior to the 30 calendar day schedule. - In the Beginning Segment - Shipping Schedule (BSS), a code value of '04' (Change) in the BSS01 element will be issued for the transmission of requirement changes for selected part numbers only; a code value of '02' (Add) in the BSS01 element will be issued for adding new part numbers or shipment requirements sent in a previous 862 transaction; a code value of '03' (Delete) in the BSS01 element will be issued for removing a part or shipment requirement sent on a previous 862 transaction. Data for other part numbers previously transmitted and not included in this transmission must be retained. 03/10/2017 V/R CHRY 1 FCA US

3 FCA US - Shipping Schedule - Daily adjustments will not be shown in the SHP segment but will be included in the Quantity element (ATH03) of the ATH segment to provide the net adjusted cum requirements. The adjustment no longer needs to be calculated to provide net requirements. Metered Parts Kanban Ship Schedule (MSDS) The Metered Parts Kanban Ship Schedule (MSDS) is intended to enable the Split ASN process. The Split ASN process using Kanban is intended to allow an offsite faciility to receive full truckloads of material from suppliers and meter the material to the plant using the MSDS. Material will arrive to the facility a day ahead of when it is to be delivered to the plant. Having projections available prior to the trucks arriving at the offsite facility will allow the trucks to be unloaded and split for the next day's shipments. DEVIATION TABLE FOR THE DETAIL AREA: 1: The NTE segment is used to show the type of SDS part (test, information, or Just In Time). 2: This PER segment will provide contact information for the specific part shown in the LIN segment. 3. The DTM segment was added to the JIT loop in order to facilitate more flexible shipment/delivery requirements as part of the Common SDS (CSDS) Rewrite. NOTE: Through this document, 'USER STATUS' and 'USER ATTRIBUTES' refer to the FCA implementation. Notes about the format of this implementation guide: 1. The requirements contained herein have not changed, with the exception of anything that may appear in the History of Changes section below. 2. The term 'Base Status' refers to the requirements as defined by the ASC X12 Standards Organization. 3. The terms 'User Status' and 'User Attributes' refer to FCA requirements. 4. Data segment sequence tables for each hierarchical level will no longer be presented at the beginning of each hierarchical level. The data segment sequence tables for each hierarchical level will now be presented at the beginning. 5. Segment Syntax and Semantic notes as defined by ASC X12 will now be included where in the 'old' format they were not. 6. Element Description as defined by ASC X12 will now be included where in the 'old' format they were not. 7. Many comments that relate to a particular code value will now appear underneath the code value description, where previously the comments would appear to the right. History of Changes: 01/13/2004: Add comments and example (8) for Metered Parts Kanban SDS. 03/01/2004: Add comments and example (9) for Customer EDI. 09/30/2004: Add functionality for (new example) Assembly Kanban: add PO4 segment, add codes to REF segment 07/19/2005: Add code 'A' (Immediate) to forecast qualifier (FST02) for Kanban. 03/10/2017 V/R CHRY 2 FCA US

4 FCA US - Shipping Schedule 08/04/2005: Add N1 loop for plant extension ship to locations 08/20/2006: Add transportation mode 'I' to both TD5 segments 04/11/2007: Add requirements and example (8) for Web Based Module Ordering (WBMO) 11/15/2007: Transition to Chrysler LLC with removal of references to Daimler 09/21/2010: Name change from Chrysler LLC to Chrysler Updated Address 10/20/2010: Minor Edits 10/30/2014: Removed requirements and example for Web Based Module Ordering (WBMO). This Is No Longer Supported 03/31/2015: Detail - NTE02 Added New Local Code 'I' Name Change To FCA US 03/10/2017: Detail - REF01 Added Note to Qualifier 'RL' Heading: Page Pos. Seg. Base User Loop Notes and No. No. ID Name Guide Status Max.Use Repeat Comments ST Transaction Set Header M M BSS Beginning Segment for Shipping M M 1 Schedule 030 DTM Date/Time/Period O Not NTE Note/Special Instruction F Not REF Reference Numbers O Not >1 045 PID Product/Item Description O Not >1 LOOP ID - N N1 Name O N2 Additional Name Information O Not N3 Address Information O Not N4 Geographic Location O Not REF Reference Numbers O Not PER Administrative Communications O Not 3 Contact 110 FOB F.O.B. Related Instructions O Not 1 03/10/2017 V/R CHRY 3 FCA US

5 FCA US - Shipping Schedule Detail: Page Pos. Seg. Base User Loop Notes and No. No. ID Name Guide Status Max.Use Repeat Comments LOOP ID - LIN LIN Item Identification O UIT Unit Detail M M NTE Note/Special Instruction O PER Administrative Communications Contact O PO4 Item Physical Details O >1 060 PKG Marking, Packaging, Loading O Not > REF Reference Numbers O SDP Ship/Delivery Pattern O Not 1 LOOP ID - N N1 Name O N2 Additional Name Information O Not N3 Address Information O Not N4 Geographic Location O Not REF Reference Numbers O Not PER Administrative Communications Contact O Not FOB F.O.B. Related Instructions O Not 1 LOOP ID - FST FST Forecast Schedule O DTM Date/Time/Period O SDQ Destination Quantity O Not LOOP ID - JIT JIT Just-In-Time Schedule O REF Reference Numbers O Not DTM Date/Time/Period O ATH Resource Authorization O 1 LOOP ID - SHP SHP Shipped/Received Information O REF Reference Numbers O Not TD1 Carrier Details (Quantity and Weight) O Not TD5 Carrier Details (Routing Sequence/Transit Time) O TD3 Carrier Details (Equipment) O Not 1 Summary: Page Pos. Seg. Base User Loop Notes and No. No. ID Name Guide Status Max.Use Repeat Comments CTT Transaction Totals M M SE Transaction Set Trailer M M 1 03/10/2017 V/R CHRY 4 FCA US

6 FCA US - Shipping Schedule Segment: ST Transaction Set Header Position: 010 Loop: Level: Heading Usage: Mandatory Max Use: 1 Purpose: To indicate the start of a transaction set and to assign a control number Syntax Notes: Semantic Notes: Comments: 1 The transaction set identifier (ST01) is intended for use by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the invoice transaction set). Notes: The transaction set control number (ST02) in this header must match the transaction set control number (SE02) in the transaction set trailer (SE). Example: ST~862~ Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes ST Transaction Set Identifier Code M ID 3/3 M Code uniquely identifying a Transaction Set 862 X12.37 Shipping Schedule ST Transaction Set Control Number M AN 4/9 M AN 9/9 Identifying control number assigned by the originator for a transaction set. A unique control number (Same as SE02). 03/10/2017 V/R CHRY 5 FCA US

7 FCA US - Shipping Schedule Segment: BSS Beginning Segment for Shipping Schedule Position: 020 Loop: Level: Heading Usage: Mandatory Max Use: 1 Purpose: To indicate the beginning of a shipping schedule. Syntax Notes: 1 At least one of BSS07 or BSS08 is required. Semantic Notes: Comments: 1 Use BSS02 to indicate a document number. 2 Use BSS03 to indicate the date of this document. 3 Use BSS05 to indicate the schedule horizon start date (the date when the schedule begins.) 4 Use BSS06 to indicate the schedule horizon end date (the date when the schedule ends.) 5 BSS08 is the identifying number for a forecast assigned by the orderer/purchaser. Notes: This segment indicates whether the schedule is shipment or kanban based. The BSS01 element shows what action is to be taken with this transaction in regard to previous shipping schedules. Example: BSS~05~ ~910603~SH~910603~910702~~ Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes BSS Transaction Set Purpose Code M ID 2/2 M Code identifying purpose of transaction set 02 Add 03 Delete 04 Change 05 Replace BSS Reference Number M AN 1/30 M AN 6/9 Reference number or identification number as defined for a particular Transaction Set, or as specified by the. The schedule issue date in YYDDDHHMM format For KANBAN, the schedule issue date will be in YYMMDD format. BSS Date M DT 6/6 M Date (YYMMDD) Current date. BSS Schedule Type Qualifier M ID 2/2 M 03/10/2017 V/R CHRY 6 FCA US

8 FCA US - Shipping Schedule Code identifying the type of dates used when defining a shipping or delivery time in a schedule or forecast KB Kanban Signal SH Shipment Based BSS Date M DT 6/6 M Date (YYMMDD) First day of the thirty calendar day schedule. For KANBAN, the current date. BSS Date M DT 6/6 M Date (YYMMDD) Last day of the thirty calendar day schedule. For KANBAN, the current date. BSS Release Number C AN 1/30 Not BSS Reference Number C AN 1/30 AN 6/9 Reference number or identification number as defined for a particular Transaction Set, or as specified by the. Same as BSS02. BSS Contract Number O AN 1/30 Not BSS Purchase Order Number O AN 1/22 Not BSS Schedule Quantity Qualifier O ID 1/1 Not 03/10/2017 V/R CHRY 7 FCA US

9 FCA US - Shipping Schedule Segment: N1 Name Position: 050 Loop: N1 Optional Level: Heading Usage: Optional Max Use: 1 Purpose: To identify a party by type of organization, name, and code Syntax Notes: 1 At least one of N102 or N103 is required. 2 If either N103 or N104 is present, then the other is required. Semantic Notes: Comments: 1 This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party. Notes: Three iterations of the N1 loop in the heading area will be used to identify the Shipping Schedule Issuer, the Release Supplier, and the Ship To location. The Ultimate Destination (MA) is not used within the Shipping Schedule. Example: N1~SI~~92~04000 N1~SU~~92~10167AB N1~ST~~92~09106 N1~SF~~92~10167AC Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes N Entity Identifier Code M ID 2/2 M Code identifying an organizational entity or a physical location. SF Ship From SI Shipping Schedule Issuer ST Ship To SU Supplier/Manufacturer N Name C AN 1/35 Not N Identification Code Qualifier C ID 1/2 Code designating the system/method of code structure used for Identification Code (67) 92 Assigned by Buyer N Identification Code C ID 2/17 ID 5/7 Code identifying a party. For FCA issued schedules: If N101 = 'SI', this contains '04000' = FCA Assembly Division; For KANBAN, this element will contain '04000KB'; For Metered Parts Kanban, this element will contain '04000MK'; If N101 = 'ST', the FCA assigned receiving plant code; 03/10/2017 V/R CHRY 8 FCA US

10 FCA US - Shipping Schedule If N101 = 'SU', the FCA assigned supplier code of the release supplier. For Metered Parts Kanban, this will be the supplier code or pool point location; If N101 = 'SF', the FCA assigned supplier code of the ship-from location; For Customer EDI schedules where FCA is the supplier: If N101 = 'SI', the FCA assigned code for the trading partner issuing the schedule; If N101 = 'ST', the FCA assigned code for the ship to location; If N101 = 'SU', the FCA assigned supplier code of the release supplier. For Customer EDI, '04006'; 03/10/2017 V/R CHRY 9 FCA US

11 FCA US - Shipping Schedule Segment: LIN Item Identification Position: 010 Loop: LIN Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To specify basic item identification data Syntax Notes: 1 If LIN04 is present, then LIN05 is required. 2 If LIN06 is present, then LIN07 is required. 3 If LIN08 is present, then LIN09 is required. 4 If LIN10 is present, then LIN11 is required. 5 If LIN12 is present, then LIN13 is required. 6 If LIN14 is present, then LIN15 is required. 7 If LIN16 is present, then LIN17 is required. 8 If LIN18 is present, then LIN19 is required. 9 If LIN20 is present, then LIN21 is required. 10 If LIN22 is present, then LIN23 is required. 11 If LIN24 is present, then LIN25 is required. 12 If LIN26 is present, then LIN27 is required. 13 If LIN28 is present, then LIN29 is required. 14 If LIN30 is present, then LIN31 is required. Semantic Notes: Comments: 1 See the Data Dictionary for a complete list of ID's. 2 LIN01 is the line item identification 3 LIN02 through LIN31 provide for fifteen (15) different product/service ID's for each item. For Example: Case, Color, Drawing No., UPC No., ISBN No., Model No., SKU. Notes: This is a mandatory segment and is used to identify the part number. Clarification on the specification of part number: When FCA issues the schedule: - BP = FCA part number When FCA receives the schedule: - BP = Customer part number - VP = FCA part number Examples: LIN~~BP~ AA LIN~~BP~BUYERPART~VP~VENDORPART (Customer EDI) Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes LIN Assigned Identification O AN 1/6 Not 03/10/2017 V/R CHRY 10 FCA US

12 FCA US - Shipping Schedule LIN M ID 2/2 M Code identifying the type/source of the descriptive number used in Product/Service ID (234) BP Buyer's Part Number LIN Product/Service ID M AN 1/30 M AN 8/10 Identifying number for a product or service FCA part number. LIN O ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) For KANBAN use only. JN Job Number VP Vendor's (Seller's) Part Number LIN Product/Service ID C AN 1/30 AN 8/10 Identifying number for a product or service If LIN04 = 'JN', for KANBAN use only: KANBAN Job Number; If LIN04 = 'VP', for Customer EDI only: FCA part number. LIN O ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) For KANBAN use only. JS Job Sequence Number LIN Product/Service ID C AN 1/30 Identifying number for a product or service For KANBAN use only: KANBAN Job Sequence Number LIN O ID 2/2 Not LIN Product/Service ID C AN 1/30 Not LIN O ID 2/2 Not LIN Product/Service ID C AN 1/30 Not LIN O ID 2/2 Not LIN Product/Service ID C AN 1/30 Not LIN O ID 2/2 Not LIN Product/Service ID C AN 1/30 Not 03/10/2017 V/R CHRY 11 FCA US

13 FCA US - Shipping Schedule LIN O ID 2/2 Not LIN Product/Service ID C AN 1/30 Not LIN O ID 2/2 Not LIN Product/Service ID C AN 1/30 Not LIN O ID 2/2 Not LIN Product/Service ID C AN 1/30 Not LIN O ID 2/2 Not LIN Product/Service ID C AN 1/30 Not LIN O ID 2/2 Not LIN Product/Service ID C AN 1/30 Not LIN O ID 2/2 Not LIN Product/Service ID C AN 1/30 Not LIN O ID 2/2 Not LIN Product/Service ID C AN 1/30 Not LIN O ID 2/2 Not LIN Product/Service ID C AN 1/30 Not 03/10/2017 V/R CHRY 12 FCA US

14 FCA US - Shipping Schedule Segment: UIT Unit Detail Position: 020 Loop: LIN Optional Level: Detail Usage: Mandatory Max Use: 1 Purpose: To specify item unit data Syntax Notes: Semantic Notes: Comments: Notes: This is a mandatory segment and indicates the unit of measure for all quantities relating to the line item. Example: UIT~EA Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes UIT Unit or Basis for Measurement Code M ID 2/2 M Code identifying the basic unit of measurement. EA Each UIT Unit Price C R 1/14 Not UIT Basis of Unit Price Code O ID 2/2 Not 03/10/2017 V/R CHRY 13 FCA US

15 FCA US - Shipping Schedule Segment: NTE Note/Special Instruction Position: 030 Loop: LIN Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To transmit information in a free-form format, if necessary, for comment or special instruction Syntax Notes: Semantic Notes: Comments: 1 The NTE segment permits free-form information/data which, under ANSI X12 standard implementations, is not machine processable. The use of the NTE segment should therefore be avoided, if at all possible, in an automated environment. Notes: This segment is used to provide part information: if the part is a Just In Time part or test part. Not used for Kanban. Only 1 NTE segment would be created for a particular part. Note: This segment will be eliminated in the future. Examples: NTE~LIN~T NTE~LIN~J Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes NTE Note Reference Code O ID 3/3 Code identifying the functional area or purpose for which the note applies LIN Line Item NTE02 3 Free Form Message M AN 1/60 M AN 1/1 Free-form text I J S T RILC Routes Just In Time Supplier Information Part In Test Mode Indicated part is in test mode. Supplier should not ship. 03/10/2017 V/R CHRY 14 FCA US

16 FCA US - Shipping Schedule Segment: PER Administrative Communications Contact Position: 040 Loop: LIN Optional Level: Detail Usage: Optional Max Use: 6 Purpose: To identify a person or office to whom administrative communications should be directed Syntax Notes: 1 If PER03 is present, then PER04 is required. Semantic Notes: Comments: Notes: This segment is used to convey information about the contact person. Examples: PER~EX~CONTACT USING PLANT~TE~ PER~EX~DON LAWES~TE~ Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes PER Contact Function Code M ID 2/2 M Code identifying the major duty or responsibility of the person or group named EX Expeditor PER02 93 Name O AN 1/35 AN 1/19 Free-form name The name of the contact person. PER Communication Number Qualifier O ID 2/2 Code identifying the type of communication number TE Telephone PER Communication Number C AN 7/256 AN 10/10 Complete communications number including country or area code when applicable The telephone number of the contact person. PER Communication Number Qualifier O ID 2/2 Code identifying the type of communication number PER Communication Number O AN 7/256 Complete communications number including country or area code when applicable 03/10/2017 V/R CHRY 15 FCA US

17 FCA US - Shipping Schedule Segment: PO4 Item Physical Details Position: 050 Loop: LIN Optional Level: Detail Usage: Optional Max Use: >1 Purpose: To specify the physical qualities, packaging, weights, and dimensions relating to the item Syntax Notes: 1 If PO402 is present, then PO403 is required. 2 If PO405 is present, then at least one of PO406 or PO407 is required. 3 If PO408 is present, then PO409 is required. 4 If PO413 is present, then at least one of PO410 PO411 or PO412 is required. Semantic Notes: Comments: 1 PO403 - The "Unit of Measure Code" (Element #355) in this segment position is for purposes of defining the pack (PO401) /size (PO402) measure which indicates the quantity in the inner pack unit. Example: If the carton contains Ounce packages, it would be described as follows: Element 356 = 24; Element 357 = 12; Element 355 = OZ. 2 PO410 defines the unit of measure for PO408, PO409, and PO410. Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes PO Pack O N0 1/6 Number of inner pack units per outer pack unit PO Size O R 1/8 Not PO Unit or Basis for Measurement Code C ID 2/2 Code identifying the basic unit of measurement. PO Packaging Code O ID 5/5 Not PO Weight Qualifier O ID 1/2 Not PO Gross Weight per Pack C R 1/9 Not PO Unit or Basis for Measurement Code C ID 2/2 Not PO Gross Volume per Pack O R 1/9 Not PO Unit or Basis for Measurement Code C ID 2/2 Not PO Length C R 1/6 Not PO Width C R 1/8 Not 03/10/2017 V/R CHRY 16 FCA US

18 FCA US - Shipping Schedule PO Height C R 1/6 Not PO Unit or Basis for Measurement Code C ID 2/2 Not 03/10/2017 V/R CHRY 17 FCA US

19 FCA US - Shipping Schedule Segment: REF Reference Numbers Position: 070 Loop: LIN Optional Level: Detail Usage: Optional Max Use: 12 Purpose: To specify identifying numbers. Syntax Notes: Semantic Notes: Comments: Notes: to identify the receiving dock, line feed, or drop point of the Ship To location. Examples: REF~DK~MAIN REF~LF~0001 REF~RL~25H1 Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes REF M ID 2/2 M Code qualifying the Reference Number. DK Dock Number LF Assembly Line Feed Location M1 Material Storage Location RL Reserve Assembly Line Feed Location Drop Zone RU Route Number REF Reference Number M AN 1/30 M AN 1/8 Reference number or identification number as defined for a particular Transaction Set, or as specified by the. The FCA assigned name for the location described in REF01. For Assembly Kanban: If REF01 = 'RL', the bay within the plant (i.e. nearest pole); If REF01 = 'LF', the station; If REF01 = 'RU', the internal plant route; If REF01 = 'M1', the material storage location; REF Description O AN 1/80 Not 03/10/2017 V/R CHRY 18 FCA US

20 FCA US - Shipping Schedule Segment: N1 Name Position: 081 Loop: N1 Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To identify a party by type of organization, name, and code Syntax Notes: 1 At least one of N102 or N103 is required. 2 If either N103 or N104 is present, then the other is required. Semantic Notes: Comments: 1 This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party. Notes: This N1 will be used only for those suppliers that should ship to a plant extension. The N1 loop in the detail area is used to identify physical locations for Ship From, Ship To and the FCA plant for which the material is ultimately intended. The Ship To location will usually be the FCA plant or a plant extension. These values must be echoed back to FCA in the ASN (856). If these codes are not accurate, contact your buyer. Example: N1~ST~~92~04010 (FCA plant or plant extension) Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes N Entity Identifier Code M ID 2/2 M Code identifying an organizational entity or a physical location. ST Ship To N Name C AN 1/35 Not N Identification Code Qualifier C ID 1/2 Code designating the system/method of code structure used for Identification Code (67) 92 Assigned by Buyer N Identification Code C ID 2/17 Code identifying a party. 03/10/2017 V/R CHRY 19 FCA US

21 FCA US - Shipping Schedule Segment: FST Forecast Schedule Position: 090 Loop: FST Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To specify the forecasted dates and quantities Syntax Notes: 1 If either FST06 or FST07 is present, then the other is required. 2 If either FST08 or FST09 is present, then the other is required. Semantic Notes: Comments: 1 As qualified by FST02 and FST03, FST04 represents either a discrete forecast date, the first date of a forecasted bucket (weekly, monthly, quarterly, etc.) or the start date of a flexible interval. 2 If FST03 - "F" (indicating flexible interval), then FST04 and FST05 are required. FST04 would be used for the start date of the flexible interval and FST05 would be used for the end date of the flexible interval. 3 FST06 - To qualify time in FST07. The purpose of the FST07 element is to express the specific time of day in a 24-hour clock, to satisfy "just-in-time" requirements. As an alternative, the ship/delivery pattern segment (SDP) may be used to define an approximate time, such as "AM" or "PM". Notes: One FST segment represents one of the thirty calendar days for FCA plants. Examples: FST~100~C~D~910303~~010~0800 FST~100~C~D~ FST~0~C~D~ FST~1366~D~D~ FST~360~D~D~910326~~010~0800 Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes FST Quantity M R 1/10 M R 1/8 Numeric value of quantity Cumulative quantity for the day. FST Forecast Qualifier M ID 1/1 M Code specifying the sender's confidence level of the forecast data. A Immediate For Kanban only: will be used for Hot Pick List - Immediate/Emergency requirements. C Firm D Planning FST Forecast Timing Qualifier M ID 1/1 M Code specifying interval grouping of the forecast D Discrete 03/10/2017 V/R CHRY 20 FCA US

22 FCA US - Shipping Schedule FST Date M DT 6/6 M Date (YYMMDD) If FST03 = 'D', the day the parts are scheduled for shipment. FST Date O DT 6/6 Not FST Date/Time Qualifier C ID 3/3 Code specifying type of date or time, or both date and time 010 Requested Ship FST Time C TM 4/4 Time expressed in 24-hour clock time (HHMMSS) (Time range: through ) Requested ship time. FST C ID 2/2 Not FST Reference Number C AN 1/30 Not AN 7/7 03/10/2017 V/R CHRY 21 FCA US

23 FCA US - Shipping Schedule Segment: DTM Date/Time/Period Position: 100 Loop: FST Optional Level: Detail Usage: Optional Max Use: Purpose: To specify pertinent dates and times Syntax Notes: 1 At least one of DTM02 or DTM03 is required. Semantic Notes: Comments: Notes: For Common SDS, the segment will be used for delivery date and time when only one shipment for the day. Example: DTM~002~930730~0930~CT Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes DTM Date/Time Qualifier M ID 3/3 M Code specifying type of date or time, or both date and time 002 Delivery Requested DTM Date C DT 6/6 Date (YYMMDD) Date qualified by DTM01. DTM Time C TM 4/4 Time expressed in 24-hour clock time (HHMMSS) (Time range: through ) DTM Time Code O ID 2/2 Code identifying the time. CD Central Daylight Time CT Central Time 03/10/2017 V/R CHRY 22 FCA US

24 FCA US - Shipping Schedule Segment: JIT Just-In-Time Schedule Position: 120 Loop: JIT Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To identify the specific shipping/delivery time in terms of a 24-hour clock and the associated quantity. Syntax Notes: Semantic Notes: Comments: Notes: The JIT loop is used when there are more than one shipment for the day specified in the FST. All times are Eastern Time. by Metered Parts Kanban. Not used by (traditional) Kanban. Example: JIT~100~0800 Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes JIT Quantity M R 1/10 M Numeric value of quantity Quantity to be shipped. JIT Time M TM 4/4 M Time expressed in 24-hour clock time (HHMMSS) (Time range: through ) Time of Shipment in 24 hour clock (HHMM). 03/10/2017 V/R CHRY 23 FCA US

25 FCA US - Shipping Schedule Segment: DTM Date/Time/Period Position: 135 Loop: JIT Optional Level: Detail Usage: Optional Max Use: Purpose: To specify pertinent dates and times Syntax Notes: 1 At least one of DTM02 or DTM03 is required. Semantic Notes: Comments: Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes DTM Date/Time Qualifier M ID 3/3 M Code specifying type of date or time, or both date and time 002 Delivery Requested DTM Date C DT 6/6 Date (YYMMDD) DTM Time C TM 4/4 Time expressed in 24-hour clock time (HHMMSS) (Time range: through ) DTM Time Code O ID 2/2 Code identifying the time. 03/10/2017 V/R CHRY 24 FCA US

26 FCA US - Shipping Schedule Segment: ATH Resource Authorization Position: 140 Loop: LIN Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To specify resource authorizations (i.e., finished labor, material, etc.) in the planning schedule Syntax Notes: 1 At least one of ATH02 or ATH03 is required. 2 If ATH03 is present, then ATH05 is required. 3 If ATH04 is present, then ATH05 is required. Semantic Notes: Comments: 1 It is imperative that negotiations defining financial commitment have previously occurred and are agreed to by both buyer and seller. 2 ATH02 - Resource Authorization Thru-Date: The date through which the buyer authorizes the seller to commit the resource defined in element ATH01. 3 ATH03 - Current Cumulative Requirements Quantity: The cumulative quantity that has been authorized to-date from the cumulative start-date (ATH05) through the resource authorization thru-date (ATH02). 4 ATH04 - Maximum Cumulative Requirements Quantity: The maximum cumulative quantity that has been authorized to-date from the cumulative start -date (ATH05) through the resource authorization thru-date (ATH02). This is a high water mark. If the forecast decreases, the current cumulative requirements quantity also decreases, but the maximum cumulative requirements quantity does not decrease. 5 ATH05 - Cumulative Start-Date: The date where the cumulative quantity count starts. This date might be the start-date of a contract period, a calendar or fiscal year, or other. Notes: The quantity fields in this segment are always cumulative quantities. Not used by KANBAN. Example: ATH~PQ~910303~13186~~ Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes ATH Resource Authorization Code M ID 2/2 M Code identifying the resource which the buyer is authorizing the seller to commit to PQ Cumulative Quantity Required Prior to First Schedule Period ATH Date C DT 6/6 Date (YYMMDD) This is the day prior to the thirty calendar day forecast. ATH Quantity C R 1/10 Numeric value of quantity 03/10/2017 V/R CHRY 25 FCA US

27 FCA US - Shipping Schedule This is the cum quantity that has been authorized from the start date (ATH05) through the end date (ATH02). This is a signed field. ATH Quantity O R 1/10 Not ATH Date C DT 6/6 Date (YYMMDD) CUM start date. 03/10/2017 V/R CHRY 26 FCA US

28 FCA US - Shipping Schedule Segment: SHP Shipped/Received Information Position: 150 Loop: SHP Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To specify shipment and/or receipt information Syntax Notes: 1 If SHP01 is present, then SHP02 is required. 2 If SHP03 is present, then SHP04 is required. Semantic Notes: Comments: 1 The SHP segment is used to communicate shipment, delivery, or receipt information and may include discrete or cumulative quantities, dates, and times. 2 If SHP01 = "02", "07", "08", "09", or "10" (indicating cumulative quantities), then SHP04 and SHP06 are required to identify the start and end dates of the quantity count. 3 SHP04 - The date shipped, delivered, received, or the cumulative quantity start date (as qualified by SHP03). 4 SHP06 - The cumulative quantity end date. Notes: This segment is used to give information on either the last shipment shipped or the cumulative quantity shipped to date. Not used by KANBAN. Examples: SHP~01~856~011~ SHP~02~13251~051~900715~~ Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes SHP Quantity Qualifier O ID 2/2 Code specifying the type of quantity 01 Discrete Quantity (i. e., CHAMPS last shipped quantity) 02 Cumulative Quantity (i. e., CHAMPS YTD shipped quantity) SHP Quantity C R 1/10 Numeric value of quantity For SHP01. This is a signed field. SHP Date/Time Qualifier O ID 3/3 Code specifying type of date or time, or both date and time If SHP01 = '01', use '011'; If SHP01 = '02', use '051'. 03/10/2017 V/R CHRY 27 FCA US

29 FCA US - Shipping Schedule 011 Shipped 051 Cumulative Quantity Start SHP Date C DT 6/6 Date (YYMMDD) If SHP01 = '01', this is supplier's 'Last Ship Date' from CHAMPS; If SHP01 = '02', this is the 'Beginning Inventory Date' (Same as ATH05). SHP Time O TM 4/4 Not SHP Date C DT 6/6 Date (YYMMDD) if SHP01 = '02' for the 'Last Supplier Ship Date'. SHP Time O TM 4/4 Not 03/10/2017 V/R CHRY 28 FCA US

30 FCA US - Shipping Schedule Segment: TD5 Carrier Details (Routing Sequence/Transit Time) Position: 175 Loop: LIN Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To specify the carrier and sequence of routing and provide transit time information Syntax Notes: 1 At least one of TD502 TD504 or TD505 is required. 2 If TD502 is present, then TD503 is required. 3 If TD507 is present, then TD508 is required. 4 If TD510 is present, then TD511 is required. Semantic Notes: Comments: 1 When specifying a routing sequence to be used for the shipment movement in lieu of specifying each carrier within the movement, use TD502 to identify the party responsible for defining the routing sequence, and use TD503 to identify the actual routing sequence, specified by the party identified in TD502. Notes: The data contained in the TD5 segment is information for carrier use when shipping to FCA. Not used by KANBAN. Examples: TD5~~~~M~~~~~~SH~0006 TD5~~~~GR~~~~~~SH~0012 Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes TD Routing Sequence Code O ID 1/2 Not TD Identification Code Qualifier C ID 1/2 Not TD Identification Code C ID 2/17 Not TD Transportation Method/Type Code C ID 1/2 Code specifying the method or type of transportation for the shipment * Pending Data Maintenance request at ANSI ASC X12, code values not assigned. AC Air Charter AE Air Express D Parcel Post DD Dedicated Delivery Service * E Expedited Truck GG Geographic Shipping/Receiving * GR Geographic Receiving * 03/10/2017 V/R CHRY 29 FCA US

31 FCA US - Shipping Schedule GS Geographic Shipping * I LT M O Common Irregular Carrier Less Than Trailer Load (LTL) Motor (Common Carrier) Containerized Ocean PD Parcel Delivery * RR Roadrailer * U VE X Private Parcel Service (UPS) Vessel, Ocean Intermodal (Piggyback) (TOFC/CO-FC) TD Routing C AN 1/35 Not TD Shipment/Order Status Code O ID 2/2 Not TD Location Qualifier O ID 1/2 Not TD Location Identifier C AN 1/25 Not TD Transit Direction Code O ID 2/2 Not TD Transit Time Direction Qualifier O ID 2/2 Code specifying the value of time used to measure the transit time SH Surface Hours TD Transit Time C R 1/4 R 4/4 The numeric amount of transit time Integer number of intransit hours (no decimals). 03/10/2017 V/R CHRY 30 FCA US

32 FCA US - Shipping Schedule Segment: CTT Transaction Totals Position: 010 Loop: Level: Summary Usage: Mandatory Max Use: 1 Purpose: To transmit a hash total for a specific element in the transaction set Syntax Notes: 1 If CTT03 is present, then CTT04 is required. 2 If CTT05 is present, then CTT06 is required. Semantic Notes: Comments: 1 This segment is intended to provide hash totals to validate transaction completeness and correctness. Notes: This segment is mandatory and allows the receiver to perform checks for completeness and correctness of this transaction set. Example: CTT~10~ Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes CTT Number of Line Items M N0 1/6 M N0 1/4 Total number of line items in the transaction set Total Number of 'LIN' segments. CTT Hash Total O R 1/10 Sum of values of the specified data element. All values in the data element will be summed without regard to decimal points (explicit or implicit) or signs. Truncation will occur on the left most digits if the sum is greater than the maximum size of the hash total of the data element. Example: First occurrence of value being hashed..18 Second occurrence of value being hashed. 1.8 Third occurrence of value being hashed Fourth occurrence of value being hashed Hash total prior to truncation. 855 Hash total after truncation to three-digit field. The Hash Total of all quantities released (FST01). CTT03 81 Weight O R 1/8 Not CTT Unit or Basis for Measurement Code C ID 2/2 Not CTT Volume O R 1/8 Not CTT Unit or Basis for Measurement Code C ID 2/2 Not 03/10/2017 V/R CHRY 31 FCA US

33 FCA US - Shipping Schedule CTT Description O AN 1/80 Not 03/10/2017 V/R CHRY 32 FCA US

34 FCA US - Shipping Schedule Segment: SE Transaction Set Trailer Position: 020 Loop: Level: Summary Usage: Mandatory Max Use: 1 Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments). Syntax Notes: Semantic Notes: Comments: 1 SE is the last segment of each transaction set. Notes: The transaction set control number value in this trailer must match the same element value in the transaction set header (ST02). Example: SE~372~ Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes SE01 96 Number of Included Segments M N0 1/6 M Total number of segments included in a transaction set including ST and SE segments The count of all segments in this transaction set including the 'ST' and 'SE' segments. SE Transaction Set Control Number M AN 4/9 M Identifying control number assigned by the originator for a transaction set. Same as ST02. 03/10/2017 V/R CHRY 33 FCA US

35 Example 1: Just In Time Shipping Schedule ST~862~0001 Transaction Set Identifier Code = 862 (X12.37 Shipping Schedule) Transaction Set Control Number = 0001 BSS~05~ ~110603~SH~110603~110702~~ Transaction Set Purpose Code = 05 (Replace) Reference Number = Date = 06/03/2011 Schedule Type Qualifier = SH (Shipment Based) Date = 06/03/2011 Date = 07/02/2011 Reference Number = N1~SI~~92~04000 N1~SU~~92~10167AA N1~ST~~92~09106 LIN~~BP~ AA UIT~EA NTE~LIN~T PER~EX~DON LAWES~TE~ REF~DK~MAIN Entity Identifier Code = SI (Shipping Schedule Issuer) Identification Code Qualifier = 92 (Assigned by Buyer) Identification Code = Entity Identifier Code = SU (Supplier/Manufacturer) Identification Code Qualifier = 92 (Assigned by Buyer) Identification Code = 10167AA Entity Identifier Code = ST (Ship To) Identification Code Qualifier = 92 (Assigned by Buyer) Identification Code = = BP (Buyer's Part Number) Product/Service ID = AA Unit or Basis for Measurement Code = EA (Each) Note Reference Code = LIN (Line Item) T = (Part In Test Mode) Contact Function Code = EX (Expeditor) Name = DON LAWES Communication Number Qualifier = TE (Telephone) Communication Number = = DK (Dock Number) Reference Number = MAIN 03/10/2017 V/R CHRY 34 FCA US

36 Example 1: Just In Time Shipping Schedule (continued) FST~100~C~D~110603~~010~0800 Quantity = 100 Date = 06/03/2011 Time = 8:00 AM FST~100~C~D~110604~~010~0800 Quantity = 100 Date = 06/04/2011 Time = 8:00 AM FST~200~C~D~ Quantity = 200 Date = 06/05/2011 JIT~100~0800 Quantity = 100 Time = 8:00 AM JIT~100~1100 Quantity = 100 Time = 11:00 AM FST~100~C~D~110606~~010~1100 Quantity = 100 Date = 06/06/2011 Time = 11:00 AM FST~100~C~D~110607~~010~0800 Quantity = 100 Date = 06/07/2011 Time = 8:00 AM FST~100~C~D~110610~~010~0800 Quantity = 100 Date = 06/10/2011 Time = 8:00 AM FST~250~C~D~110613~~010~0800 Quantity = 250 Date = 06/13/2011 Time = 8:00 AM 03/10/2017 V/R CHRY 35 FCA US

37 Example 1: Just In Time Shipping Schedule (continued) FST~100~C~D~110614~~010~1000 Quantity = 100 Date = 06/14/2011 Time = 10:00 AM FST~275~C~D~110617~~010~0900 Quantity = 275 Date = 06/17/2011 Time = 9:00 AM FST~100~C~D~110618~~010~0900 Quantity = 100 Date = 06/18/2011 Time = 9:00 AM FST~100~C~D~110619~~010~0900 Quantity = 100 Date = 06/19/2011 Time = 9:00 AM FST~100~C~D~110620~~010~0900 Quantity = 100 Date = 06/20/2011 Time = 9:00 AM FST~200~C~D~110701~~010~0800 Quantity = 200 Date = 07/01/2011 Time = 8:00 AM ATH~PQ~110602~13200~~ Resource Authorization Code = PQ (Cumulative Quantity Required Prior to First Schedule Period) Date = 06/02/2011 Quantity = Date = 07/15/ /10/2017 V/R CHRY 36 FCA US

38 Example 1: Just In Time Shipping Schedule (continued) SHP~01~100~011~ SHP~02~13251~051~100715~~ Quantity Qualifier = 01 (Discrete Quantity) Quantity = 100 Date/Time Qualifier = 011 (Shipped) Date = 06/02/2011 Quantity Qualifier = 02 (Cumulative Quantity) Quantity = 1810 Date/Time Qualifier = 051 (Cumulative Quantity Start) Date = 07/15/2010 Date = 06/02/2011 CTT~1~1825 Number of Line Items = 1 Hash Total = 1825 SE~30~0001 Number of Included Segments = 30 Transaction Set Control Number = /10/2017 V/R CHRY 37 FCA US

39 Example 2: Kanban ST~862~0002 Transaction Set Identifier Code = 862 (X12.37 Shipping Schedule) Transaction Set Control Number = 0002 BSS~05~080701~080701~KB~080701~080701~~ Transaction Set Purpose Code = 05 (Replace) Reference Number = Date = 07/01/2008 Schedule Type Qualifier = KB (Kanban Signal) Date = 07/01/2008 Date = 07/01/2008 Reference Number = N1~SI~~92~04000KB N1~SU~~92~38303 N1~ST~~92~05207 Entity Identifier Code = SI (Shipping Schedule Issuer) Identification Code Qualifier = 92 (Assigned by Buyer) Identification Code = 04000KB Entity Identifier Code = SU (Supplier/Manufacturer) Identification Code Qualifier = 92 (Assigned by Buyer) Identification Code = Entity Identifier Code = ST (Ship To) Identification Code Qualifier = 92 (Assigned by Buyer) Identification Code = LIN~~BP~0QT41CA1AA~JN~ ~JS~ = BP (Buyer's Part Number) Product/Service ID = 0QT41CA1AA = JN (Job Number) Product/Service ID = = JS (Job Sequence Number) Product/Service ID = UIT~EA REF~DK~A05B6 Unit or Basis for Measurement Code = EA (Each) = DK (Dock Number) Reference Number = A05B6 FST~215~C~D~ Quantity = 215 Date = 03/13/ /10/2017 V/R CHRY 38 FCA US

40 Example 2: Kanban (continued) LIN~~BP~ AB~JN~ ~JS~ = BP (Buyer's Part Number) Product/Service ID = AB = JN (Job Number) Product/Service ID = = JS (Job Sequence Number) Product/Service ID = UIT~EA REF~DK~F45C3 Unit or Basis for Measurement Code = EA (Each) = DK (Dock Number) Reference Number = F45C3 FST~1000~C~D~ Quantity = 1000 Date = 03/13/2008 LIN~~BP~ AB~JN~ ~JS~ = BP (Buyer's Part Number) Product/Service ID = AB = JN (Job Number) Product/Service ID = = JS (Job Sequence Number) Product/Service ID = UIT~EA REF~DK~F46D4 Unit or Basis for Measurement Code = EA (Each) = DK (Dock Number) Reference Number = F46D4 FST~300~C~D~ Quantity = 300 Date = 03/13/ /10/2017 V/R CHRY 39 FCA US

41 Example 2: Kanban (continued) LIN~~BP~ AB~JN~ ~JS~ = BP (Buyer's Part Number) Product/Service ID = AB = JN (Job Number) Product/Service ID = = JS (Job Sequence Number) Product/Service ID = UIT~EA REF~DK~C75T7 Unit or Basis for Measurement Code = EA (Each) = DK (Dock Number) Reference Number = C75T7 FST~1000~C~D~ Quantity = 1000 Date = 03/13/2008 LIN~~BP~ ~JN~ ~JS~ = BP (Buyer's Part Number) Product/Service ID = = JN (Job Number) Product/Service ID = = JS (Job Sequence Number) Product/Service ID = UIT~EA REF~DK~C98G5 Unit or Basis for Measurement Code = EA (Each) = DK (Dock Number) Reference Number = C98G5 FST~5000~C~D~ Quantity = 5000 Date = 03/13/ /10/2017 V/R CHRY 40 FCA US

42 Example 2: Kanban (continued) LIN~~BP~ AA~JN~ ~JS~ = BP (Buyer's Part Number) Product/Service ID = AA = JN (Job Number) Product/Service ID = = JS (Job Sequence Number) Product/Service ID = UIT~EA REF~DK~A05B6 Unit or Basis for Measurement Code = EA (Each) = DK (Dock Number) Reference Number = A05B6 FST~100~C~D~ Quantity = 100 Date = 03/13/2008 LIN~~BP~ AA~JN~ ~JS~ = BP (Buyer's Part Number) Product/Service ID = AA = JN (Job Number) Product/Service ID = = JS (Job Sequence Number) Product/Service ID = UIT~EA REF~DK~A05B6 Unit or Basis for Measurement Code = EA (Each) = DK (Dock Number) Reference Number = A05B6 FST~800~C~D~ Quantity = 800 Date = 03/13/ /10/2017 V/R CHRY 41 FCA US

43 Example 2: Kanban (continued) LIN~~BP~ ~JN~ ~JS~ = BP (Buyer's Part Number) Product/Service ID = = JN (Job Number) Product/Service ID = = JS (Job Sequence Number) Product/Service ID = UIT~EA REF~DK~A05B6 Unit or Basis for Measurement Code = EA (Each) = DK (Dock Number) Reference Number = A05B6 FST~700~C~D~ Quantity = 700 Date = 03/13/2008 LIN~~BP~0RB261X9AB~JN~ ~JS~ = BP (Buyer's Part Number) Product/Service ID = 0RB261X9AB = JN (Job Number) Product/Service ID = = JS (Job Sequence Number) Product/Service ID = UIT~EA REF~DK~A05B6 Unit or Basis for Measurement Code = EA (Each) = DK (Dock Number) Reference Number = A05B6 FST~600~C~D~ Quantity = 600 Date = 03/13/ /10/2017 V/R CHRY 42 FCA US

44 Example 2: Kanban (continued) LIN~~BP~0RB221X9AB~JN~ ~JS~ = BP (Buyer's Part Number) Product/Service ID = 0RB221X9AB = JN (Job Number) Product/Service ID = = JS (Job Sequence Number) Product/Service ID = UIT~EA REF~DK~A05B6 Unit or Basis for Measurement Code = EA (Each) = DK (Dock Number) Reference Number = A05B6 FST~500~C~D~ Quantity = 500 Date = 03/13/2008 LIN~~BP~0QQ06DX9AA~JN~ ~JS~ = BP (Buyer's Part Number) Product/Service ID = 0QQ06DX9AA = JN (Job Number) Product/Service ID = = JS (Job Sequence Number) Product/Service ID = UIT~EA REF~DK~A05B6 Unit or Basis for Measurement Code = EA (Each) = DK (Dock Number) Reference Number = A05B6 FST~215~C~D~ Quantity = 215 Date = 03/13/2008 CTT~11~10430 Number of Line Items = 11 Hash Total = SE~51~0002 Number of Included Segments = 51 Transaction Set Control Number = /10/2017 V/R CHRY 43 FCA US

45 Example 3: ST~862~0003 Common Ship & Delivery Schedule (CSDS) Transaction Set Identifier Code = 862 (X12.37 Shipping Schedule) Transaction Set Control Number = 0003 BSS~05~ ~101009~SH~101009~101121~~ Transaction Set Purpose Code = 05 (Replace) Reference Number = Date = 10/09/2010 Schedule Type Qualifier = SH (Shipment Based) Date = 10/09/2010 Date = 11/21/2010 Reference Number = N1~SI~~92~04000 N1~SU~~92~05203 N1~ST~~92~04088 LIN~~BP~ AB UIT~EA Entity Identifier Code = SI (Shipping Schedule Issuer) Identification Code Qualifier = 92 (Assigned by Buyer) Identification Code = Entity Identifier Code = SU (Supplier/Manufacturer) Identification Code Qualifier = 92 (Assigned by Buyer) Identification Code = Entity Identifier Code = ST (Ship To) Identification Code Qualifier = 92 (Assigned by Buyer) Identification Code = = BP (Buyer's Part Number) Product/Service ID = AB Unit or Basis for Measurement Code = EA (Each) PER~EX~LOCAL CONTROL CONTA~TE~ Contact Function Code = EX (Expeditor) Name = LOCAL CONTROL CONTA Communication Number Qualifier = TE (Telephone) Communication Number = REF~DK~T4 REF~RL~B16S = DK (Dock Number) Reference Number = T4 = RL (Reserve Assembly Line Feed Location) Reference Number = B16S 03/10/2017 V/R CHRY 44 FCA US

46 Example 3: Common Ship & Delivery Schedule (CSDS) (continued) N1~ST~~92~04088A Entity Identifier Code = ST (Ship To) Identification Code Qualifier = 92 (Assigned by Buyer) Identification Code = 04088A FST~104~C~D~ Quantity = 104 Date = 10/09/2010 JIT~28~1100 Quantity = 28 Time = 11:00 AM DTM~002~101010~1000 Date/Time Qualifier = 002 (Delivery Requested) Date = 10/10/2010 Time = 10:00 AM JIT~20~1400 Quantity = 20 Time = 2:00 PM DTM~002~101010~1300 Date/Time Qualifier = 002 (Delivery Requested) Date = 10/10/2010 Time = 1:00 PM JIT~28~1700 Quantity = 28 Time = 5:00 PM DTM~002~101010~1600 Date/Time Qualifier = 002 (Delivery Requested) Date = 10/10/2010 Time = 4:00 PM JIT~4~2000 Quantity = 4 Time = 8:00 PM DTM~002~101010~1900 Date/Time Qualifier = 002 (Delivery Requested) Date = 10/10/2010 Time = 7:00 PM JIT~24~2300 Quantity = 24 Time = 11:00 PM DTM~002~101010~2200 Date/Time Qualifier = 002 (Delivery Requested) Date = 10/10/2010 Time = 10:00 PM 03/10/2017 V/R CHRY 45 FCA US