Ch. 3: Event Codes (The Transit Cycle) Flashcards
1
Q
Event Code
A
tells what is happening to the railcar
2
Q
Primary event codes
A
- event codes that are generally expected to occur during a railcar’s trip
- W, X, P, A, J, R, D, Y, Z
3
Q
Secondary event codes
A
- event codes that are typically not expected to occur
- B, G, S, H
4
Q
W
A
- Release
- typically the first and last event code to be reported during a railcar’s trip
- railcar is available to be picked up by carrier
- the shipment process, or “cycle”, has been initiated for that shipment
- do not describe physical railcar movement
5
Q
X
A
- Pull
- being taken by carrier to be conjoined with rest of train
- first physical movement
6
Q
P
A
- Departure
7
Q
A
A
- Arrival
8
Q
J
A
- Interchange Delivered
- ready to be picked up by next carrier
- Does not guarantee that receiving carrier will pick up railcar
9
Q
R
A
- Junction Received
- Receiving carrier has picked up railcar at junction
- J and R codes do not always report in order
10
Q
D
A
- Destination Arrival
- railcar is nearing end of its trip
- does not signify the consignee has received shipment
11
Q
Y
A
- Constructive Placement
- don’t always get reported
- don’t always report at the same SPLC location as D or Z
- Key Takeaways
- carrier is unable to deliver the railcar to the consignee facility due to a “closed gate” situation
- carrier instead delivers the railcar to the carrier’s local serving yard and then notifies consignee
- the consignee must then schedule a date/time for the carrier to deliver the rail car to the consignee’s facility when their gate is open
12
Q
Z
A
- Actual Placement
- carrier has physically delivered railcar to consignee facility
- doesn’t always get reported to feed
- doesn’t always report the same SPLC location as the D and Y
13
Q
B
A
- Bad Order
- secondary event code
- railcar has malfunctioned or has mechanical defect
- either repaired by carrier crewmen or diverted to a repair shop
14
Q
G
A
- Bad Order Release
- secondary event code
- indicates that a bad ordered railcar has now been repaired and cleared to resume transit on mainline track
15
Q
S
A
- Storage
- secondary event code
- railcar set aside at a railyard for variety of reasons
- most common: client has loaded the car with product but has yet to find a customer to purchase product
- certain routes report S in place of Y
16
Q
H
A
- Hold
- indicates a hold has been placed on car
- wide variety of reasons (similar to S)
- examples: mechanical inspections, weight restrictions, lack of or modifications to shipping instructions
17
Q
Fleet Cars
A
- have 2nd leg empty return to origin facility
- owned by QTS customers
18
Q
Non-fleet cars
A
- comprise majority of cars tracked by QTS
- given by carrier to be used for single shipment
- no 2nd empty return trip
- owned and maintained by carriers
19
Q
Demurrage
A
- time-based
- result of carrier waiting on QTS customer to perform a certain action within transit cycle
- QTS customer has been notified that their car has been CP, and charged for the amount of time it takes for them to schedule AP
20
Q
“No Bill” Charge
A
- carrier arrives at origin to pull car, but a BOL issue prevents them from pulling the car
21
Q
When it comes to demurrage and No Bill charges…
A
QTS’s job is to minimize those costs through effective tracking and reconciliation of BOL issues
22
Q
Origin Performance
A
performance metrics about (W, X, P)
23
Q
Destination Performance
A
performance metrics about (D, Y, Z)
24
Q
Performance refers to…
A
- the order in which the events occur (if they occur at all)
- the individual SPLC locations where each of the events occur
- the average time that elapses between each of the events
