WIXLIB

Outbound 315 Status Details (Ocean)315 Status Details (Ocean) – OutboundFunctional Group ID QOIntroduction:This Standard contains the format and establishes the data contents of the Outbound Status Details (Ocean) Transaction Set (315) foruse within the context of the GT Nexus Electronic Data Interchange (EDI) environment. This transaction set can be used to receiveall of the status and event information for shipments and/or containers.Pos.No. Seg. IDISAGS010 ST020 B4030 N9040 Q2NameInterchange Control HeaderFunctional Group HeaderTransaction Set HeaderBeginning Segment for Inquiry or ReplyReference IdentificationStatus Details x Use1111301LOOP ID - R4Port or TerminalDate/Time ReferenceMO115Transaction Set TrailerFunctional Group TrailerInterchange Control TrailerMMM111RepeatComments6Appendices:Appendix A - Shipment Status Code (B403)Appendix B – Equipment Status Code (B409)Appendix C – Port or Terminal Function Code (R401)Appendix D - GT Nexus Events & Corresponding Outbound ValuesProprietary & ConfidentialPage 1 of 209/24/2014, 16:09 A9/P9

Outbound 315 Status Details (Ocean)Document 012CHANGES MADEClarified that the R4 loop can repeat a maximum of 5 timesAdded N901 reference number qualifiers of SI, FN, CG, PO, and 7UAdded Appendices, sample segments and message.Added Booking and Document Event List to Appendices.- Added the comment that the B408 could be either 6 or 7 characters in length depending onwhether or not the check digit is provided by the carrier.- Added Status Code ‘PQ’ (Customs Hold at Port of Discharge) and ‘VA’ (Vessel Arrived atTransship Point)- Removed “Appendix E – GT Nexus Booking & Documentation Event List”; no longersupported within Outbound 315.- Changed B411 data element from Mandatory to Conditional (if B412 is present).- Added DTM support within R4 Loop.- Added Status Code ‘CO’ (Full Container Received at Place of Receipt) and ‘RL’ (RailDeparted).Added Event ID 60, Status Code ‘E’, “Estimated Arrival at Inland or Interim Point”.Added Event ID 61, Status Code ‘C’, “Estimated Departure from Inland or Interim Point”.Changed R403 (310) data element from Mandatory to Conditional to match EDI Standard andactual transaction data output.Updated the sample 315 message, and clarified how events associated with an Interim Point areonly supported within the B4 segment (not R4).Added N901 support of ‘PO’, ‘SR’ and ‘SO’.- Added Event ID 53, Status Code ‘PA’, “Customs Hold at Port of Load”.- Added Event ID 62, Status Code ‘C1’, “Canada Customs Hold”.- Added Event ID 63, Status Code ‘HG’, “Held on Ground”.- Added Event ID 64, Status Code ‘HR’, “Hold Released”.Added R401 support of ‘I’ (Interim Point); updated Appendices, sample segments and message.Added B410 support of the Equipment Type Code, including a Comment (#5) that its’ presenceis based upon customer preference.Added N901 support of ‘CR’.Added Event ID 77, Status Code ‘AG’, “Shipment Delayed”.- Updated Sample Outbound 315 Message.- Added N901 support of ‘EV’ (GT Nexus Event Type Code), including Comment (#3), that its’presence is based upon customer preference.Added R401 support of ‘Y’ or ‘T’ (Transshipment Port)Clarified Appendix C Port or Terminal Function Code (R401) description for I, Y, T.Updated R4 repeat from 5 to 6 (R,L,D,E,Y or T, I).Clarified the presence of either N901 of ‘BN’ (Booking Number) or N901 of ‘BM’ (Bill ofLading Number), along with the N902 value, will be provided within each Outbound 315message.- Added Event ID 73, Status Code ‘VD’, “Feeder Vessel Depart”.- Added Event ID 75, Status Code ‘AE’, “On-Board Feeder Vessel”.- Added Event ID 76, Status Code ‘UV’, “Discharged from Feeder Vessel”.- Added Event ID 84, Status Code ‘FT’, “Free Time Expired”.Set R401 value for Customs Hold at Port of Discharge to ‘D’ (Appendix D).Added N901 Reference Qualifier of P8 (Pickup reference Number)Proprietary & ConfidentialPage 2 of 209/24/2014, 16:09 A9/P9

Outbound 315 Status Details (Ocean)Proprietary & ConfidentialPage 3 of 209/24/2014, 16:09 A9/P9

Outbound 315 Status Details (Ocean)Segment:Position:Loop:Level:Usage:Max Use:Purpose:ISA Interchange Control HeaderNAMandatory1To start and identify an interchange of zero or more functional groups and interchange-related controlsegments.Syntax Notes:Semantic A05MISA06MISA07MISA08MISA09Data Element SummaryDataElement NameAttributesI01Authorization Information QualifierM ID 2/2Code to identify the type of information in the Authorization Information dataelementSet to '00' – No Authorization information presentI02Authorization InformationM AN 10/10Information used for additional identification or authorization of theinterchange sender or the data in the interchange; the type of information is setby the Authorization Information Qualifier (I01)Set to 10 empty spacesI03Security Information QualifierM ID 2/2Code to identify the type of information in the Security InformationSet to '00' – No Security information presentI04Security InformationM AN 10/10This is used for identifying the security information about the interchangesender or the data in the interchange; the type of information is set by theSecurity Information Qualifier (I03)Set to 10 empty spacesI05Interchange ID QualifierM ID 2/2Qualifier to designate the system/method of code structure used to designatethe sender or receiver ID element being qualifiedSet to 'ZZ' – Mutually definedI06Interchange Sender IDM AN 15/15Identification code published by the sender for other parties to use as thereceiver ID to route data to them; the sender always codes this value in thesender ID elementSet to ‘GTNEXUS’ with 8 trailing spacesI05Interchange ID QualifierM ID 2/2Qualifier to designate the system/method of code structure used to designatethe sender or receiver ID element being qualifiedSet to 'ZZ' – Mutually definedI07Interchange Receiver IDM AN 15/15Identification code published by the receiver of the data; When sending, it isused by the sender as their sending ID, thus other parties sending to them willuse this as a receiving ID to route data to themSet to Receiver ID with empty spaces to fill 15 charactersI08Interchange DateM DT 6/6Proprietary & ConfidentialPage 4 of 209/24/2014, 16:09 A9/P9

Outbound 315 Status Details 13MISA15I14MISA16I15Date of the interchange (local time – PST)Interchange TimeM TM 4/4Time of the interchange (local time – PST)Interchange Control Standards IdentifierM ID 1/1Code to identify the agency responsible for the control standard used by themessage that is enclosed by the interchange header and trailerSet to 'U' – U.S. EDI Community of ASC X12, TDCC and UCSInterchange Control Version NumberM ID 5/5This version number covers the interchange control segmentsSet to '00401' – Draft Standards approved for publication by ASC X12Interchange Control NumberM N0 9/9A control number assigned by the interchange senderAcknowledgment RequestedM ID 1/1Code sent by the sender to request an interchange acknowledgment (TA1)Set to '0' – No Acknowledgement requestedUsage IndicatorM ID 1/1Code to indicate whether data enclosed by this interchange envelope is test,production or informationSet to 'T' – Test or ‘P’ – Production (mutually agreed upon per integrationstatus)Component Element SeparatorM AN 1/1Type is not applicable; the component element separator is a delimiter and nota data element. This field provides the delimiter used to separate componentdata elements within a composite data structure. This value must be differentthan the data element separator and the segment terminator.Set to ' 'Sample Segment:ISA*00**00**ZZ*GTNEXUSProprietary & 000001*0*T* Page 5 of 209/24/2014, 16:09 A9/P9

Outbound 315 Status Details (Ocean)Segment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic S06MGS07MGS08GS Functional Group HeaderNAMandatory1To indicate the beginning of a functional group (see Comments section) and to provide controlinformation1231GS04 is the group date.GS05 is the group time.The data interchange control number GS06 in this header will always be identical to the same dataelement in the associated functional group trailer, GE02.A functional group of related transaction sets, within the scope of X12 standards, consists of acollection of similar transaction sets enclosed by a functional group header and a functional grouptrailer.Data Element SummaryDataElement NameAttributes479Functional Identifier CodeM ID 2/2Code identifying a group of application related transaction setsSet to 'QO' – Ocean Shipment Status Information (313, 315)142Application Sender's CodeM AN 2/15Code identifying party sending transmission; codes agreed to by tradingpartnersSet to ‘GTNEXUS’124Application Receiver's CodeM AN 2/15Code identifying party receiving transmission; codes agreed to by tradingpartnersSet to DNB Code 373DateM DT 8/8Date expressed as CCYYMMDD (local time – PST)337TimeM TM 4/8Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, orHHMMSSD, or HHMMSSDD (local time – PST)28Group Control NumberM N0 1/9Assigned number originated and maintained by the sender455Responsible Agency CodeM ID 1/2Code used in conjunction with Data Element 480 to identify the issuer of thestandardSet to 'X' – Accredited Standards Committee X12480Version / Release / Industry Identifier CodeM AN 1/12Code indicating the version, release, sub-release, and industry identifier of theEDI standard being used.Set to '004010'Sample *1*X*004010 Proprietary & ConfidentialPage 6 of 209/24/2014, 16:09 A9/P9

Outbound 315 Status Details (Ocean)Segment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:ST Transaction Set Header010Mandatory1To indicate the start of a transaction set and to assign a control number1The transaction set identifier (ST01) is used by the translation routines of the interchange partners toselect the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).Comments:MRef.Des.ST01MST02Data Element SummaryDataElement NameAttributes143Transaction Set Identifier CodeM ID 3/3Code uniquely identifying a Transaction SetSet to '315'329Transaction Set Control NumberM AN 4/9Identifying control number that must be unique within the transaction setfunctional group assigned by the originator for a transaction setSample Segment:ST*315*0001 Proprietary & ConfidentialPage 7 of 209/24/2014, 16:09 A9/P9