Electrical Components & Equipment · US General Services Administration

SAM.gov Contract Awards Data

Datadory delivers sam gov contract awards data covering every US federal contract opportunity and award notice the General Services Administration publishes - isolatable to electrical purchases through Product Service Code group 61 and electrical NAICS codes - with award amounts, dates, awardee names and UEIs, set-aside designations and places of performance riding each row. Millions of notices, delivered daily, weekly, or hourly.

API, files, or your warehouse. Daily, weekly, or hourly.

Where it covers
United States federal government-wide - every civilian and military buying agency - with place-of-performance locations domestic and occasionally overseas
How far back
Active notices from the present back through multi-year archives; observed rows reach to at least 2006, and continuous series accumulate across delivery cycles
How fine
Individual notice and award level - one row per notice, filterable by PSC, NAICS, agency, set-aside and state

What is the SAM.gov contract awards dataset?

It is the American federal government telling you what electrical equipment it buys, from whom, and for how much - recorded by the buyer rather than inferred by an analyst. SAM.gov, the System for Award Management operated by the US General Services Administration, is the single authoritative registry for United States federal contracting: entity registrations, contract opportunities, and the award notices that close them. Every cabinet department, military service and independent agency that purchases wire, switchgear, relays or power-distribution equipment posts the requirement here and later records the outcome.

The registry reads two directions at once, and both matter commercially. Forward-looking, it is a pipeline: presolicitation and sources-sought notices surface requirements while they are still being shaped. Backward-looking, it is a ledger: award notices carry the obligated amount, the award date, the winning vendor's legal name and Unique Entity Identifier, and frequently a description paragraph stating exactly which equipment and installation work was bought - medium-voltage switchgear replacements appear in precisely that depth. Electrical purchases isolate cleanly along two axes: Product Service Code group 61 (Electric Wire, Power Distribution Equipment) and electrical NAICS codes such as 221121 (Electric Bulk Power Transmission and Control) and 335314 (Relay and Industrial Control Manufacturing).

Within Datadory's catalog - 1,744 datasets averaging 7.81 - the Electrical Components & Equipment slice holds 22 primary records and this one scores 8/10, ranking fifth on the best electrical components & equipment datasets list. Fifth is the honest slot: it is the only demand-side record on a shelf where everything else describes supply. Get a sample of this dataset scoped to the codes, agencies and states you sell into.

What do sample rows look like?

Three observed notices, shown as they arrive:

# award notice - the row that closes a buy, delivered shape
title            : Replace PWT Switchgear
solicitation     : FA9101-16-R-0034
notice_type      : Award Notice
psc_code         : 61 - ELECTRIC WIRE, POWER DISTRIB EQPT
naics_code       : 221121
publish_date     : 2016-06-24T13:36:00-04:00
award_amount     : 5432331
award_date       : 2016-06-15
award_number     : FA9101-16-C-0041
awardee_name     : Siemens Industry Inc.
awardee_uei      : JZXZSN3BBL98

# second award notice - same dictionary, medium-voltage scope
title            : Replace ETF-B Exhaust Medium Voltage Switchgear
solicitation     : FA9101-16-R-0069
publish_date     : 2016-11-17T17:43:27-05:00
naics_code       : 221121

# pre-award signal row - the requirement while it is still forming
title            : Z -- Repair Sectionalizing Station D
solicitation     : PR0705
publish_date     : 2006-09-11T00:00:00-04:00
notice_type      : Sources Sought
naics_code       : 238210

Read the anatomy rather than the values. The first row is a completed transaction: a titled requirement, its solicitation number, the classification pair that makes it findable (PSC 61, NAICS 221121), and then the settlement - $5,432,331 obligated, awarded 2016-06-15 to Siemens Industry Inc., keyed by UEI JZXZSN3BBL98. Money, date and counterparty on one row is what turns a notice feed into an account map. The second row shows the same dictionary carrying a different cut of scope - a medium-voltage exhaust switchgear replacement whose full description text rides the record even when award columns post later. The third row is the early-warning shape: a 2006 sources-sought notice, published while the requirement is still negotiable, which is the row a business-development desk wants to see first.

Placeholders appear where a column is filled at delivery scope - tell us the PSC codes, NAICS codes, agencies and states you sell into, and the sample returns those notices cut exactly to that frame.

Which fields does the dictionary define?

Fifteen documented fields, defined in the table below, and four of them do the structural work. psc.code and naics.code are the isolation axes - group 61 plus the electrical NAICS families - that reduce a government-wide registry to the electrical equipment trade. award.amount is the column that makes sizing arithmetic possible, and award.awardee.ueiSAM is the quiet hero: a persistent company identifier that survives renames and reorganizations, so ten years of switchgear awards roll up to the correct corporate winner without fuzzy string matching.

