BT Pole Dancing

Attached are a set of seven pages of a guidance document received by a Community network several months ago.

The subject matter is how independent community networks might go about sharing existing BT infrastructure like telegraph poles in rural areas and comments are welcomed here regarding how feasible such a contract might be in practice, from a community perspective.

Having checked that there are no issues with eg Non Disclosure Agreements, please find attached scans of the relevant document which may be helpful in the wider context of pole and infrastructure sharing which Ed Vaisey mentioned was a priority area that he has asked OFCOM to investigate.

poleshare0001

poleshare0002

poleshare0003

poleshare0004

poleshare0005

poleshare0006

poleshare0007

Comments 5

  1. fibrelight wrote:

    Excellent. If a little upside down. Thanks.

    Posted 07 Dec 2009 at 5:11 pm
  2. Sam Reed wrote:

    http://freeside.co.uk/~reedy/poleshare.pdf

    Merged, rotated, and reordered!

    Posted 16 Dec 2009 at 2:09 pm
  3. cyberdoyle wrote:

    can anyone give me the dummies guide? even the right way up they totally baffle this dummy.
    ta.
    chris

    Posted 08 Feb 2010 at 10:32 pm
  4. PhilT wrote:

    The 21 days notice required for access to maintenance of the cables on the shared pole isn’t too attractive.

    Posted 18 Mar 2010 at 10:12 am
  5. guy wrote:

    No its a deal breaker Phil, plus the part about Openreach being able to remove third party cables when it chooses without recourse for consequential losses.

    What annoyed me last year when talking to various BT bods after blogging the story is that they made out that the document was just a starting negotiating position – the reality is that in the real world of actually delivering service, we don’t have time to dick around doing deals – what is required is transparency, upfront best deal and a spirit of genuine cooperation. Haven’t given up hope yet on Openreach…

    Posted 18 Mar 2010 at 6:00 pm

Post a Comment

Your email is never published nor shared. Required fields are marked *