Perimattic
Technology and data analysis

Explainable AI

Every forecast ships with a plain-language explanation

Demand OS attributes every forecast to its contributing factors — seasonality, promotions, trend, and external signals — ranked by impact, so planners can defend a number without a day of analyst time.

Book a Demo

Per-SKU

Factor attribution on every forecast by default — no configuration required

43%

Of FDA warning letters cite inadequate change control documentation in supply operations

<2 min

Time to answer any 'why did this forecast change?' question in the planner workbench

How does explainable AI work in demand planning?

Demand OS attributes every forecast to its contributing factors — seasonality, promotional effect, trend, and external signals — ranked by impact and expressed in language a planner can present to a stakeholder. Every forecast value, override, and approval is logged with a full audit trail. No black boxes, no model shrugs, and no reconstruction effort when a regulator or a finance partner asks why a number moved.

The Problem

Why “the model decided” is not an acceptable answer

Black-box AI that planners cannot defend
When a machine learning model produces a forecast that looks wrong, a planner needs to be able to explain it to a sales director, a finance partner, or a regulator. "The model decided" is not an explanation. It is a trust problem that compounds every time it is given.
Regulatory review that cannot find the reasoning
FDA and EMA supply chain audits expect documented records of forecast changes, override decisions, and approval actions. A planning system without an audit trail creates regulatory exposure that is easier to prevent than to remediate.
Planner overrides driven by instinct rather than information
When planners cannot see why a forecast was set at a particular level, they override it based on experience and feel. Some overrides are correct. Many are not. Without factor attribution, there is no way to evaluate the override decision after the fact.
Forecast reviews that debate the number, not the driver
If the sales team's forecast and the statistical forecast diverge, the question is not who is right. The question is which factors each side is weighting differently. Without visible factor attribution on both sides, the review devolves into a negotiation rather than a fact-based reconciliation.

The Capability

How Explainable AI makes every forecast defensible

EXPLAINABILITY CAPABILITY
A forecast looks wrong and "the model decided" is the only explanation on offer.
Ranked Factor Attribution
Every forecast is decomposed into its contributing factors — seasonal index, promotional effect, trend component, external signal impact — and ranked by contribution magnitude, expressed in plain language rather than coefficient values.
EXPLAINABILITY CAPABILITY
An FDA or EMA audit asks for 24 months of forecast and override history with no structured record to hand over.
Full Audit Trail
Every forecast value, model update, planner override, and approval decision is logged with timestamps and user attribution, exportable in structured formats compatible with 21 CFR Part 11 electronic records requirements.
EXPLAINABILITY CAPABILITY
Answering "why did this forecast move?" takes an analyst a day of digging through spreadsheets.
AI Copilot Integration
Planners ask the Copilot why a forecast changed and get a grounded answer based on the factor attribution data — not a summary generated from model internals — in the workbench in seconds.

In Practice

A specialty pharma company passes its first FDA supply chain audit without a finding

The Situation
A specialty pharmaceutical company managing 14 commercial SKUs across three cold chain distribution lanes was using a combination of SAP APO and spreadsheets for demand planning. The FDA requested supply chain records during a facility inspection, requiring the company to produce a 24-month history of forecast changes, override decisions, and approval actions. The previous system had no structured audit trail — the reconstruction effort was estimated at three to four weeks.
What Demand OS Did
Demand OS maintained a complete, timestamped audit log of every forecast run, planner override, and approval action across all 14 SKUs. The log was exported in a structured format that mapped directly to the FDA electronic records request. Factor attribution was available for every forecast value in the audit window, showing the seasonal, batch supply, and patient demand factors that drove each forecast change.
The Outcome
The FDA audit resulted in zero supply planning findings. The audit trail export took four hours. The factor attribution documentation gave the review team a clear, non-technical explanation of every major forecast change over the 24-month window — eliminating the reconstruction effort entirely.
Analytics dashboard showing forecast factor attribution

Key Metrics

What transparency delivers in the first quarter

Explainable AI earns its keep in three numbers planning leadership already tracks. Demand OS reports all three continuously, from the pilot's first cycle.

9%reduction in unnecessary planner overrides when factor attribution is visible43%of FDA warning letters cite inadequate change control documentation in supply operations<2 minto answer any forecast question with full factor attribution in the planner workbench

Frequently Asked Questions

Explainable AI, answered

What factors does Demand OS attribute forecast changes to?+
The factor attribution framework decomposes each forecast into its contributing components: the baseline trend, the seasonal index, the promotional effect (if applicable), the impact of external signals (economic indicators, weather, market events), and any manual overrides applied by planners. Each factor is expressed as a percentage contribution to the total forecast value and ranked by magnitude of impact.
Is factor attribution available on every SKU by default?+
Yes. Factor attribution is generated for every SKU in every planning cycle without requiring any additional configuration. There is no separate explainability module to enable — it is part of the core forecast output. Planners can filter the attribution view by factor type, time period, or SKU segment.
Can the audit trail be exported for regulatory review?+
Yes. The audit trail is exportable in CSV and JSON formats with all required fields — timestamp, user attribution, action type (forecast update, override, approval), before and after values, and the reason logged by the planner. For pharmaceutical customers, the export format is designed to align with 21 CFR Part 11 electronic records requirements. Customers are responsible for validating the export within their own GxP environment.
How does Explainable AI help with S&OP reconciliation between statistical and commercial forecasts?+
When the statistical forecast and the commercial team's forecast diverge, the factor attribution view shows which drivers the statistical model is weighting. Commercial teams can identify whether the divergence is driven by a seasonal pattern the model is capturing that the commercial team discounts, or a promotional assumption the commercial team is including that the model does not have. The reconciliation becomes a conversation about specific factors rather than a debate about whose number is right.
Does the explanation capability work for all model types, including ML models?+
Yes. The factor attribution framework uses model-agnostic explanation methods (similar to SHAP values) that work regardless of the underlying model type — statistical, gradient boosting, neural network, or ensemble. The output is always expressed in business terms rather than model internals. Planners do not need to understand how the model works to use and trust the explanation.

Get Started

Ready to make every forecast defensible?

See ranked factor attribution and a full audit trail live on your own SKUs. You leave with accuracy benchmarks, a scoped pilot plan, and published pricing — all in one conversation.