Transcription

BNSF-EDI 322 TransactionBNSF 322 Implementation GuidelineELECTRONIC DATA INTERCHANGE (EDI)322TERMINAL OPERATIONS AND INTERMODALRAMP ACTIVITYUSINGASC X12 TRANSACTION SET 322VERSION 00401007/01/04

BNSF-EDI 322 Transaction2BNSF 322 Implementation GuidelineTable of ContentsIntroduction. 3Sample 322. 4The Transaction. 5Data Element Type. 5Date Element Requirement Designator . 5Data Element Length . 5ISAInterchange Control Header. 6GSFunctional Group Header . 7STTransaction Set Header. 8ZC1Beginning Segment For Data Correction Or Change. 9Q5Status Details . 10N7Equipment Details (N7 Loop). 12V4Cargo Location Reference . 13DTM Date/Time Reference. 14M7Seal Numbers. 15W09Equipment and Temperature . 16W2Equipment Identification . 17NACross-Reference Equipment . 18GR5Loading Details. 19Y7Priority . 20V1Vessel Information . 21R4Port or Terminal (N7/R4 Loop) . 22DTM Date/Time Reference. 23H3Special Handling Instructions. 24N1Name (N7/N1 Loop) . 25N3Address . 26N4Geographic Location . 27K1Remarks . 28N9Reference Information. 29L0Line Item, Quantity, and Weight (N7/L0 Loop) . 30L5Description, Marks, and Numbers. 31H1Hazardous Material. 32L3Total Weight and Charges . 33STTransaction Set Trailer . 34GEFunctional Group Trailer . 35IEAInterchange Control Trailer . 36

BNSF-EDI 322 Transaction3BNSF 322 Implementation GuidelineIntroductionTransaction Set 322: Terminal Operations and Intermodal Ramp ActivityFunctional Group:SOThis transaction set contains the format and establishes the data contents of the TerminalOperations and Intermodal Ramp Activity Transaction Set (322) for use within thecontext of an Electronic Data Interchange (EDI) environment. The transaction set can beused to provide all the information necessary for a railroad, terminal operation, portauthority, or Intermodal ramp to communicate rail events (e.g. arrivals, departures), aswell as terminal and Intermodal ramp activities (e.g., “ingates” or “outgates”), toauthorized parties to a shipment.Burlington Northern Santa Fe will transmit and accept the Terminal Operations andIntermodal Ramp Activity transaction published by Data Interchange StandardsAssociation (DISA) for ASC X12. The following guidelines are all-inclusive andidentify unique requirements for use of the ASC X12 322 transaction set whentransmitting data to, and receiving data from, Burlington Northern Santa Fe.To obtain X12 standards and documentation, contact:Data Interchange Standards Association, Inc.7600 Leesburg Pike, Suite 430Falls Church, VA 22043Phone: 703-970-4480Fax: 703-970-4488Web: http://www.disa.org/Or:Washington Publishing Co.5740 Industry Lane – 2nd FloorFrederick, MD 21704Phone: 301-696-0050Fax: 301-696-0024Web: http://www.wpc-edi.com/

BNSF-EDI 322 Transaction4BNSF 322 Implementation GuidelineSample N*ABC1234SE*18*1001

BNSF-EDI 322 Transaction5BNSF 322 Implementation GuidelineThe TransactionThe transaction set is used to describe the electronic transmission of a single documentbetween one company’s computer and another company’s computer.EDI transactions are defined by segments, and each item within the segment becomes adata element. Data element type, requirement designator, and length are described below.These identifiers are listed for each data element throughout the remainder of this guide.Data Element TypeSpecifies the characters that may be TimeN indicates that it is numeric; n indicates a decimal place.R indicates an optional decimal point for integer values or arequired decimal for decimal values. BNSF can acceptpositive and decimal values.A specific code taken from a table defined in the DataElement Dictionary, such as unit of measure.A series of alpha/numeric characters.YYYMMDD (ISO standard date).HHMM expressed in a 24-hr clock format.Date Element Requirement DesignatorIndicates when this element must be included in an electronic document.MCMandatoryConditionalOOptionalThe data element must be used in the segment.The data element may be required in the segment, based onwhether another element is used.The data element may or may not be used in the segment atthe option of the user.Data Element LengthThe minimum and maximum length of the characters in the data element.1/15Indicates the “1” is the minimum acceptable value and “15”is the maximum acceptable value.

