POWERING THE BUILDOUT SERIES
By Libra CEO Andrew Williams
The grid is being rebuilt on a schedule nobody planned for. Data center load, electrification, and the replacement of infrastructure installed two generations ago have put protection relays, switchgear, transformers, monitoring devices and substation automation on lead times that would have been unthinkable five years ago. Every manufacturer in that supply chain is being asked to deliver more, faster.
Underneath that demand, something quieter changed. For years, buying American was an incentive; a bonus you chased if the economics worked and skipped if they did not. That is no longer an accurate description of the landscape. Domestic content has become a condition of the sale in several different rulebooks, and increasingly something you have to prove on paper rather than assert.
It is also not arriving alone, which is the part worth understanding before the next RFQ.
Three rulebooks pointing the same direction
- Build America, Buy America. Federally funded infrastructure work, including grid programs, carries a preference for manufactured products produced in the United States. Utilities and integrators spending those dollars do not absorb that requirement. They pass it to the equipment they buy, and the equipment makers pass it to their suppliers.
- Clean energy credits with conditions attached. The technology-neutral production and investment credits, and the advanced manufacturing credit alongside them, now restrict material assistance from prohibited foreign entities. Qualifying turns on what share of a product’s direct costs came from outside those entities, and the bar steps up year over year rather than holding still.
- A credit for building power electronics here. Inverters sit on the eligible component list for the advanced manufacturing credit. The policy intent is not subtle: produce power electronics domestically rather than import them.
- Cost volatility on the offshore path. Trade policy has made landed cost a moving number in a way domestic sourcing is not. For a manufacturer quoting fixed prices against multi-year infrastructure awards, that variability is its own argument.
And a second flow-down arriving at the same time
Origin is not the only thing utilities are now required to ask about. Under the NERC CIP supply chain standard, utilities procuring cyber systems for their high and medium-impact bulk electric system facilities must build specific vendor obligations into their procurement processes: notification of vendor-identified incidents, disclosure of known vulnerabilities, verification of software integrity and authenticity for software and patches, controls around vendor remote access, and coordination of incident response.
That standard applies to the utility, not to the supplier. But an obligation on a utility becomes a clause in a purchase order, and a clause in a purchase order becomes a question on your side of the table. A relay, an RTU, or a monitoring device carrying firmware into one of those facilities is squarely in scope.
So a grid equipment manufacturer is now fielding two documentation demands from the same customers, often in the same package: where was this built and what went into it, and how was this supply chain controlled and how would we know if something changed. Different rulebooks, different origins, entirely different intent. Both answered with records that come from suppliers.
The requirement travels down the supply chain
This is the part that changes a procurement conversation. These rules land on the party claiming the credit or holding the contract, but that party cannot satisfy them alone. Compliance is calculated from the direct costs of what went into the product, which means it is assembled out of what suppliers are able to state, document, and stand behind. The interim guidance issued to implement it builds the practical mechanism around exactly that: certifications from suppliers about the origin of what they provided.
So an obligation that reads as tax or contract compliance at the top of the chain arrives at the board shop as a documentation request. And it is a request not every supplier can answer. A board house that cannot tell you, on paper, where an assembly was manufactured and what went into it is not a cheaper option that needs a little paperwork. It may be an option that cannot be used for the award at all.
That reprices supplier relationships in a way unit cost never captured. The comparison is no longer board price against board price. It is board price against board price plus the risk of not being able to certify the finished product.
Where the electronics sit
Grid and power equipment is usually described by its heavy content: the tank, the breaker, the core and coil. The intelligence, and a growing share of the value, is on boards:
- Protection and control. Relay boards, control modules, and the panels they live in.
- Regulation and excitation. Voltage regulator and excitation control electronics, and the genset control boards adjacent to them.
- Condition monitoring. Dissolved gas, bushing and partial discharge monitoring; product lines that are board-level electronics end to end enclosure included.
- Substation automation. RTUs, gateways, and the communications boards that make a substation legible from a control room. These are also the assemblies most likely to sit inside the cyber supply chain scope described above.
- Converter and drive control. Gate drive, interface and control electronics inside inverters, medium-voltage drives, and UPS systems.
- Harness and control-panel box-build. The wired, tested panel and the interconnect between it and everything else.
What the documentation must do
It is worth being concrete, because traceability is a word that gets used loosely. The record must identify the facility where an assembly was built, not just the company that sold it. It has to hold at the component and lot level, because the calculation runs on what went into the product rather than on the product. It has to be producible on request months or years later, by someone who was not in the room at the time. It must extend to who could change the firmware and how a change would be detected. And it must be consistent enough that a customer can roll it into their own certification without redoing the work.
None of that is exotic. It is ordinary discipline applied every day rather than reconstructed when somebody asks, which is the whole difference, and the reason it cannot be added to a supplier relationship retroactively.
The honest segmentation
Not every board in a piece of grid equipment needs to move, and a credible partner will say so. Design-stable, high-volume content that will never touch a federally funded or credit-linked program may reasonably stay where it is. What earns attention first is the content most likely to land inside an award with documentation attached: protection and control assemblies, monitoring devices sold as complete units, anything carrying firmware into a substation, and anything headed to a utility customer whose own funding carries conditions.
What to look for in an electronics partner
The technical bar has not moved: IPC Class 3 workmanship, traceability to the component lot, test discipline that proves a board before it reaches an assembly, and documentation a customer’s quality team can audit without translation.
What has been added is a second bar that is administrative rather than technical: the ability to state clearly where an assembly was built, to support a customer’s own certification with records rather than assurances, to answer questions about firmware handling and change control, and to keep producing that evidence as requirements tighten. Manufacturers who already work to defense and aerospace documentation standards tend to find this bar familiar. It is the same discipline, pointed at new questions.
Libra Industries builds protection and control boards, monitoring and instrumentation electronics, substation and RTU assemblies, harness and control-panel box-build — and the integrated panels and enclosures around them — from Dallas, Texas and Dayton, Ohio, to the standards our defense and aerospace customers hold us to every day. If a program in front of you is going to require this on the record rather than in principle, that is a conversation worth having early, while the supplier list is still open.
