Difference between revisions of "MRO Implemented Objects"
| Line 28: | Line 28: | ||
! width=30% | Name !! width=20% | Data type !! Comment | ! width=30% | Name !! width=20% | Data type !! Comment | ||
|- | |- | ||
| − | | VALUE || {{ | + | | VALUE || {{Boolean}} || Task is Done |
|- | |- | ||
| LABEL_FALSE || {{String}} || Upper Range value | | LABEL_FALSE || {{String}} || Upper Range value | ||
| Line 53: | Line 53: | ||
! width=30% | Name !! width=20% | Data type !! Comment | ! width=30% | Name !! width=20% | Data type !! Comment | ||
|- | |- | ||
| − | | VALUE || {{ | + | | VALUE || {{Boolean}} || Task is Done |
|} | |} | ||
| Line 62: | Line 62: | ||
! width=30% | Name !! width=20% | Data type !! Comment | ! width=30% | Name !! width=20% | Data type !! Comment | ||
|- | |- | ||
| − | | XXX || {{ | + | | XXX || {{Guid}} || Selected Item |
|} | |} | ||
| Line 71: | Line 71: | ||
! width=30% | Name !! width=20% | Data type !! Comment | ! width=30% | Name !! width=20% | Data type !! Comment | ||
|- | |- | ||
| − | | VALUE || {{ | + | | VALUE || {{Boolean}} || Task is Done |
|} | |} | ||
| Line 80: | Line 80: | ||
! width=30% | Name !! width=20% | Data type !! Comment | ! width=30% | Name !! width=20% | Data type !! Comment | ||
|- | |- | ||
| − | | VALUE || {{ | + | | VALUE || {{Boolean}} || Task is Done |
|} | |} | ||
| Line 89: | Line 89: | ||
! width=30% | Name !! width=20% | Data type !! Comment | ! width=30% | Name !! width=20% | Data type !! Comment | ||
|- | |- | ||
| − | | VALUE || {{ | + | | VALUE || {{Boolean}} || Task is Done |
|} | |} | ||
Revision as of 15:34, 19 May 2025
'MRO Implemented Objects' are configured standard MRO Objects, adding further additional logic and features. All the object described below inherits from MROCLS MRO TASK and MROCLS SEQUENTIALTASK. Values properties are set by default and they often fully implement other MRO suitable classification.
Contents
Numeric Task
A Numeric Task documents a numeric double value (e.g. read from a temperature sensor). Once a value has been entered (including Not Applicable), the task is finished. An acceptability range and a measurement unit can be set and shown, and a red colour alert and/or and update of the technical status can be triggered if out of range. The behaviour of this previous value indicator has to be specified separately.
| Name | Data type | Comment |
|---|---|---|
| VALUE | Double | Double Number |
| VALUE_MAX | Double | Upper Range value |
| VALUE_MIN | Double | Lower range value |
| VALUE_UNIT | String | Measurment unit of value |
Inspection Task
| Name | Data type | Comment |
|---|---|---|
| VALUE | Boolean | Task is Done |
| LABEL_FALSE | String | Upper Range value |
| LABEL_TRUE | String | Lower range value |
Text Task
| Name | Data type | Comment |
|---|---|---|
| VALUE | String | Inserted Text |
Picture Task
A Picture Task is finished by reporting Done or Not Applicable.
| Name | Data type | Comment |
|---|---|---|
| VALUE | Boolean | Task is Done |
Dynamic List Task
| Name | Data type | Comment |
|---|---|---|
| XXX | Guid | Selected Item |
Interface Task
| Name | Data type | Comment |
|---|---|---|
| VALUE | Boolean | Task is Done |
Calculation Task
| Name | Data type | Comment |
|---|---|---|
| VALUE | Boolean | Task is Done |
Supervisor Check Task
| Name | Data type | Comment |
|---|---|---|
| VALUE | Boolean | Task is Done |
