IOC is designed to work beneath and alongside the systems already coordinating, communicating, analyzing, and controlling.
The missing operating layer for ordinary demand below the meter
IOC is not a replacement for the systems already above or beside the building. It adds the receiving layer that lets an ordinary physical boundary know what it serves, who may act, what is safe now, when it may refuse, how it continues, how it restores, and how it proves the result.
This is not a feature contest. The question is which operating responsibility each layer carries—and which questions still remain unresolved where digital intention becomes physical action.
IOC is designed to work beneath and alongside the systems already coordinating, communicating, analyzing, and controlling.
Connectivity and command do not by themselves establish served purpose, local permission, lawful refusal, continuity, restoration, or proof.
Lighting, ventilation, charging, irrigation, recovery, and other responsibilities can share one operating grammar without becoming identical.
Most systems above the load assume that the endpoint is already known, authorized, available, safe, connected, and restorable. IOC places those responsibilities at the physical boundary instead of leaving them scattered among software, installers, operators, and human memory.
The difference becomes clearest when a wider condition asks the building to change.
The system reaches a device or group and asks for a change. Local responsibility may remain implicit or distributed elsewhere.
The condition becomes a bounded request. Each responsibility evaluates what is lawful and truthful now.
One wider condition can reach many physical systems. Their answers remain different because their served purposes, present conditions, and safe envelopes are different.
A schedule, property objective, or wider event may request lower output. The boundary preserves required visibility, duration, local continuity, restoration, and evidence.
The VFD executes speed. Sensors and safety controls establish reality. IOC governs whether a requested reduction belongs inside the approved contaminant, equipment, timing, and restoration envelope.
Charging may pause and recover before a deadline. An irrigation node retains its complete local schedule and can honor an authorized temporary hold when that capability is commissioned. Neither responsibility is merely “off.”
A router, gateway, reader, intercom, or controller can remain monitor-only until an authorized fault condition permits a bounded interruption, cooldown, restart, verification, and escalation path.
Utilities, VPPs, DERMS, BMS/BAS, EMS, OpenADR, smart panels, controllers, VFDs, device platforms, storage, and AI can remain valuable. IOC does not need to replace them to change the quality of physical participation beneath them.
The video introduces the earlier comparison language in a concise form. The page above now provides the canonical distinction: systems coordinate, communicate, optimize, and execute; IOC governs the physical responsibility.
Individual products may combine several functions, and implementations vary. These references describe common architectural roles rather than every feature of every product.
Supervise, schedule, integrate, analyze, and control building equipment and operating points.
A continuing responsibility-centered operating record at the physical boundary, including local authority, refusal, offline continuity, restoration, and proof—even where the central building layer is absent or temporarily unavailable.
Provide sensing, telemetry, remote access, device communication, and application-level automation.
A common operating grammar that makes connectivity accountable to served purpose, authority, local limits, continuity, restoration, and evidence.
Provide circuit monitoring, switching, energy insight, backup prioritization, and load management within the product architecture.
A responsibility-centered layer that can enter at the panel, controller, plug load, valve, equipment interface, or other boundary and remain intelligible across approved hardware, interface, and communication changes.
Carry events, requests, prices, reliability conditions, state, and data between parties and systems.
Authority, eligibility, lawful refusal, local continuation, ordered restoration, and proof at the receiving physical boundary.
Invite, incentivize, or require changes in customer consumption during price or reliability conditions.
Differentiated endpoint capability: what may respond, what must remain protected, what can answer partially, and how normal service returns.
Aggregate distributed resources and flexible loads to support market, portfolio, or grid objectives.
A more dependable physical resource layer beneath aggregation, where ordinary demand can declare truthful capability instead of appearing only as an anonymous controllable block.
Monitor, forecast, optimize, and coordinate distributed energy resources for distribution-system operations.
A governed demand-side endpoint beneath DERMS, including identity, local judgment, refusal, continuity, restoration, and event evidence.
Store energy at one time and deliver it later, shifting availability and supporting resilience or grid objectives.
Governance of the consuming responsibilities themselves. IOC does not store electricity; it helps known physical duties use, defer, protect, restore, and prove consumption more coherently.
Analyze, predict, compare, recommend, compose schedules, and present operating information.
A deterministic physical layer where an approved digital intention is evaluated against local authority, served purpose, present condition, and limits before action, with accountable governance and returned proof.
Provide strong specialized control inside one equipment category, protocol, or vendor domain.
A common cross-resource grammar that preserves the specialized control while making unlike physical responsibilities legible through shared identity, authority, continuity, restoration, and proof.
Follow the public operating sequence from identifying the physical responsibility through governance, answer, local continuation, restoration, and proof.
Continue into the governed-boundary architecture, two-level operating map, served purpose, dynamic criticality, authority, refusal, continuity, restoration, conformance, embodiments, and evidence requirements.
See which results are publicly sourced, internally documented, developing, or proposed—and where each claim stops.
Follow the five movements at one ordinary boundary, review the evidence, or map the physical responsibility your present stack still leaves unresolved.