From counter intake to a briefing supervisors can schedule

System Nodebase treats telecom network performance analytics as a service engagement, not a product login. The Field Process page describes how a typical Network Performance Field Assessment moves from Bangkok kickoff through optional street sampling and into a ranked findings pack.

1. Scope the cluster

We confirm markets, bands, vendor exports, and the decisions your team must make after the brief — campaign launch, landlord access priorities, or a quality reset. Scope stays written so later findings do not drift into open-ended exploration.

2. Ingest counters and tickets

Service-desk tickets and busy-hour counters arrive together. We align naming across vendor dumps, isolate the windows that match complaint peaks, and flag sectors where remote evidence already suggests a cause.

3. Sample the street when gaps remain

Where counters and tickets disagree, we plan short measurement walks or drives on nominated corridors. Samples are annotated with photos and timestamps so RF and facilities can revisit the same corners.

4. Rank findings for crews

The pack lists severity, supporting evidence, and a practical next step for each item. We deliberately keep language close to how supervisors brief crews: sector, corridor, access constraint, and owner.

5. Close with a live briefing

The engagement ends in a walkthrough with your service leads. Questions that need vendor or landlord follow-up are recorded as open items rather than buried in appendices.