Power transformers · generators · gas and steam turbines

346-276-9540 tommy@jjtransformers.com

Technical guide · data-hall transformer packages

How to Specify a Transformer Package for a 10 MW, 40 MW or 100 MW Data Hall

A transformer package for a 10 MW, 40 MW, or 100 MW data hall cannot be selected from MW alone. The engineer must define service voltage, power factor, redundancy, load blocks, harmonics, motor loads, future growth, impedance, fault duty, BIL, cooling, losses, grounding, physical layout, utility requirements, ambient conditions, altitude, and maintenance strategy.

Load basis
IT MW vs total facility MW
Convert
MVA = MW ÷ power factor
Architecture
N · N+1 · 2N defined by cases
Output
One-line + equipment schedule
Jump to a section

Why is data-hall MW not enough to size transformers?

MW is real power. Transformers are rated in kVA/MVA and must carry current associated with real and reactive power. The hall’s MW label may represent IT load, critical load, or total facility load; it may exclude cooling, UPS losses, mechanical systems, future growth, redundancy, motor starting, harmonics, and operating reserve.

For illustration, 10 MW at 0.90 power factor is 11.1 MVA, 40 MW is 44.4 MVA, and 100 MW is 111.1 MVA—before topology, redundancy, margin, growth, harmonics, auxiliaries, ambient/altitude, loss, or equipment utilization decisions. These calculations do not select a transformer count or nameplate.

Define whether the power factor is displacement, true power factor including harmonics, or a utility/UPS guarantee. Use the load-flow and harmonic studies at the points where transformers are sized rather than applying one campus-wide number blindly.

Which inputs should be frozen before requesting transformer prices?

Freeze the load basis, phases, one-line, voltage levels, redundancy, and maintenance cases before comparing price. Also control power factor, harmonics, large motors and step loads, growth, fault duty, impedance targets, grounding, BIL, cooling, losses, site conditions, sound, fire and environmental criteria, footprint, terminals, access, standards, tests, documents, and dates.

Data-hall transformer package input schedule
Input groupQuestions to answerDesign output
LoadIT or total? Initial/future? PF/harmonics? motors? utilization?MVA and load blocks by phase
ReliabilityN/N+1/2N failure and maintenance cases? largest unit loss?Transformer count, rating and bus topology
VoltageUtility/POI, campus MV, building MV/LV, generator voltage?HV/LV/tertiary and equipment interfaces
StudiesLoad flow, short circuit, protection, harmonics, grounding, motor/transient?Impedance, BIL, vector, neutral, taps and protection
SiteAmbient, altitude, seismic, sound, fire, environment, access, route?Cooling, enclosure, fluid, footprint, terminal and logistics requirements
ScheduleNeed on site, first power, energization, phases, utility milestones?Procurement paths, alternates and delivery plan

Should a data center distribute at 13.8 kV or 34.5 kV?

Compare utility service and owner standards, campus MW density, feeder lengths, cable current and losses, fault duty, switchgear, transformer availability, protection, grounding, arc-flash, expansion, maintenance, civil routing, equipment footprint, onsite-generation voltage and lifecycle cost. Neither voltage is universally correct.

Higher distribution voltage can reduce current for a given MVA but changes insulation, BIL, cable, switchgear, transformer and work-practice requirements. The system study must compare the complete architecture.

How should a 10 MW data hall transformer package be structured?

Treat 10 MW as a planning label until the load basis is defined. The package may use several pad-mounted or dry-type transformers serving repeatable load blocks, with spare capacity or cross-ties according to the redundancy design. Main service transformation may be shared at campus level or dedicated, depending on the site.

A quote-ready schedule lists each transformer rather than one total: tag, duty, quantity, kVA/MVA, HV/LV, BIL, impedance, vector/grounding, taps, cooling/fluid, enclosure/feed, harmonics, site and date. Include normal and contingency loading by unit.

Do not divide 10 MW by a preferred 2.5 MVA transformer and call the count complete. Power factor, utilization, redundancy, UPS topology, mechanical loads, growth and loss/temperature conditions change the result.

How should a 40 MW data hall transformer package be structured?

A 40 MW hall typically requires an explicit medium-voltage and redundancy architecture rather than a single transformer-size answer. Define campus service, hall buses, repeated blocks, cross-ties, spare strategy, largest-unit outage, maintenance isolation, feeder limits, protection zones, physical layout, and phased energization.

