Primary-source lens
National Grid New York long-term plan ↗
Review official strategy and program descriptions for explicit gas scope.
Limit
A strategy page alone does not establish a tender or technical specification.
Proposed gas distribution research
Metering and operational technology
Which utilities document gas-specific meter, GIS, communications or work-management modernization?
US natural gas distributionServices proposedEvidence limits included
The account decision
Start with the operating utility.
Define the program boundary before you assess fit. A combined utility’s enterprise technology plan may include gas work, electric work and shared systems with different buyers.
Read complementary source lenses.
Each source answers a limited question. The evidence must resolve to the same gas utility and jurisdiction.
Primary-source lens
CPUC natural gas regulatory context ↗
Identify relevant regulatory filings and program categories.
Limit
Approved expenditure is not proof of a specific technology purchase.
Primary-source lens
SoCalGas supplier requirements ↗
Review official supplier requirements before an account approach.
Limit
Qualification information does not identify an installed technology vendor.
Proposed deliverable
A brief that supports a specific next step.
These are proposed fields and research outputs, not a claim of an available product or completed account dataset.
- A program brief that identifies gas-specific scope and enterprise dependencies.
- A stage and requirements record with links to filings or procurement notices.
- An account-organization hypothesis marked for verification.
- An incumbent vendor field only when a public source explicitly supports it.
PROPOSED BRIEF STRUCTUREILLUSTRATIVE · NO ACCOUNT DATA
Supplier decision
Metering and operational technology
Which utilities document gas-specific meter, GIS, communications or work-management modernization?
Identity: to verifyProgram stage: source requiredProcurement: unknown
Evidence and provenance
- Primary record
- Document title, original URL and exact page.
- Date fields
- Publication date, report period, review date and separately supported status date.
Supplier interpretation
Connect only the documented scope to your offering. Mark technical fit and the buyer function as hypotheses until verified.
Action limits and next record
Retain missing procurement, implementation and budget fields as unknown. Name the next official record needed to support an action.
Illustrative research example
Separate the record from the conclusion.
Illustrative scope check: a combined utility mentions enterprise work management in a corporate plan. A proposed brief would seek a gas operating-company filing and technical procurement scope before classifying the program as a gas opportunity. No deployment or vendor identity is asserted.
Source-library review: October 14, 2026. An example does not establish current procurement status.
Unknowns and next verification
Make the missing evidence visible.
Find the program’s technical scope and buyer organization. Check procurement notices or implementation announcements. Do not infer a metering or SCADA vendor database from PHMSA reports.
- Whether a program is gas-specific or shared across business units.
- Whether the need concerns meters, communications, software or integration.
- Whether technical compatibility and cybersecurity conditions are public.
- Whether an incumbent contract already covers implementation.
Continue the account research.
Define a research scope
Which evidence would change your next decision?
Start with your offering, a defined utility segment and the account question you need to answer.