Research — Auto walkthrough (draft, unvalidated)

Station walk, auto

Sit back and watch a generic 230 kV station get checked. A compliant station is measured one group at a time, then five changes each break a check and get fixed: a higher insulation class pushes the fence out, a low stand is raised, a new road forces the bus up, and a new bus scheme needs more breakers. Pause any time or pick a story.

Story

Elevation · side view, drawn to scale in feet

Plan · same x axis, top view

Breaker bay · installed against required

Check being read

Actual

Required

Margin

How the harness read it

    All seven checks at this step · the controlling row is highlighted

    The controlling row is the first failing check, else the first tight one. There is deliberately no single station verdict.

    Regulatory-status note carried by the data (verbatim)

    Every check · before the change, after the change, after the fix

    A check reads "tight" when it passes with under 0.5 ft (6 in) of margin; that band is a display choice, not a code term. "Incomplete" means the dimension has not been entered, never a pass. The roadway card reads "n/a" when the scene has no road: that is scene state, not a harness result.

    Precomputed results:every verdict, required value and margin on this page was computed by the real Python harness at export time and is played back from a data file. The page runs no harness logic and holds no standards tables, and it never interpolates between exported values. Not a live API call. The usm-agent-harness is a draft: no substation design engineer has signed off on it, and nothing here is a compliance determination. Every verdict, required value, margin and citation was computed by calling those functions at export time (harness commit af9e873) and is played back from a data file. The station is a generic illustration: every geometry input, and all the gear drawn, is illustrative. The whole-station aggregate returned by validate_substation covers only 3 of the 7 walk checks, so it is shown for contrast and is never used as the station verdict.Real functions this maps to:check_substation_fence_height, check_substation_fence_clearance, check_substation_equipment_ground_clearance, check_substation_rigid_bus_phase_spacing, check_substation_roadway_overhead_clearance, check_substation_horn_gap_switch_spacing, check_bus_configuration_breaker_count, validate_substation.Not modeled: the other substation checks (grounding, transformer spacing, lightning shielding, oil containment and more), other fence exceptions, jurisdiction overrides of the NESC edition, and any real site data. The 2007-to-2023 NESC revision of the cited tables has not been ruled out, and whether the ANSI/NEMA Table 4-7 and 4-8 values fit the NESC-edition adoption model is an open question (the note is reproduced below).See also:Station walk, interactive · Fence clearance, auto sweep