At this scale, small differences in transformer impedance, guaranteed losses, sound, footprint, cable terminations, monitoring and spare strategy multiply across the equipment count. Use a comparison model that evaluates installed and lifecycle effects, not only purchase price per kVA.

If onsite generation is part of the plan, separate generator transformers/GSUs from campus load transformers. The generation plant may operate at a collector or plant MV level that must be coordinated with the campus design.

How should a 100 MW data hall or campus transformer package be structured?

At 100 MW class, the utility/interconnection, main substation, campus distribution, onsite generation, load blocks, contingency cases, future phases, spares, recovery strategy, and construction sequence must be modeled together. The package can span large power transformers, GSUs, auxiliary, pad-mounted, and dry-type units with different procurement paths.

The project should identify the point-of-interconnection voltage and capacity, main-transformer count and ratings, campus MV buses, generation operating modes, transformer outage consequences, transport routes, spare/recovery plan, protection zones, controls, and utility milestones before relying on online inventory.

Large power-transformer and GSU schedules can drive the critical path; repeated pad-mount or dry-type procurement can also create aggregate factory, approval and commissioning risk. Maintain a serial/model-level equipment register and interface matrix across every phase.

How do N, N+1 and 2N change transformer quantity?

Topology labels must be translated into defined normal, failure and maintenance states. Specify which source, transformer, bus, cable, switchgear, generator, control or common system can be out while the required critical load remains served, and at what utilization and duration.

A spare transformer in a yard is not the same as installed N+1 capacity; recovery time, transport, assembly, oil, testing, protection and commissioning matter. An installed cross-tie is not redundancy unless protection, capacity, operating procedure and common-mode failures support it.

How should UPS, PDU and power-electronics harmonics be specified?

Provide harmonic-current spectra and operating cases at each transformer, true/displacement power factor, neutral current, converter switching characteristics, expected future mix, point-of-common-coupling limits, ambient, cooling, and owner criteria. The responsible design then evaluates winding and stray losses, temperature rise, neutral, shielding, sound and derating.

Do not use “K-rated” as the entire requirement for a medium-voltage or large power transformer. IEEE C57.110 evaluation methods and IEEE 519 system distortion goals need the actual load and system context.

How should transformer impedance be chosen for a data hall?

Use short-circuit, load-flow, voltage-regulation, protection, motor/transient, UPS and parallel-operation studies. Lower impedance can raise fault duty; higher impedance can increase voltage drop and reactive effects. Specify percentage, MVA/kVA base, tap, reference temperature, tolerance and parallel-unit requirements.

How should transformer tags and interfaces be controlled across data-center phases?

Every transformer should have a unique tag tied to the one-line, equipment schedule, site plan, studies, submittals, procurement record, and commissioning record. The same controlled tag prevents a main substation transformer, GSU, auxiliary transformer, pad-mount, or dry-type unit from being compared against the wrong duty. Interface control becomes more important as campuses repeat blocks and add phases.

For each tag, maintain quantity, duty, normal and contingency loading, kVA/MVA and cooling stages, HV/LV/tertiary voltages, maximum system voltage, BIL, impedance and basis, winding connections, phase displacement, grounding, taps, fluid or insulation system, temperature rise, losses, harmonics, enclosure, feed arrangement, terminals, accessories, controls, alarms, dimensions, weights, location, condition acceptance, standards, tests, documents, and required dates.

Connect the transformer schedule to an interface matrix covering switchgear, cables or bus, protection, CTs, relays, arresters, grounding, neutral equipment, auxiliary power, SCADA, communications, foundations, containment, ventilation, fire strategy, access, transport, assembly, and field tests. When one interface changes, record which drawings, studies, civil work, quotes, and delivery assumptions require review.

  • Use revision-controlled tags and prohibit informal equipment substitutions based only on MVA and voltage ratio.
  • Keep base design, alternates, owner-furnished equipment, future phases, and spare units distinguishable in every schedule.
  • Assign an accountable owner and approval status to each electrical, mechanical, civil, controls, and commercial interface.

Which tests, documents, and spares should be standardized across a transformer package?

A campus-wide transformer package should use a controlled minimum document and test schedule while preserving equipment-class differences. Standardization helps procurement compare offers, helps engineering review interfaces, and gives operations consistent records. It should not force a pad-mounted, dry-type, substation, and GSU transformer into an identical test or accessory scope.

