Yeh dil maange more (RailFans, while ending their trip) - Kirti Solanki

Pardon me if I seem to be arguing bullishly here, but I don't see any need to blame SCR as well. SCR's responsibility is to provide a good/fast schedule within it's zone based on the parent zones' requirement and it has done that quite well. This train has a good 60kmph average speed in SCR even though it has almost 10 halts in this zone. Since ECoR hasnt agreed for an early arrival, SCR has given it the scheduel so that it occupies it network for the minimum possible time.
And it is being blamed for 'slowing down the train' even when the SCR stretch is the fastest in this trains entire route.
...
more...

Now even if SCR takes the rake in 2 hours early, it still can't move the rake into ECoR territory before the current time, which means that it would be slowed down by 2 hours in SCR territory, in which case again SCR would be blamed for 'excessive slack' and 'slow schedule'. Looks like it's a no win situation for SCR here. :P
Now, this is a train between NR and ECoR and both can remedy the situation by adjusting timings from their end. But if NR isn't willing to delay the departure and ECoR isn't willing to prepone the arrival, then what can an intermediate zone do? At the most, it's run time till BPQ will decrease by 2 hours and beyond that will increase by 2 hours. SCR is just being made a scape goat in a situation where it is still offering a good service even though it isn't it's priority.