ACCEPTED SOLUTION
Accepted Solutions
Hi @zajaja
Statuses are initially defined at the global level, and apply to all equipment. Statuses can be defined and configured for specific equipment types, in order to align with the actual statuses generated by that type of equipment. Statuses can also be defined and configured for individual pieces of equipment. Statuses are configured in ThingWorx Composer from the Status Definition Entries page. This page can be accessed from the Mashup page of the following entities:
PTC.SCA.SCO.StatusDefinitionEditorMashup, PTC.SCA.SCO.DefaultStatusManager, PTC.SCA.SCO.StatusUtils.
There can be no more than 9 statuses at the global level, or for any equipment type thing template, or individual equipment thing. Out of which 6 is OOTB and 3 status can be custom.
On the Status screen, the possible states for the equipment are defined. There are 6 states provided by default:
Not Configured, Planned Downtime, Warning, Running, Unplanned Downtime, and Unavailable.
Of these states, the expressions for Planned Downtime, Warning, Running, and Unplanned Downtime can be defined.
The status expressions are evaluated in the order that they appear in the table. The first expression to evaluate to true determines the state of the equipment.
You can change the order of the editable states using the and actions.
When equipment is first created, the Not Configured expression evaluates to true by default. The equipment remains in the Not Configured status until you have edited and saved the expression for at least one of the editable states, or have reordered the states.
CriticalityOrder— is a required field when configuring the status. It sort the order for the status when sorting the Asset Advisor asset list by criticality. The higher the value, the higher the criticality. This value must be unique among the statuses applicable for a particular equipment type thing template or an individual equipment thing.
Let say value for criticalityOrder for status unavailable is 40, planned downtime= 30 and Running = 10 , then on Asset advisor page sort order by criticality fist is shows the assets which are unavailable then asset with planned downtime lastly assets which are running.
To further look into the issue why your status is not evaluated immediately/correctly we required to investigate the kepware logs and application and communication logs. Additionally, which version of ThingWorx and Apps are you using?
Thanks
Abhishek
Hi @zajaja
Statuses are initially defined at the global level, and apply to all equipment. Statuses can be defined and configured for specific equipment types, in order to align with the actual statuses generated by that type of equipment. Statuses can also be defined and configured for individual pieces of equipment. Statuses are configured in ThingWorx Composer from the Status Definition Entries page. This page can be accessed from the Mashup page of the following entities:
PTC.SCA.SCO.StatusDefinitionEditorMashup, PTC.SCA.SCO.DefaultStatusManager, PTC.SCA.SCO.StatusUtils.
There can be no more than 9 statuses at the global level, or for any equipment type thing template, or individual equipment thing. Out of which 6 is OOTB and 3 status can be custom.
On the Status screen, the possible states for the equipment are defined. There are 6 states provided by default:
Not Configured, Planned Downtime, Warning, Running, Unplanned Downtime, and Unavailable.
Of these states, the expressions for Planned Downtime, Warning, Running, and Unplanned Downtime can be defined.
The status expressions are evaluated in the order that they appear in the table. The first expression to evaluate to true determines the state of the equipment.
You can change the order of the editable states using the and actions.
When equipment is first created, the Not Configured expression evaluates to true by default. The equipment remains in the Not Configured status until you have edited and saved the expression for at least one of the editable states, or have reordered the states.
CriticalityOrder— is a required field when configuring the status. It sort the order for the status when sorting the Asset Advisor asset list by criticality. The higher the value, the higher the criticality. This value must be unique among the statuses applicable for a particular equipment type thing template or an individual equipment thing.
Let say value for criticalityOrder for status unavailable is 40, planned downtime= 30 and Running = 10 , then on Asset advisor page sort order by criticality fist is shows the assets which are unavailable then asset with planned downtime lastly assets which are running.
To further look into the issue why your status is not evaluated immediately/correctly we required to investigate the kepware logs and application and communication logs. Additionally, which version of ThingWorx and Apps are you using?
Thanks
Abhishek