The document schedule can require rating and nameplate data, outlines, weights and foundation loads, terminal and compartment drawings, schematics, wiring diagrams, accessory data, controls and communications lists, loss and impedance guarantees, fluid data, bill of materials or included-scope list, test plans, certified reports, preservation instructions, shipping configuration, installation manuals, field-test guidance, spare-parts lists, and final as-built records. State format, review status, due milestone, and whether approval is required before manufacture or shipment.

Testing should follow the applicable equipment standard, purchase specification, design risk, and unit condition. Distinguish routine, design, special, type, witness, condition, and field tests. Define setup, rating and tap basis, tolerances, witness notice, preliminary results, certified reports, nonconformance handling, corrective work, and retest rules. For existing equipment, historical factory reports and valid baselines should inform which new tests are useful.

  • Evaluate common spares for bushings, fans, pumps, controls, relays, monitors, fuses, switches, connectors, gaskets, and other maintainable accessories only after compatibility is confirmed.
  • Define whether a spare transformer is installed, stored onsite, shared across phases, or only a procurement strategy, and record the restoration steps for each case.
  • Require serial- or model-specific final records so repeated units do not become mixed across tags during shipping, storage, installation, or commissioning.

How should procurement compare transformer package bids without losing technical equivalence?

Package bids should be normalized against one controlled equipment schedule and interface matrix. A lower total price is not comparable if ratings, losses, accessories, tests, freight, field work, warranty, or schedule milestones differ. Procurement should expose every variance before commercial selection.

Build one comparison row for each transformer tag and one column for every decision-critical requirement: quantity, duty, kVA/MVA stages, voltages, BIL, impedance and basis, winding connection, taps, cooling, fluid or insulation, losses, harmonics, enclosure, feed, terminals, controls, monitoring, standards, tests, documents, dimensions, weight, condition, origin, and required date.

Compare scope and commercial boundaries separately. Identify oil or fluid, bushings, coolers, fans, controls, spares, packing, freight, tariffs, offload, assembly, field testing, installation support, commissioning, warranty source, payment milestones, quote validity, exclusions, and buyer dependencies. Preserve technical exceptions as written deviations rather than allowing them to disappear inside a package total.

  • Use the same delivery milestone and Incoterm for every schedule comparison.
  • Assign engineering approval to technical deviations before scoring commercial value.
  • Carry unresolved scope as an explicit risk or allowance rather than assuming it is included.

What should the final transformer package RFQ contain?

Issue a controlled equipment schedule and one-line for every transformer tag. Include quantities, duty, kVA/MVA and cooling stages, HV/LV/tertiary, maximum system voltage, BIL, impedance/basis, vector/grounding, taps, fluid/insulation, temperature rise, losses/evaluation, harmonics, enclosure/feed, terminals, controls/monitoring, standards, tests, site conditions, dimensions/weights, documentation, need date, destination, condition acceptance and commercial requirements.

Availability is subject to prior sale, technical review, and written confirmation by J&J Transformers LLC.

Frequently asked questions

These answers explain the procurement and application questions buyers ask most often. Unit-specific ratings, availability, conformity, condition, price, and delivery are controlled by the written quotation and supporting documents.

What transformer size does a 10 MW data hall need?

Convert the approved load basis to MVA and apply topology, redundancy, blocks, harmonics, growth, site and owner criteria.

What transformer size does a 40 MW data hall need?

There is no single answer; determine count and block size from the one-line, reliability cases, voltage, studies and layout.

What transformer size does a 100 MW data hall need?

A campus-scale design must coordinate interconnection, main substations, distribution blocks, onsite generation, recovery and future phases.

How is MW converted to MVA?

MVA equals MW divided by power factor for a simplified case, but final selection also requires topology, harmonics, margin, duty and studies.

Should a campus distribute at 13.8 or 34.5 kV?

Compare utility service, load density, distance, current/losses, fault duty, equipment, protection, expansion and owner standards.

How many pad-mount transformers are required?

Divide loads into approved normal/contingency blocks; total MW alone cannot determine quantity.

How should UPS harmonics be handled?

Provide harmonic spectra and load profiles so heating, losses, neutral, shielding, sound and derating can be evaluated.

What impedance should be specified?

Use system studies to balance fault current, regulation, reactive behavior, protection and parallel operation.

Should future expansion be included?

Yes, as explicit phases and operating scenarios rather than hidden margin.

What is needed before requesting a package quote?

One-line, equipment schedule, load basis, voltage, redundancy, studies, site, documents, destination and dates.

CallRequest Quote