Junction interchange update form

Junction Interchange Update Form -- INSTRUCTION GUIDE

To ADD, CHANGE or EXPIRE an INTERCHANGE in the Junction Interchange (JUNC) Industry Reference File (IRF), it is required that a JUNCTION INTERCHANGE UPDATE FORM be submitted to RAILINC with the required information and signature(s). This INSTRUCTION GUIDE is intended to answer any questions you may have while completing the form. Should you have any additional questions and/or require assistance when completing the form, please call the Senior Data Analyst at RAILINC at [phone].

The JUNCTION_INTERCHANGE_UPDATE_FORM'>JUNCTION INTERCHANGE UPDATE FORM is divided into three sections; JUNCTION, INTERCHANGE and AGREEMENT. The INSTRUCTION GUIDE is likewise divided into these three sections.

JUNCTION - unique identification of the LOCATION of an INTERCHANGE

The information requested in this section of the form is used to uniquely identify the specific location of the INTERCHANGE. These unique locations are called JUNCTIONS. Each JUNCTION is identified by a three, four or five character JUNCTION ABBREVIATION (i.e. - CHGO for Chicago, IL).

Before an INTERCHANGE can be ADDED, CHANGED or EXPIRED, it is ESSENTIAL that the correct LOCATION of this INTERCHANGE be identified. While JUNCTION ABBREVIATION alone uniquely identifies the location of an INTERCHANGE, the other information is requested to verify that there is no misunderstanding between the parties involved (the two carriers and the RAILINC).
Should you have any additional questions and/or require assistance when completing the form, please call the Senior Data Analyst at RAILINC at [phone].

• 
  JUNCTION ABBREVIATION -- A unique 3 to 5 character alphabetic code assigned to a location by RAILINC. This information is required on all forms. If the JUNCTION ABBREVIATION is not known, please contact the Senior Data Analyst at RAILINC at [phone] for assistance.
  

• 
  STANDARD POINT LOCATION CODE (SPLC) -- The six (or nine) numeric digit code used to identify geographic places. The SPLCs are assigned by the National Motor Freight Traffic Association (NMFTA) for points in the United States and Mexico, and by the National Transportation Agency (NTA) for points in Canada. The SPLC is not required on the form, but is requested to verify that there is no misunderstanding between the parties involved (the two carriers and RAILINC). If the SPLC is not known, please contact the Senior Data Analyst at RAILINC at [phone] for assistance.
  

• 
  JUNCTION LOCATION NAME -- The city or common name for the location. The JUNCTION LOCATION NAME is not required on the form, but is requested to verify that there is no misunderstanding between the parties involved (the two carriers and RAILINC).
  

• 
  JUNCTION STATE / PROVINCE -- The US or Mexican STATE or the Canadian PROVINCE in which this location can be found. The JUNCTION STATE / PROVINCE is not required on the form, but is requested to verify that there is no misunderstanding between the parties involved (the two carriers and RAILINC).
  

INTERCHANGE - description of ACTIVITIES between two transportation entities at a JUNCTION

The INTERCHANGE is the means of describing the activities that will take place between the two transportation entities at the JUNCTION location described above. Please refer to the SUMMARY OF INTERCHANGE TYPES for more detailed information regarding the various types of INTERCHANGES that can exist.

Should you have any questions and/or require assistance when completing the form, please call the Senior Data Analyst at RAILINC at [phone].

• 
  ACTION REQUESTED -- A single character code used to indicate the type of update that is being requested to the INTERCHANGE file. This information is required on all forms. The acceptable codes are:
  

A -- ADD a new INTERCHANGE to the file. This action is used when no INTERCHANGE currently exists

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Last modified: June 10, 2005 Page 1

between these two transportation entities at the JUNCTION LOCATION described.

C -- CHANGE an existing INTERCHANGE on the file. This action is used when some aspect of the INTERCHANGE between these two transportation entities at the JUNCTION LOCATION described is being changed.

This action is NOT used to change one of the transportation entities involved in the INTERCHANGE or to change the JUNCTION LOCATION for the INTERCHANGE, both of which would require an EXPIRE of the existing INTERCHANGE and an ADD of the new INTERCHANGE.
E -- EXPIRE an existing INTERCHANGE on the file. This action is used when an existing INTERCHANGE between these two transportation entities at the JUNCTION LOCATION described is no longer needed.
Before a revenue capable INTERCHANGE can be EXPIRED, all Routes utilizing this INTERCHANGE must be EXPIRED in Industry Route File.

• 
  INTERCHANGE TYPE -- A single character code used to identify the activity that can take place between the two transportation entities involved in this INTERCHANGE beginning on the EFFECTIVE DATE OF ACTION (see below). Two entities can only have ONE type of INTERCHANGE between them at each JUNCTION location. The SUMMARY OF INTERCHANGE TYPES is the official source for information on the various types of INTERCHANGES that can exist.
  