The prose field earns its width too. descriptions.content preserves the buyer's own statement of scope, which is where 'replace medium-voltage switchgear' separates from generic facilities maintenance - classification gets you to the aisle, description tells you what is on it. solicitation.setAside flags 8(a), HUBZone, SDVOSB and WOSB requirements, and placeOfPerformance geolocates the work. Additional fields on request: attachment references, points of contact and agency-office details are pinned against live records when your sample is cut, and column naming locks there.

Where does coverage run, and at what grain?

  • Geography: United States federal government-wide. Every civilian agency and military service buys through this registry, and place-of-performance values locate the work domestically - occasionally overseas where installations require it.
  • Temporal window: active notices from the present back through multi-year archives; the observed rows above reach to 2006, and continuous series accumulate across whatever delivery cadence you set.
  • Granularity: one row per notice or award, filterable by PSC, NAICS, agency, set-aside and state - nothing pre-aggregated, so an obligation-by-agency matrix or a year-over-year win-rate curve computes downstream with plain group-bys.

That footprint is why this record sits alone in its slice. Distributor catalogs describe what can be bought; economic censuses describe what was sold in aggregate; this is the only record in the industry pool where a specific buyer, a specific dollar figure and a specific vendor meet on one row - which is also why the best-in-industry ranking calls it the sole demand-side entry.

How is the data delivered through Datadory?

API, files, or your warehouse. Daily, weekly, or hourly.

Pick the channel your stack already speaks and set the cadence to match the decision being fed - hourly pulls for a bid-no-alerting dashboard, daily files sized for overnight CRM loads, or a direct pipe into Snowflake, BigQuery or Redshift. Cadence changes are a settings conversation, not a re-integration project.

Every delivery ships flattened to one row per notice with the dictionary above unchanged, typed columns throughout, and sample rows for validation - so an award table joins onto your CRM accounts on the UEI key at the first attempt instead of after a parsing week. Name your PSC codes, NAICS codes, agencies and states when you request the sample; it comes back cut to that exact shape before any commitment.

Who builds on it, and for what?

Ranked by how directly one row settles the day job:

  1. Federal pipeline development. Work the front of the registry - sources-sought and presolicitation rows inside PSC 61 - so pursuit begins while the requirement is still negotiable (data for sales growth teams).
  2. Win-rate and competitor analysis. Join awardee UEIs across years of switchgear, wire and relay awards to measure who holds each agency account, at what values, and where incumbency finally breaks.
  3. Set-aside market mapping. Split the electrical book by 8(a), HUBZone, SDVOSB and WOSB designation to see which requirements you can bid alone and where teaming is the only door (data for competitive intel and product teams).
  4. Bid pricing and market sizing. Anchor proposals and TAM models on realized obligated amounts for comparable equipment scopes rather than list-price guesswork (market researchers use cases).
  5. Territory planning. Rank place-of-performance geographies by obligation volume to place field service capacity where the work actually lands.

For contrast within the same shelf: the Digi-Key API (Product Information V4) answers what components cost and where they stock, while this record answers which arm of the federal government is buying, from whom, for how much - supply and demand, stacked.

Which personas get the most value?

Sales growth teams get the rarest artifact in B2B data: a demand list where the buyer, the budget and the incumbent sit on the same row as the requirement. Competitive intelligence teams get attributable wins and losses by agency, priced. Market researchers get a federal electrical equipment market sized from obligations under PSC 61 and NAICS 335, with set-aside splits most commercial sources never publish. Data scientists get typed columns and a stable entity key - the difference between a modeling afternoon and an extraction quarter. Investors and quants get obligated federal dollars as a dated demand signal for equipment makers and distributors. Across all of them the constant is the same: one dictionary, one row per notice, classifications that hold - so adding an agency or a state to scope is a filter change, not a schema migration. Persona-by-persona detail lives on the Electrical Components & Equipment data hub.

Which datasets sit next to this one?

This record reads best against the supply side it prices. The Digi-Key Electronics product catalog and the ECIA electronic component sales data describe what the channel stocks and how the trade is trending; this registry describes where the government's own electrical dollars land. The data.gov federal open data catalog is the wider discovery layer beneath it - hundreds of thousands of records, this one's home turf included. For a head-to-head, the SAM.gov vs Farnell comparison works the demand-versus-supply contrast in full.

Field dictionary

Every field below is documented against real records. The full dictionary ships with the sample.

