Asset Health setup

Asset Health setup

Asset Health settings is where a Builder sets up a site's lines, equipment, thresholds, historian, work requests, people and dashboards, with a checklist that shows what is still missing.

Permissions: The settings hub needs DataMagik - Builder and the Asset Health licence. Uploading, starring or deleting machine photos and editing a health profile are Builder-only everywhere in the module. Who holds DataMagik - Maintenance is managed by a customer admin (DataMagik - Security) in the company user manager.

Opening settings

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

Setup checklist

The Setup checklist at the top of every section is worked out each time you open the page. It shows how many items are done, and each To do item has a Set up link to the section that fixes it. It checks that:

• the site has assets;
• every asset has a photo (missing ones are named);
• every line has its stations (lines without any are named);
• a historian source is connected;
• somebody holds Maintenance;
• at least one threshold watches an asset.

1. Sites

A summary of the selected site: 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 sites (PCN, time zone, credential) →, which opens /shop-floor/settings/sites. See Shop Floor.

2. Lines & stations

1. Pick a Line.
2. Under Add a station, pick a workcenter or asset from the site. Nothing is typed by ID.
3. 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.
4. 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.
5. Pick each station's Key signal from the signals bound to that machine. This is the value the schematic shows live.
6. 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 site's Asset tree lists workcenters and assets. Assets without a photo are flagged No photo. To add equipment, move it in the tree, or set its kind (for example Machine, Motor or Component), use Add or move equipment on the Equipment screen →.

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).
• Plex equipment (for work requests): search by the start of the Plex equipment ID and pick a match. Without it, work requests are raised without equipment.

Select Save health profile. 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.

4. Sensors & thresholds

Equipment thresholds lists the site'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.

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 site 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. 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 or Builder 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 site'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 site's open insights and see what Plex would receive, marked Ready to send or Would be refused. A dry run calls nothing in Plex.

7. Roles

Who holds Maintenance lists the active users who hold DataMagik - Maintenance and the roles that grant it. Maintenance lets a technician work insights and acknowledge incidents without Builder's other rights. 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.

8. Dashboards

Each screen (Portal, Lines, Assets, Insights, Analytics) has one layout for Desk and one for Wall, per site. The Customize layout button on a screen 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 (Site, 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.

9. Connectivity

Lists the connectors at this site's connector site 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.