FTTPoD has been suspended because it is too expensive to deploy ... which comes about because it consumes too much personnel time, in turn causing queues to become too long.
Neil McRae presented at UKNOF reporting that BT were trialling new techniques to reduce time, and thus costs and queues. In essence, it broke down to:
- Different fibre, using Corning SST fibre incorporating strength members. I think this is meant for the fibre deployed in FoD, rather than the fibre spine. Purpose: to be able to break through more blockages without the need to dig.
- Different blowing technique, using push/pull.
- Using fibre that is easier to split
- More connectorisation, less splicing.
It looks like quite a rethink, and I'm wondering if it alters any of the hardware chosen for the FTTP PONs (the splitter nodes, the fibre DPs, the use of BFT and manifolds).
Still, trials are happening. But don't expect FoD to return until the costs are under control.
BTW - I don't think FoD lines connect directly in to the FTTC cabinet.
Instead the FoD and FTTC deployments share the same fibre spine - which amounts to a long length of multi-fibre cable (up to 288 fibres) spreading out of head-end exchanges, with aggregation nodes (flexibility points, where PON and PtP fibres can be jointed to the spine, in splice trays) interspersed at intervals.
FTTC cabinets are connected into the spine at an aggregation node with PtP fibre (with some spares run too).
FTTPoD deployments create a PON - including splitter, fibre DP, manifold, and BFT. This PON, for up to 128 properties, is connected from the splitter back to the spine at one of the aggregation nodes ... just like the cabinets, but using fibres meant for PONs.
The previous marketing of FoD required users to be in existing FTTC areas, not because of the need to connect to the cabinet, but because of the need to connect to an aggregation node. The presence of FTTC is a shortcut that implies the spine is somewhere nearby
The pricelist for FoD specified the excess cost was proportional to the distance (as the crow flies) between user and the nearest aggregation node.