Field dictionary - SAM.gov contract awards, one row per notice (definitions verified)
fieldtypedefinitionexample
noticeIdstringStable identifier for the opportunity notice - the join key that lets one requirement be tracked from presolicitation through award without name-matching.-
solicitationNumberstringThe government's own solicitation number for the requirement, quoted verbatim on every related notice.FA9101-16-R-0034
titlestringTitle of the opportunity or award notice as posted - usually the plain-language statement of what is being bought.Replace PWT Switchgear
type.codeenumNotice type code separating pipeline stages: r (Sources Sought), p (Presolicitation), a (Award Notice) among others.a
psc.codeenumProduct Service Code. Group 61 covers Electric Wire and Power Distribution Equipment - the primary axis for isolating electrical buys.61
naics.codeenumNorth American Industry Classification System code applying to the requirement - 221121 (Electric Bulk Power Transmission and Control) and 335314 (Relay and Industrial Control Manufacturing) are the electrical workhorses.221121
publishDatedatetimeTimestamp the notice was published, time-zone aware - the spine for pipeline-timing analysis between posting and award.2016-06-24T13:36:00-04:00
award.amountnumberObligated dollar value of the awarded contract - the column that turns a notice list into a market-size model.5432331
award.datedateDate the contract was awarded, letting posting-to-award lag be measured rather than guessed.2016-06-15
award.numberstringContract number of the resulting award - the identifier procurement systems and audits quote.FA9101-16-C-0041
award.awardee.namestringLegal name of the winning vendor, as registered.Siemens Industry Inc.
award.awardee.ueiSAMstringUnique Entity Identifier of the awardee - the durable company key that survives name changes and subsidiaries, so win-rate analysis joins on code instead of fuzzy strings.JZXZSN3BBL98
descriptions.contenttextFull description body of the notice, typically stating the scope of equipment and installation work - where 'medium-voltage switchgear replacement' lives as prose.switchgear replacement scope paragraph
solicitation.setAsideenumSet-aside designation on the requirement - 8(a), HUBZone, SDVOSB or WOSB - which determines whole classes of competitors eligible to bid.SDVOSB
placeOfPerformancegeoCity, state and zip where the work will be performed - the geography of delivery, not of the buying office.-

Coverage at a glance

dimensionvalue
GeographyUnited States federal government-wide, with place-of-performance locations domestic and occasionally overseas
TemporalActive notices from the present back through multi-year archives; observed rows reach to at least 2006
GranularityIndividual notice and award level, filterable by PSC, NAICS, agency, set-aside and state

What teams do with it

  • Federal pipeline development Work the front of the registry - sources-sought and presolicitation rows in PSC 61 - so pursuit starts months before dollars obligate rather than after the award prints.
  • Win-rate and competitor analysis Join awardee UEIs across years of switchgear, wire and relay awards to measure who actually holds each account, at what dollar values, and where incumbency ends.
  • Set-aside market mapping Split the electrical book by 8(a), HUBZone, SDVOSB and WOSB designation to see which requirements you may bid alone and where a partnering play is the only door.
  • Pricing and sizing benchmarks Anchor bids and market models on realized obligated amounts for comparable equipment scopes instead of list-price guesswork.
  • Territory and placement planning Rank place-of-performance geographies by award volume to decide where field service capacity and inventory actually earn their keep.

Questions buyers ask

What does sam gov contract awards data contain?

US federal contract opportunities and award notices from the General Services Administration's System for Award Management, delivered as one row per notice: title, solicitation number, notice type, PSC and NAICS classifications, publish date, and on award rows the obligated amount, award date, contract number, winner legal name and UEI, set-aside designation and place of performance.

How do I isolate electrical equipment purchases in the data?

Two axes do it. Product Service Code group 61 covers Electric Wire and Power Distribution Equipment, and electrical NAICS codes narrow it further - 221121 for Electric Bulk Power Transmission and Control, 335314 for Relay and Industrial Control Manufacturing. Filtered on either axis, the registry reduces to the federal electrical equipment trade specifically.

What is the difference between an award notice and a sources-sought notice?

Stage, not substance. A sources-sought notice appears while a requirement is still being shaped - the market-research row a business-development desk wants first. An award notice closes the loop, carrying the obligated dollar amount, award date, contract number and winning vendor. Both ride the same field dictionary, so pipeline and outcome analyze side by side.

Does the data identify which company won each contract?

Yes, twice over: the awardee's registered legal name and its Unique Entity Identifier. The UEI is the durable key - it survives renames and reorganizations, so multi-year win-rate and share analysis joins correctly instead of fragmenting across spelling variants of the same corporate winner.

How far back does the history reach?

Active notices from the present back through multi-year archives; the sample rows observed during the August 2026 research pass include notices published in 2006. Continuous longitudinal series accumulate naturally across repeated deliveries at whatever cadence you set.

What are set-aside designations and why do they matter?

They flag requirements reserved for specific vendor classes - 8(a), HUBZone, SDVOSB and WOSB. The designation decides which competitors are eligible to bid at all, so splitting the electrical book by set-aside shows which opportunities you can pursue directly and where a partnering strategy is the only route in.

Can a sample be scoped to my codes and agencies before committing?

That is what the sample is for. Name your PSC codes, NAICS codes, agencies, states and cadence, and Datadory returns rows shaped exactly like the dictionary above, cut to your book. The sample's schema is the shipped schema; the delivery decision comes after it validates.

Datasets that pair with this one

See the rows before you pay anything.

Name this dataset and we send real records from it — scoped to the fields you asked for.

See pricing