Prism usage
Phaidra Prism is a one-stop shop for working with your data. It sits on top of everything the site already has: live telemetry, alarms, historical trends, and the site's own documents and drawings. When you ask it something, it pulls from all of that at once instead of you jumping between four tools to piece the story together.
Prism works for many different use cases:
Operators use it day-to-day to keep an eye on the plant, and Prism keeps an eye on it too: fault detection and anomaly algorithms run continuously, so a chiller quietly losing a point of efficiency or a valve hunting on the night shift shows up as an insight rather than a work order three weeks later. From there it shines at root cause analysis. Whether the issue found you or you went looking for it, Prism lines up the trend data, the alarm history, and what the equipment's supposed to do, then gives you a clear explanation instead of a chart to decode on your own.
Facility managers and energy engineers lean on that same root cause view to go a level deeper by studying system behavior over time, spotting optimization opportunities backed by real data instead of hunches, and putting a dollar figure on what a problem is actually costing.
And none of it is a black box. Prism shows the data behind its reasoning, so every answer comes with the evidence attached.
Prism is for diagnosing, troubleshooting, and analyzing data center systems. Don't use it for anything else. Specifically, don't:
Use it off-topic
It's not a general-purpose assistant. Keep it to data center infrastructure work.
Try to jailbreak it
No prompts designed to bypass its guardrails, unlock hidden behavior, or get it to act outside its intended scope — including role-play framing, "ignore previous instructions," encoding tricks, or hiding instructions inside uploaded files and logs.
Fish for internals
Don't try to extract system prompts, configuration, model details, or anything else about how Prism works under the hood.
Use outputs to build a competitor
No training, fine-tuning, distilling, or benchmarking another model on Prism's responses.
Attack or stress-test it
No scanning, reverse engineering, vulnerability probing, or automated adversarial testing without written permission.
Feed it data it shouldn't have
No personal data, health records, payment info, export-controlled material, or classified information unless separately agreed.
Act on outputs blindly
Prism can be wrong. A qualified person reviews and verifies before anything touches thermal, power, or life-safety systems.
Pass outputs off as verified
Don't present Prism's answers as human-authored or as certified by Phaidra.
Share credentials
You're responsible for everything done under your accounts.