Have you ever added a new asset using an Asset Template, only to realize you still need to manually attach all of the same PM templates every time?
For organizations managing hundreds—or even thousands—of identical assets, this quickly becomes one of the most repetitive and error-prone parts of setting up preventive maintenance in Limble.
Asset Templates already do an excellent job standardizing asset data and structure. But when it comes to deploying maintenance strategies, we still have to manually apply PM templates asset by asset.
I'm curious how other teams using Asset Templates are handling this today and whether others would find value in the ability to
