Grid Intelligence Platform

What GridKern does in your control room

Three core modules that work together: forecast, dispatch, and report. Each can run independently or as a unified platform.

Module 1

Load Forecast Engine

The core forecasting layer uses a gradient-boosted ensemble trained on your historical interval data, weather station feeds, and ISO day-ahead schedules. It outputs probabilistic forecasts at 15-minute resolution — not a single number, but a distribution you can act on.

At the 96th percentile of its test set, MAPE stays below 2.1%. For most utility operators, that precision difference translates directly to reserves procurement strategy.

  • 15-minute to 72-hour lookahead
  • Net-load aware (load minus behind-the-meter solar)
  • Weather-adjusted using NWP grid data
  • Separate models per feeder zone
  • P10/P50/P90 confidence bands
GridKern load forecast chart with confidence intervals over 72-hour period
Module 2

Demand-Response Dispatch Engine

When the forecast signals a potential reserve shortfall, the DR Dispatch Engine computes the lowest-cost curtailment sequence from your enrolled assets — industrial interruptible loads, HVAC cycling agreements, and battery storage dispatch — and issues signals automatically or sends them to the dispatcher for one-click approval.

Dispatch rules use a configurable MW-deficit threshold. You define how much lead time to allow, which asset classes have priority, and whether to auto-dispatch or require operator confirmation.

  • Asset inventory management and enrollment tracking
  • OpenADR 2.0b dispatch signaling
  • Response confirmation and MW telemetry
  • Curtailment stacking logic (no double-counting)
  • Post-event settlement export
Demand-response dispatch console with enrolled assets and dispatch workflow
Module 3

NERC Compliance & Reporting

GridKern logs every forecast issuance, every deviation event, and every dispatch action with timestamps and operator attribution. At month-end, BAL-001-3 and BAL-002-2 performance data is pre-populated in the standard NERC template format.

Your compliance team reviews and submits. No data extraction. No spreadsheet assembly. No reconciliation against a separate operations log.

  • BAL-001-3 and BAL-002-2 pre-populated reports
  • Area control error (ACE) logging at 4-second granularity
  • Audit trail with operator sign-off workflow
  • Export to CSV, PDF, and NERC eSubmit format
  • Configurable retention period (default: 7 years)
NERC compliance reporting dashboard with BAL-001 performance data
Integrations

Works with your existing EMS stack

GridKern is not a replacement for your Energy Management System. It publishes data into it through standard interfaces operators already trust.

DNP3 & Modbus TCP

Native SCADA polling via DNP3 Subset Level 2 and Modbus TCP. Configurable polling interval from 1 to 15 minutes.

REST API & Webhooks

JSON REST API for forecast data ingestion and push webhooks for alert delivery. Rate: 1,000 requests/min per subscription.

OpenADR 2.0b

Standards-compliant DR signaling to enrolled Virtual Top Nodes (VTNs). Interoperable with AutoGrid, Oracle Utilities, and similar platforms.

CIM/XML Schedule Feed

Publishes forecast schedules in IEC 61970 CIM/XML format for EMS import. Compatible with GE PowerOn, Siemens EMS, and OSIsoft PI.

RBAC & SSO

Role-based access control with SAML 2.0 and LDAP integration. Separate operator, analyst, and read-only roles with full audit logging.

On-Premises Deployment

Available as Docker containers deployable in your OT network segment. Air-gap option for critical infrastructure requirements under NERC CIP-005.

Data Flow

From SCADA telemetry to dispatch signal

GridKern processes raw interval data through three sequential stages before a decision reaches the operator console.

1

Telemetry Validation

Incoming SCADA values are checked for missing intervals, stuck registers, and outliers. Bad data is flagged, not silently imputed.

2

Ensemble Forecast

Clean interval data feeds the gradient-boosted ensemble. Forecasts update every 15 minutes on a rolling basis — not just at the top of the hour.

3

Dispatch Evaluation

The forecast is compared against configured reserve thresholds. If a curtailment signal is warranted, the DR engine sequences available assets by availability and cost.

4

Operator Console

The assembled decision — forecast, deviation risk, proposed dispatch — arrives at the operator console in a single screen view. One action required.

Pilot Program

See GridKern running on your interval data

We run a 30-day accuracy trial using your SCADA export. You see real MAPE numbers against your actual load — before any contract discussion.

Request a Demo View Pricing