Example: An asset type template for a capper machine

In this example, an organization is using several capper machines in their production line. For each physical machine, the organization has configured AVEVA Insight tags tracking the machine's availability, as well as some specific metrics for the machine's downtime that include how many times it has gone offline and for how long.

Using asset types, a solution administrator defines a "Capper Machine" template that includes properties describing each of those tags. The administrator already has an asset created for one of the capper machines, Capper 1, so they link that asset to the asset type and map the Capper 1's availability, downtime, downtime count, and downtime duration tags to the asset type properties.

With the mapping in place, the administrator then creates a chart tracking Capper 1's availability and saves that content back to the asset type. The administrator also sets up an alarm so that they will receive an email when Capper 1 goes offline and also saves that alarm back to the asset type.

From within the Asset Instances tab on the asset type summary page, the administrator creates a new asset for Capper 2. Once the administrator is finished mapping tags to properties for Capper 2, AVEVA Insight synchronizes the asset type with its associated asset instances and propagates the Capper 1 and Capper 2 assets with instances of the content and alarm items specific to those assets. The solution now has "Capper 1-Capper availability" and "Capper 2-Capper availability" content saved under the respective asset, as well as "Capper 1-Capper offline" and "Capper 2-Capper offline" alerts configured for the assets.