The crisis was the entry point.
Not the relationship.
Continuity defines what happens after the handback. SAP resumes full primary control. The layer moves to standby, enrichment, or retirement — Tennant's choice at handback. The relationship continues in a different posture. The node remains as a network participant. Cost reduces from operation levels to continuity levels. This page closes Phase 3 (Solution) and answers the question every solution must answer: and then what.
At handback, SAP resumes primary control and the layer chooses its posture. Tennant decides which one. Each has a defined role, a defined cost, and a defined handoff. No ambiguity. No surprise continuity fees.
Three postures at handback.
Tennant chooses.
At handback, Tennant decides what happens next. Retire, standby, or enrichment. Each has a defined cost, a defined role, and a defined handoff. The relationship is designed to outlast the crisis it was built for. But the shape of that relationship is Tennant's decision, not ours.
Continuity Posture · Select One
Click any posture to see the specific details, cost, and role after handback.
The layer stops. Operational writes cease. Reconciliation closes any remaining open items. SAP resumes full primary control with no ongoing layer dependency. Clean exit.
The layer remains deployed but not handling operational order flow. Adapters stay connected. Reconciliation stays running. Available as rapid-response infrastructure if a future disruption occurs.
The layer keeps running, feeding IRIS telemetry and non-authoritative signal enrichment into SAP's signal history. SAP remains authoritative. The layer becomes a signal improvement service.
Layer fully decommissioned at handback.
At handback, the layer stops. Operational writes cease. Reconciliation runs one final time to close any remaining open items. Adapter connections are torn down. IRIS and Pro-Panel integrations are disabled. SAP resumes full primary control with no ongoing layer dependency. Team members stay redeployed to higher-value work. The node remains as a network participant and proof point.
Three things continue.
Regardless of posture.
Regardless of which posture Tennant chooses, three things continue. Network participation. Telemetry continuity. Standby availability. The relationship persists as infrastructure — not as a service contract that expires, but as a network membership that remains.
Network Participation
The node remains a live participant in the ESAN network. Capability improvements from other nodes flow to Tennant. Tennant's node contributes to the pattern library. Participation is continuous.
Telemetry Continuity
IRIS and Pro-Panel telemetry continue to flow if the enrichment posture is chosen. Even in other postures, the historical data remains available for future signal work.
Standby Availability
The layer can be reactivated within fourteen days if a future disruption occurs. No re-implementation. No re-integration. The build already exists.
Before handback. After handback.
The handback is not an event that ends the relationship. It is a transition that re-shapes it. Before handback, the layer handles operational order flow. After handback, SAP handles it and the layer takes its chosen posture. Both states are defined. Both are clean.
Layer handling operational order flow
- Layer ingests orders from all channels
- Signal recomputed continuously from live orders
- Supplier routing automated from signal
- Bidirectional reconciliation hourly
- Manual POs at zero
- Drift meter at zero
SAP resumed. Layer in chosen posture.
- SAP handles all operational order flow
- Signal is SAP-authoritative
- Supplier routing back in SAP
- Reconciliation no longer required
- Manual POs remain at zero
- Layer takes chosen continuity posture
Continuity events · live
Continuity is not silence. It is a different signal.
layer writes stopped
0 open items
connected, idle
layer available, no operational load
signal_accuracy+1.2%
reactivation window 14 days
3
Three postures. Three costs.
All defined.
Continuity costs are defined for each posture. Retire is $0/month. Standby is $8K/month. Enrichment is $15K/month. Compare to the operating cost of $25K/month during the recovery window. The continuity cost reflects the reduced operational load.
Continuity, answered.
$25K/month that runs the layer during the recovery window. Continuity costs are lower because the operational load is lower. Retire: $0/month. Standby: $8K/month. Enrichment: $15K/month. Every posture has a defined cost. Nothing is left to negotiation.