How to guide superusers to leverage the best of the application for down times
1
(mandatory) Assign permissions via Settings › Users and Access Management
Persons executing the below steps, will require the following permissions:
Permission > Downtimes > Can configure downtime settings
2
(optional) Create (sub)categories via Settings › Downtimes › (sub)categories
(Sub)categories are required for reporting purposes. Although the platform allows to create reason codes without categories, we know no-one will go live without them. However, then can be skipped with initially setting up the system whilst one focuses on connections.
3
(mandatory) Create an equipment via Settings › Organization › Equipment
If this is your first module, ensure you have one or more equipment created in the general admin section.
4
(mandatory) Select an equipment via Settings › Downtimes › General
Select the equipment on which you want to log down times. Only equipment added here will be displayed in the downtimes module.
5
(mandatory) Create reason trees via Settings › Downtimes › General
In both views (line or equipment), one can create reason trees for each equipment. This will guide employees to select the proper reason codes when qualifying down times.
6
(optional) Define the qualification method for "downtimes"
When you're using the full suites of modules, you can create a skill and a course to ensure employees are trained before using the down time module.
7
(mandatory) Assign permissions via Settings › Users and Access Management
Persons using the down time module, will require the following permissions:
Permission > Downtimes > Can view downtimes
This can be done via automatic permission using the course qualification status, grouped via permission roles or via individual allocation
