Solutions30, Community Fibre join forces for FTTH deployment in London
London-based Internet Service Provider Community Fibre and Solutions30, a provider of services to the telecoms industry, have announced the signature of a vested outsource partnership. This partnership will pass more than 200,000 London homes allowing them to connect to Community Fibre’s network with further projects expected.
This contract is founded on a “vested model” where both parties have adopted a win-win agreement to align their interests and goals. Based on lessons learned from other fibre deployment plans in Europe, this contract is structured to maximise the quality of the network as well as the economic efficiency of the project, without compromising the speed and predictability of deployments that will accelerate return on investment.
To enable large ramp-up and meet expectations regarding fast delivery, Solutions30 will onboard UK employees and contractors but will also find highly qualified resources from other countries where Solutions30 is implemented and has significant references in FTTH roll outs.
Commenting on this agreement, Graeme Oxby, CEO of Community Fibre explains, “This vested outsource contract is a new step in the relationship we initiated with Solutions30 last year. We are pleased to have them on board to help us achieve our ambitious roll out targets. This innovative partnership, built on mutual trust, transparency, and collaboration, will allow us to deliver exceptional value to our customers and investors.”
Paul Garston, UK CEO for Solutions30 says, “This is the second large vested outsource contract that Solutions30 has signed, we are very happy to have the opportunity to replicate the model of our sister company in Belgium. This contract win demonstrates Solutions30’s ambition and continued growth in the UK fixed telecoms market. Our European footprint and FTTx project experience brings much needed additional capabilities and capacity to the UK market, which we are delighted to offer to Community Fibre.”
Comment on this article below or via Twitter @IoTGN