Baseline & Event Performance Calculator
Guided Configuration
Configure a defensible baseline in five guided steps.
Load telemetry, define the event, choose a method, then review every assumption before running the calculation.
Multiple baseline methods
Import and export performance
Timezone-aware interval handling
Adjustments and holiday rules
Drop a telemetry CSV here
or choose a file
Timestamps are processed exactly as supplied.
This calculator does not convert timezones or offsets.
Normalize timestamps first
Sample analysis is available without signup. Sign in to upload and analyze your own telemetry.
Include event-day telemetry if you plan to use same-day adjustment.
Download CSV templateSelects the top X usage days from Y recent qualifying days and averages each event interval.
Enter integers from 1 to 20. X must be less than or equal to Y.
Use End of Interval if 1:15 represents interval 1:00-1:15. High-day ranking currently follows the event window.
Compares same-day actuals vs unadjusted baseline over the selected window and applies bounded additive or multiplicative adjustment based on the selected SDA model.
No holidays selected.
Save Configuration
Save the reusable baseline logic and adjustment settings so you can apply this profile to future events.
Saved profiles appear in the Saved Baselines tab and can be reused with new event timing.
System Baseline Templates
Start from common market-style baseline configurations, then adjust any setting in the builder before you run or save your own version.
Saved Baseline Configurations
Select a saved baseline to load it into the builder or delete it.
Load a saved setup into the builder to run against the current dataset.
DER validation workspace
Simulated Distributed Energy Resources
Define test devices, schedule dispatch windows, and compare expected telemetry before connecting a physical asset.
DER profiles
Saved device capabilities and telemetry defaults are reused across dispatch and playback tests.
| Device ID | Name | Type | Rated Power (kW) | Energy / SoC | Actions |
|---|
No DER devices yet. Create your first DER to begin telemetry simulations.
Profile details
New DER Profile
Stable identifier used by API and dispatch requests.
Schedule a test dispatch
Choose compatible DER profiles, define one control window, and preserve the dispatch for repeatable playback.
1
Select DER targets
Select one or more DERs to create a grouped dispatch.
2
Configure the control window
Control options are limited to capabilities shared by the selected DER types.
Selected DER status
Current Mode
Idle
Select a DER to inspect queued controls and dispatch windows.
Queued Controls
0
Next Control Start
--
Scheduled controls
Device-level windows created from saved dispatches.
| Control | Target | Start | End | Status | Action |
|---|
No control requests queued for this DER yet.
Dispatch history
Select a dispatch in Telemetry & Playback to inspect device-level response.
| Dispatch | Control | Window | Targets | Created | Action |
|---|
No multi-device dispatches queued yet.
Generate and replay telemetry
Build a deterministic device-level series, then compare it with the response to a saved dispatch.
Set on the saved DER profile.
Repeatable for the same profile and settings.
Targeted DERs
0
DERs Changed
0
No Visible Change
0
No Control Overlap
0
Max Device Reduction (kW)
0
| Device | DER Type | Control | Max Reduction | Avg Reduction | Status | Action |
|---|
Run a dispatch preview to inspect device-level responses.
Active Controls In Range
0
Max Reduction (kW)
0
Telemetry Impact View
Compare the uncontrolled telemetry profile to the controlled output and visually inspect each control window.
DR Baseline Scenario Comparator
Compare two baseline profiles against the same event and telemetry. GridMango preserves uploaded timestamp values as supplied; use the Timezone Conversion tool first only when your source data needs normalization.
Drag & Drop telemetry CSV here
or click to browseExpected columns: timestamp and kW value. Duplicate or invalid intervals are rejected before calculation.
Download Sample CSV TemplateComparison Event
One event window is applied to both profiles so the comparison isolates baseline logic.
Profile A
Select a profile to preview its calculation rules.
Profile B
Select a profile to preview its calculation rules.
| Profile | Quality | Avg. baseline (kW) | Baseline energy (kWh) | Performance energy (kWh) | Performance (%) | Selected days |
|---|---|---|---|---|---|---|
| Run a comparison to view results. | ||||||
Synthetic Meter Load Generator
Generate AMI-ready test data
Build deterministic interval datasets for baseline QA, event replay, and forecasting validation. Import and export remain separate channels, while net is calculated as import minus export.
1. Dataset
Deterministic model
Define the interval range and load profile
2. Import channel
Set grid consumption limits
3. Export channel
Configure behind-the-meter generation
AMI channel convention
Import and export are positive, separate readings. Net may be negative and always equals import minus export.
4. Generate
Review and generate your AMI dataset
Create the preview using the configuration above. All timestamps are emitted as explicit UTC instants.
Dataset preview
AMI channel summary
Intervals
—
Average import
—
Peak export
—
Net energy
—
| Time (UTC) | Import (kW) | Export (kW) | Net (kW) |
|---|
Download dataset
Use the combined AMI file or a two-column channel file for downstream GridMango tools.
Green Button Import
Metadata-aware import
Convert Green Button interval streams without guessing their units or direction.
ReadingType metadata determines the multiplier, unit, interval, and import/export/net channel. Original energy and calculated average power remain separate.
No manual sign conversionForward and reverse readings remain positive import and export channels. Net is derived only when both are available.
Drag & Drop Green Button XML here
or click to browse
Used only when opening the normalized data in the baseline calculator.
Green Button epoch timestamps are exported with an explicit UTC designator.
Output rows
0
Channels
-
Intervals
-
Warnings
-
| Detected stream | Channel | Source unit | Multiplier | Rows | Quality |
|---|
Data Timezone Converter
Convert interval timestamps without changing telemetry values or other uploaded columns. Embedded UTC offsets are honored automatically; Source Timezone is used only for timestamps without an offset.
Offset-free timestamps must use an unambiguous ISO format such as 2026-01-15T14:30:00.
Drag & Drop telemetry CSV here
or click to browseRows-
Embedded offsets-
Timestamp column-
Before
-
→
After-
Telemetry Data Patching
Guided repair
Fill short internal gaps without changing recorded readings.
Choose the timestamp and meter channels to validate. Import, export, and net values are patched independently, while large gaps remain unresolved for review.
Linear interpolation only
New values are inserted only between two known readings. The tool does not extrapolate beyond the first or last reading.
Drag & Drop telemetry CSV here
or click to browse
Timestamps must be ISO 8601; explicit offsets are supported.
Select one or more numeric channels. Each is interpolated separately.
Longer gaps stay unresolved and are listed in the audit.
Input rows-
Output rows-
Inserted rows-
Unresolved gaps-
| Timestamp | Status | Method | Channel values |
|---|
OpenADR 2.0b VEN
Use this client to create party registration, poll a VTN, register telemetry reports, and push EiReport update payloads.
For secure communication, you can upload certs here per request or configure mTLS defaults in Netlify env vars: OPENADR_CLIENT_CERT_PEM, OPENADR_CLIENT_KEY_PEM, optional OPENADR_CA_CERT_PEM.
Advanced: Certificate Authentication
If certificate files are not uploaded, requests run without uploaded client cert auth.
Usage and history reports accept ISO timestamp/value rows. Status reports use the saved device state, data quality, and manual override fields instead of deriving status from wattage.
OpenADR 3.1 VEN-to-VTN UAT Validator
BOUNDED INTEGRATION UAT
Verify the REST path from authentication through active events and reporting.
GridMango checks the configured VTN endpoints, validates returned object relationships, records protocol evidence, and executes pinned OpenAPI schemas when the Alliance artifact is installed.
Scope boundary
This produces pre-certification UAT evidence. It is not OpenADR Alliance certification and does not run a continuous listener or MQTT service.
1 Connection
2 Expected scope
3 Run & findings
CONNECTION PROFILE
VTN endpoint and credentials
GridMango appends
vens, resources, programs, events, and optional reports paths to this URL.
Credentials are encrypted with the dedicated OpenADR 3 application key and are never written to run evidence.
EXPECTED SCOPE
Define what the VTN should expose to this VEN
Comma-separated downstream assets expected to be visible.
This is the only mutating VTN action in the bounded run. Leave it disabled for read-only discovery.
Ready to validateOAuth → VENs → Resources → Programs → Active events → Optional report
RUN HISTORY
Validation evidence
Verdict--
Assertions--
Passed--
Failed / blocked--
Findings
Run validation to view assertions.
Protocol timeline
No protocol evidence yet.
OCPP 2.x Integration Validator
Configure a charge point profile, verify connection readiness, and run a real bounded Core exchange against an external CSMS.
Credentials are encrypted with the dedicated OCPP application key. Production validation requires a trusted TLS endpoint.
Smart Charging and OCPP 2.1 bidirectional/DER-control scenarios will be enabled only after their message exchanges and assertions are implemented.
Run Details
No run selected.
Protocol Transcript
Timeline will appear here.
Matter Energy Profile Validator
Validate declared Matter 1.3/1.4 energy-management profile metadata using your shared DER device profiles. This readiness check does not connect to a Matter fabric, exercise a device, or represent certification testing.
Use the non-root endpoint that exposes the energy device.
Readiness Results
No run selected.
Validation Evidence
Timeline will appear here.
OpenADR Event Debugger
Analyze supplied OpenADR traffic evidence using correlated event and request identifiers. Sensitive credentials are redacted before display or export.
Missing stages are reported only when required by the selected workflow.
Detected Dialect
--
Distributions
--
Acknowledgements
--
Opt In / Out
--
Report Updates
--
Median Ack Latency
--
Latest Signal
--
Protocol Errors
--
Findings & Recommendations
| Timestamp | Direction | Stage | Correlation | Signal / Opt | Level | Redacted Evidence |
|---|---|---|---|---|---|---|
| Analyze logs to view correlated evidence. | ||||||
Uploaded Data Overview
Previewing up to 7 days of uploaded telemetry data to validate structure.
Event Window
SDA Window
Data QA Summary
Rows Ingested
--Telemetry Days
--Date Range
--Detected Interval
--Max Intervals / Day
--Days With Missing Intervals
--Calculation output
Analysis Results
Result status
Event coverage —
Baseline coverage —
Timestamps used as supplied
Export calculation evidence
Download interval results, candidate selection details, or the complete JSON evidence bundle.
Visualization
See actual interval load against the selected baseline logic.
The chart combines actual load, the unadjusted baseline, event-window overlays, and same-day adjustment context so operators can review the calculation visually before export.
Actual Load
Unadjusted Baseline
Adjusted Baseline
Event Window
SDA Window
Average Unadjusted Baseline
-- kW
Unadjusted Baseline Energy
-- kWh
Average Adjusted Baseline
-- kW
Adjusted Baseline Energy
-- kWh
SDA Factor
--
Event Performance
--
Event Delivered Energy
--
Eligibility Summary
Historical Days Considered
--Qualified For Ranking
--Selected For Baseline
--Skipped Weekend / Type
--Skipped Holidays
--Skipped Coverage < 100%
--Skipped Low Usage
--Qualifying Highest Days Used (Selected):
Valid Candidates Excluded (Low Usage Status):
Skipped (Insufficient Interval Coverage < 100%):
Skipped (Excluded Holiday):
Skipped (Weekend / Type Mismatch):