Search This Blog

Tuesday, January 20, 2015

Press release: ITF repeats call for Rotterdam dialogue as dockers protest

Please find this release attached and below.
Yours,
Sam Dawson
ITF


20 January 2015

ITF repeats call for Rotterdam dialogue as dockers protest

The ITF (International Transport Workers' Federation) today called for all-party talks on the future of the port of Rotterdam, as dockers refused to unload a ship loaded at the new Rotterdam Gateway (RWG) terminal. RWG, unlike other companies at the port, refuses to negotiate a collective bargaining agreement with port workers, who are represented by the FNV Havens union.

 

On Sunday the vessel Alsvin loaded containers at RWG, in what was believed to be a test operation. It then moved to the ECT terminal in Rotterdam to discharge them. Dockers refused to unload them.

 

ITF president and chair of the ITF dockers' section, Paddy Crumlin, stated: "Rotterdam is a giant among the world' ports and should be a model of good industrial relations. It is notable that all the operators there bar one have signed agreements with the union representing its workers. This is despite many previous warnings* and widespread concern about the port's future."

He concluded: "We urge all parties, and that includes not just all operators and port authorities, but also the shipping lines, to get together to defuse this situation and reach an agreed settlement to ensure the dispute does not escalate more widely."

ENDS

* www.itfglobal.org/en/news-events/press-releases/2014/october/itf-and-fnv-call-for-dialogue-on-rotterdams-future

 





ITF communications: getting the message out - when and where it matters

www.itfglobal.org 
www.facebook.com/ITFglobal 
Twitter: @itfglobalunion




This email is confidential and may be privileged. If you have received it in error, please notify the sender and then delete it immediately. You should not copy it or use it for any purpose nor disclose its contents to any other person. Any views or opinions expressed within the email are solely those of the sender and do not necessarily represent those of the ITF.

No comments:

Post a Comment