Phase 2 · Node Layer 08 · The Signal

Suppliers got the wrong signal.
Every day since November 2025.

Tennant's disclosed language is precise: the system was "not providing correct demand signals to suppliers." That is a specific technical failure with a specific downstream cost — material shortages, expedited freight, manual PO workarounds, delayed shipments, and order-to-cash disruption. This page is what that signal failure actually means, and how the parallel layer recomputes the signal from live orders instead.

Incorrect signals since Nov 2025 Manual POs compensating Recomputed from live orders Restorable in weeks 3–8 months to H1 2027
The Contrast

Same orders. Same suppliers.
Different signal.

Every order Tennant receives still exists. Every supplier Tennant uses still exists. What broke is the translation between them — the demand signal that tells a supplier what to ship, when, and in what quantity. Here's the broken path and the restored path, side by side.

Signal Path · Broken SAP Live State

IN Order intake delayed
SC Signal computation broken
PO Supplier PO incorrect
MF Material flow mismatch
EX Expedited freight surcharge
SP Shipment close manual

Signal Path · Restored Layer Available Now

IN Order intake live
SC Signal computation recomputed
PO Supplier PO correct
MF Material flow matched
EX Expedited freight avoided
SP Shipment close automated
100%
Supplier POs affected by broken signals
Manual
PO correction layer required in the interim
<2s
Restored signal recompute time per order
3–8 mo
Window before H1 2027 remediation target
Live Signal · Recomputed

The signal, computed from live orders.

Every time a new order enters the pipeline, the signal recomputes. The chart below runs continuously — every bar is a signal cycle, colored by state. Watch the pattern shift as the signal stabilizes against incoming orders.

Demand Signal · Live Recompute

Status · Idle · Press Play to begin compute cycle

— Broken signal accuracy
T-30 T-15 T-0 · Now
Restored signal Broken signal Recompute event
Components

Five inputs. One signal.
Click any component.

The restored signal is computed from five inputs. Each one is a source of truth that the broken SAP path was reading incorrectly — or not at all. Click any component to see its live state and its role in the signal.

IN

Live Order Intake

The actual orders entering the pipeline right now — from dealer portal, direct, and EDI sources. The signal's primary source of truth.

Source · Dealer Portal, Direct, EDI
Cadence · Continuous
Broken SAP · Delayed intake, incomplete capture
Restored layer · Live, complete, every order
IR

IRIS Telemetry

Usage signals from deployed Tennant equipment in the field. Real-world consumption, not just order history — catches demand ahead of orders.

Source · Connected Tennant equipment
Cadence · Streaming
Broken SAP · Not integrated to signal computation
Restored layer · Feeds signal in real time
VH

Historical Velocity

Prior-period order rates by SKU and region. Anchors the signal against seasonal and cyclical variation.

Source · Historical order warehouse
Cadence · Rolling 90 days
Broken SAP · Contaminated by disrupted intake
Restored layer · Clean baseline, isolated from disruptions
SC

Seasonal Coefficients

Region-specific seasonal adjustments that shift the signal by market. Keeps the signal accurate as demand moves seasonally.

Source · Regional demand curves
Cadence · Weekly rolling
Broken SAP · Static, not refreshed
Restored layer · Recomputed from live orders
SL

Supplier Lead Times

Actual supplier lead times by material and route. The signal is offset against lead time so POs arrive when they need to, not late.

Source · Supplier confirmation data
Cadence · On confirmation
Broken SAP · Stale, disconnected from real performance
Restored layer · Live-updated as suppliers confirm
PO

Supplier PO Output

The computed signal that leaves the layer and reaches suppliers. Correct quantities, correct timing, correct destination.

Format · Standard EDI + API
Cadence · Per signal recompute
Broken SAP · Incorrect quantities, wrong timing, manual correction
Restored layer · Accurate, automated, sent in <2s from signal
The Case

A signal computed wrong
is a signal that costs money.

An incorrect demand signal is not a single failure. It's a compound one. Suppliers ship the wrong quantity — either too much (carrying cost) or too little (expedited freight). Materials arrive out of phase with production. Manual POs replace automation, generating a growing labor burden. And order-to-cash closes late, if it closes at all. Tennant has been absorbing these costs since November 2025.

The parallel signal layer recomputes from live orders. Correct quantities. Correct timing. Correct destinations. Automation replaces the manual workaround. And the layer hands back control to SAP when SAP is remediated — no rework, no duplicate computation, no conflict.

Next

Correct signal now.
Not on SAP's timeline.

The signal layer runs alongside SAP remediation. It operates inside the 3–8 months before H1 2027 — closing the gap that SAP remediation leaves open.

Signal —