The layer that runs
beside the fix. Not inside it.
The parallel layer is a standalone operating component that runs alongside Tennant's existing SAP instance. Six components handle order intake, signal compute, supplier routing, material coordination, production sequencing, and reconciliation. The layer operates across the recovery window, then hands back cleanly at H1 2027. No rip-out. No replacement. No rework. Every other page in Phase 3 refers back to this one.
Each component is a standalone service with its own lifecycle. The OMS can be redeployed without touching the Signal Engine. The Routing Engine can be upgraded while reconciliation continues. Independent components mean independent failure domains — no single point of failure in the layer.
Same orders. Same time.
Two paths. One contract.
SAP is still running. Its state is still authoritative. But it cannot route demand signals, cannot generate correct POs, and cannot close order-to-cash reliably. The layer handles those stages while SAP holds the authoritative state. The two run in parallel, contracted through standard interfaces.
Contract: every layer write is reconciled to SAP hourly. Every SAP read is baseline-verified. Nothing crosses the boundary without a signature.
Six components. Independent. Replaceable.
Each component is a standalone service. Each has its own lifecycle, its own failure domain, its own upgrade path. Click any component to see its interface, its dependencies, and its role in the order lifecycle.
Order Management
Order intake from every channel — dealer portal, direct, EDI, rep. Normalizes into a canonical order object. First stage of the layer pipeline.
Signal Engine
Recomputes demand signals from live orders and IRIS telemetry. This is what SAP cannot do correctly. Fully independent of SAP state.
Routing Engine
Routes each order line to the correct supplier based on signal, lead time, cost, and capacity. Auto failover. This is the manual-PO elimination engine.
Material Coordinator
Tracks inbound material flow against the signal. Surfaces shortages before they hit the line. Coordinates with supplier EDI and warehouse WMS.
Production Sequencer
Schedules production against the restored signal. Coordinates build order across Tennant's manufacturing footprint. Full traceability to source order.
Reconciliation Bridge
Bidirectional sync with SAP. Hourly reconciliation job. Drift meter continuously measured. This is what makes coexistence safe.
Three planes. Independent. Composed.
The layer has three architectural planes. The operational plane handles the order lifecycle. The bridge plane synchronizes with SAP. The interface plane exposes everything to the outside world. Each plane is independently deployable.
Replace. Or run beside.
Only one preserves the investment.
The decision is not about technology preference. It's about what happens to the SAP investment Tennant has already made, and what happens to the remediation timeline that's already been disclosed.
Replace SAP Rip-Out Path
- Full rip-out and re-implementation of the entire ERP
- Migration of all master data, history, and integrations
- Existing $59.1M investment becomes sunk cost
- Timeline extends well beyond H1 2027
- Multi-region rollout restarts from zero
- Full change management program required
- Emotional cost — years of internal defense reopened
Run Beside SAP Parallel Path
- SAP stays primary throughout the recovery window
- Master data and history stay in SAP
- Remediation spend fully preserved
- Order-to-cash restored inside the window
- Clean handback at H1 2027 — no rework
- Standard SAP-native interfaces only
- No internal defense cycle reopened
A fraction of one remediation quarter.
The layer's cost is designed to be a rounding error against the disclosed remediation spend. Activation is $250K. Operation is $35K per month. The full cost across the recovery window is less than one remediation quarter.