Client and scenario
Ruder Finn Asia is a leading global communications consultancy. The Hong Kong office runs Asia-Pacific operations and works daily with more than twenty offices worldwide. IT in a firm like this has one characteristic: few people, but an enormous dependence on the network and collaboration tools. An email, a cross-timezone video call, a live client pitch — if any one of them stalls, it is a business incident.
The office infrastructure was already in place, on mainstream brands. The client did not want a rebuild; they wanted someone accountable for the long run on top of the existing stack — nothing replaced, responsibility settled.
Three questions before taking over
The difficulty here is not technical. It is ownership, once one stack, three vendors and two timezones are added together.
One network, three vendors, three consoles
Fortinet owns the perimeter, Cisco the switching, Aruba the wireless: three consoles, three log streams, three firmware cadences. When something breaks, the first step is rarely diagnosis — it is working out which layer owns it.
Daytime faults happen at night too
The Hong Kong office links more than twenty sites worldwide: faults raised locally by day must close the same day, while Europe's and America's daytime is Hong Kong's small hours. Cover cannot be one forwarded phone.
Cross-border work has to be traceable
Staff accounts, guest access and device changes must all answer who changed what, and when. A stronger password does not solve that; process and records do.
How we took over
Take over first, improve second: protect what the client has already bought, and draw the line of responsibility clearly.
No replacement, just takeover
The existing Fortinet / Cisco / Aruba estate stayed. The first step was a clean handover of the asset list, configuration backups, accounts and permissions — the ledger everything else is built on.
Certification to match the kit
Three vendors on site means three certification tracks. Our engineers hold the relevant Fortinet, Cisco and HPE (Aruba) certifications, so they work on the equipment directly instead of escalating layer by layer.
ITIL in practice
Incidents, changes, assets and reporting run on ITIL practice: what takes the emergency path, which changes need prior approval, how often reports appear — agreed up front and auditable afterwards.
Cover and language
The Hong Kong team provides 7×24 on-site and remote support in Mandarin, Cantonese and English. Requests at a multinational come from different regions, and a language gap turns straight into response delay.
Cross-border compliance
Access and records follow Hong Kong and international data protection requirements: who may enter a device, what trace a change leaves, how long logs are kept — all fixed in process.
Scope of service
The day-to-day running of one office from perimeter to endpoint — not just fixing the box that raised the ticket.
Where it stands
The contract was signed in May 2026 and service began then; delivery continues. The client's internal service metrics are contractual and are not disclosed here — this page only describes how delivery runs.
For a client like this the measure is plain: people in the office stop talking about the network. Meetings connect, files open, the client pitch does not drop — IT fades into the background, which is where it belongs.
Compiled from the company's WeChat announcement of 11 May 2026 and project site records; the client name has been publicly disclosed, and the contract governs the specific terms and metrics.