Power Servicing Times
Jun 23, 2018 9:24:26 GMT -6
Post by Clint on Jun 23, 2018 9:24:26 GMT -6
It is becoming pretty obvious that the power servicing times are causing a bottleneck specifically in West Colton, I think Barstow would be in a similar situation if not for all the cancellations. I think the problem is lack of manpower to hostle the engines around when they are ready, not so much the 4 hour service time.
For example, after last session we had power in Barstow that was finished servicing at 0100, but because it didn't get moved at 0100, the next set of power will be spotted at 0300 and not ready until 0700, where as if it was moved right at 0100, the next set would be ready at 0500, therefore losing 2 hours of service time.
My solution was to tag the next set based on the previous set, so the next set at Barstow would be tagged ready at 0500 instead of 0700, regardless of the fact that it wasn't spotted until 0300. This would eliminate the manpower issue of getting them swapped out right when they are ready.
I did have a discussion with Chris the other day on this topic, and another solution is just to do away with the servicing times all together. We all know there are limitations to what we can and can't simulate based on manpower and limitations in Run8 itself. So I post this topic for discussion to get input from everyone to make a better decision on how to alleviate this problem. Any suggestions, comments, or ideas are greatly appreciated from anyone, not just admins alone.
While Mike has the final say on all decisions, I do know that he is very good at taking suggestions and opinions from all members into consideration, so don't be afraid to speak your mind.
Thanks,
Clint
For example, after last session we had power in Barstow that was finished servicing at 0100, but because it didn't get moved at 0100, the next set of power will be spotted at 0300 and not ready until 0700, where as if it was moved right at 0100, the next set would be ready at 0500, therefore losing 2 hours of service time.
My solution was to tag the next set based on the previous set, so the next set at Barstow would be tagged ready at 0500 instead of 0700, regardless of the fact that it wasn't spotted until 0300. This would eliminate the manpower issue of getting them swapped out right when they are ready.
I did have a discussion with Chris the other day on this topic, and another solution is just to do away with the servicing times all together. We all know there are limitations to what we can and can't simulate based on manpower and limitations in Run8 itself. So I post this topic for discussion to get input from everyone to make a better decision on how to alleviate this problem. Any suggestions, comments, or ideas are greatly appreciated from anyone, not just admins alone.
While Mike has the final say on all decisions, I do know that he is very good at taking suggestions and opinions from all members into consideration, so don't be afraid to speak your mind.
Thanks,
Clint
