Coverage: which layers, which maps, which files
A walkthrough is only as wide as the extracts you can show. This page states what Releasegridpath will read, where the field examples on this site come from, and what we will not pretend to cover. If your cluster sits inside this frame, write to correspondence with the cluster name.
Radio and quality layers
We read accessibility and retainability counters that a radio quality desk already exports: CSSR and related attempt/success pairs, dropped speech or data sessions, handover failure, and PRB busy hours when the extract includes them. We will look at neighbour lists as exported. We do not retune OSS objects. Core signalling traces and probe farms are out of scope unless they already appear as files the desk owns and wants lined up in a chronology.
Geography in the notes
Written examples refer to Georgian operating conditions: ridge-and-valley neighbours, coastal weekend busy hours, and mixed urban cabinets around larger cities. We will work remotely on extracts from other countries when the naming file is stable. On-site days are quoted when the radio room is the only place the files can be shown.
Outage plant
Chronologies accept fibre tickets, microwave LOS notes, generator run hours, and rectifier or door-open logs. They do not accept a single sentence that names a cause without a timestamp. Power-group paper logs are welcome if they can be photographed; the minute may be marked approximate.
Local utility
The companion tracking utility stores notes on a machine you control. It is not a coverage map of live cells. Listing for that utility is a ordinary link to Veve.