Bulk Documentation
Product referenceInsights and visual managementDashboards

Review OEE assets

Read the OEE Assets dashboard for each machine's running, downtime, and inactive time, per-asset OEE, sensor activity, and output on a chosen day.

Last updated

The OEE Assets dashboard is a timeline view that shows what each machine (an asset in Bulk — a press, an oven, a CNC cell, and so on) was doing across a day: when it was running production, when it was stopped, and how much time it sat inactive in between. OEE stands for Overall Equipment Effectiveness: the score in this timeline uses recorded running time divided by running plus downtime. Inactive time is excluded. Output and quality quantities appear separately. The Assets view applies that lens to your equipment, so a shift lead can see machine productivity and stoppages one asset at a time.

Use it at the end of a shift, during a stand-up, on a wall display beside a line, or when investigating a drop in output. Each row is a machine and each colored block is a real event, so you can see which asset lost time, when, and to which category of loss — then open the details or, within a short window, correct a mis-recorded entry.

This is the machine counterpart to Review OEE people, which shows the same timeline per operator.

Before you start

Two things must be in place to read the dashboard, and a third is only needed if you intend to correct entries:

  • Permission to view OEE. The dashboard reads the View OEE analytics permission (analytics.view_oee). The built-in Super user, Entity admin, Manager, and Dashboards roles all include it. Without it, the timeline cannot load its data.
  • At least one OEE dashboard configured. An OEE dashboard is a saved, named list of the assets you want to watch together (for example, one line or one cell). If none exists, the page shows an empty state instead of a timeline. Creating or editing these dashboards needs the Manage OEE dashboards permission (analytics.manage_oee_dashboards), held by the Super user, Entity admin, and Manager roles.
  • To correct timeline entries, permission for manual timer entry. Resizing a segment, changing a downtime reason, or filling a gap uses the Manual timer entry permission (production_operate.timer_manual_entry), held by the Super user, Entity admin, Tablet user, and Master data roles. Viewing never requires it — a Manager can read every board but cannot edit the timeline; the backend enforces this regardless of what the browser shows.

The running, downtime, and output figures come from production activity on each asset: time booked against a production timer counts as running, a logged stoppage counts as downtime under its reason category, and the units recorded against the machine feed the output column. Machines with an attached sensor also get a thin sensor lane, described below.

No dashboard yet?

If you open OEE Assets and see "No asset dashboards configured", use the Go to Settings button. It takes you to Settings, OEE, Dashboards, where you can create your first one by giving it a name and selecting at least one asset.

Gotham Housing OEE overview with five bench rows, recorded activity, and a sensor lane.
Five benches with real recorded training history. The sensor lane has no device data and shows the native inactive fallback; output remains 0/0.

Open the dashboard

  1. Open the Dashboards area. The picker page ("Open a dashboard.") lists every board as a card.
  2. Find the OEE / Assets card (code DASH-OEE-A) and select it. The dashboard opens full-width with no sidebar.
  3. Use the back control (labelled Back to dashboards) in the top-right to return to the picker.

You can deep-link to a specific saved dashboard by adding the query parameter ?dashboard= followed by the dashboard's ID to the page address, which is useful when pinning one board to a wall display.

Read the timeline

Choose what you are looking at. The nav bar at the top holds the controls:

  • A dashboard selector (showing the current board name) lets you switch between saved OEE dashboards. Type in Search dashboards... to filter; if nothing matches it reads "No dashboard found."
  • Previous day and Next day arrows and a date picker move the day in view; Show Today jumps back to the current day.
  • Zoom in and Zoom out change the window from as wide as seven days to as narrow as one hour.

Read the summary row. Above the timeline, five plain columns summarize the whole board for the visible time range:

  • OEE: the score for the selected assets and time range.
  • Running, Downtime, and Inactive: summed asset-time in each state, each with its share of total time.
  • Losses: how downtime splits across Availability, Performance, and Quality.

The footer beneath the timeline reads "Asset-time is summed across all displayed assets", and a footer shows the exact range the metrics cover ("Showing metrics for: ...").

Read each machine's row. In the timeline itself:

  • The left Assets column shows each machine's name, the operator currently logged into that machine when someone is assigned, and a color-coded OEE % bar. The bar turns green at 85% or above, blue from 70%, amber from 50%, and red below 50%. The operator name is live: it stays after a timer stop and clears when that person signs out of the station. It does not change when you page to another day.
  • The main track is a literal, minute-by-minute strip. Green means running; red, amber, and blue blocks are downtime colored by loss category (Availability, Performance, Quality); a hatched gray block means unknown coverage; plain gaps are inactive.
  • If a machine has an attached sensor, a thinner sensor lane sits under its bar, showing when the sensor read Active, Inactive, or Unknown, with its own percentage. Compare this lane with the timers only when the sensor has actual readings. The current binary timeline fills missing coverage as Inactive, so an offline sensor with no readings can show a gray lane and 0%. That fallback alone does not establish that the machine was physically inactive.
  • The right Output column shows produced versus quality quantities for that machine over the window.
  • The Status Key legend under the timeline names each color. Very short events can appear as hairlines at day zoom — zoom in to inspect them.
