Network and managed IT

Run it, supply it, support it, and watch it. Four things a buyer picks between, and most clients start with one of them rather than all four. The layer every other system on this site inherits its problems from.

Managing the network

  • Switching and routing

    Traffic goes where it should and you can see why, because VLANs, routing and QoS are documented and changed under control rather than at the switch at four in the afternoon.

  • Wireless

    Coverage holds in the far corner of the warehouse, because the design is surveyed, tuned and validated on site rather than estimated from a floor plan.

  • Firewall and segmentation

    A compromised thermostat cannot reach your records, because operational traffic is separated from office traffic by policy, and remote access goes through one door.

  • Internet and WAN

    A cut fibre does not stop the site, because failover is configured and the call to the carrier is ours to make rather than yours.

  • Servers and cloud

    Workloads sit where they cost least to run, across on-premises hosts, virtualization and cloud, decided rather than inherited.

  • Microsoft 365 and identity

    A stolen password is not enough on its own, because multi-factor authentication, tenant policy and email security are configured and then reviewed.

  • Backup and recovery

    You find out the restore works before you need it, because recovery is tested on a schedule instead of assumed.

  • Patching and security baselines

    Every machine is at the same standard, because there is a written baseline per client and updates run against it.

Providing the hardware

  • Procurement

    The switch that arrives is the one the design called for, specified and sourced rather than substituted for whatever was in stock.

  • Staging and deployment

    A laptop reaches the user working, because imaging, configuration and installation happen before it leaves us.

  • Lifecycle and refresh

    You know what fails next year and what it costs, from an asset register with warranty dates and a planned replacement schedule.

  • Hardware as a service

    Equipment comes out of the operating budget instead of a capital request, because it is bundled into the monthly fee.

Supporting the people

  • Service desk

    Someone answers, and you know how long that should take, through phone, email and portal against response targets that are published rather than implied.

  • Onsite dispatch

    When it cannot be fixed remotely a technician comes, rather than the ticket staying open while everyone waits.

  • Onboarding and offboarding

    A departure removes access the same day, because joiners and leavers run as a defined process rather than as a favour someone remembers.

  • User training

    Staff stop being the easiest way in, through security awareness and short sessions on the tools they actually use.

The operations centre

  • Continuous monitoring

    Devices, servers and services are watched every hour of the year, not only while your office is open.

  • Alerting and first response

    Most faults are triaged and acted on before you notice them, because the alert reaches us first.

  • After-hours escalation

    An overnight outage has a named person attached to it, rather than a queue that opens at nine.

  • Capacity and health reporting

    You know what needs money next quarter from the trend, rather than from the failure.

Testing and assessment

  • Security assessment

    You find out where you are exposed before somebody else does, from a written review with findings in priority order rather than a tool report forwarded on.

  • Vulnerability and penetration testing

    The gap is found by someone being paid to find it, and what was tested and what was not is written down.

Related work

Let’s talk about your project.

Early concept, active specification, out to tender, or a system already in place. Wherever you are in the process, our team can help.