Presume this will also affect metro between Pelaw and South Hylton, as the signals through there are network rail's, rather than South Gosforth?
(14 May 2015, 8:23 am)JakeSavage wrote [ -> ]Presume this will also affect metro between Pelaw and South Hylton, as the signals through there are network rail's, rather than South Gosforth?
Correct.
I'd say the probability is trains will run but at a heavily reduced service. Management could cover signallers on strike.
Bank Holiday Monday has been named as the day of the strike.
(15 May 2015, 6:31 am)Andreos1 wrote [ -> ]Bank Holiday Monday has been named as the day of the strike.
It's from 5pm on Monday to 5pm on Tuesday.
(15 May 2015, 6:48 am)danpick wrote [ -> ]It's from 5pm on Monday to 5pm on Tuesday.
Ah is it?
Cheers.
Only heard a small snippet on the news earlier and just thought it was for the 25th.
(15 May 2015, 7:22 am)Andreos1 wrote [ -> ]Ah is it?
Cheers.
Only heard a small snippet on the news earlier and just thought it was for the 25th.
Well that's what my dad said. It Also means I will struggle to get to my hospital appointment as I live at Brockley Whins.
(28 May 2015, 4:49 pm)Andreos1 wrote [ -> ]http://www.socialistworker.co.uk/art/406...twork+Rail
Strike action back on?
It's certainly looking that way.
I'm not sure how the membership is split across the RMT and TSSA, but I'd question whether it's the best course of action, when the TSSA are balloting their members on the offer? That's happening over the next two weeks, so even if the TSSA members reject, they still don't have enough time to give notice for the same dates.
4th June 1700 for 24 hours and 9th June 1700 for 48 hours.
Strike action is the best course for this IMO; such a large company like Network Rail should be paying its frontline staff more.
(28 May 2015, 8:55 pm)northern156 wrote [ -> ]4th June 1700 for 24 hours and 9th June 1700 for 48 hours.
Strike action is the best course for this IMO; such a large company like Network Rail should be paying its frontline staff more.
It's dragged on for far too long now imo. The offer is piss poor, and I can't see why for one minute that Network Rail bosses would have thought it would be acceptable to the workers? 1.0% for this year, around 1.4% for next year as part of a two year deal. Despite the profits the company is turning.
(28 May 2015, 9:21 pm)aureolin wrote [ -> ]It's dragged on for far too long now imo. The offer is piss poor, and I can't see why for one minute that Network Rail bosses would have thought it would be acceptable to the workers? 1.0% for this year, around 1.4% for next year as part of a two year deal. Despite the profits the company is turning.
Exactly which is why I feel a strike of 3 days in total (plus industrial action short of a strike [not working overtime or undertaking call-out duties for 1 week from 6th June]) to cause Network Rail the most hassle possible is the right way forward.
It can be argued they're in some pretty bad debt however the bonuses top management get paid is just stupid for it not to be shared out more evenly.
Again.
Strike action by RMT members working for Network Rail - latest information
Updated 1 June, 13.45
The RMT trade union has announced that industrial action and action short of a strike (overtime ban) which was planned between Thursday 4 June and Thursday 11 June has been suspended.
(01 Jun 2015, 3:18 pm)Tommy_1581 wrote [ -> ]Again.
Strike action by RMT members working for Network Rail - latest information
Updated 1 June, 13.45
The RMT trade union has announced that industrial action and action short of a strike (overtime ban) which was planned between Thursday 4 June and Thursday 11 June has been suspended.
And for an extremely poor offer from the brief scan I've had of their press release.
Two year deal. 2% for 2015, and a match with RPI for 2016. If RPI drops to a negative figure, the pay 'award' will be 0% for the 2016 element.
I really can't make my mind up whether they'll want to vote for strike action again - especially for such a poor offer. Quite strange that if they've been getting their backs up about it previously...
(01 Jun 2015, 5:50 pm)northern156 wrote [ -> ]I really can't make my mind up whether they'll want to vote for strike action again - especially for such a poor offer. Quite strange that if they've been getting their backs up about it previously...
See I can completely understand the offer initially being rejected, as Network Rail tried to sell it to the unions as up to 2% for 2015 in exchange for terms and conditions. Unions like the RMT would always reject such proposals out of hand, and it's baffling as to why companies still try to hold members over a barrel, rather than negotiate any proposed terms changes separately.
The next offer took the terms and conditions off the table, but they put down an offer of 0% for 2015 with a non-consolidated £500 payment instead, then RPI inflation for 2016, 2017 and 2018 as a four year deal. The offer did however add a no-compulsory redundancy agreement until Dec-2016, but as a whole, the offer was quite rightly rejected as a shocking 4 year package.
The new offer is:
- 1% consolidated for 2015 under pinned by £250, and backdated to 01/01/2015
- 1.4% consolidated for 2016 from 01/01/2016.
- Extension of no compulsory redundancy agreement across the bargaining units until 31/12/2016.
- Agreement to enter into discussions to agree a 'comprehensive job security package'.
I'm not sure whether they'll go for it myself. I'd be wanting Network Rail to increase those percentages slightly, and certainly have a better underpinning on both years. After all, 1% of sod all is still sod all. The last point has the potential to be beneficial, but it's never a given that the two parties will agree on something.
Loco in picture is 66428 first reports indicate that it is a write off due to damage at both ends plus the centre of the loco
(02 Aug 2015, 5:14 pm)Coppercap40 wrote [ -> ]Loco in picture is 66428 first reports indicate that it is a write off due to damage at both ends plus the centre of the loco
Don't be silly. There's been locos in the past with more damage than that which have been returned to service.
66428 66305. 6K06 and 6K07. While I can guess what the cause is, I won't speculate on an open forum.
No DRS drivers involved and no serious injuries.