Home / Resources / Case Studies

Resources

Case Studies

Every project starts with a problem the catalog can’t solve. See how utilities and commercial & industrial operators worked with our engineers to define the challenge, build the solution, and measure what changed on the grid.

Filter:

Filter by Industries

Industry

39 results

Case Study

Government Agency Bridge Upgrade

Challenge:An inland waterway bridge built in the 1950’s was in serious need of an upgrade. It was originally constructed as a two lane bridge but upgraded to four lanes in the 1960’s. The electrical…

Case Study

Automatic Fault Isolation

CHALLENGE:As part of an extensive effort to reduce system outages and increase service reliability, a government agency is in the process of converting all overhead distribution lines to underground. At the same time, the…

Case Study

Three Phase Protection – Oil Fuse Cutout Replacement

CHALLENGE:The university added new buildings which required three phase protection. The existing service is an older underground system utilizing oil fuse cutouts here overcurrent protection was required. The university has a long-term plan to…

Case Study

Utilities

G&W Electric Strategic Energy Management

G&W Electric designs and provides power grid solutions for commercial and industrial consumers. G&W Electric joined the ComEd Strategic Energy Management (SEM) program in 2020 to build internal, technical and organizational capabilities to save…

We start with the diagnosis, not the datasheet

Engineered to order means the specification comes from the site — footprint constraints, flood exposure, the automation platform already in service, the crews who will maintain it. Our application engineers work the problem with your team before anything is built.

These case studies are the record of that work: what was constraining the network, what was engineered in response, and what the utility measured afterward.

Engineered to order. Built to last.

Engineered for your grid, not off the shelf

Working through a footprint constraint, a submersibility requirement, or an SF6 transition of your own? Start with an application engineer, not a catalog.