Condition monitoring beside the plant historian.
Anomaly models run at the plant's data layer, against the historian and sensor stores. Plant networks stay closed: the agent initiates every connection, and no inbound ports open.
The loop runs at the plant's data layer.
Nothing in it requires the historian to leave home, and the plant network stays closed throughout.
Capture
Sensors write to the historian: vibration, temperature, throughput.
data stays at the plant's data layer
Score
Anomaly models run beside the historian and attach a reason to every flag.
K·03 scores in place
Queue
Flags rank into the maintenance queue. The noisiest line rises to the top.
Intervene
A work order goes out. The intervention and its trigger stay linked on the ledger.
Review
Shift review reads scores against outcomes, and thresholds adjust for the next cycle.
the loop tightens each cycle
agent egress stays under your firewall rules · restricted and air-gapped patterns are a design target
What a shift supervisor wants scored.
Scores computed beside the sensor stores, with the reason attached to each flag.
K·03 · anomaly scoring
A ranked queue across lines, ordered by score, explained per item.
K·03 · attention queue
Live views over the historian as it stands. No extract to a second platform.
K·03 · live views
Where the agent sits.
KEZEL · DEPLOYMENT · MANUFACTURING
- agent
- beside the plant historian
- components
- K·02 orchestration + K·03 analytics
- network
- no inbound ports · egress under your firewall rules
- patterns
- restricted and air-gapped · design target
Restricted and air-gapped patterns are a design target. Shipped today: outbound-only connections over TLS 1.3, initiated by the agent.
Show us the data you are not allowed to move.
That's the workload we should discuss. Start with a demo on our sample boundary; move to a pilot in yours once your security review clears it.