Current Losses Requiring Attention
Every active stop or constrained machine, ranked by urgency.
0 shown
| Machine | Status / reason | Duration | OEE |
|---|
Dashboard
Plant Overview
Demo data LiveLast updated: --:--:--
Derrimut Plant — Day ShiftPlant-wide production and loss overview across all connected machines.
All machines updating live
All Machine Status
Select any machine to open its detailed operator screen for the selected reporting period.
Downtime Reasons — All Machines
Combined loss summary with affected machines.
Performance Trend
Track plant or machine performance over time.
Plant Production vs Target
Selected shiftActual OutputTarget Output
Downtime Category Summary
Selected shift0minTotal
Plant Alerts
All-machine Run / Stop Timeline
Hover any segment for details. Click a downtime segment to open that machine on the exact recorded date and shift.
06:0008:0010:0012:0014:00
RunningStoppedStarvedChangeoverScheduled Down
Manager Actions
Line 2
RUNNINGCurrent Production Order
Select the product, enter the order number and required quantity. ClearRivet tracks this order separately from total shift production.
Run / Stop Timeline
Selected shift machine state. Runtime and downtime below are reflected in the Event Log.
Downtime Reason Pareto
Duration by reason for this machine.
Event Log
One history of runtime, downtime, product/orders, quality and operator comments. Runtime rows include quantity and average run speed.
Machine Connections
Read-only acquisition is preferred. The production control network never needs to accept commands from ClearRivet.
| Machine | Source | Protocol | Status | Last data | Count confidence | Run confidence | Sequence | Device security |
|---|
Existing network data
Use an existing PLC/HMI tag when the customer already has a reliable production total and run state. This avoids adding another counter sensor.
- PLC protocol / OPC UA
- HMI OPC UA / MQTT / API when available
- Read-only credentials
Direct machine signal
Use isolated 24 V run/count signals or a dedicated sensor where the control system cannot expose usable data.
- Run input
- Production pulse
- Optional blocked / starved / reject
Validation before go-live
ClearRivet should not mark a machine commissioned until its source has passed a count and run-state verification.
- 20-part count test
- Run/stop transition test
- Timestamp / heartbeat check
Recent Changes
Who changed what, when, and why.
| Time | User | Type | Machine / area | Change | Details |
|---|
Settings
Configure ClearRivet to match each customer’s operation.
Daily Report Preview
Loading server-calculated report…
Delivery History
Outbox is used locally. SMTP delivery becomes active only after production email credentials are configured.
| Time | Type | Recipient | Status | Subject | Error |
|---|---|---|---|---|---|
| No deliveries yet. | |||||
Module
This module is planned for the next build phase. The navigation is active so the final workflow can be tested.