New article
Recently updated
Getting started with Lucidity Permit to Work
Who is this article for?Users getting started with Permit to Work.
No elevated permissions are required.
Lucidity's Permit to Work module enables organisations to seamlessly manage the end-to-end processes involved with Permits to Work. Permits can be drafted, submitted for approval, and subsequently approved once all requirements are met. Necessary isolations are identified and applied, ensuring work can only commence on an approved permit with the required isolations in place. During the active work period, isolations remain enforced and cannot be modified. Upon completion of work, isolations are reinstated, allowing the permit to be closed. This systematic approach ensures isolations are properly managed throughout the permit lifecycle, prioritizing safety and compliance.
1. Overview
Video: Permit to Work Webinar
Video: Module Overview
The following diagram summarises the Permit to Work workflow:
Note: This webinar was recorded in March 2019, so any updates to the Permit to Work module after that date are not covered. This video provides a comprehensive 30-minute training webinar, focusing on the Permit to Work module for the first 22 minutes, followed by a 10-minute segment on the shared Bulk Change feature.
2. Permit to Work Access roles
Users are given different permission levels based upon their access requirements. Permissions for all Lucidity applications are set via Lucidity Access and are generally configured by the system administrator. The standard roles typically provided in all new Lucidity system builds are as follows. These can be edited by system administrators as required.
|
User Role |
Role Description |
|---|---|
|
Read Only |
Using Permit to Work, a user can view Permits |
|
Manager (Creator) |
Using Permit to Work, a user can create and edit permits and run reports (cannot delete) |
|
Approver |
Using Permit to Work, a user can approve and close permits and run reports(cannot delete) |
|
Administrator |
Administrator role for Permit to Work |
2.1. Read only
End-users may be given read only to Lucidity Permit to Work in order to allow them to view existing permits and isolations and run reports.
2.2. Manager (Creator)
The permit manager is able to create new permits and edit existing ones as well as manage isolations and run reports. They are unable to delete or approve permits.
2.3. Approver
An approver is able to approve permits which, in turn, allows work to commence. This role would typically be assigned in conjunction with the manager role but can be assigned in isolation if required.
2.4. Administrator
Unless they are allocated the approver role, administrators cannot approve permits. They can however view all permits and related isolations and have access to the delete function. In addition to the access managers have, administrators will also have access to the Settings tab where data lists are generated and managed.
3. Retaining system integrity
Only the administrator has the permission to manage master data such as managed lists. It is recommended that the number of administrators per instance of Lucidity Software is kept to a minimum to retain integrity and consistency across the system configuration and to avoid duplication. It is a worthwhile exercise to create a standard set of guidelines that all new master data entered must follow.