Operator Compliance
Are downtime reasons, required checks and shift handovers complete enough to trust and act on?
Dashboard
Plant Overview
🔒Access: —
Connecting… LiveLast updated: --:--:--
Online ECM50A devices
Generic factory-prepared devices appear here automatically as Online / Unassigned as soon as they reach ClearRivet. Assign Customer → Plant → Machine only after the hardware is online.
Looking for online devices…
Customer registry
Customer lifecycle and routing metadata only. Production details stay inside each customer's workspace.
| Customer | Customer ID | Lifecycle | Storage | Users | Devices | Status |
|---|
Finish setting up ClearRivet
No machines are connected yet, so there is nothing to show on this overview. Two steps get real data flowing.
Derrimut Plant — Day ShiftPlant-wide production and loss overview across all connected machines.
All machines updating live
Plant output vs target
Mixed production units are compared by attainment; unlike units are never summed.
Ask ClearRivet AI
Ask about today's production, OEE, downtime, quality, losses or which machine needs attention. ClearRivet calculates the numbers first; AI only interprets tenant-scoped read-only facts.
Historical Comparison
Fair like-for-like comparisons, including partial shifts.
Production Orders
Every machine, its live order, progress and estimated completion — across shifts and machines.
Live plant
All Machine Status
Select any machine to open its detailed operator screen for the selected reporting period.
Current Losses Requiring Attention
Every active stop or constrained machine, ranked by urgency.
0 shown
| Machine | Status / reason | Duration | OEE |
|---|
Downtime Reasons — All Machines
Combined loss summary with affected machines.
Performance Trend
Track plant or machine performance over time.
Plant Production vs Target — Hour by Hour
Actual production compared with the planned target in each hour of the selected period.
Actual OutputTarget Output
Downtime Category Summary
Selected shift0minTotal
Plant Alerts
All-machine Run / Stop Timeline
Hover any segment for details. Click a downtime segment to edit its downtime code/comment. Historical fallback segments open the recorded date and shift.
06:0008:0010:0012:0014:00
RunningStoppedStarvedChangeoverMaintenanceScheduled Down
Manager Actions
Machines
Event types
Event History
Choose dates and machines, then load events.
| Date | Shift | Time | Machine | Event | Product | Duration | Quantity | Speed | Comment | Details | User |
|---|---|---|---|---|---|---|---|---|---|---|---|
| No event query loaded yet. | |||||||||||
No machine data yet. Machines appear here once a gateway or PLC connection has been commissioned and ClearRivet has received its first sample.
Line 2
RUNNING00m 00sMachine KPI comparisonChange is shown in %% so partial-shift comparisons stay clear.
Current Production Order
Select the product, enter the order number and required quantity. ClearRivet tracks this order separately from total shift production.
Run / Stop Timeline
Live current-shift machine state. Hover any segment for exact status, local start/end time, duration and recorded detail. Gray means the machine state was not verified. The window advances automatically when the configured shift changes.
Downtime Reason Pareto
Duration by reason for this machine.
Event Log
Last 24 hours by default. Select up to 7 days; use CSV export for longer analysis.
NORMAL GATEWAY SETUP
Connect a machine in three steps
The gateway already knows its permanent hardware identity and customer-safe bootstrap credential. Once it is online, setup stays inside ClearRivet — no USB, Terminal, Thonny, API keys or internal connection records.
1 · AssignChoose Customer → Plant → Machine for the online gateway.
2 · Data sourceChoose Direct I/O (DI1 RUN + DI2 COUNT) or PLC / Modbus TCP.
3 · Prove automaticallyThe gateway proves the selected source before ClearRivet accepts it as production truth.
Later changesMove machines or change I/O ↔ PLC remotely. Hardware return is only for exceptional recovery.
PHYSICAL ECM50A REGISTRY
Which physical ECM is on which machine?
Only controllers with a permanent hardware Device ID appear here. Older ECM connection records remain in history but are hidden from this physical-device list, so one controller cannot look like five devices. Already see a device online below but not on a machine yet? Use the button to connect it in seconds — no USB required.
Checking…
Loading ECM50 devices…
MACHINE REGISTRY
Loading…Set up one machine at a time
A machine being enabled in ClearRivet is not the same as its telemetry being online. Each machine shows its real live state and its configured/online source count separately. Historical ECM records without a hardware Device ID do not count as installed devices.
Loading machines…
CONNECTION TROUBLESHOOTING
Why is a machine not reporting?
ClearRivet checks the connection chain in order and shows the first thing that is broken, because everything after it is usually a symptom rather than a second fault. Fix the one action shown, then re-check.
Loading connection diagnostics…
Machine Go-Live Readiness
A machine is Ready only when its signals, schedule, product target, downtime reasons, operator checks, alert routing and live telemetry have all been verified.
Select a machine to check readiness.
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 |
|---|
Managed Gateway Fleet
See software version, heartbeat and staged update state across every ClearRivet edge connection. Update and rollback controls are Administrator-only.
Loading gateway fleet…
CLEARRIVET INTERNAL
PLC / Signal Health Log
Platform-admin engineering log for connection loss, recovery and source-health transitions. These events are deliberately kept out of the customer's production Event Log and Audit Trail.
| Time | Machine | Protocol | Transition | Error | Details |
|---|---|---|---|---|---|
| Loading… | |||||
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.
🔒 Customer account boundary: user accounts created here inherit this customer's tenant ID on the server. Site and machine permissions can narrow access further, but they can never grant access to another customer.
Customer Accounts
Access changes are audited. Administrators cannot accidentally deactivate or demote their own signed-in account.
Security Posture
A customer-facing summary of account protection, backups and deployment safeguards.
Today Report Preview
Loading verified production intelligence…
Delivery History
Only email delivery attempts are kept here for traceability. Generated-file history is intentionally not shown.
| Time | Type | Recipient | Status | Subject | Error |
|---|---|---|---|---|---|
| No deliveries yet. | |||||
Calendar Exceptions
Production OFF removes planned time; Production ON adds planned time for an otherwise non-working window.
Exceptions Requiring Review
Failed checks and currently due/overdue requirements are shown first so the manager knows exactly which machine needs attention.
Required Check Definitions
Product-change checks appear immediately when an operator loads a new production order.
Completed Check Log
Pass/fail result, machine, operator and time are retained for traceability.
| Completed | Machine | Check | Trigger | Result | Operator |
|---|
Help / Andon — Needs Response
Every call has a unique Andon ID and a live response timer. Acknowledge freezes response time; Resolve closes the request and freezes total resolution time.
Improvement Actions — Active
Machine, owner, due date and required work remain visible until completed.
Andon Event Log
One row per unique request ID from raise through acknowledgement, resolution or cancellation. Operator comments and response timing stay with the same request.
| Request | Machine | Type | Operator comment | Raised | Response | Resolution | Status |
|---|---|---|---|---|---|---|---|
| No Andon requests yet. | |||||||
Verified Improvements
Completed improvement actions stay here only when they can teach the plant something: ClearRivet measures before vs after, recovered downtime and capacity. Andon history is retained separately above and also remains in each machine Event Log.