TAA-Designated Rack PDUs for Federal Server Rooms

The Trade Agreements Act question is about origin, and it has a specific shape. Under FAR 25.003 an end product qualifies if it is wholly the growth, product or manufacture of the United States or of a designated country, or if it was substantially transformed in one of those places into a new and different article of commerce with a name, character or use distinct from what it was made from. "Designated country" is itself four lists rolled into one term — the WTO Government Procurement Agreement countries, the free trade agreement countries, the least developed countries and the Caribbean Basin countries — and the composition of those lists is exactly the part that changes over time. As of August 2026 the FAR text published on acquisition.gov reflects FAC 2026-01, effective 13 March 2026. Treat any list you have saved as a snapshot, and confirm the current one at acquisition.gov or through GSA's own designated-country lookup before you rely on it in a determination.

What the designation on a catalog title does not do is settle the other compliance questions in the same order. It says nothing about NDAA Section 889, which is a different statute asking a different question and carrying no dollar threshold whatsoever: it applies at every acquisition value, including micro-purchases and commercial off-the-shelf items, and it names specific entities — Huawei, ZTE, Hytera, Hikvision and Dahua, with their subsidiaries and affiliates — rather than countries. A unit built in a designated country by an unrelated manufacturer answers the origin test and has nothing to do with the covered-entity test; a unit that clears the covered-entity test may still have been made somewhere that is not on the FAR 25.003 lists. Nor does the designation speak to encryption validation: where a networked PDU's management interface has to meet a cryptographic requirement, that is a NIST Cryptographic Module Validation Program question answered by looking the specific module up on csrc.nist.gov, not by reading a product title.

The four PDU tiers are a ladder of questions you can answer from your desk, and the origin clause tends to bite hardest at the top of it. A basic unit distributes outlets behind a breaker and nothing more, which in a comms cupboard somebody visits anyway is genuinely the whole requirement. A metered unit puts the circuit's load on a display at the rack, which is what stops a cabinet being filled until something trips. A monitored unit puts that reading on the network, where a threshold can raise an alert and a load history makes capacity planning possible. A switched unit adds per-outlet control, and its value is measured in trips not taken — a cage, an unstaffed edge site or a building across a campus pays for one the first weekend it saves a drive. The reason the clause matters more as you climb is that the networked tiers are where the part numbers proliferate: a vendor will carry near-identical monitored units differing only in inlet and origin, and the designated one is not always the one that comes up first in a distributor search.

Two planning notes save most of the rework on a federal rack build. Dual-corded equipment wants two feeds from two circuits, which means PDUs in matched pairs with the load balanced so either side can carry the rack alone — and if the order carries an origin clause, both halves of that pair have to satisfy it, which is a detail that gets missed when the second unit is added late. And the convention of loading a continuously loaded branch circuit to roughly eighty percent of its rating is a facility question to settle with your electrician against the actual circuit, breaker and local code, not something to infer from a product page. Send the rack elevations, the circuits the room provides and the equipment list, and the PDUs, the racks and cable management, the upstream power and any monitoring licensing can be quoted together on one document with lead times attached.