|
Post by hawk777 on Aug 9, 2020 20:56:24 GMT -6
What's the difference between the Work status and the On Duty status? Both are listed to be used for locals only.
Also! Does a particular local have a home track (e.g. L-CAL0314 always lives on Bakersfield 4)? Or should it go into an arrival track when it comes back after working, instead? In the latter case, after the local departs its home yard, is one supposed to make a registry entry without track number to identify that the local is on duty, plus a second registry entry for the track number but with no train to identify that the track is now empty?
|
|
|
Post by daverice on Aug 10, 2020 15:17:37 GMT -6
Good questions Hawk! I recently started using the "Work" and "Completed" status for locals in BAK and BK...but probably not consistently, yet.
Here's the way I'm using these three status for BAK and BK: - "Work" - train is ready to be worked (similar to "Released" for mainline trains) - "On Duty" - crew has arrived and ready to move the train (similar to "Departed" for mainline trains) - "Completed" - train has arrived at it's final destination and all work is completed (similar to "Arrived" for mainline trains)
For track assignments in BAK and BK, since UP, BNSF and SJVR share those yards I like to have SJVR use BAK tracks 13-19 and BK tracks 6-14. If a local returns to the yard track from which it originated that keeps things simpler, just update the track as "Assigned" and update train lengths and weights. Typically, the first two tracks at BAK and BK are used for mainline train arrivals. Then track 3-4 in BK are used for UP departures/locals and 3-7 in BAK are used for BNSF departures/locals.
Hope that helps.
Dave
|
|
|
Post by hawk777 on Aug 12, 2020 12:00:04 GMT -6
Sounds good, thanks! Maybe those explanations, at least the part about the statuses, could be copied somewhere permanent, either the registry update form itself or the documentation in the first tab of the registry?
|
|