Skip to main content
KMS

Fiber optics

Connecting buildings: how to plan a fiber backbone between sites

Linking a second building is not a cabling job — it is an infrastructure decision that will outlive several generations of equipment. What to settle before anyone digs a trench.

Author:
KMS

An organization acquires or builds a second building on the same site — a teaching block, a warehouse, an administrative wing. The first ideas usually look for a quick fix: run a copper cable along the fence, put a wireless bridge on the rooftops, or connect the buildings over the internet with a VPN. Each of these is acceptable in some situations. But if both buildings belong to one organization and will operate together for years, a fiber backbone is almost always the most reliable and, over the long term, the most rational choice.

A fiber backbone between buildings is more than a cabling job: it is an infrastructure decision that will probably outlive several generations of active equipment. Below are the questions that need answers before the trench is dug. They are especially relevant to education campuses, hospitals and industrial sites.

Start with what has to run over the link

Fiber count should be driven by a list of systems, not by what seems enough today. List every system that needs a connection between buildings: the corporate network, video surveillance, access control, telephony, the building management system, fire alarm integration, perhaps a separate guest network or an extension of a carrier circuit.

A practical rule: every independent connection needs a pair of fibers; double that for redundancy; then add at least as many again as spares. For example, if you need two pairs today, a 12-fiber cable is the minimum sensible choice and a 24-fiber cable is often better — the cable is a small share of the total project cost, while the groundworks are expensive to repeat.

Topology and redundancy

For two buildings, one link is enough. For three or more there are two main patterns: a star, where every building connects back to the main building housing the core switch and server room; and a ring, where buildings connect in a loop so that if any single section is damaged, traffic continues the other way round.

Redundancy is only real when the routes are different too. Two cables in the same trench or duct will be cut by the same excavator at the same moment. If the link is critical — between hospital blocks, for example — the second link must physically take another route and enter the building at a different point.

The route: underground, aerial or existing services

The most durable option is an underground duct with access chambers at bends and along long runs. Direct burial is possible with a suitable armoured cable, but adding or replacing a cable later means digging again. An aerial run on poles or between buildings is quick and cheap but more exposed to wind, ice, sunlight and mechanical damage.

  • Who owns the land along the route, and is a permit or a neighbor's consent required?
  • Does the route cross a road, a parking lot or other services — water, gas, power cables?
  • Are there existing unused ducts that can be reused, and what condition are they in?
  • Where will the access chambers be, and how will they be reached for maintenance?
  • Will a spare duct be laid for future cables? Compared with the cost of the groundworks, it is a negligible expense.
  • How will the underground route be marked — warning tape above the cable and markers at the surface?

Choosing cable for the outdoors

Between buildings, single-mode fiber (OS2) is almost always used: distances run to hundreds of meters or more, and single-mode optics accommodate future speeds without limitation. The cable must be rated for outdoor use: fibers in loose tubes, with water-blocking elements and a UV-resistant jacket. On underground routes, consider rodent protection — metallic or dielectric armour.

Outdoor cable jackets are often not intended for long runs inside a building because of fire-safety requirements. So a transition point is usually planned close to the building entry — a splice closure or box where the outdoor cable joins an indoor cable, or terminates directly in the fiber patch panel.

Building entry and termination

The building entry is the most frequently neglected point. The duct entry must be sealed, or water and rodents will follow it into the basement or the telecom room. The cable needs a slack loop near the entry for future re-termination, and the fibers should be terminated in a labeled fiber patch panel, from which patch cords connect to the switch. Port numbering in the panels at both ends should match — a simple rule that saves a great deal of time later.

Active equipment and separating systems

Both ends need switches with optical ports and single-mode transceivers matched to the distance and wavelength. On one physical link, systems are separated logically with virtual LANs (VLANs), so that video surveillance and access control do not interfere with the corporate network. In some cases — for example, when the security system is run by a separate operator — it is better to give it dedicated fibers. That is why spare fibers are not only for growth: they also make physical separation possible.

Alternatives, and when they make sense

A point-to-point wireless bridge goes up quickly and needs no groundworks. It is a good fit for a temporary connection, as a backup path, or where digging is practically impossible. But it needs clear line of sight, is affected by weather and other radio sources, and offers less bandwidth than fiber. A leased line from a carrier is the answer when buildings are far apart or on different streets — but it is a recurring monthly cost and an external dependency.

Project stages

  1. List the systems needed between buildings and calculate the fiber count, with spares.
  2. Decide on topology and redundancy, including whether a second, physically separate route is needed.
  3. Survey the route on site: land ownership, existing services, crossings, permits.
  4. Choose the cable type and protection for the route; plan building entries and transition points.
  5. Install, splice and terminate at both ends with consistent labeling.
  6. Loss-test every fiber and record an OTDR trace; compare results with the calculated budget.
  7. Document the as-built route on a drawing, with landmarks and access-chamber locations.

The last stage is often the weakest. A few years later, when new works start on the site, an accurate route drawing is the only thing that stops an excavator from cutting the cable. Documentation is part of the network infrastructure, not an optional extra.

If you are planning to connect buildings, get in touch — we will survey the route on site and help you compare the options before any work begins.

Planning a technology or infrastructure project?

Tell us about the facility, the systems involved and your timeline. We will review the scope and come back with the next steps.