The AI Kernel is the intelligence layer of EnergizeOS. It reads audited operational data, produces recommendations and explanations, and routes every actionable suggestion through EMS safety gates. It holds no direct device authority of any kind.
| Aspect | Definition |
|---|---|
| Purpose | Conversational interface for operators and owners: answers questions about site state, history, performance, and risk in plain language. |
| Input data | EMS states, alarms, events, dispatch results, meter data, reports, documentation. |
| Output | Natural-language answers with citations to underlying records. |
| Decisions supported | Daily operations, shift handover, owner inquiries, incident review. |
| Must not control | No device commands, no setpoint writes, no alarm acknowledgement on equipment. |
| Aspect | Definition |
|---|---|
| Purpose | Quantifies and explains the difference between expected and realized revenue or savings. |
| Input data | Tariff/price signals, dispatch plans vs. results, meter data, availability and derating records. |
| Output | Ranked gap attribution (e.g., derate, missed window, forecast error) with monetary impact. |
| Decisions supported | Commercial review, performance guarantees, operational improvement priorities. |
| Must not control | Cannot modify dispatch or tariffs; analysis only. |
| Aspect | Definition |
|---|---|
| Purpose | Produces day-ahead and intraday dispatch plans optimized for value within hard constraints. |
| Input data | Load forecast, price/tariff signals, weather forecast, SOC, power limits, degradation cost model. |
| Output | Candidate dispatch plan with constraint check results and expected value. |
| Decisions supported | Plan approval by operator; automated execution only via gated EMS scheduler. |
| Must not control | Cannot push commands to PCS; plans execute only through the deterministic EMS scheduler after safety-gate validation. |
| Aspect | Definition |
|---|---|
| Purpose | Tracks degradation and recommends operating adjustments that protect asset life. |
| Input data | BMS rack data, SOC/temperature/current histories, cycle counts, health snapshots. |
| Output | Health trend, anomaly flags, recommended operating envelope adjustments. |
| Decisions supported | Warranty management, derate decisions, maintenance scheduling. |
| Must not control | Cannot change BMS or PCS limits; limit changes are engineering-controlled EMS configuration. |
| Aspect | Definition |
|---|---|
| Purpose | Explains alarms and faults: cause, criticality, affected functions, recommended response. |
| Input data | Alarm/event streams, relay status, interlock states, device fault codes, historical patterns. |
| Output | Structured explanation with severity classification and response guidance. |
| Decisions supported | Operator triage, escalation decisions, post-event reporting. |
| Must not control | Cannot acknowledge, suppress, or reset alarms or trip lockouts on equipment. |
| Aspect | Definition |
|---|---|
| Purpose | Simulates operating scenarios: outage response, peak events, export-limit stress, capacity changes. |
| Input data | Site data model, historical profiles, forecast data, asset parameters. |
| Output | Scenario outcomes, risk scores, sensitivity analysis. |
| Decisions supported | Planning, capacity decisions, operating procedure design. |
| Must not control | Simulation only; no interaction with live control. |
| Aspect | Definition |
|---|---|
| Purpose | Supports FAT/SAT execution: test sequencing, expected results, evidence capture. |
| Input data | Test procedures, interlock definitions, live status during supervised tests, prior results. |
| Output | Step-by-step guidance, pass/fail evidence records, deviation flags. |
| Decisions supported | Commissioning engineers during witnessed tests. |
| Must not control | Cannot initiate tests or operate devices; humans execute, the assistant documents and verifies. |
| Aspect | Definition |
|---|---|
| Purpose | Generates daily, monthly, and incident reports for owners and stakeholders. |
| Input data | Audited operational records, meter data, dispatch results, alarm history, revenue analytics. |
| Output | Formatted reports with verified figures and plain-language narrative. |
| Decisions supported | Customer communication, compliance records, management review. |
| Must not control | Read-only; reports cite audited records and never alter them. |