These are accounts of specific assessments — a Kutaisi cluster walkthrough, a disputed overnight,
a four-week night block, a glossary day. They are not marketplace stars. Names are shortened
because the operators did not ask to be used as a billboard.
They sat with the hourly CSSR file for our Kutaisi cluster and refused to let us talk in region averages. The walkthrough note named three sectors we had been blaming on ‘the bypass’ as a whole. I still think two days is long for one cluster if the extracts are clean, but the neighbour mismatches would have stayed in a slide if they had rushed.
The fibre ticket for the April cut was already closed when they started. The chronology still showed the rectifier door-open ten minutes later on a cabinet we had not put in the first report. That second line changed how we wrote the regulatory note.
The weekend notes were short enough that the day shift actually opened them. Repeating cabinets showed up on a separate page instead of buried in the alarm paste we used to forward.
We had three names for the same drop counter across vendor exports. The glossary did not make anyone fond of anyone else, but customer-care and the radio desk now point at the same line in the extract.
They asked for the unofficial site-code list before they would look at complaints. That felt pedantic at 09:00 and saved us from retuning a face that only shared a road name with the failing sector.
Extended: the rectifier that arrived after the cut
An incident manager brought a closed fibre ticket and a request for a chronology “for the pack.”
The counter files showed two sites dark with the trail, which matched the ticket. A third site’s
attempts fell ten minutes later. The power group’s paper log, photographed that afternoon, showed
a door-open on a shared rectifier while the night crew was still on the first joint.
The chronology listed three timestamps and two source clocks. It did not accuse the transmission
group of lying about the cut. It refused to end the quality paragraph at the cut. That refusal is
the piece of work people keep asking us to repeat.
Extended: complaints that named a road
A quality walkthrough on a bypass corridor started with complaint text that never named a sector.
The unofficial site-code list showed two faces sharing the road name in customer-care shorthand.
Hourly drops sat on only one of them. The mild complaint from that supervisor — that two days felt
long — sat beside the fact that the wrong face would have been the one in the retune request.
Cookies on this site
We use an essential cookie-preference record so this banner does not return every visit.
Optional analytics cookies are described on the
cookies page.
Rejecting optional cookies does not block reading the site.