A copy of the records on contracts.ocp.dc.gov, the website where DC's Office of Contracting and Procurement publishes contracts, purchase orders and payments, as we pulled them. About this source. Not a complete record of District contracting or spending.
Vendors with contracts or purchase orders at many agencies, and products named in contract titles at more than one agency. Where several agencies buy the same thing separately, one citywide purchase might cover them.
These are counts of what DC's site lists. They can't show whether a single purchase would have been cheaper, or possible.
One row per vendor name exactly as spelled on DC's site (why names aren't merged). Click ▸ for each agency's contract titles and orders; click a heading to sort, and hover it for what it counts. One vendor at many agencies doesn't mean one product. Some of the vendors with the most agencies are resellers of many makers' products (Carahsoft's contract titles name Salesforce, Dell, Splunk and Microsoft, among others). Read a row's titles before treating its spread as one purchase repeated.
Type a product or brand name to see every contract whose title contains it, by agency. Read the titles before counting anything.
Each agency types its own titles, so a product may be spelled several ways (try a shorter word), and a word can match a title about something else. Purchase orders have no title on DC's site and can't be searched by product; the second table matches the text against the supplier name on orders instead, which answers a different question.
DC's site doesn't standardise vendor names. One company can be "CDW GOVERNMENT LLC" on a contract and "CDW GOVERNMENT INC" on an order; each spelling is its own row above. A contract's vendor and an order's supplier are joined only when spelled exactly alike, capitals included. Supplier names on orders stop at a fixed length ("Mary's Center for Maternal and Child Car"), so a long name on an order won't match its contract spelling.
This repository has a file of vendor-name merges, vendor_aliases.yaml, that isn't used here. Its merges
come from a mechanical rule (strip punctuation and endings such as INC, LLC and CORP, then group names that come out the same), are
recorded only for one set of technology payments, and cite no source. (Each agency-name fix in agency_names.yaml cites the
source that ties the two names together.) A rule like that can join two different companies. To group spellings yourself, type part of
a name in "Name contains": the box under it totals every matching spelling, counting each agency, contract and order once.