Asset Health setup

Updated Nov 14, 2026
Shop Floor

Asset Health setup

Asset Health settings is where a Shop Floor Admin sets up a location's lines, equipment, thresholds, historian, alerts, work requests, people and dashboards. A six-step setup guide shows what is still missing.

Permissions: The settings hub needs DataMagik - Shop Floor Admin and the Asset Health licence. DataMagik - Builder and the general DataMagik - Viewer give you nothing here. Only a Shop Floor Admin can upload, star or delete machine photos, or edit a health profile, anywhere in the module. A customer admin (DataMagik - Security) gives out DataMagik - Shop Floor Admin, DataMagik - Maintenance and DataMagik - Shop Floor Viewer in the company user manager. Nobody has them by default.

Opening settings

Open Settings from the module's tab strip, or go to /shop-floor/asset-health/settings. Settings apply to the location picked in the Location picker.

Setup steps

Until setup is finished, Settings opens on Set up Asset Health. It has six steps, in order:

  1. Location & Plex connection: the location's Plex PCN, the Plex credential that reaches it, and its connector group.
  2. Lines & stations.
  3. Equipment: added and placed on a line.
  4. Signals: from a historian source or the tag map.
  5. Thresholds.
  6. Review & go live: somebody is told when an alarm opens.

Each step is marked Done, Next, Needs attention or Not started, and links to the screen that does it. Worth a look lists up to three problems, such as a failing historian or equipment with no signals. While setup is unfinished, every section shows a Setup N of 6 line with the next step and Open setup. The steps are worked out each time you open the page.

1. Locations

A summary of the selected location: Plex PCN, Plex company code, Plex credential, Time zone, Plex environment (Test or Production) and whether an On-site connector serves it. To change any of these, use Edit locations (PCN, time zone, credential) →, which opens /shop-floor/settings/sites. See Shop Floor.

Units for part dimensions

Choose how your Plex part attributes, such as Gauge, Thickness and Width, are read when a value has no unit: Auto-detect (guess from each value), Metric (mm) or Imperial (in). A unit written in the value or the attribute name always wins. The card previews a few of your parts under each choice. This setting applies to the whole company. Select Save units, and the card says what changed.

2. Lines & stations

  1. Pick a Line.
  2. Answer How is this line set up in Plex? Choose The whole line is one workcenter, then pick it and select Use this workcenter. Or choose Each station is its own workcenter.
  3. Under Add a station, pick a workcenter or asset from the location. Nothing is typed by ID.
  4. Put the stations in the order material moves through them. Drag a station by its handle (this works on touch screens too), use the up and down arrows, or press the arrow keys.
  5. For each station, optionally change its label, and choose its picture: Machine photo (upload one in place with Upload photo) or Icon. The icons are Coil car, Uncoiler, Leveler, Feeder, Press, Die, Scrap conveyor, Stacker, Conveyor, Robot and Machine.
  6. Pick each station's Key signal from the signals bound to that machine. This is the value the schematic shows live.
  7. Check the Preview strip, which shows the line as it looks on the Portal and in App Designer, then select Save stations.

A station with no signal shows No signal instead of looking healthy. If a machine has no signals yet, bind them on the tag map first. See PLC connectivity.

3. Assets

The location's Asset tree lists workcenters and assets. Assets without a photo are flagged No photo. You manage equipment here. It does not need the OT licence.

  • Add equipment: select + Add equipment, or + Add here on a line. Answer What is it? and give it a name. A Code (optional) is made from the name if you leave it blank.
  • Where it sits: select a piece of equipment to set its line, its Parent equipment and its own Plex workcenter. Leave the workcenter empty to use the line's.
  • Rename it, or Delete equipment. Before a delete, you see what still refers to it. Scripts and addresses name equipment by its code, so changing the code changes how they must name it.
  • Not on a line: tick equipment that is on no line, then place it on a line.
  • Equipment types: give a type to many pieces at once, on a line or across the whole location, or accept a type suggested from the names. Equipment of one type is compared side by side on Analytics.
  • Set machine class for a line: sets the ISO 10816 class on every piece of equipment on the line, parts included.

