Estimate the power-system state from network measurements, with bad-data suppression. It is a newer Garmo Solvers module from the October 2026 benchmark campaign, outside the 1.0.2 release. Results are checked against the original input; the measured result below states where it is ahead and where it is not.
BUILT FOR
Grid operators and energy-management teams running state estimation on large networks.
CHALLENGES → PRODUCT RESPONSE
The problem you face. What the product changes.
YOUR CHALLENGEWITH STATE ESTIMATION
01
The problem needs the right operation
A MATPOWER network model and a measurement set with standard deviations.
Estimate the power-system state from network measurements, with bad-data suppression.
02
A result must answer the original question
An answer detached from its original constraints or input is difficult to rely on.
The suite rechecks the answer against the original input and identifies the applicable result state.
03
The comparison needs a defined scope
A capability or benchmark result is not a universal promise for a different workload.
Evaluate the selected input, resource budget, complete cost and required certificate against your baseline.
WHAT YOU GET
A defined capability. A useful result.
01
Selected solving capability
Estimate the power-system state from network measurements, with bad-data suppression.
02
Original-input result
Bus voltage magnitudes and angles, with a chi-square consistency test and normalized residuals for bad data.
03
Common access
Run it as garmo powerflow se or through the garmo-mcp server; headless execution fits scripts and automated workflows.
04
Checked result
The chi-square test and normalized residuals show whether the estimate is consistent with the measurements.
GARMO SOLVERS / MEASURED RESULT
Measured: 25k buses in 1.18 s
A 25,000-bus network with 204,000 measurements estimated in 1.18 s, chi-square consistent, with robust bad-data suppression. No head-to-head comparison against an external estimator is recorded.
Source: Garmo Labs benchmark campaign, October 2026. Results apply to the stated inputs, hardware and conditions; they are not universal competitor rankings.
A customer has a supported model and wants an accepted result without adopting every other module.
Illustrative customer use—not a new benchmark or completed customer deployment.
01→
Provide the original input and define the useful outcome.
02→
Run the selected module under its supported resource and interface scope.
03→
Review the returned answer, original-input checks and completion state.
FIT & ACCEPTANCE
Start with the task. Agree the useful outcome.
What you bring
A MATPOWER network model and a measurement set with standard deviations.
What a useful evaluation measures
+Accepted original-model result
+Appropriate certificate or disclosed uncertified state
+Total time, memory and operating cost
Delivery
License the selected capability, commission an implementation, or agree an operated service. Infrastructure and additional engineering are specified separately.
QUESTIONS BEFORE BUYING
A clear scope. A clear relationship.
What is the important boundary?−
The estimate is only as good as the network's observability and the supplied measurement model.
How is it priced?+
No new standalone price is supplied for this product; request a scoped proposal. The platform plans buy qualified workflows and capacity, not a second charge every time a compatible method is selected. Existing bundle inclusions do not expand automatically.
How do we get access?+
Available through garmo CLI and garmo-mcp, including headless execution. Product-specific inputs, runtime dependencies, budgets and result checks remain explicit.
PUT THE PRODUCT TO WORK
Tell us what needs to improve.
Bring a task, an accepted outcome and the environment in which the product needs to work.
Select the capability you need directly or include its compatible role in a qualified platform workflow. Production scope identifies release, environment, capacity and support; a product count is not an entitlement.
