The CIOS AI assistant is a read-only helper that answers questions about the live MDCX plant using the same site APIs an operator already has.
It can look up health, tickets, usage, metrics, and capacity forecasts. It cannot change a setpoint. Writes always go through controlled writes.
Read-only by design
The assistant's tool list is closed and read-only: health, list or get a ticket, list usage, query metrics, and capacity forecast. Unknown tools are refused. There is no write verb in this list, and there is no back door around the site API.
If you need a pump, breaker, or valve to move, you use the controlled-write flow — including Class A two-person approval. The assistant will not do it for you.
Your data stays on premises
Inference is local. The model host must be on the site or on your private network (loopback or a private address). Public DNS names and public IP addresses are refused, including after a redirect.
Site data — ticket text, telemetry, usage — is concatenated into the prompt. That is why the red line is fail-closed: a public model host would be an exfiltration path. The assistant talks to CIOS over the site API; it does not phone home.
What to ask it
Typical questions:
- What is firing, and which tickets are still open?
- Show usage for this site over the last period
- Query a path or a glob — temperature, flow, status
- What does the capacity forecast look like for power and cooling?
- Is the core healthy?
Ask for analysis and summary. Do not ask it to execute a write. For how points are named, see the asset model.