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
DELIVERY

Six stages, each ending in a deliverable

Network projects rarely fail on technology; they fail in the gaps between stages, where nothing can be signed off. This page sets out six stages from first contact to steady state: what happens, what is handed over at the end, and who signs.

The six stages

From first contact to steady state

Network projects come adrift not on technology but on missing deliverables between stages: a survey with no written conclusion, a proposal with no bill of materials, a cutover with no rollback plan. The six stages below each end in something that can be accepted.

StageDeliverable at the endSigned by
01 InventoryCurrent-state and risk registerCustomer contact
02 Proposal and quoteProposal, bill of materials, quotationCommercial leads on both sides
03 Contract and kick-offContract, SLA annex, implementation planAuthorized representatives
04 Build and cutoverConfiguration baseline, cutover record, rollback planProject manager
05 Acceptance and handoverAcceptance report, asset register, operations manualCustomer acceptor
06 Steady-state operationsMonthly SLA scorecard, quarterly review minutesService manager

01 — Inventory

We count devices, circuits, vendor contracts and open issues. Nothing is bought and nothing is reconfigured: the current state is written down as a document you can argue with.

Output: a current-state and risk register stating which equipment still has life, where the risks are, where operational load sits and when existing contracts expire. Scope and duration follow the project.

02 — Proposal and quote

A proposal has to land as a list: what goes in each site, which link, who installs it and when. The quote comes from the same source as the proposal, with no later costs buried in it.

Output: proposal, bill of materials and quotation. The four service lines — managed operations, implementation, spares and support, advisory — are priced separately, so a customer can buy just one.

03 — Contract and kick-off

The contract annex pins two things down: the severity definitions (what counts as a P1) and the acceptance criteria (what counts as passed). Leave either vague and every incident and every acceptance becomes a fresh argument.

Output: contract, SLA annex and implementation plan. The kick-off confirms the customer contact, the working windows and the change approval path.

04 — Build and cutover

Multi-site work runs at night with trading as usual by day. A rollback plan exists before the cutover, the configuration baseline is captured during it, and the asset register is checked afterwards.

Output: configuration baseline, cutover record and rollback plan. Where no downtime window exists, the cutover design is reviewed separately at design stage.

05 — Acceptance and handover

Acceptance follows the criteria agreed in the contract, with no extra conditions added late. Handover clears assets, configuration, accounts and contacts in one go, so operations does not have to go back and ask the build team what happened.

Output: acceptance report, asset register and operations manual. Projects under MLPS or industry audit add log retention, policy configuration and remediation records.

06 — Steady state

A monthly SLA scorecard and a quarterly service review. The scores feed the next period's adjustments — including whether to extend to other sites, which is a decision that should rest on data, not on a hunch.

Output: monthly scorecard and quarterly review minutes. The quarterly review also checks asset changes against contract headroom.

Not found what you need? Call or email, and we will answer against your site.
See office addresses and contact details →

Establish the current state, then agree the scope.

Contact us →