Release path
1.0.1Published Mar 4, 2026@pasar6987/sf-energy-utilities-energy-services
Service agreements, service points, and usage impact analysis for energy and utility operations.
Published package · Latest published 1.0.1 Mar 4, 2026 · 8 datasets / 7 measures in the latest review · Updated Mar 11, 2026
Publisher
@pasar6987Published Mar 4, 2026Structure snapshot
8 datasets7 measures · 76 dimensionsReference context
Secondary package facts stay compact
- Updated
- Mar 11, 2026
- Visibility
- Public hub listing
- License
- MIT
- Created
- Mar 4, 2026
Reference facts
Secondary package facts after the usage path is clear
Licensing, categorization, ownership, and linked metadata stay below the runnable path so the page reads in the right order.
Format
Upstream
Repository
Domain
Source
Owner
@pasar6987Organization
License
Visibility
Publisher
Latest published version
Tags
Schema preview
SDK handoff
Use this package in code and AI
After structure review, move straight into typed reads with load() or compact LLM context with to_prompt().
Python SDK
Python example for @pasar6987/sf-energy-utilities-energy-services
This example uses the current package ref and, when preview data is available, fills in real dataset names from the published summary.
import rawctx
model = rawctx.load("@pasar6987/sf-energy-utilities-energy-services")
prompt = rawctx.to_prompt(
"@pasar6987/sf-energy-utilities-energy-services",
datasets=["EnergyServiceAgreement", "EnergyServiceAgreementItem"],
max_tokens=2000,
)
print(model.datasets) # ["EnergyServiceAgreement", "EnergyServiceAgreementItem", "ServicePoint"]
print(model.measures) # [Measure(name="EnergyServiceAgreementItem.OneTimePrice", ...), Measure(name="EnergyServiceAgreementItem.RecurringPrice", ...), Measure(name="EnergyServiceAgreementItem.UsagePrice", ...)]
print(model.dimensions) # [Dimension(name="AccountId", ...), Dimension(name="ActivationDate", ...), Dimension(name="BillingSchedule", ...)]
print(model.relationships) # [Relationship(name='...', ...)]
print(prompt)README
Package narrative and examples
Use documentation after the package clears provenance, ownership, and runnable-path checks.
@pasar6987/sf-energy-utilities-energy-services
Service agreements, service points, and usage impact analysis for energy and utility operations.
Overview
| Count | |
|---|---|
| Objects (Datasets) | 8 |
| Dimensions | 76 |
| Measures | 7 |
| Relationships | 0 |
Objects
- EnergyServiceAgreement — The services or commodities purchased by a customer, for a specified product and optionally linked to a Contract. Contracted Services can be physical goods (eg. appliances), commodity services (eg. electricity, gas or water) or other miscellaneous services (eg. homeowner insurance, boiler maintenance contract).
- EnergyServiceAgreementItem — Represents the details of the Energy Service Agreement object such as the time, location, and pricing information.
- ServicePoint — Represents an entry point for services to a premises. The service provided to each service point is separately metered (or measured). Useful for energy services including electricity, water and gas services.
- UsageImpactFactor — Represents a collection of fields to set up the Usage Impact Factors used across jurisdictions and programs.
- UsageImpactGroup — Represents a collection of fields to set up the Usage Impact Groups used across jurisdictions and programs.
- UsageImpactGroupFactor — Represents a junction between an Usage Impact Group version and Usage Impact Factor.
- UsageImpactGroupPgmMeasure — Represents a junction between the program, product, and Usage Impact Group version.
- UsageImpactGroupVersion — Represents a collection of fields to set up the versions of Usage Impact Groups.
Install
rawctx snapshot-download @pasar6987/sf-energy-utilities-energy-services
Structure review
Inspect package structure after the usage path is clear
Use the structural review when you need the package footprint, field counts, and model paths before a deeper explorer pass.
Topology
Semantic graph
Use the graph last, once provenance, documentation, and the runnable path are already clear.
Semantic Graph
Topology counts appear after the graph loads.
Loading graph
Semantic topology is still loadingCounts and graph nodes appear after the latest published summary has been fetched.
