Using issues for maintenance requests (with assets)

Thanks for the great feedback @Andrew-K 

The ability to link and Asset to and Issue is being explored and possibly released towards the end of the year. We have also been spending a lot of time looking at expanding the workflow for issue categories, like closing and Issue when all Actions or Inspections are completed. 

These features are being considered, and we are glad to hear they would be useful.

Thanks again for the suggestions.

Hi @Matt Lewandowski, are there any updates regarding these features? Still part of the roadmap?

@Andrew-K and @Mattia T. 

We’re building a feature set for planned asset maintenance.

The idea is the concept of an admin creating a maintenance program which could consist of one or many plans within it.

Either sensor data, if your equipment has telematics, or manual inspection data will trigger an action when a threshold is met, ie: every 10,000km, or 500 engine hours.

Issues<> Assets is still on the roadmap, but we’ve not got to it yet. 

Happy to discuss further with you and get your feedback if you’d like to hop on a zoom call. 

Cheers,

Duncan 

We are still limited in our usage of the Issues feature and so far are only using Assets for forklifts at a few sites.  However, this is because we have a full blown CMMS that we’ve used for years, and SafetyCulture will not replace it.  We have to figure out how they can complement each other.  One site is using Issues with categories for “Maintenance Request” and “Property Damage.” The maintenance team then determines if that reported issue is worthy of putting into our maintenance system CMMS or not.  They preferred non-maintenance employees to not put on the fly repair/breakdown work orders directly in that system.  Other sites, however, have trained all employees to put it straight in the CMMS.

Is there an update on when/if this will become a thing