Contents

Using Device Criticality

Summary

Assigning Criticality to devices according to their importance within your organization.

Overview

Device criticality is an attribute of a device that you define for its importance within your organization. You must first agree the criteria for importance within your organization, and ensure all Tachyon users have the same understanding of criticality and how they are expected to use it. 

Criticality is set on devices using an instruction, as described below in Setting Device Criticality.  

Tachyon allows you to use Criticality to define the following:

  • rules to create Management Groups - see Tachyon Platform 5.2 - Management groups page
  • coverage for instructions, for example, you can choose to target an instruction to be sent only to devices whose criticality is set to any one of the following:
    • Undefined (or not set)
    • Non-critical
    • Low
    • Medium
    • High
    • Critical.

Criticality is displayed in the following app pages in the Tachyon Portal:

Experience
Explorer
Guaranteed State
Nomad
Patch Success
Settings
On this page:

Setting Device Criticality

Device criticality is set using the instruction Set the criticality of my devices to <criticality> where <criticality> is selected from the list above.

In Tachyon Explorer, type the instruction and then choose the desired criticality from the dropdown.

Select the coverage for the instruction and submit it. After approval, devices which match the specified coverage value will have their criticality set to the specified value.

Any devices that do not have their criticality set are reported as Undefined or Not set.

There is a corresponding instruction What is the criticality of my devices? 

The two instructions 1E-Explorer-TachyonAgent-GetCriticality and 1E-Explorer-TachyonAgent-SetCriticality are available by uploading the Classic Product Pack 1E-Explorer-TachyonAgent, which is included in the Tachyon Platform zip downloaded from the 1E Support Portal.