BNSF-EDI 322 Transaction6BNSF 322 Implementation GuidelineSEGMENT ISA – Interchange Control HeaderMANDATORYMaximum User: 231*0034*U*00401*123456789*1*P * on QualifierAuthorizationInformationSecurity InformationQualifierSecurity InformationInterchange SenderID QualifierInterchange Sender IDInterchange ReceiverID QualifierInterchange ReceiverIDInterchange DateInterchange TimeInterchange ControlStandards IdentifierInterchange ControlVersion NumberInterchange ControlNumberAcknowledgementRequestedUsage IndicatorComponent ElementSeparatorData Element #/ TypeI01 / IDMin/MaxREQContents02 / 02MI02 / AN10 / 10MI03 / ID02 / 02M00I04 / ANI05 / ID10 / 1002 / 02MMSender’s ID qualifierI06 / ANI05 / ID15 / 1502 / 02MMSender’s IDReceiver’s ID qualifierI07 / AN15 / 15MReceiver’s IDI08 / DTI09 / TMI10 / ID06 / 0604 / 0401 / 01MMMI11 / ID05 / 05MYYMMDDHHMMU US EDI Community of ASCX12, TDCC, and UCS00401 X12 version 4010I12 / N009 / 09MI13 / ID01 / 01MI14 / ID01 / 01MI15 /01 / 01M00Sender’s interchange controlnumber0 No acknowledgement needed1 Acknowledgement requestedP ProductionT TestBNSF uses a tilde “ “NOTE: Spaces must be used when the maximum length requirement is not met by the contents of thedata element. Spaces are shown above in the example ISA by periods ( . ). These are not part of the ISA,but used here to illustrate that spaces are required even if no data is supplied within the position. TheISA segment must be exactly 106 positions long, including the ISA, all delimiters and mandatory fields,plus a Hex 15 immediately following the ISA16 to indicate a carriage return/line feed.

BNSF-EDI 322 Transaction7BNSF 322 Implementation GuidelineSEGMENT GS – Functional Group HeaderMANDATORYMaximum Use: 001*X*004010#Name1Functional IdentifierCodeApplication SenderIDApplication ReceiverIDGroup DateGroup TimeGroup ControlNumberAgency CodeVersion2345678Data Element #/ Type479 / IDMin/MaxREQContents02 / 02MSO 322142 / AN02 / 15MSender’s ID124 / AN02 / 15MReceiver’s ID373 / DT337 / TM28 / N008 / 0804 / 0401 / 09MMMYYYYMMDD of transmissionHHMM of transmissionSender’s message control number455 / ID480 / AN01 / 0201 / 12MMX ASC X12004010 Sender’s transmissionstandard version.

BNSF-EDI 322 Transaction8BNSF 322 Implementation GuidelineSEGMENT ST – Transaction Set HeaderMANDATORYMaximum Use: 1 per transaction setExample:ST*322*10010001#12NameTransaction SetIdentifier CodeTransaction SetControl NumberData Element #/ Type143 / ID329 / ANMin/MaxREQContents03 / 03M32204 / 09MSender’s message control number

BNSF-EDI 322 Transaction9BNSF 322 Implementation GuidelineSEGMENT ZC1 – Beginning Segment For Data Correction Or ChangeOPTIONALMaximum Use: 1 per transaction setNOTE: THIS SEGMENT IS NOT USED BY BNSF#12345678NameShipment ID NumberEquipment InitialEquipment NumberTransactionReference NumberTransactionReference DateCorrection IndicatorStandard CarrierAlpha CodeTransport Type CodeData Element #/ Type145 / AN206 / AN207 / AN244 / ANMin/MaxREQ01 / 3001 / 0401 / 1001 / 15OOMM243 / DT08 / 08M202 / ID140 / ID02 / 0202 / 04MM91 / ID01 / 02MContents

