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
Services / Delivery and long-term operations

Planning, delivery, spares and 7×24 cover

Service is not a ticketing system. NOC cover, on-site delivery, spares replacement and architecture advice are four separate lines — priced separately and accepted separately.

7×24
Shift cover
30 minutes
P1 response time
3 languages
CN / EN / Cantonese
Monthly
SLA scoring

Response times and severity

Severity is not set by how big the customer is, but by how much the business is affected. The definitions sit in a contract annex, so no incident starts with an argument about whether it counts as a P1.

SeverityResponse timeApplies to
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, with partial business impact
P324 hoursA single failure or performance issue with no impact on the main service
P448 hoursAdvisory, improvement requests, routine changes

The table shows the standard tier. Actual times follow the signed contract, shorter ones can be agreed for key accounts, and different systems at one customer may carry different tiers.

Four things written into the contract

01

Shift cover

Someone is always on, 7×24, in Chinese, English and Cantonese; cross-timezone projects are rostered to the customer's clock.

02

Regular reporting

Incident reports follow each event, quarterly inspections give conclusions, and the annual review gives trends and budget advice.

03

Spares and managed support

The spares pool is bound to the equipment register: core units in stock, swap before repair.

04

Traceable change

Every change goes through the customer's CAB, configuration snapshots are kept, and afterwards you can trace which change caused the problem.

Where spares and support end

Spares are not whatever happens to be on the shelf. We line the equipment register up against stock and decide what to hold by failure probability × business impact:

01

Core layer

Core switches, firewalls and controllers are held 1:1 or 1:N — replaced on failure, without waiting for a vendor RMA.

02

Access layer

3–5% by model mix, with district rotation stock on multi-site rollouts.

03

Consumables and cabling

Optics, patch cords and power supplies are stocked once for the project cycle, so a second purchase never delays the schedule.

How advisory and architecture are delivered

Usually two to three weeks, with three outputs: a current-state and risk register, a three-year roadmap, and a budget and option comparison. The assessment starts from your requirements, and the report states plainly what existing equipment still has life and what need not be replaced.

Typical triggers: two networks to merge after an acquisition, a data room to relocate, a head office mandating one standard — or simply fixing something every year without being able to say where the problem is.

Establish the current state, then agree the scope.

Contact us →