Technology

IT & Infrastructure Consulting

We design, build and run the IT that sites depend on, where downtime or data loss has regulatory, clinical or operational consequences. We mastered that in healthcare, where the bar is about as high as it gets, and the same engineering serves a factory, a laboratory, a warehouse or an office. One team covers the whole stack: the cabinet, the network, the cloud tenant and the devices, so there is no gap between suppliers.

How we work

Three ways in, and most clients use more than one

Our background is sterile services, where the standards are about as demanding as they get. Build to that bar and the rest is straightforward: the same engineering applies anywhere a site has machines, data and people to keep apart, including manufacturing floors, laboratories, warehouses and offices. You do not need to be a hospital, and you do not need to be large. A single site with one comms cabinet is work we take, and so is an estate with twenty.

Design and build

A fixed-scope project, from survey through bench build and installation to an audit-ready handover pack.

Managed service

We monitor, patch and support the estate after go-live, with secure remote access and a change log kept per site.

Advisory

Independent design reviews, security posture checks and transition plans for when responsibility moves between suppliers.

What we look after

From the comms cabinet to the cloud tenant

One supplier across the whole stack, so there is no gap between the network, the machines on it and the systems behind it.

UniFi is the platform we standardise on. We design, install and run UniFi networks, and UniFi Protect for CCTV and access control, as our default across regulated and industrial sites. Where an estate already runs something else, we work with what is there and connect it in rather than replacing kit that still does its job.

01

Networks & Wi-Fi

UniFi (Ubiquiti) gateways, switching and Wi-Fi, where every kind of device sits on its own network and only the traffic a process needs is allowed through. Resilient internet with automatic failover, chosen to suit the site.

UniFiSegmentationInternet resilience
02

CCTV & door access

UniFi Protect camera systems and access control, on their own isolated networks and sized around your retention policy. Standards-based cameras can often be brought in without replacing kit that still works.

UniFi ProtectONVIFPaxton Net2
03

Security & compliance

We design to the same controls we are audited against, and provide the evidence your assessment or toolkit return needs. Segmentation is enforced at the firewall rather than assumed.

ISO 27001Cyber Essentials PlusDSPT
04

Microsoft 365 & Intune

Tenant setup and migration, MFA for everyone, Conditional Access, and laptops, kiosks and phones enrolled, patched and secured through Intune.

Microsoft 365Entra IDIntune
05

Microsoft Azure

Landing zones, private networking closed to the internet by default, site-to-site VPNs, Azure SQL with point-in-time restore, and backups designed so a recoverable copy always exists.

AzureAzure SQLBackup & recovery
06

Data analytics

From spreadsheets to SQL and Power BI: migrations that clean and validate data on the way, dashboards, and production and energy analytics.

SQLPower BIMicrosoft Fabric
Segmentation

Every device in its place, from the cabinet to the cloud

A production machine has no business reaching the internet, and a guest laptop has no business reaching it either. The same rule runs the whole way up the stack: the firewall enforces it on site, Entra ID and Intune enforce it on the laptops and phones, and the cloud tenant stays closed by default. One team designs all three, which is why they agree with each other.

Fixed lineprimarySecond pathautomatic failoverGateway and firewalldefault denySwitchSwitchSwitchresilient ring: one link can failOfficeinternetProductioninternetMachinesisolatedPrinterslimitedCCTVisolatedDoor accesslimitedGuestrate limitedIntegration gatewaysno inbound accessCloud-hosted systemencrypted in transitoutbound only
Every service runs on its own network and every crossing passes through the firewall. Machines and cameras are isolated with no route to the internet at all. The exact set of networks is tailored to each site.Select a network to see what it can and cannot reach.

Officeinternet

Staff laptops, desk phones and the printers they are allowed to use.

Can reach
The internet, the file and mail services staff need, and a print queue.
Cannot reach
The machine network, the camera network and the door controllers. An office laptop cannot reach a washer-disinfector even by accident.

Productioninternet

Workstations on the floor: tracking terminals, labelling, packing stations.

Can reach
The tracking system, the print queue and the specific services the process depends on.
Cannot reach
General web browsing, and anything on the camera or door networks.

Machinesisolated

Washer-disinfectors, endoscope washers and sterilisers.

Can reach
Nothing, except the integration gateways that collect their cycle data, and that connection is outbound only.
Cannot reach
The internet entirely. A machine on this network has no route out and nothing can reach in to it.

Printerslimited

Label and document printers shared across the department.

Can reach
Print traffic from the office and production networks, and nothing else.
Cannot reach
The internet, and any attempt to start a connection of its own. Printers are a common way in, so they get their own network.

CCTVisolated

Cameras and the recorder they write to.

Can reach
The recorder, and the staff who are entitled to view footage.
Cannot reach
The internet, and every other network on site. Footage does not leave the recorder unless someone authorised asks it to.

Door accesslimited

Readers, door controllers and the access control server.

Can reach
Its own controller, so a door still works when something else on site does not.
Cannot reach
The internet and the rest of the estate. Access control failing open or being reachable from a desk is not acceptable.

Guestrate limited

Visitors, contractors and personal devices.

Can reach
The internet, at a capped share of the line so it cannot starve the rest of the site.
Cannot reach
Everything else, including other guest devices. A contractor laptop is treated as hostile until proven otherwise.

And once it is built, this is the view we work from

Every network we run is monitored, so a failover or a machine that stops reporting reaches us before it reaches you. Below is how a site looks on an ordinary day.

Example client siteIllustrative
NetworkSwitching and Wi-FiOnline
Washer-disinfectorsCycle dataReporting
SterilisersCycle dataReporting
CCTVIsolated networkRecording
Door accessIsolated networkOnline
InternetPrimary and failoverOn failover
Assurance

Built to standards we are certified against

We design to the same controls we are audited on, and we are clear about where our responsibility ends and another supplier's begins.

ISO 27001Information security management, certified
Cyber EssentialsUK government-backed cyber certificationView certificate ↗
Cyber Essentials PlusIndependently audited assessment
Questions

What people ask before they call

Do we have to replace everything we already have?

No, and we would usually advise against it. UniFi is what we standardise on for new work, but kit that still does its job can normally be brought into a new network rather than skipped. Standards-based cameras in particular can often be reused without moving a cable. Where something genuinely has to go, we will tell you why rather than quietly schedule it.

Will you support a network you did not build?

Yes. It starts with a design review and a security posture check, so we both know what is actually there as opposed to what the documentation says. Taking on someone else's estate is a different job from building one, and we scope it as one rather than pretending otherwise.

Who holds the administrative credentials?

You do. Credentials, licences and administrative access are documented and formally handed over, whether or not you keep us on afterwards. We have seen too many sites held hostage by a supplier who would not hand over a password to do it to anyone.

Do you replace our IT team or work alongside them?

Alongside, in almost every case. Most of our work is the part an internal team does not have the time or the specialist kit to do: the design, the build, the segmentation, the out-of-hours cutover. Day-to-day support stays wherever it works best, and we are explicit in writing about where our responsibility ends and someone else's begins.

Can you work to a fixed date, like a validation or an audit?

That is most of what we do. The reason we bench-build and test before anything reaches site is precisely so a fixed date survives contact with reality: installation day becomes patching and checking rather than configuration. A recent build went from approval to live testing in five weeks on that basis.

Next step

Network not behaving, or a site to build?

Whether it's a department going in, a tenant that needs sorting out, or support you can actually reach, tell us what's happening.