BNSF-EDI 322 Transaction10BNSF 322 Implementation GuidelineSEGMENT Q5 – Status DetailsMANDATORYMaximum Use: 1 per transaction meData Element #/ Type157 / IDMin/MaxREQContents01 / 02O1Status Code234DateTimeTime Code373 / DT337 / TM623 / ID08 / 0804 / 0402 / 02OCC567Status Reason CodeCity NameState or ProvinceCodeCountry CodeEquipment InitialEquipment NumberReference NumberQualifierReference NumberDirection ID CodeReference NumberQualifierReference NumberDirection ID Code641 / ID19 / AN156 / ID03 / 0302 / 3002 / 02OCOA ArrivedB Bad orderG Released from bad orderI In gateJ Delivered to connecting lineP Departed terminal locationR Received from prior carrierAL Loaded on railAR Rail arrival at destinationNF Free time to expireNT NotificationOA Out gateRL Rail departure from originUR Unloaded from railYYYYMMDD of statusHHMM of statusAT AlaskanCT CentralET EasternLT LocalMT MountainNT NewfoundlandPT PacificTT AtlanticNot usedRail location for status updateState or Province for status update26 / ID206 / AN207 / AN128 / ID02 / 0301 / 0401 / 1002 / 03OOOCNot usedNot usedNot usedNot used127 / AN1280 / ID128 / ID01 / 3001 / 0102 / 03COCNot usedNot usedNot used127 / AN1280 / ID01 / 3001 / 01CONot usedNot used8910111213141516

BNSF-EDI 322 Transaction11BNSF 322 Implementation Guideline1718PercentPick-up DeliveryCode954 / R108 / ID01 / 1001 / 02OONot usedNot used

BNSF-EDI 322 Transaction12BNSF 322 Implementation GuidelineSEGMENT N7 – Equipment DetailsMANDATORYMaximum Use: 1 loop per transaction 4000***7****U203*BNSF#Name1234Equipment InitialEquipment NumberWeightWeight Qualifier56789Tare WeightWeight AllowanceDunnageVolumeVolume UnitQualifierOwnership CodeEquipmentDescription CodeStandard CarrierAlpha CodeTemperature ControlPositionEquipment LengthTare Qualifier CodeWeight Unit CodeEquipment CheckDigitType of Service CodeHeightWidthEquipment Type101112131415161718192021222324Standard CarrierAlpha CodeCar Type CodeData Element #/ Type206 / AN207 / AN81 / R187 / IDMin/MaxREQContents01 / 0401 / 0601 / 1001 / 02MMOC167 / N0232 / N0205 / N0183 / R184 / ID03 / 0802 / 0601 / 0601 / 0801 / 01COOCCEquipment’s identifying initialEquipment’s identifying numberNumeric value of the weightE Estimated weightG Gross weightN Net weightCE Certified weightNot usedNot usedNot usedNot usedNot used102 / ID40 / ID01 / 0102 / 02OO140 / ID02 / 04ONot usedCC Container on chassisCH ChassisCN ContainerRR RailcarTL TrailerSCAC319 / AN219 / AN567 / N0571 / ID188 / ID761 / N003 / 0601 / 0304 / 0501 / 0101 / 0101 / 01OOOCOONot usedNot usedFormat is feet/inches: 40 ft. 4000Not usedL PoundsCheck digit for equipment56 / ID65 / R189 / R24 / ID02 / 0201 / 0801 / 0804 / 04OOOO140 / ID02 / 04ONot usedNot usedNot usedCode identifying equipment’s ISOsize & typeSCAC301 / ID01 / 04ONot used

BNSF-EDI 322 Transaction13BNSF 322 Implementation GuidelineSEGMENT V4 – Cargo Location ReferenceOPTIONALMaximum Use: 1 per N7 loopNOTE: THIS SEGMENT IS NOT USED BY BNSF#1NameVessel StowageLocationData Element #/ Type877 / ANMin/MaxREQ01 / 12MContents

