Busway and bus duct systems for North American data hall builds sit at 20–36 weeks from major OEMs as of September 2026, with rating, fault duty, and tap-off density the main swing factors [S2]. That window is materially shorter than the 52–80 weeks that 15 kV class medium-voltage switchgear is commanding at the same OEMs, but it now sits on the same critical path as the upstream gear, so the PO clock has to start inside the design phase, not after it [S6].
Hyperscale and colocation operators are running parallel procurement tracks for busway, MV/LV switchgear, transformers, and UPS modules, and the equipment set that arrives last is the one that sets the energization date [S3]. A typical 2026 data hall project runs 18–36 months of vertical construction, but the 4–9 month busway window plus 6–12 month switchboard window routinely overrides the architectural schedule [S4].
What 20–36 weeks actually means in the field
Schedules blow out beyond that range when the spec includes nonstandard IP ratings, seismic certification beyond UBC Zone 4, integrated monitoring CTs on every joint, or factory pre-assembly with custom tap-off boxes for a specific rack layout [S2][S3].
The 20-week floor assumes a clean repeat of a previously built configuration. New fab lines and joint designs that have not been built before at the named rating commonly add 6–12 weeks, and copper-tariff-driven raw material volatility continues to add quote-to-PO slippage that the buyer cannot see until the order acknowledgment lands [S2]. A busway spool is shorter than a transformer or an MV breaker, but its delivery is gated by the same OEM scheduling system, which means a Tier-1 data center order placed in Q4 2025 can still be sitting in the queue behind a 2026 hyperscaler blanket agreement [S2].
Comparison: busway vs MV switchgear vs transformer vs LV switchboard
The clearest way to read 2026 lead times is to put the four gating items on one line. The data hall cannot take load until the last of these lands, and the last one is rarely busway: Standard panelboards sit at 28–48 weeks from major OEMs (16–24 weeks at tier-2 houses), standard LV switchboards with MCCB incomers run 52 weeks, power circuit breaker switchboards with ACB incomers run 84+ weeks, MV switchgear at commercial spec runs 52–78 weeks, MV switchgear at data center spec approaches 2–3 years at peak demand manufacturers, busway/busduct runs 20–36 weeks, and motor control centres sit at 26–40 weeks [S2]. Medium-voltage gear at the 38 kV class stretches further, with 38 kV equipment running on similar extended cycles during the same window [S6].
Translated into procurement sequencing for a 100 MW campus phase: the MV switchgear PO is the gating order, the LV switchboard PO follows 4–6 weeks later inside the same release window, the transformer PO goes in parallel, and the busway PO is placed 8–12 weeks after switchgear because the busway one-line depends on the switchgear breaker layout and tap-off coordinates [S1][S3]. The 20–36 week busway window then arrives in time to support the same energization date as the upstream gear, but only if it was released on time.
Standards and product classes that drive the spec
At low voltage, busway is typically specified against UL 857 (busways and associated fittings) in North America, with the adjacent switchgear lines that the busway feeds commonly built to UL 1558 for metal-enclosed low-voltage power circuit breaker switchgear and UL 891 for switchboards [S1]. Picking the wrong product class costs both dollars and weeks: a switchboard quoted against a switchgear one-line can fail short-time withstand testing, and a busway section rated for a 65 kA fault on paper will not pass witness test if the upstream breaker cannot deliver that duty.
For data hall overhead distribution, the three common architectures are plug-in busway (800–1600 A) running down the aisle with rack-mount tap-off units, feeder busway (2000–6300 A) running from the LV switchboard to the PDU, and a hybrid where a high-amp feeder drops into a row of plug-in sections. The 2026 supply pattern favors the plug-in architecture because it maps cleanly onto the modular white-space build that hyperscale operators are repeating across multiple campuses, which gives Tier-1 OEMs a known quantity to schedule production against [S3][S9].
Who busway lead times actually impact, and who they do not
Busway lead times in the 20–36 week band matter intensely to the general contractor, the electrical subcontractor, and the owner’s project manager, because every week of busway slip is a week of dark white space and unbilled IT load. They matter less to the rack-and-stack commissioning crew, who show up after the busway is energized, and to the network and security teams, whose scopes do not depend on the busway landing date. If your scope is commissioning a tenant fit-out, the busway schedule is someone else’s problem; if your scope is energization, it is the single item on your critical path that no one else can shorten. [S3]
For a tenant taking 2 MW of white space inside a shell that the landlord built, the busway order is already placed and the question is delivery date, not lead time negotiation. For a build-to-suit hyperscaler, the order is the project’s gating decision and the lead time has to be written into the master agreement as a fixed number of weeks from confirmed PO, with liquidated damages that match the actual revenue at risk per week of dark megawatt [S2].
Failure modes and field constraints that override the schedule
The published 20–36 week window assumes the design is frozen at PO. On real projects, the busway one-line typically shifts after the upstream LV switchgear breaker layout is finalized, which happens 6–10 weeks into the switchgear build, and a tap-off count change at that point resets the busway clock rather than absorbing into it [S1][S3]. Order acknowledgment documents that look like confirmations are in practice reschedule notices, and the field crew is the one that absorbs the impact.
Field constraints add their own time: busway sections over 3 m require crane access to the data hall slab, joint torquing and insulation testing run 2–4 weeks per floor of distribution, and integrated monitoring (branch CTs, thermal sensors at every joint) adds commissioning time on top of mechanical install. The plan for 4–9 months from PO to first rack energization has to be built with that installed-system time on top of the 20–36 week factory window, not instead of it [S1][S3].
Sourcing signals and what to track next
Three trackable signals will move busway lead times in the next two quarters: domestic busway fabrication capacity additions (the FabTek model of pulling substation steel, bus duct, and enclosure scopes into one ISO 9001:2015 quality system is a direction Tier-2 shops are watching, and U.S.-based capacity is the lever that pulls lead time down on the North American market) [S3]; copper tariff rulings, which the data center supply chain has been routing around through forward buys and quoted material escalators, and which a single Section 232 outcome can change [S2]; and OEM allocation releases, since the Tier-1 busway manufacturers (Siemens, Schneider Electric/Square D, Eaton, ABB, GE, and the Asian OEMs that supply U.S. data hall integrators) prioritize hyperscaler blanket agreements first, with the residual capacity setting the price for everyone else [S2][S3].
Track busway lead times on the same weekly cadence as the LV switchboard and the upstream MV switchgear, and treat any one of those three moving out by 6+ weeks as a project-level event that triggers a re-pull of the energization date. Related reading on adjacent supply pressure is in NEC 2026 cable plant cost signals and on the heavy-lift freight that follows the busway onto the slab in breakbulk and heavy-lift capacity for transformers. For the upstream MV gear that defines the busway one-line, see VCBs at transmission voltage in 2026.
The underlying component specifications are covered under busway, data logger, and lead screw.