Find the Electric Utility That Operates the Asset

A supplier finds a holding company in a news release, adds it to a target list, and calls it the utility. That shortcut can send a substation proposal to the wrong team. The company that reports customers, the company that owns the parent brand, and the organization that issues a purchase order may have different names. Start with the operating footprint, then test the corporate and purchasing relationships.

Start with an operating record

The Energy Information Administration’s Form EIA-861 data gives suppliers a useful first pass. Its “Utility Data” file records activities such as generation, transmission, distribution, wholesale marketing, and retail marketing. Its “Service Territory” file lists counties and states where a utility has equipment to distribute electricity to final customers. These fields answer different questions. An entry that sells power does not, by itself, show that it maintains local wires. A service-territory county does not identify every substation or the office that buys equipment.

Download the latest available annual files and record the reporting year beside each conclusion. Search for the operating name and likely variants. Keep the EIA utility identifier with the record so a later name change does not break your work. Then check whether the entity reports distribution, transmission, or another activity relevant to your offer. For a distribution automation supplier, the distribution field is more useful than a parent company’s consolidated customer count. For a transmission hardware supplier, it is a screening clue, not proof that the entity owns a particular line.

The annual release includes a mergers file and a service-territory file. Use both when an old procurement document names a utility that no longer appears in your current list. Keep a dated note such as “reported distribution in the 2024 EIA-861 file” instead of calling the data a live operating map. The EIA page labels the time frame for each file, and some records use the short Form EIA-861S. That matters when you compare entities of different sizes.

Build four separate name fields

Create four columns: operating utility, parent or holding company, asset or service area, and purchasing entity. Leave a column blank until a source supports it. EIA helps with the first and third columns. It does not certify a company’s purchasing authority. The distinction is visible in the public presence of PG&E Corporation and Pacific Gas and Electric Company: the corporate and customer-facing names point to related, but distinct, entities. That example is a prompt to verify legal names, not a claim about which team buys a given item.

Use the operating utility’s regulatory filings, corporate structure pages, and supplier site to fill the remaining fields. PG&E’s purchasing page, for example, describes a supplier profile and prospective-supplier requirements. It is a different source and purpose from EIA’s operating survey. The registered supplier name, contracting company, and field user should each be checked against the specific opportunity.

Turn the identity work into a sales decision

Suppose your team sells feeder sensors in a county that appears in a utility’s EIA service-territory file. A sensible next step is to check the utility’s distribution plan and supplier rules. It is not yet sensible to claim that a named feeder needs sensors, that a capital budget is approved, or that a bid is open. The EIA territory field establishes a county-level presence for distribution equipment; it does not supply a project list.

For each target, write a one-line evidence chain: “Entity A reports distribution in county B in Form EIA-861 for year C; source D names its parent; source E describes supplier registration; purchasing responsibility remains to confirm.” This sentence prevents a common database error: filling every field with one brand name. It also makes research easy to update when a merger or procurement change occurs.

A useful target record includes the EIA reporting year, utility identifier, operating activities, service-territory counties, parent source and date, and procurement source and date. Add a confidence note for each relationship. If two entities share a brand but have separate utility records, preserve both rows until you can verify the buying path.

The result is a cleaner call list. Sales can discuss the right operating system. Product staff can match an offer to distribution or transmission work. Procurement staff can check the correct registration path. If you need a researched account map for a market, discuss the research scope with ElectricUtility.ai.