Will this just add more alarms?+
No — the opposite. FDD replaces threshold floods with a ranked deviation view and likely causes, and nuisance alerts are reviewed out during tuning.
What data do we need to start?+
Most engagements start with 6–24 months of historian, lab or document data. We audit coverage in the first week and tell you plainly if it is not enough — before you commit.
How long until we see results?+
A proof of concept on your historical data typically lands in 4–8 weeks. Production deployment follows once the KPI target is met and your team signs off.
Where does it run, and who sees our data?+
On your infrastructure — plant-side servers, your Azure or AWS tenancy, or an air-gapped network. Data never leaves your boundary, and nothing is used to train third-party models.
Who owns the result?+
You do. Handover includes source code, documentation, training sessions and a retraining plan.