Evaluation
Send one export.
Get the answer in three weeks.
We run your own historical data with the outcome withheld from us, and report how many hours of warning the engine would have given, and how often it would have been wrong. There is no fee, no integration and no connection to anything you operate. If the answer is unimpressive you will have that in writing too.
01 How it works
Three steps, and one of them is yours.
You send one export
Twelve to twenty-four months of logged sensor data from a single system. Whatever your control system or historian exports is fine: CSV, Excel, a database dump. Plus a short note on what each channel measures and which readings your operators actually trust.
We run it blind
You give us the dates of two or three events you would like explained. Dates only. Not what happened, not how it ended, not what you think caused it. If we know the answer we can find it, and so could anyone. Withholding the outcome is what makes the result mean something.
You get a written report
How many hours ahead the engine would have flagged each event, the false alarm rate across the quiet stretches, the model structure and assumptions we used, and the cases where it failed. Yours to keep and circulate internally, whatever it says.
02 Terms
What you are agreeing to.
Nothing. There is no fee for an evaluation and no commitment attached to one.
None. We never connect to a live system, we never touch a control loop, and we never change a set point. This is a file, offline, on our machines.
Mutual NDA before anything moves. Your data is never used to train anything for anyone else, and it is deleted when the report is delivered.
You get that in writing too. A negative report is still a report you can use, and it costs you an hour to find out.
If the result earns it, a paid ninety-day pilot on one system with an agreed performance floor. If it does not, we say so and you have lost a file.
The engine is read-only. It reads a file and returns a forecast with a confidence band. It connects to no control loop and changes no set point.
03 Request
Tell us what you have.
A rough answer is fine. If you are not sure what you log or whether it is usable, say so, that is a normal place to start and it is a five minute conversation rather than a project.