BNSF-EDI 322 Transaction14BNSF 322 Implementation GuidelineSEGMENT DTM – Date/Time ReferenceOPTIONALMaximum Use: 2 per N7 e Qualifier234DateTimeTime Code5Date/Time FormatQualifierDate/Time Period6Data Element #/ Type374 / IDMin/MaxREQ03 / 03M08 / 0804 / 0402 / 02CCC1250 / ID02 / 02O017 Estimated delivery069 Promised for deliveryYYYYMMDDHHMMAT AlaskanCT CentralET EasternLT LocalMT MountainNT NewfoundlandPT PacificTT AtlanticNot used1251 / AN01 / 35CNot used373 / DT337 / TM623 / IDContents

BNSF-EDI 322 Transaction15BNSF 322 Implementation GuidelineSEGMENT M7 – Seal NumbersOPTIONALMaximum Use: 1 per N7 loopExample:M7*SN1234567*SN1234568#Name1Seal Number2Seal Number345Seal NumberSeal NumberEntity ID CodeData Element #/ Type225 / ANMin/MaxREQ02 / 15M225 / AN02 / 15O225 / AN225 / AN98 / ID02 / 1502 / 1502 / 03OOOContentsUnique number on seal used toclose a shipmentUnique number on seal used toclose a shipmentNot usedNot usedNot used

BNSF-EDI 322 Transaction16BNSF 322 Implementation GuidelineSEGMENT W09 – Equipment and TemperatureOPTIONALMaximum Use: 1 per N7 loopNOTE: THIS SEGMENT IS NOT USED BY BNSF#Name1EquipmentDescription CodeTemperatureUnit/Basis ForMeasurement CodeTemperatureUnit/Basis ForMeasurement CodeFree-Form MessageVent Set CodePercentQuantity23456789Data Element #/ Type40 / IDMin/MaxREQ02 / 02M408 / R355 / ID01 / 0402 / 02CC408 / R355 / ID01 / 0402 / 02CC3 / AN1122 / ID488 / N0380 / R01 / 6001 / 0101 / 0301 / 15OOOOContents

BNSF-EDI 322 Transaction17BNSF 322 Implementation GuidelineSEGMENT W2 – Equipment IdentificationOPTIONALMaximum Use: 1 per N7 loopExample:W2*BNSF*123456**CN*L#Name1234Equipment InitialEquipment NumberCommodity CodeEquipmentDescription Code511Equipment StatusCodeNet TonsIntermodal ServiceCodeCar Service OrderCodeDateType of LocomotiveMaintenance CodeEquipment Initial12136789101415161718Data Element #/ Type206 / AN207 / AN22 / AN40 / IDMin/MaxREQContents01 / 0401 / 0601 / 3002 / 02MMOM578 / ID01 / 02M577 / N0177 / ID01 / 0301 / 02OOEquipment’s identifying initialEquipment’s identifying numberNot usedCC Container on chassisCH ChassisCN ContainerRR RailcarTL TrailerE EmptyL LoadNot usedNot used240 / ID03 / 05ONot used373 / DT502 / AN08 / 0802 / 02CCNot usedNot used206 / AN01 / 04CEquipment Number207 / AN01 / 06CEquipment CheckDigitPositionCar Type CodeYes/No Condition orResponse CodeAEI Tag Status CodeEquipmentOrientation761 / N001 / 01OUsed when W204 “CC”. Thiswill be the chassis initial, “NONZ”will be used when initial isunknownUsed when W204 CC. This willbe the chassis numberNot used219 / AN301 / ID1073 / ID01 / 0301 / 0401 / 01OOONot usedNot usedNot used1554 / ID1543 / ID01 / 0101 / 01OONot usedNot used

