Wired Networking

We do the whole layer, firewall included. That means specifying an appliance sized to your throughput and user count, installing it at the edge, building the rule base from a default-deny position, segmenting the internal network behind it, and configuring intrusion prevention, DNS and content filtering to your policy.

We also set up logging and retention so an incident can be investigated after the fact, take a configuration backup, and agree a change process with whoever will own it day to day.

The configuration is documented and handed to you. If you have an existing security partner or an internal IT team, we work to their standard rather than around it.

AV Over IP is about carrying audio and video across a network — encoders, decoders and the AV-specific switching that distribution needs. Office Network is the network itself: the cabling, the switching, the Wi-Fi and the firewall that every system in the building shares, AV included.

In most projects they are one piece of work. The same cabling design serves desks, cameras, access points and AV endpoints, and the same VLAN plan keeps AV traffic from contending with everything else. Scoping them together is usually cheaper and always more reliable than treating them as two projects.

We survey. Quoting access points by floor area is how buildings end up with dead spots behind a lift core and three access points fighting over the same channel in an open-plan corner.

Our process is a predictive survey against your floor plan and construction details, then an on-site validation walk. That produces a placement plan, a channel and power plan, and a mounting schedule. After installation we walk the space again and hand over a report showing measured coverage and throughput, so what was promised is what you can verify.

Cat6 or Cat6A copper to desks, access points, cameras, panels and AV endpoints, and OM4 fibre for backbone runs between comms rooms and floors. The choice depends on run lengths, the PoE draw of the connected devices, and the uplink speeds you expect to need over the life of the fit-out.

Every run is terminated in a labelled patch panel and certified with a test result you keep. You also get an outlet register and a port schedule, so the next change is a lookup rather than another survey.

Yes, and it is common. We can take the physical layer and the design while your team retains policy and administration, or run the whole thing and hand over to them at a defined point.

What we ask for is a single technical contact and agreement on standards — addressing, naming, VLAN allocation and firewall change control — before we start configuring. What you get is documentation in a form your team can pick up, not a black box.

Usually very little, and it is planned. New cabling and switching go in alongside what is already running, so the cutover is a scheduled window rather than a day of outage. Firewall replacements are staged with the new policy tested before the change, and a documented rollback if it does not behave.

Where downtime is genuinely unacceptable we design high-availability pairs at the edge and dual uplinks from the access layer, so a single failure — or a single maintenance window — does not take the floor down.

You do. At handover you receive as-built diagrams, the IP schedule, VLAN and port maps, firewall rule notes, wireless survey results and configuration backups.

We would like to keep supporting the network, and most clients take a monitoring and maintenance agreement. But that should be because the support is worth having, not because nobody else can read the configuration.