Research — Scenario Walkthrough

Make-ready scenarios

Five poles, five outcomes. A new communications attacher asks for space on a pole that already carries primary, a transformer and a secondary. Each request is checked against the GO-95 clearance minimums and an illustrative strength gauge, then fixed the least disruptive way: nothing, a repack, a taller pole, or a stronger pole. The last one shows a failure that was already there before anyone asked.

Scenario

Elevation · pole attachment stack · drawn to scale in feet

Pole strength · illustrative

0%
0%130%

Illustrative: strength comes from a pole loading analysis, not computed here. Only a utilization percent is shown.

Check being read

Actual

Required

Margin

How the check read it

    Every check · before the request, after the request, after make-ready

    Required values: GO-95 Table 1 type 3 (urban thoroughfare) for the 18 ft communications ground minimum, Table 2 type 2 for primary-to-secondary (4 ft), secondary-to-comm (4 ft) and comm-to-comm (1 ft). A check is "tight" under 0.2 ft of margin. Strength rows are illustrative.

    Real numbers, illustrative sequence:constants are copied from the harness; the walkthrough order is staged. GO-95 Table 1 (urban thoroughfare ground clearance) and Table 2 type 2 (between-attachment separation) values, and ANSI O5.1 Douglas-fir setting depths, are real values from the overhead-calc-harness; the ported tables on this page are checked against 130 cases exported from the Python by scripts/export_demo_golden.py. The poles, the attachers and the order of each sequence are scripted illustrations, and the repack and replacement steps are this demo's own simple logic (slide existing attachers up just enough, plus a 0.2 ft buffer), not a harness function. Strength utilization is illustrative: the harness has no pole-strength function, and strength comes from a pole loading analysis (a tool such as O-Calc, SPIDAcalc or PLS-POLE), not computed here. The before-and-after clearance comparison with fault attribution in scenario 5 previews a pipeline that is planned, not built.Real functions this maps to:lookup_go95_table1_clearance, lookup_go95_table2_clearance, derive_setting_depth.Not modeled: wind and ice load cases, guying, transformer mounting clearance (separate construction-standard provisions, not a Table 2 conductor pair), pole-class strength tables, and cost allocation for make-ready or replacement.See also:Ground-clearance auto demo