Difference between revisions of "MRO (Plugin)"
(Created page with "The MRO plugin provides a set of {{UBIK}} objects for automatic calculation of the cumulated status and progress of tasks, work packages and administrative objects. A detailed...") |
m |
||
Line 1: | Line 1: | ||
− | The MRO plugin provides a set of {{UBIK}} objects | + | 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 == | ||
+ | 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 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 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== | ==Prerequisites== |
Revision as of 12:25, 3 August 2016
The MRO plugin provides a set of UBIK® objects which allow to represent and document maintenance, repair and operations work on the mobile client.
Contents
Status Information
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 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 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
The UBIK® OPC UA components are acting as an OPC Client, therefore a secure connection to the respective OPC Server needs to be established in order to be able to communicate. The security standards that need to be applied are highly dependent on the server configuration and security infrastructure, but normally at least a client certificate needs to be issued that has to be trusted by the server:
- Open a command box on the UBIK® server with administrator privileges ("Run as administrator...")
- Run the program CreateCertifcate.exe from the archive CreateCertificate.zip
- Open the program Manage computer certificates (typically C:\WINDOWS\System32\certlm.msc)
- Navigate to Personal - Certificates and find the certificate named UBIK OPCUA Interface
- Export the certificate and trust it on your OPC server
UBIK® Activities
Activity | Category | Purpose (Short) |
---|---|---|
CreateOPCUAConnection | UBIK OPC UA Interface | Creates a new connection to an OPC UA data source |
ConfigureOPCUAVariable | UBIK OPC UA Interface | Configures a single OPC variable in a connection for later access |
CreateOPCUAScope | UBIK OPC UA Interface | Defines a scope in an OPC UA connection wherein variables can be accessed |
AccessOPCUAVariable | UBIK OPC UA Interface | Reads or writes a single configured OPC UA variable |
Examples
Download example workflow OPCReadVariables.uwf for use against the OPC Quickstart Data Access Server.
See also
- MROCLS MRO TASKOWNER (Classification)
- MROCLS MRO WORKPACKAGE (Classification)
- MROCLS MRO TASK (Classification)
- MROCLS MRO MEASUREMENT TASK (Classification)
- MROCLS MRO PROGRESS TASK (Classification)
- MROCLS MRO CHECK TASK (Classification)
- MROCLS MRO INSPECTION TASK (Classification)
- MRO Objects (UBIK WinX)