IOC Was Discovered From the Field Up.
Infrastructure Orchestration Core did not begin as a software theory. It began with real buildings, real circuits, old timers, wasteful schedules, and the realization that ordinary demand was physically connected but logically blind.
Smart Light Management proved the first wedge: circuit-level control for routine lighting loads. IOC is the broader architecture behind that discovery — a physical operating layer for ordinary demand below the meter.
From Field Problem to Operating Layer
The Discovery
The original problem was simple: routine building loads were being controlled by old schedules, timers, disconnected devices, and manual site visits. The deeper problem was structural: ordinary demand had no operating identity at the boundary.
The timer problem
Legacy timers could turn loads on and off, but they could not understand what the load served, how important it was, or how it should respond.
The blind circuit problem
Lighting, pumps, irrigation, plug loads, and routine equipment were physically connected, but operationally anonymous.
The operating layer problem
The grid could measure buildings through meters, but it could not see the ordinary demand structure underneath the meter.
Smart Light Management Was the First Wedge.
Lighting was the practical starting point because it is visible, repetitive, measurable, and retrofit-friendly. But IOC is not a lighting company. Lighting proved the first doorway into a much larger operating layer.
- Lighting: proved staged control, savings, schedules, visibility, and retrofit practicality.
- Irrigation: showed that water-side routines have the same missing-layer problem.
- Plug loads: revealed the need for reset, recovery, isolation, and proof.
- Pumps and equipment: showed that routine infrastructure needs envelopes and operating rules.
- Portfolios: showed that one building can become the proof for the next.
- IOC: names the broader architecture underneath all of those examples.
What IOC Believes
The thesis is practical: before civilization keeps overbuilding around blind demand, ordinary demand should become visible, ranked, bounded, locally enforceable, restorable, and verifiable.
Demand is not one number
Behind every meter are circuits, loads, zones, pumps, equipment, and priorities.
The boundary matters
The real operating layer begins where resource meets use.
Local behavior matters
Nodes should enforce safe rules locally, not depend only on remote commands.
Proof matters
The system must show what happened, what refused, and how it restored.
The Claim Boundary
IOC does not claim every load is flexible, every building saves the same amount, or that demand-side orchestration replaces generation, storage, transmission, utilities, or planning.
The Founder
IOC was developed by Mehdi Doorandish through years of field work with building infrastructure, circuit-level lighting control, timers, panels, electrical systems, routine loads, and the practical operating problems property owners face every day.
The core insight was simple but deep: buildings were already wired, but their demand was not truly governable. IOC was created to build that missing operating layer.
From Lighting Proof to Infrastructure Orchestration.
IOC began with ordinary building problems and grew into a broader architecture for making demand visible, ranked, bounded, locally enforceable, restorable, and verifiable.