Back

Copper Network Withdrawal

Manage the full decommissioning of copper infrastructure — address by address, exchange by exchange — without a single order going to the wrong network

Migrating from copper to fibre is one of the most operationally complex programmes a network operator undertakes. It’s not a single switch-over — it’s a rolling, multi-year programme of equipment decommissioning, address migrations and service transitions that touches every layer of your OSS, your sales systems and your field operations simultaneously.

The biggest risk isn’t technical. It’s operational. The moment a property has been migrated to fibre, your sales and provisioning systems must know — immediately, completely and irreversibly. A copper order raised against a migrated address doesn’t just fail. It wastes engineer time, damages customer relationships and in regulated markets, can carry compliance consequences.

Confideo Copper Network Withdrawal manages the entire decommissioning programme within the OSS platform — tracking withdrawal status at address, exchange area, and ISAM equipment level, enforcing automatic sales order blocks the moment an area enters withdrawal and providing a complete, auditable record of every transition from copper to fibre.

The risk without proper withdrawal management

Without automated order blocking, a sales agent can raise a copper service order against a property that has already been migrated to fibre — or is mid-migration. The result: a provisioning failure, a failed engineer visit, a frustrated customer and a regulatory headache. Confideo Copper Network Withdrawal eliminates that risk entirely.

Order Protection

The right order. Every time. Automatically.

The most damaging failure in a copper withdrawal programme isn’t a missed fibre installation. It’s a copper order raised — by a sales agent, an OLO, or an API call — against an address that’s already been migrated. That order will fail at provisioning, trigger an unnecessary engineer visit and leave a customer without service while the mess is untangled.

Confideo Copper Network Withdrawal enforces order blocking at the OSS level — before the order is even accepted into the system. The block is applied automatically when an address enters the withdrawal programme, covers all order channels simultaneously, and cannot be bypassed without an explicit, audited authorisation from a named administrator.

Exchange & Equipment Management

From ISAM to postcode. Every level tracked.

Copper withdrawal doesn’t happen at a single address. It happens across entire exchange areas, cabinet clusters and ISAM equipment groups — all rolling at different phases, on different timelines, with different sets of affected customers.

Confideo manages withdrawal at every level of the hierarchy simultaneously. You define the programme at exchange area level, the system propagates the withdrawal status down to every cabinet and address within it. Individual addresses can be ahead of or behind the area programme — for example, a property where fibre was installed early moves to blocked status immediately, regardless of where the broader exchange area sits in its withdrawal timeline.

The withdrawal lifecycle

Six phases. Every address managed through each one.

Every address in a withdrawal zone moves through a defined lifecycle. Confideo tracks and enforces each phase automatically.

Confideo manages withdrawal at every level of the hierarchy simultaneously. You define the programme at exchange area level, the system propagates the withdrawal status down to every cabinet and address within it. Individual addresses can be ahead of or behind the area programme — for example, a property where fibre was installed early moves to blocked status immediately, regardless of where the broader exchange area sits in its withdrawal timeline.

1. Exchange & ISAM Area Management

Define withdrawal zones at exchange level, cabinet level, or down to individual ISAM equipment. Each zone has its own withdrawal timeline, status, and notification schedule — managed centrally within Confideo OSS.

2. Address-Level Withdrawal Tracking

Every property within a withdrawal zone is tracked individually. Each address moves through a defined migration lifecycle — from copper-active through notification, fibre-available, migrated, and finally copper-withdrawn — with full history retained.

3. Automatic Sales Order Blocking

Once a property reaches the migrated or withdrawal-pending state, Confideo OSS automatically prevents any new copper service orders being raised against that address — across all channels, all products, and all OLOs. No manual rules. No exceptions unless explicitly authorised.

4. Fibre Installation Coordination

As fibre is installed at properties within a withdrawal zone, the system automatically updates the address status and adjusts which services are orderable. A property with confirmed fibre installation is immediately available for fibre orders and blocked from copper — simultaneously.

5. Customer & OLO Notification Management

Manage the legally required notification programme for affected customers and wholesale partners. Define notice periods per withdrawal zone, track notification delivery and maintain a complete record of who was informed and when — essential for regulatory compliance.

6. Withdrawal Reporting & Audit Trail

Every address transition, every order block, every notification sent — all logged with timestamps, user attribution and system source. Full audit trail available for regulatory review, board reporting and programme management at any point in the withdrawal programme.

OSS integration

Native to Confideo OSS. No separate system to manage.

Copper Network Withdrawal is built directly into Confideo OSS — not a bolt-on module or an external tool. It shares the same inventory, the same order management engine and the same audit infrastructure.

Running a copper withdrawal programme?

Whether you’re planning your first withdrawal zone or managing a multi-exchange national programme, Confideo can help you do it without the operational risk. Talk to our team about how the module fits into your existing OSS deployment.