Operator context
PHMSA annual report data ↗
Annual operator-reported material, mileage and installation-date context.
Limit: Preserve report year and file version. No live telemetry, safety diagnosis or installed vendor identity.
Proposed gas distribution research
Primary-source lenses, a defined gas distribution scope and a visible method for dates and unknowns.

Proposed scope covers US investor-owned LDCs, municipal systems and gas subsidiaries of combined utilities. Resolve the entity and jurisdiction before comparing records.
Production, LNG, interstate transmission and commodity trading require different research tracks. An energy-company name alone does not establish distribution scope.
Operator context
Annual operator-reported material, mileage and installation-date context.
Limit: Preserve report year and file version. No live telemetry, safety diagnosis or installed vendor identity.
Operational history
Reported performance measures with definitions and reporting periods.
Limit: Historical repaired leaks are not current leaks. Avoid unsupported safety rankings.
Company and jurisdiction
Annual company and delivery context for account segmentation.
Limit: Reporting company, operating utility and holding company need reconciliation.
Regulatory programs
A concrete state source for enhancement-plan applications and related records.
Limit: An application and an effective decision show different stages; portals vary by jurisdiction.
Regulatory scope
A starting point for California gas utility regulatory context.
Limit: The case filing and effective order must establish a specific program claim.
Municipal funding
Official program materials and award-year context.
Limit: Check the applicable period and conditions; funding does not establish a current bid.
Supplier participation
Official vendor registration and eligibility guidance.
Limit: Registration does not guarantee business or participation rights.
Supplier requirements
Official safety, insurance, financial and legal qualification context.
Limit: Verify current requirements for the selected work category.
Utility program strategy
Official utility program context to compare against regulator records.
Limit: Separate forecasts and company explanations from approvals and procurement.
| Field | Question answered | Handling rule |
|---|---|---|
| Publication date | When was this document published? | Keep the original date and later amendment dates. |
| Report period | Which operating year or fiscal period does it describe? | Do not present the report period as today’s status. |
| Retrieval or review date | When did the analyst check this version? | A fresh retrieval does not make an old award current. |
| Status date | When was a procurement or implementation status established? | Require a current supporting record; otherwise state unknown. |
Source-specific IDs, aliases and multi-state subsidiaries need review. Corporate parents and operating gas buyers can differ.
A proposed brief would classify a primary statement, an analyst interpretation and an unresolved question separately. Missing fields remain unknown.
Public records can omit technical standards, incumbent contracts, tender invitations and budget details. Public access does not provide unrestricted reuse rights.
NPMS is not a distribution-pipe mapping source. Annual operator statistics do not establish street-level infrastructure, live telemetry or predictive safety scores.
NPMS scope and access ↗Linked agencies and utilities are sources, not partners or customer endorsements. No exhaustive public-source coverage is claimed.
Define a research scope
Start with your offering, a defined utility segment and the account question you need to answer.