This information is required on all forms. In summary, the ten INTERCHANGE TYPES acceptable today are:

C Indirect Haulage Linehaul Revenue & Rail-to-or-from-Rail

Indirect Operating

E End-of-Train Device Direct Operating Only Rail-to-or-from-Other (non-rail)

Transportation Mode

I Joint Motor-Rail Linehaul Revenue Joint Motor-Rail Movements

N Normal Linehaul Revenue & Rail-to-or-from-Rail

Direct Operating

O Operating Only Direct Operating Only Rail-to-or-from-Rail

P Per Diem Relief Direct Operating Rail-to-or-from-Intermodal Storage

R Rubber Indirect Operating Rail-to-or-from-Rail via Drayman -or-

Rail-to-or-from-Owner

S Shop Direct Operating Rail-to-or-from-SHOP -or-

TTX-to-or-from-SHOP

V Revenue Only Linehaul Revenue Rail-to-or-from-Rail

Only

W Water Linehaul Revenue & Rail-to-or-from-Water Carrier

Direct Operating
Should you have any additional questions and/or require assistance when completing the form, please call the Senior Data Analyst at RAILINC at [phone].

• 
  INTERCHANGING CARRIER -- The two or four character MARK or SCAC (Standard Carrier Alpha Code) that uniquely identifies the transportation entity involved in this INTERCHANGE. This information is required on all forms for both MARK / SCAC 1 and 2.
  

There is no significance to the designation of 1 or 2; all INTERCHANGES are considered to be bi-directional and will be stored in the central files in MARK/SCAC alphabetical order. For example, an INTERCHANGE of any type between the MARKS XYZ and ABC will be stored in the central files with ABC as MARK/SCAC 1 and XYZ as MARK/SCAC 2.

Should you have any additional questions and/or require assistance when completing the form, please call the Senior Data Analyst at RAILINC at [phone].

• 
  REPORTING CARRIER -- The two or four character MARK or SCAC that uniquely identifies the transportation entity that will report activity at this INTERCHANGE to TRAIN-II for either MARK/SCAC 1 or 2. This information is required on all forms for both MARK / SCAC 1 and 2.
  

When the same MARK/SCAC is used as the REPORTING CARRIER for both MARK/SCAC 1 and 2, this situation is commonly referred to as ONE ROAD REPORTING. When the INTERCHANGE TYPE is E, I, P, S or W, ONE ROAD REPORTING is REQUIRED. Please refer to the SUMMARY OF INTERCHANGE TYPES for more detailed information regarding the various requirements for TRAIN-II reporting with each of the INTERCHANGE TYPES.

Should you have any additional questions and/or require assistance when completing the form, please call the Senior Data Analyst at RAILINC at [phone].

• 
  CSM STATION FSAC -- The 5 digit numeric Freight Station Accounting Code (FSAC) from the Centralized Station Master (CSM) file that identifies a specific station that supports this INTERCHANGE. The CSM STATION FSAC is not required in all circumstances. Please refer to the SUMMARY OF INTERCHANGE TYPES for more detailed information regarding the various types of INTERCHANGES that can exist and their CSM STATION requirements.
  

In summary, the CSM STATION requirements for the ten INTERCHANGE TYPES acceptable today are:

C Indirect Haulage Stations required for BOTH railroads - Station types must include R

E End-of-Train Device Stations are NOT required

I Joint Motor-Rail Station required for railroad only - Station types must include R

N Normal Stations required for BOTH railroads - Station types must include R&O or R & H

O Operating Only Stations required for BOTH railroads- Station types must include O or H

P Per Diem Relief Stations are NOT required

R Rubber Stations are NOT required

S Shop Station is required for railroad only - Station types must include O or H

V Revenue Only Stations required for BOTH railroads - Station types must include R

W Water Station is required for railroad only - Station types must include R

Besides the appropriate station type(s) as indicated above, the CSM stations also require that the same JUNCTION ABBREVIATION be included in the station record as is being used to uniquely identify this INTERCHANGE's location.
Should you have any additional questions and/or require assistance when completing the form, please call the Senior Data Analyst at RAILINC at [phone].

• 
  DELIVERY ONLY FLAG -- This special TRAIN-II code is used when the INTERCHANGE participants want to report on "delivery" only to TRAIN-II and any report of a "receipt" would be rejected by TRAIN-II.
  

The default value for this information is "N" (no). When the DELIVERY ONLY FLAG is set to "Y" (yes), then both REPORTING CARRIERs must be different; one-road reporting is not allowed.

Please be advised that setting the DELIVERY ONLY FLAG to "Y" (yes) carries significant implications and should not be used unless you fully understand these implications. A full description of those implications is beyond the scope of this document; please contact the TRAIN-II Project Leader at RAILINC at [phone] with any questions you have regarding the implications of this flag in TRAIN-II.

