Phase 4 · Node Layer 19 · Systems & Proof

The hub every order
routes through. And the log every system reads from.

The OMS is the central hub of the Tennant node. Every order routes through it. Every event is logged there. Every downstream system reads from it. It owns the order state machine and the event log — the single source of truth for the entire order lifecycle. Five states. Every transition logged. Zero events lost.

Order hub 5-state machine 99.97% uptime 0 events lost Single source of truth
ORD
Orders / Day
160
Routed through OMS
STA
State Machine
5 states
Placed → Delivered
EVT
Events / Day
~2.4K
Logged to append-only log
LAT
Order → Ack
1.42s
p95 end-to-end
The State Machine

Five states. One order. Every transition logged.

Every order advances through exactly five states. Each state transition fires an event to the append-only log. Each event is subscribed to by the systems that need to know. Nothing moves without a state change. Nothing changes without a logged event.

OMS State Machine · Running
01
Placed
—
02
Verified
—
03
Packed
—
04
Shipped
—
05
Delivered
—

Order PM-847291 · Placed

The OMS has accepted the order. Order ID assigned, inventory soft-reserved, customer identified. First event fired to the append-only log. Downstream systems notified that a new order exists.

Current State
Placed
Elapsed
0.0s
The Capabilities

Three things the OMS owns.

The OMS owns three things: the order state machine (the sequence every order advances through), the append-only event log (the record of everything that happened), and the downstream coordination (which systems get notified at which transitions).

01

Order Intake

Every order from every channel — dealer portal, direct, EDI — is captured by the OMS. It assigns the order ID, validates the payload, reserves inventory, and admits the order to the pipeline.

02

State Machine

Five states: Placed, Verified, Packed, Shipped, Delivered. Every transition is defined. Every transition fires an event. No state can be skipped. No transition can happen silently.

03

Append-Only Event Log

Every state change, every downstream notification, every reconciliation event is written to the append-only log. Nothing is ever mutated. Nothing is ever lost. Full audit trail for every order.

Live Stream

OMS event stream · append-only

Every state transition fires an event. Every event is logged. Every log entry is preserved. This is what the OMS event log looks like during normal operation.

OMS Event Log · Append-Only 12 events
16:48:31.042 PLACED Order PM-847291 accepted · inventory reserved
16:48:31.108 PLACED Event fired · order.placed → signal layer + Pro-Panel
16:48:31.512 VERIFIED Order PM-847291 passed dealer validation
16:48:32.011 PACKED Fulfillment scan complete · package PKG-48291
16:48:32.298 PACKED Event fired · order.packed → SAP Adapter
16:48:32.514 SHIPPED Carrier scan · tracking 9400 1000 0000 0000 0000
16:48:32.614 SHIPPED Event fired · order.shipped → Pro-Panel + IRIS
16:49:03.221 PLACED Order PM-847292 accepted · pipeline routed
16:49:04.417 VERIFIED Order PM-847292 verification complete
16:51:47.108 DELIVERED Order PM-847290 delivered · service schedule updated
16:51:47.211 DELIVERED Event fired · order.delivered → Pro-Panel + IRIS
16:52:22.445 DELIVERED Order PM-847289 closed · 1.42s end-to-end
Metrics

OMS metrics. Continuous measurement.

Four primary OMS metrics: orders processed per day, p95 latency, events logged, and event loss. All measured continuously. Click any metric tile for detail.

Orders / Day
160
Routed through the OMS
Latency p95
1.42s
Order intake to ack
Events / Day
~2.4K
Written to append-only log
Event Loss
0
Zero loss · zero duplication
Questions

OMS, answered.

An Order Management System (OMS) is the central system that tracks every order from placement to delivery. It captures orders, reserves inventory, coordinates fulfillment, handles payment authorization, logs every state change, and fires downstream events to every system that needs to know. At Tennant, the OMS is the hub that every order routes through.

Because every order routes through it and every event is logged there. Every downstream system — signal, routing, reconciliation, visibility — reads from the OMS. It is the single source of truth for the order lifecycle.

Five primary states: Placed, Verified, Packed, Shipped, Delivered. Each state transition fires an event. Each event is logged. Downstream systems subscribe to the states they care about. No state can be skipped. No transition can happen silently.

The OMS never talks to SAP directly. Every write to SAP goes through the SAP Adapter, which uses standard interfaces. Every event is logged in the OMS first, then reconciled to SAP on the adapter schedule. This keeps the OMS as the source of truth while SAP remains authoritative for its own system of record.

Every order is idempotent. Every event is preserved. Failed events go to the dead-letter queue for manual replay. No order is ever lost, and no event is ever duplicated. The append-only log ensures the full audit trail survives any failure.

The hub is defined.

Five states. Every transition logged. Single source of truth. Now the upstream — supply chain, integration proof, security.