Towards a Framework for Autonomous Microgrids

Table of Contents

  1. Introduction

  2. Core Concepts

    • Assets

    • Foundational Capabilities

    • Application Capabilities

  3. Automation vs Autonomy

  4. Levels of Operational Autonomy

    • Level 1 — Manual Local Operation

    • Level 2 — Automated Supervisory Control

    • Level 3 — Autonomous Supervisory Control

  5. Operational Criticality

    • Safety-Critical Capabilities

    • Business-Critical Capabilities

    • Optimization Capabilities

  6. Applying the Framework

  7. Implications for a Microgrid OS

A picture with worth a thousand words 

Microgrid Capability Framework.png

Introduction

As distributed energy resources become increasingly software-defined, microgrids are evolving from manually operated electrical systems into digitally coordinated energy platforms. This evolution creates a need for a clear framework describing the degree of operational autonomy assigned to different microgrid functions.

This document proposes a simple three-level autonomy model for microgrids inspired by concepts from industrial automation, supervisory control systems, and autonomous systems engineering.

Unlike autonomous vehicle frameworks that classify an entire vehicle into a single automation level, this framework applies autonomy levels to specific operational capabilities operating on specific assets.

For example:

Each capability may operate at a different level of autonomy.

A microgrid could therefore simultaneously contain:

This capability-oriented approach allows microgrids to evolve incrementally toward higher levels of operational autonomy.


Core Concepts

Assets

Assets are physical, digital, or economic components participating in the operation of the microgrid.

This framework groups assets into three primary categories.

1. Physical Assets

Physical assets are hardware systems that generate, store, distribute, consume, or protect electrical energy.

Examples include:

2. Digital Assets

Digital assets are software systems, communications systems, and computational services used to monitor, coordinate, optimize, and operate the microgrid.

Examples include:

3. Economic and Contractual Assets

Economic and contractual assets represent the financial, commercial, and policy relationships governing the microgrid.

Examples include:

These asset categories recognize that modern microgrids are not purely electrical systems. They are virtual-physical-economic systems integrating energy infrastructure, software platforms, and operational business logic into a unified operational environment.


Foundational Capabilities

Foundational capability domains are the core operational primitives from which higher-order microgrid behaviors and applications are constructed.

Rather than treating every operational function as a separate foundational capability, this framework identifies a small set of core capabilities that can be composed together to create more advanced orchestration, optimization, commercial, and autonomous behaviors.

These foundational domains operate across physical, digital, and economic assets.

1. Observability

Observability capabilities measure, record, analyze, and communicate system state.

Observability forms the awareness layer of the microgrid.

Examples:

2. Steering

Steering capabilities execute operational actions intended to guide system behavior toward desired operational outcomes.

Unlike traditional low-level control systems, steering emphasizes adaptive orchestration, policy-driven operation, and outcome-oriented system management across distributed assets.

Steering forms the action layer of the microgrid.

Examples:

3. Intelligence

Intelligence capabilities generate predictions, recommendations, classifications, reasoning, and adaptive operational decisions.

Intelligence forms the reasoning layer of the microgrid.

Examples:

4. Governance

Governance capabilities define and enforce operational rules, permissions, priorities, compliance requirements, and safety boundaries.

Governance forms the constitutional layer of the microgrid.

Examples:


Application Capabilities

Operational application domains are higher-order business and operational functions constructed from combinations of the foundational capabilities.

These applications are not themselves foundational primitives. Rather, they emerge from orchestrating observability, steering, intelligence, and governance capabilities together.

Coordination

Coordination capabilities orchestrate workflows across systems, users, assets, and operational processes.

Coordination typically combines:

Examples:

Optimization

Optimization capabilities improve operational efficiency, economics, reliability, or customer experience.

Optimization typically combines:

Examples:

Commercial Operations

Commercial operations capabilities manage the economic and business functions of the microgrid.

Commercial operations typically combine:

Examples:


Automation vs Autonomy

The distinction between automation and autonomy is foundational to this framework.

Automation

Automation refers to systems that execute predefined instructions or workflows under human-defined logic.

Examples:

An automated system follows instructions.

Autonomy

Autonomy refers to systems capable of independently managing operational objectives under changing conditions while operating within defined technical, economic, and safety constraints.

