+1, don't think you can combine allowances.

I would say ask your OR account manager for confirmation (but then we have
an excellent helpful account manager, YMMV).

Rich.

Exa Networks Ltd :: AS30740
[email protected]


On Thu, 7 Nov 2019 at 09:13, Neil J. McRae <[email protected]> wrote:

> Chris,
> Pretty sure you can't use the allowance of the second one on the ECC for
> the first one I'm afraid.
>
> Cheers,
> Neil.
>
> On 06/11/2019, 18:54, "uknof on behalf of Chris Wilkie" <
> [email protected] on behalf of [email protected]> wrote:
>
>     Hi All
>
>     Is anyone experienced with ordering EAD circuits from Openreach and
> able to advise, please?  I’ve tried asking OR directly but they don’t seem
> to know, or at least I’ve found myself banging my head on a brick wall
> before I was able to speak to someone with any clue.
>
>     We’ve ordered a circuit which is going to incur significant ECC’s, I’m
> expecting in the order of £10k (on top of the £2.8k-ish allowance)
>
>     I need to order a second circuit out of the same site to a different
> destination.  Obviously once the first one is connected the construction of
> the route to the site will be complete and it will just be a case of
> splicing up a new core (there is fibre present at the other end already).
>
>     OR give an allowance towards construction costs when a circuit is
> ordered.  When the second circuit is ordered the majority of this will be
> wasted because all the work will have already been done.
>
>     Is there some way of combining the two orders such that I can make use
> of the allowance on both circuits against the overall ECC?
>
>     To be clear, both circuits are ’normal’ EAD (not ‘local access' or
> ‘long reach’) and both share a common A end.  It’s almost as if I should
> order this as a resilient circuit somehow, although I’m not too concerned
> if the two circuits share any physical route.
>
>     I have CP status with OR so I’m working directly with EMP.
>
>     Any pearls of wisdom gratefully received!
>
>     Thanks, Chris
>
>
>

Reply via email to