Two housing bench rows showing running and changeover, OEE, a sensor lane, and output columns.
Review Bench 1 shows running before and after a recorded changeover. The training sensor has no readings, so its gray lane is an inactive fallback; no output was recorded.

Drill into detail

The rows are interactive:

  • Right-click a segment to open a small Segment menu at the cursor. On a running segment it offers View details, which opens a Running Segment panel with the machine name and code, the duration, start and end times, and a summary of batches, produced units, and quality items recorded during that run.
  • Select the Output column for a machine to open the Production Output panel, which lists the produced and quality batches for that machine, broken down by production mode.
  • Hover any segment to see a tooltip with its duration and, for a downtime block, its reason.
  • Left-click a segment to select it. On its own this only highlights the block; on entries you are allowed to edit it also reveals the drag handles described next.

Correct recent entries

If your role includes the Manual timer entry permission, the OEE Assets timeline is not only a viewer — you can fix a recently mis-recorded entry directly on the chart, without leaving the dashboard. Editing is limited to a rolling 48-hour window: only segments whose underlying record started within the last 48 hours can be changed, and a proposed new edge must also stay inside that window. Eligibility is decided by the server, so the option only appears on entries you can genuinely edit.

You can:

  • Resize a segment. Select an eligible running or downtime block, then drag its left or right edge. The left edge moves the start time, the right edge moves the end time, and both snap to the nearest whole minute. You can also nudge a selected edge with the left and right arrow keys (hold Shift for five-minute steps). A successful change shows a "Timeline updated" confirmation.
  • Change a downtime reason. Right-click an eligible downtime block and choose Change downtime reason. Pick a new reason; its loss category (Availability, Performance, or Quality) is set automatically from the reason, and some reasons ask for a short note. Saving shows "Downtime reason updated".
  • Fill a gap. If you shorten a running session so that it pulls away from an active neighbour, Bulk offers a gap-fill step so the vacated minutes are handled deliberately rather than left as an accidental hole.

Editing changes recorded production history

Resizing a segment or changing a reason rewrites the underlying timer session or downtime event — the same records that feed OEE, output, and downtime reporting. Change entries only to correct a genuine mistake, and prefer fixing data where it originates when you can. Edits outside the rolling 48-hour window are rejected with "Edits are only allowed for the last 48 hours."

Selected closed Fixture Changeover with native reason-change menu and resize hint.
A selected recent closed changeover exposes Change downtime reason and the resize hint. This picture opens the controls without changing history.

Example: Gotham housing cell

Bruce Wayne opens Gotham Housing to review five training benches. Review Bench 1 has recorded running time and a closed Fixture Changeover; benches 2 and 3 have earlier stoppages, while the other benches are inactive. Zooming into the changeover separates the green running blocks from the red Availability interval.

The sensor lane belongs to an unsignaled training sensor. It shows the native inactive fallback, not measured machine activity, and the output columns remain 0/0 because this exercise records no physical production. Bruce selects the closed changeover and right-clicks to inspect the reason-change and resize controls. Opening the menu leaves the recorded history unchanged.

What you can expect

For any day and any saved dashboard, OEE Assets gives you a per-machine view of recorded activity of running time, stoppages by category, inactive time, sensor activity, output, and an OEE score, all filtered to the exact window you have in view. Switching the date or zoom recomputes the summary row and OEE bar for the new range. Where you have edit rights, a correction you make on an eligible recent entry is reflected as soon as the timeline refreshes.

Limitations and feature state

  • This dashboard is available (generally released), not a beta.
  • Viewing is read-only unless your role includes the manual timer entry permission. Even then, editing is confined to the rolling 48-hour window and to eligible entries; older history is not editable here and must be corrected where it originates.
  • Rows exist only for assets added to the selected OEE dashboard. Machines not on any dashboard do not appear until someone adds them in Settings, OEE, Dashboards.
  • A sensor lane appears only for a machine that has a sensor attached. Machines without a sensor simply show no lane; this is expected, not an error.
  • Figures depend on operators using production timers and logging stoppages against the machine. Time with neither shows as inactive, and output counts come from the units recorded against the asset.
  • Metrics always reflect the visible time range. Zooming or paging changes the totals, which is expected.

Troubleshooting

  • "No asset dashboards configured." No OEE dashboard exists for this plant yet. Select Go to Settings (Settings, OEE, Dashboards) and create one, choosing at least one asset.
  • A machine is missing. It is not on the selected dashboard. Switch dashboards using the selector, or edit the dashboard to include the asset.
  • A row is all inactive. That machine booked no timer time and logged no stoppage in the window. Confirm operators are using production timers on it, and check you are viewing the right day.
  • You cannot edit a segment. Either the entry is older than 48 hours, or your role lacks the manual timer entry permission. The drag handles and edit menu items only appear on entries you can actually change; ask an administrator if you need edit rights.
  • A yellow "Analytics data is delayed" banner appears. The dashboard is showing the last trustworthy timeline while fresh data catches up. It notes the time the data is current through; use the Retry action to refetch. A persistent load failure usually means your account lacks the view permission — ask an administrator to grant an OEE-viewing role.