A Deactivate This Instance node represents an action to deactivate the current policy instance. You can use this node to ensure that an action is taken only once per instance.
When a Deactivate This Instance node is executed, the policy instance whose values caused the node to be executed will be deactivated automatically. If more than one policy instance is associated with the policy, all other policy instances will remain unchanged.
After the conditions that caused the instance to be deactivated have been addressed, you can reactivate the policy instance manually from the Instances pane in Policy Designer or the Policies section in Asset Health Manager.
Other than optionally specifying a name for the node, there are no properties to configure for a Deactivate This Instance node.
The following example illustrates how you can use a Deactivate This Instance node to ensure that only one Policy Recommendation record is created as a result of the policy conditions being met for a specific policy instance. Consider the following nodes and connection.
In this example, the OPC Tag node and the Condition node to which it is connected indicate that a Policy Recommendation record should be created when the DA Reading Value associated with the OPC Tag node exceeds 200.
Assume that the following records are associated with the OPC Tag node via policy instances:
When the policy is executed, a Policy Recommendation record for Pump 101 will be created. Because the policy also includes a Deactivate This Instance node, after the Policy Recommendation record is created, the GE Digital APM system will deactivate automatically the policy instance that is associated with Pump 101. The policy instance that is associated with Pump 102 will remain active.
Because the policy instance that is associated with Pump 101 is no longer active, even if the DA Reading Value associated with the pump continues to exceed 200, additional Policy Recommendation records will not be created.
Copyright © 2018 General Electric Company. All rights reserved.