Select an asset to edit its Health profile:

  • Criticality: High, Medium or Low. This sets the Plex work request priority.
  • Assignee: picked from your company's people. Work requests are assigned to that person's Plex user.
  • Equipment type: a description, for example "Hydraulic press".
  • Offline after silence of: how long the asset may be silent before it reads Offline (30 seconds to 24 hours, 5 minutes by default).
  • Machine class (ISO 10816): sets where the vibration zones start (Good, Satisfactory, Unsatisfactory and Unacceptable RMS velocity). If it is not set, Class II is assumed.
  • Plex equipment (for work requests): click in the box to see suggestions based on the asset's name, or type any part of the ID, description or location, then pick a match. Without it, work requests are raised without equipment.

Select Save changes. Under Photos, upload real machine photos, select Show on schematics to star the one used on schematics and cards, or delete one. A workcenter's health comes from Plex and its signals, so a workcenter has photos here but no health profile.

PM by run hours

For equipment Plex does not schedule PM on, a Shop Floor Admin can set PM every (run hours) on the asset's card on the Assets screen, then select Save interval. It is counted from the motor's sensed run hours. Leave it blank for none. If Plex schedules PM on the equipment, the interval is not used. The card then lists upcoming and overdue PM, and a technician (Maintenance) or a Shop Floor Admin can select Mark PM done, which starts the run-hour count again.

4. Sensors & thresholds

Equipment thresholds lists the location's threshold conditions on equipment. Select New threshold, then:

  1. Pick the Equipment and the Signal to watch. Signals can come from the PLC or from a mapped historian series.
  2. Choose Fires when the value is above, at or above, below, at or below, or equal to.
  3. Give a Warning limit, an Alarm limit, or both. Each limit becomes its own condition: the warning opens a warning incident, and the alarm a critical one. Their names end in "warning" and "alarm".
  4. Set Hold: how many minutes the value must stay past the limit before an incident opens (0 to 1440).
  5. Write up to 10 Possible causes and 10 Recommended checks, 200 characters each. Technicians see these on the alarm and the insight.
  6. Select Create threshold.

Severity, Armed and the guidance lists change in place.

Tune limits on real data

Pick a signal to see its last 30 days, its normal band and suggested warning and alarm limits. Where the suggestion comes from explains how they were worked out. Drag the lines or type the numbers, and see how many warnings and alarms the limits would have raised. Select Accept to save them. Accept for this and N similar applies the limits to similar equipment, each scaled to its own normal band, with a preview first. For an RMS velocity signal, you can fill in the ISO zone limits from the asset's machine class.

Apply ISO zone limits to a line

This sets the warning (zone C, Unsatisfactory) and the alarm (zone D, Unacceptable) on every RMS velocity signal on a line, from each asset's machine class and the signal's unit. Limits someone set by hand are kept unless you tick Replace hand-set limits. Select Preview first. Nothing is saved until you apply.

Changing the equipment, signal, comparison, limit, hold, name or description replaces the condition with a new one. Its escalation rungs are removed with it, and the confirmation says how many. Incidents it already raised are kept. A threshold marked Pages nobody has no escalation rung. Other kinds of conditions at the location are managed on the escalation screen (Open escalation →). See Conditions and escalation.

5. Historian sources

Connect a SQL historian in your own database through your on-site connector, and map its tags or columns to equipment signals. The list shows each source's polling state (Polling, Off, Failing or Not polled yet), its mapped series and when it was last polled, with edit, disable and delete. Nothing is ever written to your database. The full walkthrough is on SQL historian.

6. Review & go live

This is the last setup step. It shows what switching the limits on will watch: the assets, lines, limits and signals, and how often they are checked. Lines, equipment and limits each show their state, with a link to fix them.

  • Who is told, and how fast: the escalation rungs, in order, with when each one fires and who it reaches. Notification groups are worked out against the shift running now. Select Send a test alert to me to check it. Nobody else is sent anything.
  • If you switched on now: any limit that is switched off but is crossed right now, so it would alarm once its hold passes.
  • Start watching: switches on every limit that is off, after you confirm. The confirmation says how many have no notification rung and how many are crossed right now. Add a notification rung first, or an alarm would reach nobody. Only a Shop Floor Admin can switch limits on.

