Settings and activity
73 results found
-
63 votes
An error occurred while saving the comment Ashley Nuttall supported this idea ·
-
66 votes
Ashley Nuttall supported this idea ·
-
78 votes
Ashley Nuttall supported this idea ·
-
99 votes
Ashley Nuttall supported this idea ·
-
141 votes
Ashley Nuttall supported this idea ·
-
71 votes
An error occurred while saving the comment Ashley Nuttall commented
A lot of Comments about pausing a PM, i find setting the filter up in the console and grouping to the required group will allow you to cancel all the dates that are forecasted. This only works if the PM's have been forecasted and would be better if it was just an active/in active value in the PMS
An error occurred while saving the comment Ashley Nuttall commented
I believe the changing of the Date first works to set the forward generation dates, however, a recent change to the generation function does mean the user needs to delete the forecasted PMSD data. The planner seems to cover this but only for the range set. Would be best maybe to monitor this field and have an action that removes all forecasted dates so that duplicates are not created. An inactive function would be good to be able to set a PMS to stop it from generating without changing any of the settings. There are ways to paulse a PMS for a time period already setting the manual date next to do will stop anything generating until the set date.
There is definitely a requirement to actively check the current eq status so that work is not generated, equally, there needs to be a report that shows all PMS records that will be affected by the equipment status. This will help if there are any expected PMS not generated because the eq has the wrong status.
Ashley Nuttall supported this idea ·
-
84 votes
Ashley Nuttall supported this idea ·
-
89 votes
Ashley Nuttall supported this idea ·
-
100 votes
Ashley Nuttall supported this idea ·
-
76 votes
An error occurred while saving the comment Ashley Nuttall commented
This is very important, all possible requestor function should be in the workplace. We need to keep the consistency.
Ashley Nuttall supported this idea ·
-
3 votes
Ashley Nuttall shared this idea ·
-
6 votes
Ashley Nuttall supported this idea ·
-
18 votes
An error occurred while saving the comment Ashley Nuttall commented
The are so many reasons that this is important, and all of the ones suggested are definitely warranted. SWG has created a Permit to a work function that allows for Pertmit as questionnaires. The problem we have is printing out the questionnaires.
The lack of reports linked to checklists is very worrying. We are trying to encourage clients to use this function more but being able to fill in a checklist is great. but not being able to properly report and action on the finding from within this checklist response is causing a lot of negative feedback.
Proper access to chick list data after the work has been archived is also a big must-have. If the client is going to go fully paperless then the checklist response needs to be accessible everywhere the work request data is accessed and all statuses, especially history. A lot of this work is statutory, and access to evidence is a must without it the system is of little help to prove work was completed and the correct check is in place with the results.
Ashley Nuttall supported this idea ·
-
106 votes
Ashley Nuttall supported this idea ·
An error occurred while saving the comment Ashley Nuttall commented
This is a problem; I also find it difficult to quickly workout which message is being used. This would be better if it were simplified
-
5 votes
Ashley Nuttall shared this idea ·
-
3 votes
Ashley Nuttall shared this idea ·
-
7 votes
Ashley Nuttall supported this idea ·
-
6 votes
Ashley Nuttall supported this idea ·
-
19 votes
Ashley Nuttall supported this idea ·
-
9 votes
Ashley Nuttall supported this idea ·
in the current climate with AI and all the new systems being released, we need a far simpler option to connect to the systems via API i think via a connector with REST would be a really good starting point, as the mapping feature is in place. It would be good if this could be configured for both inbound data and outbound.