• 
  INHIBIT JUNCTION ADVICES -- This special TRAIN-II code is used when the INTERCHANGE participants want TRAIN-II to NOT send notice of an INTERCHANGE when it is requested by an equipment owner for INTERCHANGES that occur between these two carriers at this JUNCTION location.
  

The default value for this information is "N" (no).

Please be advised that setting the INHIBIT JUNCTION ADVICES flag to "Y" (yes) carries significant implications and should not be used unless you fully understand these implications. A full description of those implications is beyond the scope of this document; please contact the TRAIN-II Project Leader at RAILINC at [phone] with any questions you have regarding the implications of this flag in TRAIN-II.

• 
  EFFECTIVE DATE OF ACTION -- The date on which the ACTION REQUESTED (as described above) is to become effective. This is NOT (necessarily) the date the form is being signed as INTERCHANGES can be added, changed and expired with future effective dates.
  

The date is required on all forms and the proper format must be used; CCYY-MM-DD where C is century, Y is year, M is month and D is day. For example, July 23, 1996 would be written 1996-07-23.

The rules governing when an INTERCHANGE can and cannot be added, changed or expired in the past are complex and are beyond the scope of this document. Should you have any additional questions and/or require assistance when completing the form, please call the Senior Data Analyst at RAILINC at [phone].

AGREEMENT - signatures of transportation entity representatives (as required by Interchange TYPE)

Bilateral concurrence is not required for all types of interchanges. Please refer to the SUMMARY OF INTERCHANGE TYPES for more detailed information regarding the various types of INTERCHANGES that can exist and their signature requirements.

In summary, the signature requirements for the ten INTERCHANGE TYPES acceptable today are:
C Indirect Haulage bilateral agreement 2 signatures

E End-of-Train Device signature required from 1 signature

railroad only

I Joint Motor-Rail signature required from 1 signature

railroad only

N Normal bilateral agreement 2 signatures

O Operating Only bilateral agreement 2 signatures

P Per Diem Relief signature required from 1 signature

railroad only

R Rubber signatures required from 1 or 2 signatures

all (and only) railroads involved

S Shop signature required from 1 signature

railroad only

V Revenue Only bilateral agreement 2 signatures

W Water signature required from 1 signature

railroad only

At each major carrier and many of the shortline carriers, only one person (or sometimes a small group) is authorized to sign INTERCHANGE AGREEMENTS. If you are initiating an update to the JUNC IRF using this form, you will need to identify who on the other road needs to sign the form before it can be updated into the central file.
Should you need to know who the authorized contact person is at a specific railroad or if you have any additional questions and/or require assistance when completing the form, please call the Senior Data Analyst at RAILINC at [phone].

• 
  SIGNATURE -- Signature of the/an authorized person at the carrier(s) as described above.
  

• 
  CONDITIONAL AGREEMENT? -- The default value for this information is "N" (no). When the CONDITIONAL AGREEMENT? field is set to "Y" (yes) by either or both MARK/SCACs, they are indicating that they agree to this Interchange update ONLY when some condition is met. That condition must accompany the form in writing and be signed and must make clear all special conditions for agreement to this Interchange update.
  

An example of a common condition for Interchange agreement is the need for another Interchange to be ADDed, CHANGEd or EXPIREd simultaneously.

• 
  NAME -- The name of the person signing the form. Please print for clarity.
  

• 
  COMPANY -- The name of the railroad or company for which the signatory works.
  

• 
  PHONE NUMBER -- The full (including area code) phone number of the signatory for use in case of questions by the Railinc staff or the other Interchange participant.
  

• 
  FAX NUMBER -- The full (including area code) facsimile (fax) number of the signatory.
  

SUBMISSION - FAX completed form to RAILINC at [phone] (or mail to address in the instructions)

For INTERCHANGE TYPES that require bilateral agreement and 2 signatures (as described above), the typical form creation - submission path is as follows:

• 
  MARK / SCAC 1 initiates the update by completing a form.
  

• 
  MARK / SCAC 1 faxes the form to MARK / SCAC 2 as well as the AAR.
  

• 
  If the type of Interchange requires only one signature (as described above), the AAR keys the update into the central system.
  

• 
  If MARK / SCAC 2 signature is required for the type of interchange, the AAR will hold the form awaiting MARK / SCAC 2's reply for 5 business days.
  

• 
  If after five business days there is no reply, the AAR will fax the form to MARK/SCAC 2 with a cover note asking for a response. The AAR will follow-up in a proactive manner as required.
  

• 
  When a fax is received from MARK/SCAC 2, the form is keyed and the update becomes part of the central file.
  

Should you need to know who the authorized contact person is at a specific railroad or if you have any additional questions and/or require assistance when completing the form, please call the Senior Data Analyst at RAILINC at [phone].

If you wish to send a form to the RAILINC via mail, the address is:

Senior Data Analyst

Business Services Division

RAILINC

7001 Weston Parkway - Suite 200

Cary, NC 27513