7. Insights & work orders

  • How an insight opens: an incident on a piece of equipment joins its open insight, or opens a new one named after the condition. No work request is raised automatically. A technician (Maintenance) or a Shop Floor Admin raises it from the insight, after a dry run.
  • Plex data sources for work requests: the four Plex Maintenance data sources a work request uses, in order: Priorities_List_Get (the High, Medium and Low priority keys), Work_Request_Statuses_Get (the status a new request starts in), New_Work_Request_No_Get (the next work request number) and Work_Request_Add (creates the work request). The location's Plex credential must have all four. Select Check with Plex to see whether each one is Enabled for that credential. The check runs only when you select it.
  • Try it on an insight: select Dry run to build the work request for one of the location's open insights and see what Plex would receive, marked Ready to send or Would be refused. A dry run calls nothing in Plex.
  • Days until Unsatisfactory: the lead time, from 1 to 30 days. When a motor's vibration trend says it will reach its ISO Unsatisfactory zone within this time, a work request is suggested for a person to confirm. Select Save lead time. Nothing is sent to Plex until someone confirms it.

Daily digest

At the start of each shift, Asset Health emails a digest for each line: assets that got worse overnight, PMs due or overdue, repairs that did not hold, and yesterday's downtime, including what Plex did not record. Every item links to its asset card.

  1. Tick the notification groups that receive it. The members on the starting shift get it, and members who are always on get it once a day.
  2. Select Save digest groups.
  3. Select Preview to see it, or Send a preview to me to get it by email. Nobody else gets the preview.

If the location has no notification groups yet, use Manage notification groups to create one. See Conditions and escalation.

8. Roles

Shop Floor and Asset Health have their own roles. DataMagik - Shop Floor Viewer sees every screen and can acknowledge alarms. DataMagik - Maintenance can also work insights: change their state, add notes and raise a Plex work request. DataMagik - Shop Floor Admin can also change settings. DataMagik - Builder and DataMagik - Viewer give you nothing here.

Who holds Maintenance lists the active users who hold DataMagik - Maintenance and the roles that grant it. To change who holds it, a customer admin opens Change who holds it in the company user manager → (/datamagik/company-user-manager) and adds or removes the DataMagik - Maintenance role. Roles also links to Notification groups: who gets alarm email, per shift.

9. Dashboards

Each screen (Portal, Lines, Assets, Insights, Analytics) has one layout for Desk and one for Wall, per location. The Customize layout button on a screen, which only a Shop Floor Admin sees, opens this section for that screen.

  1. Pick the Screen and the Desk or Wall layout.
  2. Reorder panels by dragging them or with their arrows. Select a panel to set its Title (optional) and Width (1 to 6 columns), or to Remove panel.
  3. Under Add a panel, choose one of: KPI strip, Line cards + stations, Line schematic, Active alarms, Alarm detail, Asset health summary, Assets needing attention, Asset tree, Asset detail, Insights, Top faults, Downtime by line, Availability trend, Asset signal trend or Custom app.
  4. Select Save layout. Reset to default goes back to the built-in layout.

A Custom app panel shows a published App Designer app you can open. Choose which selections to pass to it (Location, Line, Asset, Insight), its Height (Medium or Auto) and Show (Title + open link, or App only).

Linked apps in the module menu adds up to 12 apps to the module's tab strip. Each one opens full screen with the same selection. Give each a menu label of up to 40 characters, choose what it is passed, then select Save linked apps. See Asset Health in App Designer.

10. Connectivity

Lists the connectors at this location's connector group and their status. OPC UA certificates are downloaded from Connector Setup, in the Download Connector menu next to the agent: the company CA and each connector's own client certificate, as PEM, CER or DER. Links go to Connector Setup and to the OPC UA gateways on the tag map. If an OPC UA server refuses the connection, compare the certificate's SHA-256 fingerprint with the newest file in the server's rejected list, then move it to trusted. See Connector setup and PLC connectivity.

Was this page helpful?