- Manually assembled test data
- Calculations spread across files
- Integration failures found late
- Evidence recreated for every review
Automated validation for demand response and DER programs
Test DER programsbefore they reachproduction.
GridMango automates the repetitive QA work behind baseline validation, telemetry checks, simulated DER assets, and end-to-end protocol testing—so energy teams can find problems earlier and preserve the evidence behind every result.
UtilitiesDER aggregatorsDERMS vendorsEnergy consultants
Event coverage100%
Baseline coverage100%
Evidence outputs3
Real product output Review the calculation, selection logic, and evidence—not just a pass/fail badge.
The validation gap
Critical programs are still tested with one-off spreadsheets, scripts, and manual coordination.
DERMS and demand response teams need to prove that telemetry, calculations, simulated assets, controls, and external integrations behave correctly together. The work is specialized, repetitive, and difficult to reproduce when every project starts from scratch.
GridMango turns those recurring tasks into visible, repeatable validation workflows.
- Reusable simulated data and assets
- Transparent, repeatable calculations
- Controlled end-to-end test scenarios
- Exportable findings and evidence
GridMango Workflows
Automate a complete validation process.
Start from an uploaded dataset or a scheduled run, then chain GridMango tools into a repeatable M&V, end-to-end testing, or protocol-validation workflow.
Workflow builderProgram validation
Program M&VCalculate and document event performance
Data upload
TriggerUpload interval data
→
Quality checkValidate telemetry
→
CalculateBaseline + performance
→
OutputEvidence package
End-to-end testExercise a complete DER program scenario
Scheduled run
TriggerStart test run
→
PrepareProvision simulated assets
→
ExerciseDispatch scenario
→
VerifyTelemetry + device state
Protocol validationVerify the exchange between test endpoints
Scheduled run
TriggerStart protocol run
→
ConnectRegister test endpoint
→
ExerciseSend event or command
→
VerifyAcknowledgements + reports
Start with the workflows that carry the most delivery risk
One validation workspace, two core paths.
01
Baseline and event performance
Make the calculation defensible before it reaches settlement or audit.
Validate interval coverage, candidate-day selection, methodology assumptions, same-day adjustments, and delivered event performance from one guided workflow.
- Multiple baseline methods and scenario comparison
- Selection and exclusion audit trails
- Interval, summary, and evidence exports
InputInterval telemetry
ValidationMethod + coverage
OutputDefensible evidence
02
Integration and protocol validation
Validate control and reporting workflows before field deployment.
Configure test endpoints and simulated assets, exercise protocol-specific events and commands, and inspect acknowledgements, state changes, telemetry, and reporting behavior in one controlled environment.
- OpenADR 2.0b and 3.0 event and reporting workflows
- OCPP 2.x Core charge-point lifecycle validation
- Matter energy-profile and cluster readiness checks
- Timelines and evidence for integration diagnosis
1ConnectProfiles, identities, and capabilities
2ExerciseEvents, commands, and controls
3VerifyState, acknowledgements, and telemetry
Supporting validation infrastructure
Prepare the data and test conditions around the core workflow.
Telemetry QA
Inspect interval alignment, convert timestamps, repair short gaps, and preserve correction evidence.
Synthetic data
Generate deterministic meter and DER telemetry with separate import, export, and net channels.
Green Button import
Interpret ReadingType units, direction, multipliers, and quality before downstream analysis.
Evidence exports
Keep calculations, selected inputs, findings, and run context available for technical review.
How it works
From test condition to reviewable outcome.
GridMango keeps configuration, execution, and evidence connected so a test can be understood and repeated.- 01
Choose the workflow
Start with a baseline, telemetry, simulation, or integration objective.
- 02
Configure the conditions
Load source data and define the methods, assets, targets, or expected behavior.
- 03
Run and inspect
Execute the scenario and review calculation quality, state changes, timelines, and failures.
- 04
Export the evidence
Retain the normalized data, results, and audit detail needed for the next decision.
Designed for technical scrutiny
Transparent assumptions. Controlled testing. Reviewable evidence.
Visible configuration
Methods and test conditions remain available for review instead of disappearing behind a score.
Customer data ownership
Uploaded data and generated outputs remain the customer’s data.
Security as product work
Access controls, operational safeguards, and enterprise security readiness are part of the platform roadmap.
Have a validation workflow in mind?