Asset Health in App Designer

Updated Nov 14, 2026
Shop Floor

Asset Health in App Designer

Build your own screens on Asset Health data in App Designer: drop live PLC tags onto the canvas, chart alarms, downtime and signal history, and place your apps inside the Asset Health module.

Permissions: The Tags panel and the Shop floor (Asset Health) data source appear only if your company has the Shop Floor licence. To load their tags, lines and equipment, you also need a Shop Floor role: DataMagik - Shop Floor Viewer, DataMagik - Maintenance or DataMagik - Shop Floor Admin. DataMagik - Builder and the general DataMagik - Viewer give you nothing here. Building apps needs App Designer access. Placing an app in an Asset Health panel or in the module menu needs DataMagik - Shop Floor Admin and the Asset Health licence. People who use the app need permission to open it. Live tag tiles need nothing more. Every Data kind except Downtime by reason also needs the Asset Health licence and a Shop Floor role, so make sure everyone who uses the app has one. To open the app inside the module, people need a Shop Floor role too.

Live tags: the Tags panel

In the App Designer editor, the Tags tab sits beside the components palette. It lists the bound signals of your company's first location, grouped by line, then by machine, then by signal, with each signal's current value and data type. Values refresh every 15 seconds while the tab is open. Use Search lines, machines, signals to find one.

  1. Open the Tags tab.
  2. Drag a signal onto the canvas. You can also select it and press Enter, or double-click it, to add it at the next free position.
  3. A Live tag tile is created. In its properties, set the Label, Unit and Decimals.
  4. Under Thresholds, optionally set Warn at or above, Warn at or below, Alarm at or above and Alarm at or below. Leave a limit blank for no limit.
  5. Optionally switch on Show trend (this session only) for a small sparkline of the readings since the screen opened. It is not saved: it starts again when you reload or leave the screen, and it keeps the last 120 readings.

The tile's dot is green, amber or red by your thresholds. It is grey when the value is stale or missing: a stale value is still shown, greyed, next to the word Stale. All tiles on a screen share one live connection, and if a live connection is not possible, for example inside the browser extension or the mobile app, the tile re-reads every 15 seconds instead.

If the Tags tab says no tags are bound yet, bind them on the Shop Floor tag map first. See PLC connectivity. Signals mapped from a SQL historian appear here too. See SQL historian.

Charts, KPI cards and tables: the Shop floor data source

A chart, KPI card or data table can take the data source Shop floor (Asset Health). In its Shop-floor data settings, choose what to show under Data:

  • Active alarms
  • Line status
  • Location KPIs (KPI cards and tables only)
  • Equipment health (the asset tree with each machine's status)
  • One machine's health (KPI cards and tables only)
  • Insights
  • Downtime by line
  • Line reliability
  • Signal history
  • Machine reliability (KPI cards and tables only)
  • Downtime by reason

Then pick, as needed:

  • Line (or All lines) and Equipment (or All equipment). These lists show every location's lines and equipment, so pick ones at the app's location.
  • Signal, for signal history, from the same tag list the Tags panel uses.
  • Time range: Default for this data, Today, Last 24 hours, Last 7 days, Last 30 days or Last 90 days.
  • Refresh: how often the component re-reads: every 15, 30, 60, 120, 300 or 900 seconds. The default is 60 seconds.

Choosing a kind fills in sensible defaults. A chart gets its label and value fields, a KPI card gets a Metric picker (for example Active faults), and a table gets the kind's columns. IDs are never typed: every line, machine and signal comes from a list. If something you picked is no longer in the list, it shows as Missing (no longer in the list).

The pareto chart

Charts have a Pareto type. The bars are sorted largest first, and a line shows the running share on a 0 to 100% axis. Show the 80% line (on by default) draws a dashed line at 80%. Downtime by reason and Downtime by line make natural paretos.

Putting your app inside Asset Health

There are two ways to place an app in the module. A Shop Floor Admin sets up both in Settings, Dashboards. Only published apps you can open are offered. See Asset Health setup.

  • As a panel. Add a Custom app panel to any screen's desk or wall layout. Choose its Height (Medium or Auto) and whether to Show a title with an open link or the app only.
  • As a menu tab. Under Linked apps in the module menu, add the app with a menu label. It appears in the module's tab strip and opens full screen.

What your app receives

For each panel or linked app, choose which of the module's current selections to pass to it: Location, Line, Asset and Insight. The app receives them as filter values and runtime inputs when it opens. When someone selects a different line, asset or insight on the screen, a panel is updated with the new values and refreshes, and the linked apps in the menu update their links so they open with the same selection.

An app reads shop-floor data for one location only, never another. If your company has more than one location, an app must declare its location; a classic app cannot, so its live tiles and shop-floor components show No signal or fail to load. The line and equipment pickers list every location's lines and equipment, but an item from a location other than the app's is refused when the app runs.

Was this page helpful?