Project
Choose or create your Anomaly Detection project.
A scope for data drafts and saved scoring history
- Scope
- Anomaly project
- History
- Saved scoring runs
- Selection
- Choose intentionally

MAG OptiAIOperational AIAnomaly DetectionEarly Access
Find unusual points in your operational series and review them in context. Prepare the data, choose a detector, run scoring and inspect the flags and explanations before deciding what needs attention.
Prepare the series. Choose the detector. Review what the flagged points mean.
The anomaly challenge
Data quality, the surrounding pattern and detector settings shape which observations deserve review.
An unusual point deserves a look at the input as well as the outcome.
Dates, values and optional contextual inputs need to represent the series correctly. Missing or inconsistent records can change how a result should be interpreted.
Impact
Review data readiness before drawing conclusions from flagged points.

The challenge is more than highlighting a spike.
It is reviewing unusual points with their data, detector settings and operational context connected.
Why MAG OptiAI
Keep the data, detector settings and scoring result connected throughout the review.
Prepare or restore a named data draft with the series and applicable contextual inputs.
Choose a supported method and inspect the settings used to identify unusual points.
Inspect flagged observations, scores, threshold and available explanation before deciding what to investigate.
Saved projects hold data drafts and scoring history. Review the data and detector settings behind the result you are investigating.
Process
From a prepared series to unusual points you can review.
MAG OptiAI guides your team from preparing the data to choosing a detector and reviewing its scoring result.
Choose or create your Anomaly Detection project.
A scope for data drafts and saved scoring history
Prepare and validate the data draft.
Dates and values · applicable contextual inputs · upload or samples
Choose the detection method and scoring settings.
Supported detector · applicable seasonality and sensitivity settings
Run scoring for the prepared series.
Generate and save scores, the returned threshold and flagged indices
Review the unusual points and their context.
Series chart · flagged points · scores · exports · grounded explanation
Core capabilities
A connected workflow for preparing series data, configuring detection and inspecting unusual points.
Upload or use samples, inspect readiness and restore saved data drafts.
Use single-series or multivariate inputs where supported by the detector.
Select from Z-score, seasonal/contextual methods, Isolation Forest, LOF and One-Class SVM.
Unusual points.
Review with context.
Configure the settings supported by the detector and inspect the returned threshold.
Open a saved scoring run intentionally as the reference result.
Review series charts, flagged observations and scores, then export results.
Use the applicable seasonal and contextual settings of the chosen method.
Ask for interpretation tied to the successful anomaly result and its context.
Upload or use samples, inspect readiness and restore saved data drafts.
Use single-series or multivariate inputs where supported by the detector.
Select from Z-score, seasonal/contextual methods, Isolation Forest, LOF and One-Class SVM.
Use the applicable seasonal and contextual settings of the chosen method.
Configure the settings supported by the detector and inspect the returned threshold.
Open a saved scoring run intentionally as the reference result.
Review series charts, flagged observations and scores, then export results.
Ask for interpretation tied to the successful anomaly result and its context.
All in one place.
The tools to prepare, score and review in one connected workflow.
Anomaly Detection in action
Review the unusual points alongside the surrounding series. This illustration explains the concept; it is not a measured detector result.
Inspect the point's value, score, returned threshold and surrounding observations. Expected values can provide additional context where the detector returns them.
Use flags to focus investigation. An unusual value does not by itself establish a fault or root cause.
| Observation | Value | Review |
|---|---|---|
| Point 4 | 130 | Flagged for review |
| Point 8 | 38 | Flagged for review |
Who it’s for
For teams reviewing unusual observations in a defined operational series.
Prepare a relevant series and investigate changes, spikes or drops against its operational context.
Select supported methods and evaluate applicable seasonal, contextual and sensitivity settings.
Inspect scoring outputs and surrounding observations before deciding what needs attention.
Every series and review question is different. Evaluate whether the selected detector and inputs provide useful signals for your investigation.
The Anomaly Detection Evaluation
Bring your anomaly review question and evaluate the fit with your organization’s information.
Apply through the existing beta process to evaluate beyond the smaller free-trial limits.
Frame the operational question and prepare a series with the applicable context.
Choose supported methods and inspect the settings used for scoring.
Discuss setup difficulties, unclear flags and requirements that need a better fit.
Inspect flagged observations and available interpretation to judge usefulness for investigation.
Bring the operational series and the unusual patterns your team wants to investigate.
Provide dates, values and applicable contextual inputs. Anonymized data should retain the patterns and required relationships.
Tell us where preparation, detector configuration or interpretation needs improvement.
Investigate the flagged points in your operational context before drawing a conclusion.
Real Problem
Real Evaluation
Better planning decisions.
Bring your anomaly detection problem and real or anonymized historical data. We will review the fit and help you get started.
Anomaly Beta
What to know before evaluating your anomaly requirements.
Start with a dated series and a clear review question. Prepare the values and contextual inputs required by your chosen method, then review the product's requirements and readiness checks.
The current workspace supports Z-score, STL Z-score, contextual Z-score, Isolation Forest, Local Outlier Factor and One-Class SVM. Input and setting requirements depend on the method.
This product's workflow is Data, Detector and Score. Choose the detector and scoring settings, run scoring and review saved results. It does not use Forecasting's model-training and staging workflow.
Yes, where supported by the selected detector and dataset. Applicable settings and input requirements differ between methods.
No. Review the method, returned threshold and flagged points together. Scores should not automatically be interpreted as probabilities or compared as if they share one scale.
No. A flag identifies a point for review under the selected method. Check the surrounding observations and operational context before deciding whether there is an issue.
Early Access describes product maturity. Start Free uses the existing 14-day trial with lower limits. Larger evaluations use the existing beta application and team approval; there is no separate access-request system.
Explanation can interpret the successful scoring result and available context. It does not prove root cause, establish causality or replace an operational investigation.
Use Apply for the Anomaly Detection Beta to reach the existing product-specific application. Our team reviews your requirements and confirms the fit for an evaluation.
Still have a question?
Talk to us about your anomaly evaluation.
Ready to get started?
Tell us about your operational series and anomaly review requirements. We will review your application and confirm whether the current Anomaly Detection Beta is a good fit for your organization.
No payment requiredApplication reviewed by our team