Mobile Health
Depending on the parameters of the VIMS data that is collected for each equipment unit type, a Health Profile token may be defined for each model type. Only the Code, Description and Abbreviation need to be defined for each Health Profile.
Health Item tokens define the information to be collected from the VIMS system - the fan speed, the oil pressure, etc.
|
Attribute
|
Data Type | Description |
|---|---|---|
| Vehicle System | T | Currently, VIMS is the only monitoring system available. |
| Known Tag | T |
The name of the health measure to be captured. Define either a known tag type, such as EngineOilPressure, or define the following four attributes. |
| System Tag | T | The ID of the health measure to capture (if the tag is not known). |
| Scaling Factor | N | Enter the scaling factor to be applied to the value. |
| Minimum Value | N | Valid minimum value. |
| Maximum Value | N | Valid maximum value. |
| Maximum Age On Server | N | The number of days that the server will keep this information. |
| Maximum Values On Server | N | The number of values that the server will keep for this item. |
Health Actions
| Attribute | Data Type | Description |
|---|---|---|
| Health Profile | T | Select from the list of defined HealthProfile tokens already defined (see above). |
| Health Item | T | Select from the list of defined HealthItem tokens (see above). |
| Execute On Logon | 0 or 1 | Define whether the action will be executed on login. |
| Execute On Logoff | 0 or 1 | Define whether the action will be executed on logoff. |
| Execute On Value Change | 0 or 1 | Define whether the action will be executed when the value changes. |
| Execute On Time Change | 0 or 1 | Define whether the action will be executed when the timer fires. |
| Execute On Action | 0 or 1 | |
| Maximum Frequency | N | The minimum frequency this action will be performed in seconds. Note: this will initially be UI limited. |
| Raise Alarm | 0 or 1 | An alarm will be raised on the server. |
| Raise Alarm Locally | 0 or 1 | An alarm will be raised locally and on the server. |
| Submit As Attribute | 0 or 1 | The value will be set as a dynamic attribute and sent to the server. |
| Attribute Code | T | Define the code. |
| Submit As Health | N | The value will be buffered and submitted ot the server with other health information in an optimised format. |
| Trigger Action | If the conditions for this action are met, other actions will be triggered. | |
| Notify Mobile Core | 0 or 1 | Notifies the mobile core that this has occurred. |
| Condition One | T | The first condition that must be met. This will be one of the defined HealthConditions. |
| Condition Two | T | The second condition that must be met. This will be one of the defined HealthConditions. |
| Condition Three | T | The third condition that must be met. This will be one of the defined HealthConditions. |
| Condition Four | T | The fourth condition that must be met. This will be one of the defined HealthConditions. |
| Condition Logic | T |
The is either AND or OR. Either Condition One AND Condition Two or Condition One OR Condition Two, for example. |
Health Conditions
| Attribute | Data Type | Description |
|---|---|---|
| Operation | Boolean |
Set the boolean operation for the condition. If the condition, for example is: less than 20 The Operation = < |
| Value | N | Define the value of the condition. In the example above = 20. |
Options for requesting additional data such as log and video files in a Mobile Health Panel allow an operator to collect and analyse a wide range of information from equipment. See: Requesting Logs from Mobile.