Our website uses cookies to improve user experience, analyse website traffic and assist in our marketing efforts. By clicking “Accept”, you agree to the storing of cookies on your device. View our Privacy policy for more information. You can change your preferences at any time.
Orange cross to indicate close page icon.
Steel Mill, Foundry, Furnace, Iron - Metal, Metal
Oct
2024
(c) iStockphoto (498859470)

Large single-site heavy engineering plant, South Yorkshire (confidential)

A plant network designed around production, not legacy cabling

Industrial network redesign: resilient core, rationalised uplinks and zone-based access control

The problem (a legacy estate that had outgrown its own cabling)

Every production area depended on a handful of communications cabinets that had accumulated links to each other over years of extensions. A single failure could take out more than the area it served, and nobody could say in advance how far the impact would reach.

The site covers about 5.2 hectares across five production zones, served by 24 access cabinets. It had grown in stages. New buildings stood alongside old ones, clean production and finishing areas sat next to dusty ones, and successive cabling projects had been layered on top of each other. Each addition made sense at the time. Together they created inter-cabinet dependencies that cascaded, so failure domains were far larger than anyone had designed for.

That shaped day-to-day operations as much as outages. Changes were hard to plan because the knock-on effects were difficult to predict, and fault-finding started with tracing cables rather than reading documentation.

The estate was Cisco in principle. In practice, some of the cabinet additions had been built with cheaper switches, so capability, support status and configuration varied from one part of the site to the next. That variation made the dependencies harder to reason about, and any design had to work with equipment of mixed capability.

The route in was a conversation rather than a tender. The plant had appointed a new IT manager who had worked with Oxspring at a previous employer, and he called us for advice before committing to a plan.

The brief called for a topology with redundant cores at opposite ends of the site, cabinet uplinks rationalised into something the site team could understand and support, and access control that reflected how the plant actually operates. Replacing serviceable equipment was not the aim.

What “good” looks like (outcomes)

  • Failure domains sized to the area they serve, with no cascading dependencies between cabinets.
  • Redundant cores at opposite ends of the site, so losing a core or a single link does not stop production.
  • A documented uplink hierarchy that can be changed without a site-wide outage.
  • Access control aligned to production zones rather than to historical cabling convenience.
  • One switching standard across the site, so the estate behaves predictably and can be supported as a single network.
  • A topology the customer’s own team can support and extend without rediscovering it.

Risk & Challenges

  • Live production throughout, with change confined to agreed windows.
  • Mixed building stock, so distances, containment and environmental conditions vary across the site.
  • A mixed switching estate, with capability and support status varying by cabinet.
  • End-of-support access switches in around 40% of positions, which had to be replaced rather than carried forward.
  • Existing fibre that could not be assumed to support 10 Gbps, so the survey had to prove it before design.
  • Legacy patching that was poorly documented, which made discovery a prerequisite for design.
  • Dirty and clean areas requiring different equipment choices and access arrangements.
  • Cascading dependencies that made staged migration necessary, with a rollback position for each stage.

Our approach (discovery first, then topology)

We started with the physical and logical estate rather than with equipment. Mapping what connected to what, and what failed with what, established the real failure domains before any design decision was taken.

The first phase was a detailed cabinet survey across all 24 access cabinets, recording what connected to what and testing fibre specifications and distances against the 10 Gbps requirement. Fibre within each zone is multimode, with single-mode runs from each zone back to the core, so the two had to be assessed separately. That determined which routes could carry the new uplinks and set the scope of the switching replacement before any equipment was ordered.

From that picture we designed a collapsed backbone: two Cisco Catalyst 9400 chassis switches as cores at opposite ends of the site, cabinet uplinks rationalised into a hierarchy rather than the web of dependencies that had grown up, and zone-based access control boundaries drawn around production areas. The chassis cores gave the site a single aggregation point for its cabinet uplinks and headroom to grow without replacing the core again. Access control uses VLAN segregation to keep IT and OT networks apart, so production traffic and business systems share the physical infrastructure without sharing a broadcast domain.

Sixteen fibre runs were replaced in all, either because the cabinet itself moved or because the existing cable could not carry a 10 Gbps uplink.

Around 40% of the access switches were replaced because they were end of support. The rest were retained where they were serviceable and appropriately located, which kept the work focused on structure and resilience rather than a wholesale refresh.

The programme ran for about four months from receipt of order to handover to business as usual, including a month of pre-staging at our office. That left roughly three months of onsite work.

Implementation started with the two cores, then moved through the site zone by zone. Working in zones kept each change contained: a zone could be migrated, tested and left stable before the next one started. Each zone had a defined rollback position, which mattered on a site that could not stop production.

Core and uplink failover scenarios were tested as part of pre-handover validation, so the redundant design was proven rather than assumed.

The goal was a resilient, supportable network, and that is what the site now has. What changed is the structure: fewer dependencies, contained failure domains, and a documented topology the IT team can work from.

Deliverables (what the customer actually receives)

  • Documented cabinet survey of the existing physical and logical estate.
  • Fibre assessment covering specification and distance against 10 Gbps uplink requirements.
  • Collapsed backbone design, covering core placement, uplink hierarchy and zone boundaries.
  • Zone-based access control design and configuration, with VLAN segregation between IT and OT networks.
  • Staged migration plan with rollback positions.
  • Commissioning and failover test records, including core failover validation before handover.
  • As-built documentation for the customer’s support team.

Proof (resources and examples)

If your plant has grown around its network rather than the other way round, and a single cabinet failure still reaches further than it should, that's worth a conversation. You can reach out to our team at solutions@oxspring.com or phone 01226 761188.

Our client

No items found.

Our services

In this project we delivered the following services:

Our partners

Got a project in mind? Our experienced team are ready to help
Orange arrow icon for back to top link.