Research — Auto Demo · Precomputed (draft, unvalidated)

Vault sizing and cable training — auto

No controls here: five short stories play on their own. A small vault takes up to eight conduits. A switch makes the sizing function's own pick fail working clearance. A fifth conduit overflows four ports. A bigger cable makes a loop the vault cannot hold. A higher voltage class leaves no catalog vault that passes. Use Pause, or the story and step buttons, to stop on any frame.

Story

The request · what the sizing function recommends and what is drawn

Vault cutaway · isometric, feet

Plan · true scale, 1 ft grid

Harness catalog · common scale · C = working clearance, B = loop fits

Not a standard: the harness's own vault list. The outlined one is drawn above; the star marks the sizing function's pick. Dashed circle: the cable loop at its minimum radius.

Cable training · does the loop fit?

Every check at this step · the controlling row is highlighted

Source column: harness = a real harness function; demo logic = the exporter's own rule. None of these limits is a published standard here.

How the checks read it

What to know before trusting these numbers

  • Draft code. 'This is a starting inventory from the 2026-07-18 extraction/audit, not a completed review -- nothing below has had human or SME-agent sign-off yet.' Standards ingestion: 'Not started'. Ported calculation services (including vault sizing): 'Not reviewed -- inherited as live production code, predates this guide's process'. Ported calculation services: not reviewed, inherited as live production code. Standards ingestion: not started.
  • The vault list is the harness catalog, not a standard. A code comment calls it "ANSI standard" with no source; this page does not repeat that.
  • The two functions disagree. With equipment the sizing function only widens the plan size; it ignores the equipment projection and headroom, so its pick can still fail the working-clearance function. At 34.5 kV with the 3 ft switch no catalog vault passes.
  • Illustrative inputs. The splice (0.5 ft) and switch (3.0 ft) projections are the exporter's numbers; the harness has no footprint for either. The 6.5 ft headroom, the 12 x OD bend multiplier and the congestion bands have no cited source, and the NEC 110.34 label on the working-space table is a code comment that was not verified.
  • Demo logic, not harness. "The loop fits" (loop diameter against the smaller plan dimension minus the equipment) and "over 100 percent" (conduits above ports) are the exporter's rules. Port positions are not exported; the port grid is a visual layout.

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

Required values are read from the data file. The vault list is the harness catalog, not a standard. The bend and over-capacity verdicts are the exporter's own rules (demo logic); the sizing and working-clearance rows are harness functions. A row marked value is a number the function returns with no verdict.

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. Precomputed by the real functions recommend_vault_size, check_working_clearances, calculate_minimum_bending_radius and calculate_vault_conduit_utilization in uvm-agent-harness (commit a267697); the tests are 17 internal self-consistency checks, not a standards check. Harness maturity, verbatim from its VALIDATION.md: 'This is a starting inventory from the 2026-07-18 extraction/audit, not a completed review -- nothing below has had human or SME-agent sign-off yet.' Standards ingestion: 'Not started'. Ported calculation services (including vault sizing): 'Not reviewed -- inherited as live production code, predates this guide's process'. Standards ingestion: Not started. The vault list (HH-1 to MH-5, PB-1, PB-2) is the harness catalog, not a standard; a code comment calls it ANSI standard but cites no source, so this page does not. The working-space table is labelled NEC 110.34 in a code comment but was never ingested or checked against the standard; the 6.5 ft headroom, the 12 x OD bend multiplier and the 50 / 75 / 90 percent congestion bands have no cited source. Equipment is a generic splice (0.5 ft projection) or switch (3.0 ft) chosen by the exporter because the vault functions take only a depth number: both sizes are illustrative. The fit verdict for cable training and the over-100-percent fail on utilization are the exporter's own rules (demo logic), not harness functions. The scripted choice of which bigger vault to try is demo logic. Conduit port positions are not exported, so the port grid is drawn only as a visual layout.Real functions this maps to:recommend_vault_size, check_working_clearances, calculate_minimum_bending_radius, calculate_vault_conduit_utilization.Not modeled: conduit sizes, duct-bank geometry or port positions, cable racks and supports, training of more than one circuit at once, ladders and manhole necks, groundwater and structural loading, and any standards-based vault size or working-space rule. Vault wall thickness, equipment height and width, and the bundle width are drawing choices.See also:Vault sizing, interactive with free play · Cable pull, hands-off · Conduit fill, hands-off