BNSF-EDI 322 Transaction18BNSF 322 Implementation GuidelineSEGMENT NA – Cross-Reference EquipmentOPTIONALMaximum Use: 1 per N7 loopExample:NA***BNSF*123456*F#Name1Reference NumberQualifierReference NumberEquipment InitialEquipment NumberCross ReferenceType CodePositionStandard CarrierAlpha CodeEquipment LengthStandard CarrierAlpha CodeChassis TypeYes/No Condition orResponse Code234567891011Data Element #/ Type128 / IDMin/MaxREQContents02 / 03ONot used127 / AN206 / AN207 / AN231 / ID01 / 3001 / 0401 / 0601 / 01CMMONot usedEquipment’s identifying initialEquipment’s identifying numberF Conveying flat car219 / AN140 / ID01 / 0302 / 04OONot usedNot used567 / N0140 / ID04 / 0502 / 04OONot usedNot used845 / ID1073 / ID02 / 0201 / 01OONot usedNot used

BNSF-EDI 322 Transaction19BNSF 322 Implementation GuidelineSEGMENT GR5 – Loading DetailsOPTIONALMaximum Use: 10 per N7 loopNOTE: THIS SEGMENT IS NOT USED BY BNSF#Name1Special HandlingCodeSurface/Layer orPosition CodeMeasurement ValueUnit/Basis ForMeasurement CodeStatus Reason Code2345Data Element #/ Type152 / IDMin/MaxREQ02 / 03M752 / ID02 / 02C739 / R355 / ID01 / 2002 / 02CC641 / ID03 / 03OContents

BNSF-EDI 322 Transaction20BNSF 322 Implementation GuidelineSEGMENT Y7 – PriorityOPTIONALMaximum Use: 1 per N7 loopNOTE: THIS SEGMENT IS NOT USED BY BNSF#Name123PriorityPriority CodePriority CodeQualifierPort Call FileNumberDate45Data Element #/ Type467 / N0470 / N0471 / ANMin/MaxREQ01 / 0101 / 0101 / 01OCC468 / N004 / 04O373 / DT08 / 08OContents

BNSF-EDI 322 Transaction21BNSF 322 Implementation GuidelineSEGMENT V1 – Vessel InformationOPTIONALMaximum Use: 1 per N7 loopExample:V1**VESSELNAME**12345#Name12Vessel CodeVessel Name34Country CodeFlight / VoyageNumberStandard CarrierAlpha CodeVessel RequirementCodeVessel Type CodeVessel CodeQualifierTransport Type Code56789Data Element #/ Type597 / ID182 / ANMin/MaxREQContents01 / 0802 / 28CC02 / 0302 / 10OO140 / ID02 / 04ONot usedName of ship as documented inLloyd’s Register of ShipsNot usedIdentifying designator for thevoyage on which the cargo travelsNot used249 / ID01 / 01ONot used854 / ID897 / ID02 / 0201 / 01OONot usedNot used91 / ID01 / 02ONot used26 / ID55 / AN

BNSF-EDI 322 Transaction22BNSF 322 Implementation GuidelineSEGMENT R4 – Port or TerminalMANDATORYMaximum Use: 6 loops per N7 loop (N7/R4 ta Element #/ Type115 / IDMin/MaxREQ01 / 01M1Port or TerminalFunction Code234Location QualifierLocation IdentifierPort Name309 / ID310 / AN114 / AN01 / 0201 / 3002 / 24CCO5678Country CodeTerminal NamePier NumberState or ProvinceCode26 / ID174 / AN113 / AN156 / ID02 / 0302 / 3001 / 0402 / 02OOOOContents1 Final port of discharge5 Activity location6 Origin rail terminal7 Destination rail terminalD Port of dischargeL Port of loadingSL U.S. SPLCCode which identifies locationPort name where ocean carrieroriginates or terminates itsshipmentsNot usedNot usedNot usedState or Province

BNSF-EDI 322 Transaction23BNSF 322 Implementation GuidelineSEGMENT DTM – Date/Time ReferenceOPTIONALMaximum Use: 15 per N7/R4 loopNOTE: THIS SEGMENT IS NOT USED IN THE R4 LOOP BY BNSF#Name12345Date/Time QualifierDateTimeTime CodeDate/Time FormatQualifierDate/Time Period6Data Element #/ Type374 / ID373 / DT337 / TM623 / ID1250 / ID1251 / ANMin/MaxREQ03 / 0308 / 0804 / 040