Opened the wrong way — this page has no styling and no images.
Image and stylesheet paths are resolved from the site root (/assets/…), so opening the file directly resolves them to C:\assets\… and nothing loads.
To see it properly: unzip 2_双击进后台改字_仅Windows.zip and double-click 启动后台.bat — the browser then shows the full site with styling, images and the ZH/EN switch.
(This zip is a plain static preview: opened directly it shows one page at a time, without styles, images or the language switch.)
Once uploaded it works normally: live traffic arrives over http, not by double-clicking a file.
This notice only appears when the file is opened locally; online visitors never see it.
ProductsWireless access & coverageSwitching & data centerOptical access & transportOptics & cabling
ServicesManaged NOCImplementation & deliverySpare parts & maintenanceAdvisory & architecture
SolutionsManaged network operations & NOCCampus & wireless coverageCloud-network branchesSecurity & compliance
Case studiesScale · managed operationsSpeed · bulk migrationContinuity · legacy retrofitTechnical notes
About usCompany profileCertificationsOffices & contactTechnical notes
Resources & contactTechnical notesFAQDelivery processPricingPrivacy & termsContact usOffice address
Solutions / Managed network operations and NOC

Managed network operations: cross-timezone cover under one SLA

For a multinational the hard part is rarely building the network — it is availability questions and ownership across timezones. We turn shift cover, tiered response, change control and asset documentation into a service that can be measured, so head office faces one counterparty at any hour.

10 years
Continuous operations
100 offices
Offices in one project
7×24
Follow-the-sun cover
30,000+
Devices under management

What makes this hard

Handing a hundred offices to one company sounds like signing an outsourcing contract. In practice it all comes down to three questions: who owns it, how fast you turn up, and how you prove it.

PAIN 01

No single counterparty

A local integrator runs part of it, the vendor another part, head-office IT owns change. When something breaks, responsibility is settled before diagnosis starts — and half the fixing time goes into meetings.

PAIN 02

Nobody at night

Europe's daytime is China's small hours. Forwarding to one duty phone puts the whole P1 on a single person — who has to work again tomorrow.

PAIN 03

A service you cannot measure

Responsive is an adjective. Without tiers, deadlines and a monthly score, quality rests on impressions and renewal talks have nothing to point at.

PAIN 04

Documents always behind the network

Circuit lists, topology, high- and low-level designs — leave them six months and the next incident starts with rediscovery. Most root causes are documents, not hardware.

Delivery model: six things at once

Operations is not a role, it is a mechanism. Drop any one of the six below and within six months the service is a fire brigade again.

01 / Cover

Three shifts, following the sun

Ten people across three shifts cover Europe, the Americas and Asia-Pacific. Nights go to SD-WAN and network management, days to change and project work.

02 / Tiers

L2 handles, L3 digs in

The first line works standard incidents from the knowledge base; complex ones escalate on a defined path to L3. Every ticket names who gets it next — no heroics.

03 / Measurement

A monthly SLA scorecard

Response, recovery, change success rate and documentation currency are all quantified. Anything missed gets an improvement plan that month and a review the next.

04 / Change

Through the customer's CAB

Request, technical design, review, implementation and quality check are all recorded. Emergency changes take a fast path, with the paperwork completed within 24 hours.

05 / Assets

One ledger for circuits, topology and certificates

Cross-border circuit schedules, design documents, topology, SSL certificates and backups — reconciled quarterly, physically counted once a year.

06 / Coordination

Named contacts at vendors and carriers

Fixed contacts and escalation paths at Equinix, Fortinet and the carriers, so time is not lost waiting for a reply.

Commitments: times written into the tiers

The commitment is split into four tiers, each with a stated response time, and attainment is reported monthly.

SeverityResponse timeWhen it applies
P130 minutesCore service down or the whole network unusable — emergency response starts at once and management is notified
P28 hoursA critical link or device degraded, affecting part of the business or some sites
P324 hoursA single failure or performance issue with no impact on continuity
P448 hoursAdvisory, improvement requests, routine changes

Missing a time is handled as the contract sets out. We do not promise that nothing fails — that is vendor language. We promise that when it does, someone is on it in a stated time and you get a conclusion in a stated time.

Reporting: a quality record you can measure

WEEKLY

Weekly

This week's incidents, changes carried out, backup status and open items. One page, sent on Friday.

MONTHLY

Monthly report and SLA scorecard

SLA attainment, capacity trends, IDS and authentication events, asset changes and next month's plan, walked through at the service review.

ANNUAL

Annual review

A year of incidents and their root-cause distribution, architecture recommendations, next year's capacity and budget, and the physical asset audit result.

ON DEMAND

Major incident report

For P1 / P2, issued within 48 hours of recovery: timeline, root cause, blast radius, remediation and prevention.

"The customer does not want a handsome report. They want to prove, next time something breaks, that this process has actually run." — delivery lead

A live project

A diversified international group headquartered in Hong Kong, China, spanning logistics, cosmetics, pharmaceuticals and trading: a hundred offices and some thirty thousand staff across several timezones. A team of ten took on its network operations — three consecutive years without a major service interruption, SLA met throughout, renewed annually.

3 years
Continuous service · no major outage
100 offices
Offices covered
3,000 devices per engineer
Devices per engineer

The full post-mortem — seven kinds of site problem, how ten mechanisms were put in place, and where it stood after three years — is on the case page.

Read the full case →

How we start

STEP 1

Inventory the current state

We count devices, circuits, vendor contracts and open issues, and put the judgement in writing: what still has life, where the risks are, where the operational load actually sits. Scope and duration follow the project.

STEP 2

Parallel running (1–2 months)

Both providers run in parallel while the incumbent is still in place: knowledge transfer, document rebuild, monitoring onboarding and an emergency drill.

STEP 3

Steady state

Delivered to the SLA, scored monthly. Each quarter a service review turns the question of expanding to other sites into a decision backed by data.

Take stock first, then decide about changing supplier.

Contact us →