Conductor Power

Travis Leanna, PE, is the Director of Energy Storage at Conductor Power, where he serves as the technical authority and strategic lead for utility-scale battery energy storage systems (BESS). With over 15 years of engineering in the energy sector and a decade focused on renewable energy, he guides BESS projects across the full EPC lifecycle—from feasibility and technical specifications to safety compliance and field execution—advancing Conductor Power’s mission of Constructing America’s Energy Infrastructure™.

Single-line diagrams and site plans never show the friction that actually derails a battery storage schedule.

On drawings, everything looks clean: enclosures sit in straight rows, inverter skids have plenty of clearance, and medium-voltage home-runs route straight to the substation.

Then the equipment lands on gravel, and the real job begins.

A conduit stub-up poured two weeks ago misses an enclosure penetration by two inches. The central plant controller can’t pull basic telemetry from the BMS because a vendor’s latest firmware build tweaked the Modbus register map. Meanwhile, the local fire marshal visits the job trailer and asks for wider turning radii that nobody flagged during preliminary civil reviews — right as grading crews cut access roads.

In utility-scale storage, project margins rarely get wiped out by bad cell chemistry. Lithium ion is proven, tier-1 OEMs build solid hardware, and developers are moving fast to hit aggressive commercial operation dates. The real risk is interface friction. When multiple specialized packages move in parallel—battery containers, inverters, switchgear, foundations, and utility controls—small coordination gaps compound fast.

How can these delays be mitigated? Proactive alignment long before equipment ships. That is where an EPC adds real value: sitting at the center to tie owner requirements, vendor boundaries, engineering, and constructability into a build plan that works.

The High-Risk Interfaces

When storage projects slip on cost or schedule, the trouble almost always traces back to a few specific integration points:

1. The Physical DC-to-BOP Boundary

A utility-scale BESS is part factory product, part heavy civil and electrical work. The OEM supplies self-contained DC enclosures with internal thermal loops, venting, and safety systems. At the same time, Balance of Plant (BOP) crews are pouring foundations, pulling 34.5 kV feeder cables, and setting pad-mount transformers.

Problems crop up where these packages meet. If an OEM tweaks base channel details late, or auxiliary loads aren’t nailed down during design, the site team wears the cost. Missing a stub-up location sounds minor on paper. On site, it means concrete coring rigs, re-pulling and terminating heavy feeders, and paying crane rental minimums while crews wait on revised drawings. That isn’t a defective product; it’s an engineering coordination gap.

“We treat the facility as an integrated power plant, not just vendor skids dropped on a pad.”

2. Digital Integration and Grid Interconnect Compliance

Treating commissioning as a brief final step before COD is a sure way to blow a schedule.

A modern BESS functions like a utility-scale computer tied directly into a dynamic grid. It isn’t just about getting the BMS, inverters, and site EMS to talk over internal protocols like Modbus or DNP3. The bigger hurdle is satisfying utility plant controller (PPC) requirements, IEEE 2800 grid standards, and dynamic model validations (such as PSCAD and PSSE) during trial operation.

When vendor control logic doesn’t match utility dynamic response models, or firmware updates alter register mappings, functional testing stops cold. Having test crews and commissioning engineers idle on site while control specialists troubleshoot models and patch code over cellular hotspots quickly burns through project contingency.

3. Balancing Layout Density, Safety, and O&M Access

There is always pressure early in development to pack maximum megawatt-hours onto minimal acreage to control civil costs. Squeezing container spacing down to the bare code minimum, however, creates serious field headaches.

Crews need physical clearance to set heavy equipment safely during construction. Local fire departments need designated access lanes and staging areas. Asset owners must maintain that equipment for twenty years. If a technician can’t pull an inverter module or get a service truck up to an HVAC chiller, upfront land savings turn into an ongoing operating expense.

How the EPC Drives the Coordination

Solving these issues means treating cross-discipline coordination as a core engineering responsibility from day one:

• Lock Down Interface Control Documents (ICDs) Early: Interface documents cannot be treated as contract boilerplate. Storage engineers need to sit at the table during procurement to nail down exact physical dimensions, conduit entry windows, auxiliary loads, and communication points before equipment enters manufacturing.

• Standardize the Boundaries: Trying to force every project to use the exact same battery enclosure doesn’t work with today’s supply chains. Instead, standardize the boundaries. Setting consistent medium-voltage termination points, standard inverter skid layouts, and proven network architectures allows equipment to adapt without tearing up civil and structural designs.

• Bridge Interconnect Studies with HIL Testing: Don’t wait for energization to discover grid compliance mismatches. The EPC coordinates upfront between OEM controls, utility interconnect requirements, and dynamic models (PSCAD/PSSE). Running HIL simulation and Factory Acceptance Testing (FAT) on the integrated control stack lets engineers benchmark transient response, grid-code compliance, and signal handshakes in a digital environment months before site commissioning.

• Coordinate Early with Local AHJs: Engaging local code officials and fire departments during early civil design prevents late-stage surprises over access roads, turning radii, or water supply connections.

At Conductor Power, this is how we execute utility-scale energy storage. We treat the facility as an integrated power plant, not just vendor skids dropped on a pad. When the EPC actively coordinates between developer targets, OEM requirements, and field realities, interface friction gets resolved on drawings and in test labs—not out on the gravel.

Closing the Gap

Battery tech will keep improving, but cell density won’t save a project with blown interface deadlines. The difference between hitting COD on schedule or burning through contingency comes down to how much work gets done before the first truck rolls onto site. When the EPC drives that coordination early, the gap between design theory and field reality closes fast.