Skip to content
Proof

What has actually been demonstrated?

IOC separates public third-party recognition, internally documented field evidence, developing embodiments, and proposed institutional fields.

The strongest public anchor remains a real multifamily lighting deployment at 8600 Glenoaks. Other deployments add meaningful physical evidence, but each result retains its own source, scope, maturity, measurement method, and limitation.

8600 Glenoaks — public proof anchor

A real existing multifamily property, a documented lighting-control project, and a result publicly recognized through the U.S. Department of Energy Integrated Lighting Campaign.

256fixtures in the deployment
50%+reported energy reduction
2024DOE / ILC recognition
Evidence maturity at a glance

Proof is not one pile of claims.

A recognized project, an internal field record, a working embodiment, and a future institutional field are all meaningful—but they are not interchangeable.

Public third-party anchor Externally published project evidence 8600 Glenoaks lighting scope, project partner, fixture count, recognition category, and reported reduction appear on the official DOE / ILC project page.
Internal field record Measured or documented operating evidence Garage, commercial, high-rise, monitoring, recovery, and continuation records support specific claims within their stated source and measurement boundaries.
Developing embodiment Physical architecture awaiting fuller outcomes Irrigation expansion, Rain Action, Water Activity Guard, EV sequencing, ventilation/VFD, and other forms need their own application-specific evidence.
Proposed institutional field Governed density beyond one property Feeder-aware, utility, municipal, manufacturer, and institutional fields require bounded demonstrations, permissions, and independent measurement.
Public third-party anchor

8600 Glenoaks — multifamily lighting control inside an existing building.

The official Integrated Lighting Campaign page identifies 8600 Glenoaks in Los Angeles as a 2024 recognized partner in the Advanced Use of Sensors and Controls for Lighting category.

The public record describes circuit-level control of 256 common-area and exterior fixtures and reports energy-consumption reduction of more than 50 percent. Smart Light Management is named as the project partner.

The claim boundary

What the Glenoaks result establishes—and what it does not.

What it establishes

  • Existing building circuits can be retrofitted without rebuilding the entire property.
  • Lighting schedules and output can be changed at the circuit level.
  • Prior and improved operation can be compared through real field evidence.
  • A contained first project can create measurable owner value.
  • A verified result can earn evaluation of the next property or operating responsibility.

What it does not establish

  • It is not government certification of the complete later IOC grammar.
  • It does not mean every property will save 50 percent.
  • It does not prove that every physical responsibility is flexible or controllable.
  • It does not prove irrigation, recovery, EV, ventilation, utility, water, or city outcomes before those applications produce their own evidence.
  • It does not remove site review, commissioning, code compliance, permissions, field expertise, or suitable equipment.
Current field record

The public anchor sits inside a broader physical record.

The examples below come from company project records and paid or active deployments. They are meaningful evidence, but they remain separate from the third-party public status of the Glenoaks recognition.

Measured garage operation · internal field record

54.3 to 23.6 kWh per day.

At an active Van Nuys multifamily garage deployment, documented staged lighting operation reduced daily energy during the measured period.

56.5%Documented reduction during the measured period—not a universal property result.
Before
54.3 kWh
After
23.6 kWh
Commercial continuation · internal calculation

Seven restaurant parking-lot poles.

A Glendale commercial deployment used staged 0–10 V lighting control. Company records estimate savings over approximately two years.

≈$6,000Internally calculated commercial evidence; exact tariffs, schedules, and time window belong with the project record.
7poles
0–10 Vstaged control
≈2 yrrecord period
High-rise pilot · contained evidence

Two floors before a 43-floor decision.

A contained San Diego high-rise lighting deployment established a practical baseline and staged-output test before any whole-building proposal.

2 / 43Two floors were tested. Full-tower savings remain a proposal question until the wider scope is measured and verified.
Visual shorthand only: contained pilot evidence must not be multiplied into a tower-wide claim without circuit count, operating hours, rates, and measured scope.
Cross-resource embodiment · outcome records developing

Irrigation, monitoring, and recovery are physically present.

Working six-zone irrigation nodes, paid monitoring channels, and deployed recovery paths show that IOC extends beyond lighting. Their outcomes remain application-specific.

