Expertise

Enterprise network

A network is designed around its degraded modes, not its headline bandwidth.

Parent division
Networks and communications

The problem

The quoted bandwidth describes normal operation; the rest of the time, architecture decides.

An enterprise network is judged on one figure: the bandwidth of the main link. That figure describes the situation where everything works, which is the situation nobody is interested in.

What separates a network that holds from a fragile one is its behaviour when a link, a power supply or a device disappears. Fallback paths, traffic prioritisation and segmentation are decided with the architecture. Added later, they mean reworking the cabling, the addressing and sometimes the carrier contract.

And there is a question rarely asked in time: who will operate this network in three years. An undocumented network, whose configuration exists only inside the devices, effectively belongs to whoever installed it.

What holds when a link disappears, schematic

01Accepted cabling
Link-by-link measurements, labelling at both ends, records handed over.
02Access layer
Access switches, power over the network, backed-up power consistent with the services carried.
03Redundant core
Aggregation, documented addressing plan, recovery from the failure of any one device.
04Fallback path
A different technology and a different route. Two links in the same duct fail together.
05Segmentation
Office, security, industrial, voice and guest separated, filtering rules justified one by one.
06Operation
Monitoring, configuration backups, current diagrams and skills transfer.
Schematic. The accented path is the property that quoted bandwidth never describes.Typical sizing figures. The failover time is what a rapid convergence protocol holds on a properly sized core.

Scope

What the service covers

Cabling and technical rooms
Route study, copper and fibre cabling, racks, systematic labelling at both ends, acceptance by measurement, and handover of the test records.
Core and distribution
Redundant switching, link aggregation, routing versus switching decided per layer, documented addressing, and a recovery plan for the failure of any one device.
Segmentation
Office, security, industrial, voice and guest access separated; filtering rules between segments written down and justified one by one.
Wireless access
Coverage study on plans then on site, density by use, roaming, separate networks for staff and guests, and network access control.
Site interconnection
Carrier links, fallback paths on a different technology, automatic failover proven in practice, and prioritisation of critical flows on the fallback link.
Operation and documentation
Monitoring, configuration backups, a maintained addressing plan, current diagrams, intervention procedures and skills transfer to the in-house team.

Situations

The most frequent situations

New build or refurbishment
The network is installed with the second fix. Decided afterwards, it forces surface-mounted routes and expensive rework in rooms already handed over.
Branch network
Identical configurations replicated, industrialised deployment, centralised monitoring. A branch configured differently is a branch nobody can troubleshoot remotely.
Industrial or mining site
Long distances, harsh environment, controllers living alongside office IT. Segmentation is not good practice here, it is an operating condition.
Taking over an undocumented network
The survey comes before any change: with no addressing plan and no current diagram, every modification is a wager.

Requirements

What to require, of us as of anyone

These requirements hold whichever supplier is appointed. Written into a tender, they filter out the responses that will not hold.

  • An addressing plan and current diagrams handed over at completion, in a format the client can edit.
  • The network’s behaviour on the loss of each link and each core device, described and proven at acceptance.
  • Cabling acceptance measurements, link by link, with the records handed over rather than a conformity certificate alone.
  • Configuration backups, where they are kept, and the procedure for restoring a replaced device.
  • A written justification for every filtering rule between segments.
  • Backed-up power for active equipment, consistent with the duration adopted for the services it carries.
  • Training for the in-house team and full access to the equipment, with no account reserved to the provider.

Pitfalls

Common mistakes, and what they cost

Sizing on bandwidth rather than on uses
The link is oversized, segmentation is absent, and a single compromised workstation reaches the whole system. Bandwidth protects nothing.
Treating wireless as an add-on
Coverage is estimated on plans and never verified on site. Difficult areas — stairwells, basements, steel-framed buildings — are discovered after acceptance.
Planning a fallback on the same technology
Two links from the same carrier running through the same duct fail together. A fallback path is only one if it shares as little as possible with the main path.
Leaving documentation until the end
It never gets produced. A network with no diagram and no addressing plan is repaired by trial and error, which lengthens every incident and ties the organisation to whoever installed it.

Questions

Questions asked before consulting

Is fibre needed inside the building?

Between technical rooms and between buildings, yes: it removes the distance limits of copper and most electrical disturbance. Towards the desk, copper remains relevant because it also carries power for telephones, cameras and access points. The choice is made segment by segment, not for a whole site.

How long does cabling stay relevant?

Far longer than the active equipment, which is replaced as needs and support dictate. That is why cabling and cable routes are the wrong place to economise: they are the most expensive part to redo, and the part that blocks any later evolution once undersized.

How should the industrial network be separated from the office network?

Through segmentation whose permitted flows are enumerated, not through a simple change of addressing. Controllers and supervision systems cannot be patched, so segmentation is their main protection. It presupposes knowing which flows are genuinely required, which calls for a survey before a single rule is written.

Is a guest network really necessary?

As soon as a visitor, a contractor or a personal device connects. A guest network grants internet access without granting access to the information system; without one, the internal network password gets handed out and stops being a password.

What should be required at acceptance of a cabling project?

Per-link measurements, labelling actually applied at both ends, rack diagrams, the addressing plan, and handover of the configuration backups. A certificate with no measurement records attests to nothing verifiable.

Can an existing network be upgraded in stages?

Yes, and it is usually the right approach. It starts with the survey, then the core and segmentation, which govern everything else. Access layers and wireless follow building by building. What cannot be staged is the addressing plan: it is decided once, for the whole.

Evidence

Where we have applied it

  • Telecommunications2023

    Regional operator — core network modernisation

    Replacement of the core network and backup power at fourteen points of presence, with no commercial service outage.

    Points of presence migrated
    14
    Longest outage window observed
    4 min

    Reference KP-2023-021

  • Enterprise and sensitive-site security2025

    Industrial group — security supervision centre

    A single control room for six sites whose security systems did not talk to each other.

    Sites connected
    6
    Threat scenarios rehearsed before commissioning
    3

    Reference KP-2025-002

All projects

Consultations · Pre-qualifications · Partnerships

Let us discuss the actual case.

Describe the site, the dominant constraint and the deadline. We will say what requires a preliminary study and what can be committed directly.