Changes
The MRO plugin provides a set of {{UBIK}} objects which allow to represent and document maintenance, repair and operations work on the mobile client.
== Status Information Basic Features ==
Objects classified as MRO objects in general provide a technical and organisational status as well as the overall work progress based on the underlying data branch.
=== Technical Status ===
The technical status indicates whether all tasks from on this or on subsequent objects in the underlying data branch have been finished. Also other information is included in this status, e.g. if a inventory object is reported as damaged, its parent objects will receive a certaub status indicating that a problem was reported in the child items.
=== Organisational Status ===
The organisational status indicates the amount of confirmed work done in the data branch. It can include a work package already confirmed or tasks that are already locked by their owning workpackage.
==Prerequisites= Work Progress ===[[File:UI_OPCUA_Certificate.png|border|thumb|Export Certificate]]The {{UBIK}} OPC UA components are acting as an OPC Client, therefore a secure connection to work progress is calculated from the respective OPC Server needs to be established current work progress and from the progress cumulated from subsequent objects in order to be able to communicatethe underlying data branch. The security standards that need to be applied are highly dependent on This indicator shows the server configuration and security infrastructure, but normally at least a client certificate needs to be issued that has to be trusted by amount of work done in the server:data branch.
=={{UBIK}} Activities=Task Owner ={| class="wikitable sortable" | width = "50%"|-! Activity!! Category !! Purpose (Short)|- align="left"| A [[Activity:CreateOPCUAConnection (Activity)MROCLS_MRO_TASKOWNER|CreateOPCUAConnectionTask Owner]]|| UBIK OPC UA Interface || Creates is an object having a new connection substructure of jobs to an OPC UA data source|- align="left"| [[Activity:ConfigureOPCUAVariable (Activity)|ConfigureOPCUAVariable]]|| UBIK OPC UA Interface || Configures be done. It can have a single OPC variable in tree of other task owners or work packages underneath that will update the status of the task owner. This status consists of technical, organisational and progress information. With a connection for later access|- align="left"| [[Activity:CreateOPCUAScope (Activity)|CreateOPCUAScope]]|| UBIK OPC UA Interface || Defines task owner a scope in user can get an OPC UA connection wherein variables can overview of all the work to be accessed|- align="left"| [[Activity:AccessOPCUAVariable (Activity)|AccessOPCUAVariable]]|| UBIK OPC UA Interface || Reads or writes a single configured OPC UA variable|- align="left"|}done in the underlying job structure.
==Examples=Work Package===A [[MROCLS_MRO_WORKPACKAGE|Work Package]] is a collection of objects to collect and summarize other task owning objects, workpackages, or tasks. A simple workpackage has a certain amount of tasks that have to be finished in order to confirm the workpackage as done. More complex workpackages can also own other underlying workpackages that have to be confirmed. Confirming a workpackage itself requires a progress of 100% of all related tasks, as well as 100% confirmed sub work packages. === Task ===A [[MROCLS_MRO_TASK|Task]] is an object reporting a certain progress to the owning workpackage. There are several specialized types of task objects. All kinds of tasks have a property called '''VALUE''' in common. It is very important, that this property is able to be validated. Therefore, a MetaAttribute (providing a validation timestamp by default) has to be attached on the used MetaProperty. Download example workflow {{FileLinkAttention|OPCReadVariablesThe MetaProperty ''VALUE'' has to use [[Attributes]] in order to be validated.uwf|OPCReadVariablesOtherwise, the calculation of work progress will not be possible.uwf}} for use against ==== Measurement Task ====A [[MROCLS_MRO_MEASUREMENT_TASK|Measurement Task]] inherits from [[MROCLS_MRO_TASK|Task]] and documents a measured value (e.g. read from a pressure gauge). Once a value has been entered, the OPC Quickstart Data Access Servertask is finished. Alternatively, the task can also be closed by the option ''Not Applicable'' to document the situation of not being able to fullfill the measurement (e.g. the pressure gauge is broken). ==== Progress Task ====[[MROCLS_MRO_PROGRESS_TASK| Progress Task]] inherits from [[MROCLS_MRO_MEASUREMENT_TASK|Task]] and reports a certain progress while fullfilling a task. The progress will influence the overall progress of the owning workpackage. If the task cannot be fullfilled, it can also be finished with the option ''Not Applicable''. ==== Check Task ====A [[MROCLS_MRO_CHECK_TASK|Check Task]] inherits from [[MROCLS_MRO_TASK|Task]] and is finished, when the user reports with a positive or negative answer or ''Not Applicable'' (e.g. reporting a yes/no answer for existing equipment). ==== Inspection Task ====[[MROCLS_MRO_INSPECTION_TASK|Inspection Task]] inherits from [[MROCLS_MRO_TASK|Task]] and is finished by reporting ''Done'' or ''Not Applicable''. This is intended for a simple To-Do task that is either done or not.
== See also ==