Examples:

An autonomous system manages outcomes.


Levels of Operational Autonomy

This framework distinguishes between:


Level 1 — Manual Local Operation

At Level 1, foundational capabilities are operated directly by humans physically present at the asset location.

The asset itself provides the operational interface.

Examples:

Operational Characteristics

Question Answer
Who monitors the system? Human operators on-site
Who makes decisions? Human operators on-site
Who executes actions? Human operators on-site
Who handles failures? Human operators on-site

Characteristics

Relevant Standards

Relevant standards may include:

At Level 1, however, most operational authority remains local and manual.


Level 2 — Automated Supervisory Control

At Level 2, foundational capabilities are supervised remotely through software platforms and communications networks.

Humans remain responsible for operational decisions, while software automates telemetry collection, visualization, alarms, workflows, and execution of predefined control logic.

Examples:

Operational Characteristics

Question Answer
Who monitors the system? Human operators remotely
Who makes decisions? Human operators remotely
Who executes actions? Automated systems under human-defined logic
Who handles failures? Human operators with software assistance

Characteristics

Relevant Standards

This level aligns closely with existing industrial automation and microgrid supervisory standards including:

Level 2 corresponds closely to modern SCADA and DERMS architectures.


Level 3 — Autonomous Supervisory Control

At Level 3, foundational capabilities are operated autonomously by software systems capable of independently managing operational objectives within defined technical, economic, and safety constraints.

Humans define policies, operating boundaries, escalation procedures, and override authority, but the system continuously makes operational decisions without requiring constant human supervision.

Examples:

Operational Characteristics

Question Answer
Who monitors the system? Autonomous software systems with human oversight
Who makes decisions? Autonomous systems operating within defined policies
Who executes actions? Autonomous software systems
Who handles failures? Autonomous systems first, humans upon escalation

Characteristics

Key Requirements

Level 3 systems should include:

Relevant Standards

Existing standards partially address autonomous operation today. Relevant references include:

Further industry standardization may be required to fully define autonomous microgrid operation.


Operational Criticality

Not all microgrid capabilities carry the same operational importance or risk.

This framework distinguishes between different classes of operational criticality.

Safety-Critical Capabilities

Capabilities whose failure or misuse could threaten human safety, equipment safety, or grid stability.

Examples:

These capabilities typically require strict operational constraints, auditability, and human override mechanisms.

Business-Critical Capabilities

Capabilities necessary for the commercial and operational sustainability of the microgrid business.

Examples:

These capabilities are operationally important but must remain subordinate to safety-critical protections.

Optimization Capabilities

Capabilities intended to improve efficiency, economics, customer experience, or asset utilization.

Examples:

Optimization capabilities should degrade gracefully without compromising safety or core operations.

Supporting Capabilities

Capabilities that support operational continuity, efficiency, maintenance, coordination, or administrative workflows, but whose temporary failure does not immediately compromise safety or core service delivery.

Examples:

Supporting capabilities improve operational effectiveness and resilience but are generally lower priority during constrained or degraded operations.

Informational Capabilities

Capabilities whose primary purpose is visibility, insights, diagnostics, learning, or reporting without direct operational authority over the system.

Examples:

Informational capabilities provide situational awareness and decision support but typically do not directly influence operational behavior.


Applying the Framework

The framework is intended to classify autonomy at the capability level rather than the whole microgrid level.

Example:

Asset Foundational Capability Domain Operational Function Autonomy Level
Smart Meter Observability Usage telemetry Level 2
Battery Storage Steering Battery dispatch Level 3
Diesel Generator Steering Generator operation Level 1
EV Chargers Observability Charger monitoring Level 2
EV Chargers Steering Charging orchestration Level 3
Billing System Commercial Operations Automated billing Level 2
Smart Relay Steering Service disconnection Level 3

This allows gradual evolution toward autonomy without requiring the entire microgrid to transition simultaneously.


Implications for a Microgrid OS

A Microgrid OS designed around this framework should:

The Microgrid OS becomes the orchestration layer coordinating assets, capabilities, policies, and autonomy levels across the energy system.


Revision #4
Created 2026-05-28 13:52:36 UTC by aaron.tushabe
Updated 2026-05-28 14:48:29 UTC by aaron.tushabe