End-to-End Flow
Consider the following example to understand how the technical attributes are associated to assets and attribute history is displayed.
A healthcare device manufacturer has a requirement to monitor the power input information for all the mammogram devices of type DMR Plus. There have been issues with power fluctuation in the devices and the devices have been shutting down, so the company wants to monitor the power input scenarios. Also, the company wants to check whether the software version installed on the devices has any impact on the issue.
Setup:
1. Create two technical attributes: Power Input and Software Version
2. Create a technical attribute template with the following:
◦ Create an attribute group named Operating Parameters.
◦ Add technical attributes Power Input and Software version to the Operating Parameters group.
◦ Create a template match value with the product DMR Plus.
3. Create a template rule with Product from template association match with Product from Asset.
At runtime:
Open any asset record which belongs to product DMR Plus. In real-time, the asset technical attribute engine executes to fetch the technical attribute templates that match with the template match rule. In this case, the asset's product DMR Plus matches with the template's Product value DMR Plus. As a result, one template is found and technical attributes Power Input and Software Version are listed on the Technical Attributes view.
The field engineers and technicians can update the power input and the software version details periodically. Over time, the attribute history information helps the company to view the trend and check whether the software version of the devices has any impact on the power fluctuation situation.
 |
When multiple templates are applied and if there are any common technical attributes between templates, then that specific technical attribute is listed only once on the UI. It is listed in the section which was created first.
|