01
Hardware
Workplace and data-centre hardware, specified for the job.
View domain
Outcome pillar · Connect
Networks built from edge to core.
The position
Most network faults are physical. We install the passive plant, terminate it, certify every link and hand over the results. Then we run the active layer on infrastructure we can prove rather than infrastructure we inherited.
Portfolio scope
Core, distribution and access switching, VLAN and routing design, stacking and redundancy that has actually been failover-tested. Configurations backed up before and after every change.
Predictive design validated by an on-site survey, controller-based Wi-Fi 6 and 6E, and roaming tuned so a call survives the walk from the lobby to the lift.
Monitoring on uplinks, controllers and power, configuration backup and change control, branch connectivity with SD-WAN or dual-carrier failover.
Cat6 and Cat6A permanent links, OM4 and OS2 backbone, splicing and termination, rack elevations, containment, earthing and a labelling scheme that means the same thing at both ends.
Certified test results per port, as-built drawings, port schedules and rack layouts handed over as a pack. If it is not documented, it is not finished.
Outcomes
Technology ecosystem
Specified against the requirement, not against whichever line card pays best. Authorisation levels are confirmed in writing at quotation.
How we deliver it
Planning, procurement, deployment, operation, maintenance and disposal are not a separate product. They are how every domain reaches production, stays there, and eventually leaves without becoming somebody’s problem.
A site survey, a look inside the risers, and a read of the existing port schedule, if one exists. Wireless is surveyed, never assumed from a drawing.
Cable, panels, optics and active kit ordered against the approved design, with lead times confirmed before the programme is committed and no drop to a lower category to make a price work.
First fix to the drawings, terminate, certify every link, label both ends, then hand over the test results with the as-builts.
Config backups mean a failed switch is a swap, not a rebuild. Escalation to the vendor is our conversation.
Monitoring on uplinks and controllers, firmware cycles scheduled in a window, and capacity flagged before the access layer runs out of ports.
Retired switches and controllers wiped of configuration and credentials, abandoned cable pulled out rather than left in the tray, and the port schedule corrected to match.
An engineer will look at the environment you actually have before anyone writes a proposal.