Platform · sense
The signals we monitor.
A supply chain announces its problems early — a confirmation that doesn't arrive, a forecast that drifts, a carrier that starts declining tenders. The trouble is that those announcements are scattered across systems, and by the time a human collates them into a Monday meeting, options have expired. ADIP's agents read the signals continuously, at the source, so the decision starts when the signal fires — not when the report runs.
Six signal families
- Order signals. Committed orders vs. available-to-promise, promise dates at risk, holds and releases, allocation pressure building on a constrained SKU.
- Supply signals. Supplier confirmations (and their silences), OTIF drift, lead-time inflation, purchase orders aging past their acknowledgment windows.
- Inventory signals. Positions against safety stock, expiry horizons, imbalances across locations, the slow build of excess where demand moved and stock didn't.
- Logistics signals. Tender rejections, transit-time variance, port and lane disruptions, the reroute that costs less today than the delay costs next week.
- Demand signals. Forecast-vs-actual deviation, order-pattern breaks, promotions and seasonality colliding with capacity.
- External signals. The world outside your four walls — weather, strikes, supplier news — read as context that changes which internal signals matter.
A signal is not an alert
Dashboards already produce alerts — most of them noise, all of them homework. In ADIP a signal is the start of a decision: the agent that caught it prices the options, applies the constraints and preferences in the Judgment Layer, and arrives with a recommendation and its alternatives — not a red dot. If the decision clears the bounds you've set, it can run; if not, it waits for a human with the work already done.
That's the difference between monitoring and sensing: monitoring tells you something happened; sensing starts doing something about it.
Where the signals come from
No new sensors, no rip-and-replace: agents read the systems your operation already runs — ERP, order management, WMS, TMS, planning — the same categories they write decisions back to. Which signals matter most, and the thresholds that make them fire, are set per deployment and tightened by the Judgment Layer as your team's responses accumulate.
Signal families are illustrative of what ADIP agents watch; the concrete signal set and thresholds are established per engagement. SCOR — the Supply Chain Operations Reference model — is stewarded by ASCM.