Inspect a single machine

Everything one machine's page tells you, and which tab answers which question.

The header says what the machine is doing right now. The tabs below it hold the history: counts, runtime, stops, jobs, vibration and meters.

Prerequisites. A machine with a paired sensor, see Add a machine. Every number here is defined in Metrics.

Open a machine

Click any card on the Assets page, or open /assets/selected-asset/:id directly. The breadcrumb reads Assets / Doosan 2600, and Assets takes you back with your filters intact.

The control bar under it holds the shift selector for the header, a bell for event rules, Auto-Detect for the operations the sensor should count, and a menu with Edit, Hide, Archive, Delete Data and Delete, covered in Edit, hide, archive, or delete a machine.

One machine's page. The header answers what it is doing right now.

The header

The pill has two states, because a sensor reports a machine as running or down and nothing else. The color adds how long the stop has lasted: green until the orange threshold, one minute by default, orange until the red threshold, five minutes by default, and red after that. A classified stop is dark red at once.

Both thresholds are organization-wide, see Status colors.

The sensor tile lights orange while the machine runs and cyan while it is stopped. A flat gray tile means the cloud has not heard from the device since you opened the page.

The Wi-Fi icon's three levels are defined in Read the connectivity indicators. A weak signal here is the usual cause of gray stretches on the status bar.

The sensor tile carries signal strength as a Wi-Fi icon. A weak signal here explains gaps in the charts below.

Pick the shift that had the problem rather than the whole day. A day spanning three shifts averages away the one you are looking for.

The Analytics tab

Analytics is the default tab. It holds five cards: Operation(s) Production, Uptime/Downtime (hours), Runtime Comparison (hours), Downtime Classifications and Activity. Each has its own date range and shift filter, remembered per machine.

Operation(s) Production lists one row per operation run in the window. An operation is one part and the step this machine performs on it, see Parts and operations.

Each row shows the count against its goal, good and scrapped parts per hour or day, and cycle time or production rate. For example, Bracket 4417-A · Mill reads 212 of 240 at a cycle time of 1:42 against a goal of 1:30.

The amber Auto-Detecting label names what the sensor is counting. If it is empty, the machine counts nothing. Set it with Auto-Detect, see Auto-detect operations.

The Analytics tab: production counts per operation, and how they moved day to day.

Uptime/Downtime (hours) stacks running, down and unknown hours per day, seven days by default, with an Uptime gauge for the range. Exclude None drops stops of severity None from both figures, see The None severity.

Runtime Comparison (hours) draws the current period in blue over the previous one in gray, Daily or Monthly, for one shift. It catches a machine that has quietly slowed: a gray line consistently above the blue is a week of lost hours nobody noticed.

Daily runtime and the runtime comparison chart, for spotting a machine that has quietly slowed.

Downtime Classifications is this machine's downtime Pareto, categories ranked by hours lost, with a severity filter. It reads like the fleet report in Read the Pareto chart. Its Classify button opens the modal on any stop in the range.

Production counts and backfilling

The sensor counts parts on its own. To backfill is to record a count it missed, for example forty parts made while the device was offline for an hour.

1. On the Operation(s) Production card, click Modify Counts. The Record Production modal opens.
2. Pick the Operation.
3. Set the Session Time to the window the parts were made in.
4. Replace Good Parts with the true number. It is pre-filled with what the sensor detected in that window, and Use Auto-Count restores that figure.
5. Click Add Scrap for any rejects, with a reason code for each.
6. Click Record Production.

The count is stored as a manual session on the work-order timeline above the operation rows, and a toast reads Production recorded.

Backfill counts only when you know the true number and why the sensor missed it. A backfilled count changes OEE and FPY for that period permanently, and nothing on the Advanced Report marks it as manual. If the sensor misses parts while online, the fix is in Troubleshoot part counts, not here.

Backfilling a count. It changes OEE and FPY for that period permanently, and nothing marks it as manual.

The activity feed

An activity is one interval of the machine's timeline in a single state, running or down. The Activity card lists every activity in the window, newest first, under pills for All, Uptime, Classified and Unclassified. The count on each pill is the size of that group.

A stop shows its start, duration and category, with icons to split, classify or delete it. A running interval shows the operation it was counted against. The steps are in Classify a downtime event and Delete an activity.

You do not need the feed to classify a stop you can see; use the status bar. The feed is for the end-of-shift backlog, when Unclassified is the only pill that matters.

The activity feed: every state change and edit on this machine, newest first.

Notes

Notes are free text attached to the machine, not to a shift, so a note about a bearing that started to whine in March is still there in June. They live in the Notes list on the Health tab and in the Notes tab of Operator View. Both write to the same list.

1. On the Health tab, click Add Note.
2. Leave the date and time at now, or set them to when it happened.
3. Type the note and press ⌘+Enter.

Each note shows its text, timestamp and author. Click the pencil to edit in place: Enter saves, Escape cancels, and the note is marked as edited. The trash icon deletes at once, with no confirmation on the Health tab.

A timestamped note is also a marker on the health charts. Click it and the charts jump to that moment, see Monitor machine health and vibration.

Notes are timestamped and attached to the machine, not to a shift.

The other tabs

The Health tab is absent for a BeamTracker asset, because a beam sensor reads no vibration. A SenseAi on firmware below 5 keeps the tab but shows raw vibration, mean, standard deviation and RMS charts instead of the health score. Firmware is listed in View your devices.

On mobile

On a phone, a back link to Assets and a filter icon replace the breadcrumb and control bar, and the shift selector moves into the Filters sheet. Tapping the status bar opens the classification sheet, and tapping the Uptime gauge opens the goal modal. Each Analytics card collapses under its heading, and the page remembers which you closed.

Errors

See also

• Monitor machine health and vibration
• Classify a downtime event
• Set OEE and utilization goals
• Metrics