Voltron Controller
Hardware agnostic microgrid management software
The Voltron Controller is the control layer for commercial microgrids: solar, battery storage, biofuel gensets and EV charging, dispatched together against live prices, network tariffs and the physical limits of the site.
Briefing document · October 2026
Is there a strategic advantage to spinning off the microgrid controller software as an independent product managed by a distinct corporate entity?
Microgrid management software developed in-house by hardware manufacturers or suppliers faces a critical barrier to market adoption: competing hardware manufacturers or suppliers are unlikely to use software developed by a competitor.
The market only opens to a neutral vendor
Key segments of the market will automatically reject a controller tied to a specific hardware manufacturer:
- Direct competitors in energy rental and remote power.
- OEMs whose generators and inverters the platform manages.
- Asset owners whose procurement teams view supplier-owned software as vendor lock-in.
- Any site operating a mixed fleet of hardware.
Hardware neutrality has to be structural
To effectively manage diverse batteries, generators, inverters, and meters, a controller must be demonstrably hardware-agnostic. A software vendor backed by an equipment manufacturer inherently compromises this trust, as every integration priority and dispatch algorithm risks being perceived as favoring the parent company. True neutrality is a structural reality, not a marketing claim.
Data governance becomes possible
A microgrid controller’s long-term value lies in aggregating operational data to establish cross-site benchmarking. However, operators will never entrust their proprietary performance metrics to a software provider that simultaneously competes for their business. Establishing a separate corporate entity provides the necessary legal and structural guarantees of data confidentiality, unlocking the ability to deliver comprehensive benchmarking analytics.
OEM partnerships become a channel
Conversely, independence unlocks significant channel opportunities. A standalone platform can forge strategic integration partnerships with major generator, inverter, and switchgear manufacturers, leveraging their established networks to reach fleets far beyond the capacity of a direct sales team. If the platform remains tethered to a competing manufacturer, this lucrative distribution channel is permanently closed.
The Devaluation of Software in Hardware Procurement
When bundled with multi-million-dollar equipment orders, control platforms are routinely discounted to zero to secure the hardware sale. While this may close the immediate deal, it permanently undermines the software’s commercial viability. Bundled software fails to establish independent pricing, generate recurring renewal revenue, or demonstrate standalone value. Ultimately, the long-cycle capital procurement model and the SaaS subscription model are inherently incompatible; within a single organization, the larger hardware transaction will inevitably cannibalize the software’s value.
Divergent Requirements for Capital, Talent, and Governance
Software development demands sustained R&D investment with a long-term payback horizon, whereas equipment businesses require working capital to fund fleet operations and fulfill contracted revenue. Within a single organization, software initiatives will consistently, and rationally, lose budget allocations to immediate revenue-generating hardware orders. Furthermore, establishing a dedicated entity allows the software business to compete effectively in the tech talent market, offer equity incentives directly tied to the product, and appoint board members with proven experience in scaling enterprise software.
Retained Strategic Value for the Originating Business, Strategic decoupling preserves the core commercial benefits for the parent organization. The hardware business retains a cornerstone equity position and preferential licensing rights, transitioning into the platform’s primary design partner and flagship reference client. Furthermore, the established installed base across prominent industrial operators provides an unparalleled market proof point that remains fully intact post-separation. Ultimately, the originating business retains participation in the software’s financial upside while successfully offloading its operating costs and R&D liabilities.
There is also a critical risk management imperative. Power dispatch software carries consequential-loss liabilities that vastly exceed standard software licensing revenue, while remote connectivity into critical energy infrastructure introduces stringent cybersecurity and compliance obligations. Housing these operations within a purpose-built entity, complete with specialized insurance and a dedicated security posture, effectively ring-fences this risk. Furthermore, this structural separation insulates a highly predictable, recurring-revenue software business from the inherent volatility of the parent company’s hardware commodity cycles.
Where the Voltron Controller sits
Capability
The following capability set is categorized by the core operational functions expected of an enterprise-grade microgrid controller.
Grid Interface, Islanding, and Stability
- Seamless Islanding: Autonomously decouple from the utility grid during outages or voltage sags, aligning with IEEE 2030.7 standards.
- Resynchronization: Precisely match voltage, frequency, and phase angle to safely reconnect without disrupting site operations.
- Deterministic Fast Execution: Deliver the sub-second response times required for active control, the critical differentiator between a true microgrid controller and a passive reporting dashboard.
- Grid Forming: Establish and maintain the local voltage and frequency reference during islanded operation.
- Breaker Management: Execute main breaker separation and orchestrate controlled returns to parallel grid operation.
- Grid Code Compliance: Ensure strict adherence to connection-point regulations, including dynamic export limitation as mandated by network operators.
- Ancillary Stability Services: Provide inertia, system strength, short-circuit contribution, oscillation damping, and black-start capabilities where market structures and physical plant permit.
Forecasting, Dispatch, and Optimization
- Comprehensive Data Ingestion: Integrate wholesale market prices, complex network tariffs, demand charge structures, localized weather/solar forecasts, and real-time site load data.
- Predictive Interval Dispatch: Execute optimized asset commands ahead of every dispatch interval, operating proactively rather than reactively.
- Asset-Level Orchestration: Direct specific hardware actions, including battery charge/discharge cycles, solar export/curtailment, flexible load shifting, EV charging schedules, and generator start/stop sequences.
- Advanced Peak Shaving: Mitigate demand-based network charges utilizing ratchet-aware load management strategies.
- Self-Consumption Maximization: Optimize solar generation by directing surplus energy to EV charging or battery storage rather than exporting at low-value market rates.
- Negative Price Mitigation: Automatically curtail energy exports during negative wholesale pricing events to prevent financial losses.
- Market Arbitrage: Capitalize on wholesale price spreads where market regulations and asset capabilities permit.
- Lifecycle Financial Tracking: Conduct pre-investment feasibility modeling using the site’s native interval data, and subsequently benchmark live operational performance against that original business case.
Constraints, Guardrails, and Asset Protection
- Critical Reserve Guardrails: Ensure battery State of Charge (SOC) never drops below the threshold required to sustain critical loads while generators start and synchronize.
- Resilience as a Hard Constraint: Subordinate economic optimization to operational resilience. Capacity reserves are strictly enforced in the model, never treated as optional preferences.
- Physical Constraint Modeling: Enforce real-world plant limitations, including transformer thermal ratings, breaker capacities, generator ramp rates, and inverter/export maximums.
- Logical Energy Apportionment: Isolate the exact energy required for critical load ride-through, safely releasing only the surplus capacity for market participation.
- Demand High-Water-Mark Tracking: Prevent EV charger output oscillation by actively monitoring and managing against peak demand thresholds.
- Localized Capacity Limits: Enforce per-group power limits to protect shared cable runs and sub-boards from thermal overload.
Load Management and Shedding
- Dynamic Load Prioritization: Execute automated load shedding during generation constraints, sacrificing non-critical loads first according to configurable facility policies.
- Dynamic EV Load Balancing: Throttle EV charging rates in real-time to respect the site’s total grid connection limit, enabling charger deployment without costly utility upgrades.
- Proportional Power Allocation: Distribute available power across active chargers dynamically, supporting both priority queuing and fair-share distribution algorithms as site demand fluctuates.
- Comprehensive Electrical Support: Manage single- and three-phase charging (including phase rotation) across both AC and DC hardware, explicitly accounting for DC conversion losses within the site’s total power budget.
- Automated Demand Response: Ingest and execute external curtailment signals from network operators, market aggregators, or Building Management Systems (BMS).
Market Participation
- Capacity Obligation Management: Maintain mandated State of Charge levels throughout contracted market intervals before releasing capacity for alternative use outside those windows.
- Dispatch Compliance: Respond precisely to market dispatch instructions within required notification timeframes and ramp rates.
- Portfolio Aggregation: Consolidate multiple distributed sites into a single, unified portfolio position to support Virtual Power Plant (VPP) operations.
- Wholesale Exposure Management: Facilitate secure market access and risk mitigation through licensed retail and aggregation partners.
- Optimized Revenue Stacking: Simultaneously capture multiple revenue streams where operational parameters permit concurrency, while explicitly modeling and avoiding conflicting obligations.
Transparency and Reporting
- Comprehensive Audit Trails: Log every automated dispatch decision alongside its activating trigger, executed action, and validated physical constraints.
- Standardized Performance Metrics: Report financial savings and carbon emissions using transparent, fully inspectable calculation methodologies.
- Real-Time Analytics: Provide live operational dashboards tracking system performance, financial costs, and carbon abatement.
- Predictive Anomaly Detection: Automatically flag degrading asset health or misconfigured operational limits before they result in financial loss.
- Standardized Data Export: Support transaction and interval data exports in industry-standard formats, including NEM12.
- Deep Diagnostics: Enable granular, per-asset diagnostics and protocol-level logging to streamline fault investigation and root-cause analysis.
Decision Audit Trail and Deterministic Dispatch
Deterministic Dispatch
The Voltron Controller executes dispatch based on a rigorous, explicit model of the site, incorporating asset capabilities, physical limits, tariff structures, environmental forecasts, and operational constraints. Because the logic is inherently deterministic, identical inputs consistently yield identical dispatch decisions, ensuring the underlying reasoning is fully transparent and mathematically verifiable.
This predictability is critical when managing physical plant infrastructure. A control system that behaves unpredictably cannot be safely commissioned, cannot satisfy stringent grid connection agreements, and cannot be entrusted with the critical energy reserves required for facility resilience.
Decision Audit Trail
Every action executed by the controller is comprehensively logged alongside its underlying rationale. This record includes the specific telemetry signal that triggered the action, the alternative options that were evaluated and discarded, and the physical constraints validated prior to execution.
The ultimate benchmark of this transparency is that a site’s own engineering team must be able to independently verify operational data without requiring vendor intervention or clarification. For financial savings to be confidently billed, audited, or reported, the supporting evidence must be entirely transparent and rigorously inspectable.
Why: Evening peak; network demand window open; forecast price falling after 18:00
Checked: SOC 78% > 35% obligation floor · inverter limit 1,000 kW · transformer 92% rated · reserve for critical load intact
Why: Spot price negative; exporting would cost money
Checked: Battery absorbing 310 kW to SOC ceiling · EV chargers raised to 180 kW to absorb surplus · site load 220 kW
Why: Site approaching 780 kW demand high-water mark; shaving avoids resetting the demand ratchet
Checked: Group B cable run rated 110 kW · no session below minimum deliverable current · priority channel unaffected
Why: Battery SOC sufficient to carry load to solar onset; running cost exceeds import cost at current tariff
Checked: SOC 46% · forecast PV onset 06:20 · projected floor 31% > 25% reserve
Illustrative example. Values shown are for a representative 1 MW commercial site, not a specific installation.
A prime example of AI in a microgrid controller is predictive solar and load forecasting. Machine learning algorithms analyze historical site consumption, real-time weather data, day-of-week trends, and localized temperature forecasts to predict exactly how much energy a facility will need tomorrow, and how much power its solar arrays will generate.
The microgrid controller then takes these probabilistic AI forecasts and feeds them as inputs into its deterministic dispatch engine. For example, if the AI predicts heavy cloud cover and a spike in facility demand for the following afternoon, the deterministic engine will calculate that the battery won’t charge sufficiently from solar, and will automatically schedule the battery to pre-charge from the grid overnight during low off-peak tariff periods.
Operating modes
A commercial microgrid cycles between three states continuously, and the transitions matter more than the states.
Under baseline operation, the controller executes a localized energy optimization strategy. On-site solar generation primarily offsets immediate facility demand, while excess yield is captured by the energy storage system. To minimize operational expenditure, the battery discharges during high-cost Time-of-Use (TOU) windows, actively reducing grid imports and mitigating peak demand spikes. Simultaneously, EV charging is dynamically allocated to periods of surplus generation or off-peak grid pricing.
When subject to a market capacity obligation or external dispatch instruction, the controller dynamically reserves the required State of Charge (SOC) for the duration of the contracted window. It executes the dispatch upon command, and immediately reallocates any remaining capacity back to the facility’s baseline economic optimization once the obligation is fulfilled.
In the event of a utility grid failure, the controller autonomously isolates the facility at the main breaker and establishes a localized microgrid using the battery system. It dynamically dispatches backup generators to sustain critical operations and automatically sheds non-essential loads according to predefined facility policies. Once stable utility power is restored, the system seamlessly resynchronizes with the grid and safely reconnects the facility without disrupting operations.
Seamless Integration & Interoperability
The Voltron Controller is engineered to manage your existing infrastructure. We eliminate the need for costly re-platforming and prevent vendor lock-in by completely decoupling the control software from hardware procurement.
Supported Protocols & Interfaces: OCPP 1.6 / 2.1, Modbus TCP/RTU (RS485), SunSpec, IEC 61850, CAN (BMS), REST / Webhooks, MQTT, BMS and SCADA interfaces, NEM12 export, Genset AMF and sync, and revenue-grade metering.
Hardware Agnostic (“Any Asset”)
Procurement decisions for batteries, inverters, generators, meters, and chargers remain entirely with the facility’s engineering team. To the control layer, hardware branding is simply a configuration detail.
Flexible Market Access (“Any Route to Market”)
The platform is completely retailer and aggregator agnostic. Market access is facilitated through your choice of licensed partners, rather than restricted by a bundled service contract.
Fail-Safe Architecture (“Degrades Safely”)
In the event of lost communication with the cloud, an aggregator, or a charger management system, the controller automatically defaults to a predefined, secure local control state, guaranteeing operational stability rather than falling into an undefined state.
EV Charging Control: Local Authority, Cloud Reporting
EV charging represents the most volatile load on a commercial microgrid, yet it is also the most highly controllable. The architecture below establishes a strict division of responsibilities: physical power authority is enforced locally by the Voltron Controller, while commercial operations are managed by the cloud-based Charge Point Management System (CPMS). This structure is the preferred configuration for industrial sites, remote operations, and heavy fleet depots, where local grid stability must always supersede cloud-based functionality.
What the Voltron Controller Owns
All decisions impacting the facility’s power budget. The controller continuously monitors the grid connection limit, active solar generation, battery State of Charge (SOC), and islanding status. Based on this telemetry, it writes a hard kilowatt ceiling to each charger via a secure local industrial connection. These limits are updated every few seconds and strictly override any conflicting commands from the cloud.
What AMPECO Owns
All user-facing and commercial functions. This includes driver authentication (via RFID or card), payment processing, tariff application against metered energy, session logging, and exportable fleet reporting. AMPECO operates as the financial ledger, receiving standard OCPP payloads, such as StartTransaction, StopTransaction, and MeterValues, exactly as it would in a conventional deployment.
Mandatory Passive Cloud Configuration. To ensure operational stability, the cloud platform must be configured in a strictly passive state. All cloud-based smart charging and dynamic load management (DLM) features must be explicitly disabled for the site. If the cloud platform attempts to push a charging profile that conflicts with the microgrid controller’s local limit, the hardware receives competing setpoints. This results in power oscillation and inevitable charger faults. Deactivating cloud control is a mandatory configuration requirement, not a design assumption, and failing to enforce this is the single most common cause of system failure in this architecture.
Two Ways to Implement Local Control
- Method 1: Dual-Protocol Architecture (Optimal). Enterprise-grade chargers (such as Kempower, ABB, and Tritium) support concurrent communication protocols. Under this model, the microgrid controller connects locally via Modbus TCP, reading real-time telemetry and writing hard power limits directly to the charger’s registers. Simultaneously, the charger maintains an independent OCPP session with the cloud platform strictly for billing and authorization. Because the two data streams are entirely segregated, there is no risk of command conflict.
- Method 2: OCPP Proxy Gateway (Fallback). If the charging hardware only supports OCPP, the local controller must act as a transparent proxy. The chargers are configured to route their OCPP traffic to the local controller rather than the cloud. The controller intercepts the connection, injects its own SetChargingProfile commands to enforce site-level power limits, and then securely forwards the authorization requests and meter values upstream. The cloud platform behaves exactly as if it were communicating directly with the chargers.
The Trade-Off, Stated Plainly
- The Advantage: Absolute Resilience. This architecture guarantees local stability. If the facility loses internet connectivity, the cloud platform drops offline, but the microgrid controller continues to manage the chargers seamlessly. The microgrid does not trip, site limits remain strictly enforced, and vehicles continue charging.
- The Concession: Loss of Driver-Level Prioritization. Because the local controller only evaluates electrical loads, it is blind to user identity. It cannot throttle a visitor’s vehicle to prioritize a critical fleet vehicle. Driver profiles and vehicle State of Charge (SOC) reside in the cloud platform, which has ceded active power authority. If granular prioritization is more critical than local outage resilience, the cloud-led alternative is required.
The Alternative: Cloud-Led Capacity Negotiation
If driver-level prioritization is the absolute priority, a cloud-led architecture is the standard approach. Rather than splitting power control from reporting, this model utilizes two distinct protocols operating at two different layers.
- OSCP (The System-to-System Negotiator): The Open Smart Charging Protocol operates strictly between software systems. It transmits an aggregated energy budget from the local controller to the cloud platform (e.g., establishing a 200 kW limit for the site over the next four hours). OSCP can also transmit 24-hour capacity forecasts based on anticipated solar generation, but it remains completely blind to individual drivers or tariffs.
- OCPP (The System-to-Device Executor): Operating at the hardware level, the cloud platform receives the aggregated OSCP budget, applies its internal logic to prioritize connected vehicles based on driver profiles, and then dispatches tailored OCPP charging commands to each specific connector. In this model, final power authority resides in the cloud.
Corporate Vehicle to Grid: How OCPP 2.0.1 and 2.1 Change the Picture
- Distributed Energy Resource (DER) Control: OCPP 2.1 introduces dedicated functional blocks for DER management. Rather than merely throttling charger output defensively to prevent grid overloads, the charging platform can now be explicitly instructed to prioritize the consumption of on-site solar generation and stationary battery storage over expensive grid imports.
- Bidirectional Power Transfer (V2G/V2B): Supported by the ISO 15118-20 standard, corporate EV fleets transition from passive loads into dispatchable energy storage. Instead of simply pausing a charge session during peak demand events or grid outages, connected vehicles can actively discharge power back into the facility to sustain critical operations and offset peak tariffs.
Protocol behavior and integration architectures described here reflect design intent and are not a certification claim. Charger protocol support varies by make, model and firmware and must be confirmed per site. Payloads shown in the interactive diagram are illustrative examples.
Where It Runs
Remote and Off-Grid Industrial
- Operational Goal: Minimize fuel consumption and generator run-time while maximizing renewable energy contribution, with zero tolerance for compromised availability.
- Coordinated Assets: Solar arrays, Battery Energy Storage Systems (BESS), diesel or HVO generators, and critical process loads.
Commercial and Industrial Microgrids
- Operational Goal: Mitigate peak demand charges, defer costly network upgrades, maximize solar self-consumption, and manage embedded network supply for tenants.
- Coordinated Assets: Rooftop solar, batteries, site load profiles, and tenant sub-meters.
Service Stations & Public EV Charging
- Operational Goal: Enable the installation of high-power DC fast chargers without exceeding existing grid connection limits, maintain operational continuity during outages, and ensure strict compliance with hazardous-area separation protocols.
- Coordinated Assets: Canopy solar, batteries, HVO backup generators, DC fast chargers, and retail facility loads.
Fleet and Depot Charging
- Operational Goal: Orchestrate fleet-wide charging within the constraints of existing electrical infrastructure, ensuring vehicles are charged using the lowest-cost available energy.
- Coordinated Assets: Solar generation, batteries, and clustered AC/DC charging infrastructure.
Micro Data Centers & Edge Compute
- Operational Goal: Guarantee continuous power for mission-critical loads while simultaneously utilizing the primary battery for market revenue generation, without compromising resilience.
- Coordinated Assets: Primary battery systems (operating upstream of the IT UPS), solar, generators, and precision cooling loads.
Portfolios and Virtual Power Plants (VPP)
- Operational Goal: Aggregate multiple distributed energy resources into a unified market position, unlocking wholesale value and grid service revenues that individual sites cannot access alone.
- Coordinated Assets: Geographically distributed batteries, solar arrays, and aggregated flexible loads.