Week 1-2
Data review and setup
Review available telemetry, map the target system, and prepare a read-only data flow.
Start with a focused pilot to see whether Neraium can surface useful abnormal-behavior observations for your operators.
What We Scope
Timeline
Week 1-2
Review available telemetry, map the target system, and prepare a read-only data flow.
Week 3-4
Build a picture of normal operating behavior and look for readings that move together.
Week 5-6
Review any abnormal-behavior observations with your operators and compare them to known events.
Week 7-8
Deliver a clear summary of what worked, what did not, and whether expansion makes sense.
Deliverables
A plain-English view of what normal looks like across your selected system.
A summary of abnormal behavior observations and how they compared with your operating history.
A practical recommendation for how operators would review and use Neraium observations.
Commercials
Final pricing is set after fit-call scoping.
Pilot ROI Calculator
Pilot FAQ
We start with existing telemetry exports or read-only connections and scope the pilot to one environment first.
No. Neraium is designed for observation and review. It does not write commands, change setpoints, or control equipment.
We define data boundaries before ingestion, use scoped access, and keep the pilot focused on the minimum data needed for review.
The goal is to review early directional findings during the pilot and decide whether they are useful enough for your team to keep using.
Operator Brief
Share this with operators and facility leadership: problem, approach, pilot plan, and benchmark disclosure.
Ready to evaluate one system?