IrrigationLocal six-zone scheduling and cellular/radio architecture.
MonitoringSelected circuit visibility supporting evidence and diagnosis.
RecoveryDefined restart paths for supported equipment.
Real IOC and Smart Light Management field installation beside existing electrical panels and circuit enclosures
Internally documented field installation Real panel-side retrofit work inside existing electrical infrastructure—not an idealized new-build environment.
This company field image is separate from the Glenoaks DOE / ILC public proof anchor.

Every future case study should carry its evidence with it.

A project-specific proof record should keep the physical context attached rather than turning the result into a floating marketing number.

  • Customer permission and public naming status
  • Dates, duration, equipment, circuits, zones, or channels
  • Baseline, tariff, schedule, and operating assumptions
  • Measurement method and source documents
  • What changed, what restored, and what remained unchanged
  • Claim maturity and explicit limitation
What remains to be proven

The architecture can extend before the outcome has been validated.

Physical embodiment, architectural readiness, commercial deployment, and institutional validation are different milestones.

Irrigation outcome

Does local scheduling and remote visibility reduce water and field burden?

Measure schedule compliance, rain holds when available, abnormal activity, site visits, runtime, water use where available, and owner or field-worker outcomes.

Recovery outcome

Did the supported system truly return?

Record the authorized interruption, restoration timing, device or network response, avoided trip, and whether service remained stable afterward.

Condition-governed equipment

Can ventilation, pumps, charging, and thermal duties answer inside safe envelopes?

Validate local sensors, permissions, dynamic criticality, full or partial capability, refusal, ordered restoration, and rebound behavior.

Institutional field

Does governed density become useful to a feeder, city, utility, or portfolio?

Design a bounded field with independent measurement, location relevance, participant permissions, cybersecurity, restoration, and evidence requirements.

Evidence discipline

Not every valuable result belongs in the same evidence category.

IOC separates direct field results from calculations, prevented operating costs, qualitative improvements, and future possibilities.

MeasuredMeter, bill, current, state, timing, event, water, runtime, or device evidence from a real deployment.
EstimatedCalculated from ratings, tariffs, schedules, samples, baselines, or clearly stated assumptions.
AvoidedPrevented truck rolls, excess runtime, repeated diagnosis, complaints, interruption, waste, or emergency response.
QualitativeBetter visibility, easier management, faster recovery, clearer maintenance, accountability, or less scattered memory.
ProjectedPotential future value across boundaries, properties, portfolios, utilities, water systems, cities, or institutions.
How the next proof is created

A useful first project reduces uncertainty before expansion.

The purpose of the first installation is not to force the second. It is to create enough physical evidence for an owner, operator, utility, city, or partner to make the next decision with less guesswork.

1

Define the physical responsibility and prior condition.

Name the property, circuit, controller, zone, device, served purpose, owner objective, baseline, and field constraints.

2

Choose the evidence before installation.

Decide what will be measured, estimated, observed, avoided, treated qualitatively, or left explicitly projected.

3

Install and commission the first node.

Confirm identity, authority, present condition, limits, local continuity, restoration behavior, and the reporting method.

4

Operate long enough to see the real pattern.

Collect the runtime, energy, water, state, recovery, refusal, restoration, labor, or service evidence appropriate to that project.

5

Let the result decide what comes next.

Repeat only where the responsibility, equipment, authority, installation method, and expected value remain meaningfully comparable.

Continue from here

Review the mechanism—or bring the next proof question.

How IOC Works

See how Identify, Govern, Answer, Continue + Restore, and Prove operate at one physical responsibility.

Property Owners & Managers

See how a property begins with one repeating burden, one physical entry, and a defined evidence plan.

Technical White Paper V2

Continue into the governed-boundary architecture, embodiments, deployment, conformance, and evidence boundaries.

Proof earns expansion

One verified boundary earns the next.

Bring one real physical problem and decide in advance what evidence will matter. The result—not the promise—determines whether the pattern should expand.

The 8600 Glenoaks recognition and reported energy reduction apply to that lighting-control project. Every new IOC application requires its own site review, permissions, commissioning, evidence method, maturity label, and claim boundary.