Industrial HVAC · cross-cloud
Facilities and energy teams ask questions across HVAC estates that already span Azure, AWS and on-prem historians. Our engineers shipped a governed question layer so the answer is produced next to the data, not in a public model.
Energy and facilities teams could not ask a simple question of the plant. Telemetry sat in three places at once: Azure, AWS, and on-prem SQL and historians. Each vendor controller spoke a different schema. A specialist wrote a new query for every site. A cloud copilot could see one tenant and invent SQL against the rest.
Cross-Cloud Query Governance & Validation Flow
If the question is English, does the SQL still run with the caller database role, in the cloud the data already lives in?
A governed question layer on Private AI Foundation, inside the delivery environment, not in a public model.
A catalog of approved schemas per environment: Azure stores, AWS stores, on-prem SQL and time-series. A planner that turns English into a bound plan, not free-form SQL. Execution with the caller database role. The model never gets a raw admin connection. The answer comes back with the rows, the SQL that ran, and which environment it hit.
DLP on occupancy and identity joins. No path out of the tenant.
Enterprise boundaries / Guardrails
Plant telemetry, occupancy and energy data often cannot leave the tenant. A query that works in one cloud copilot still cannot see the other historian or the on-prem SQL box. Invented SQL against a live plant is a safety issue, not a convenience.
These controls run on Private AI Foundation. Every ask goes through the same path.
Thirty to forty-five days. Fixed fee. In the customer environment. One site, one question class, two stores. Success criteria and conversion price agreed in writing before starting. If it misses the threshold, the customer keeps the report and owes nothing further.
A typical first question: which AHUs drifted setpoint against outdoor temperature over a fixed window, answered without copying the data together. Expert-agreed answers, zero unsanctioned SQL, no egress.
Talk to an engineer about air-gapped, on-prem or single-tenant deployment for this workflow.
Contact usA paid proof of value, 30 to 45 days, in your own environment. Success criteria agreed in writing before we begin.
In your office, on your documents, with the cable pulled out. No competitor's sales engineer can do this.
