Standard Activities are a critical aspect of any asset management system and serve a very useful purpose.
Firstly, they can be used to define the preventative maintenance requirements for an asset based on user-defined triggering mechanisms that may be calendar and/or usage based.
Secondly, they can be used to define the action required to address known breakdown/corrective scenarios, thus serving as a template for such activities.
For either use, they serve as job templates for subsequent job creation and as such include relevant information including checklist, material and resource requirements, instructions and reference to external documents via a library reference.
One very important consideration when creating standard activities for an asset is to determine whether the asset is unique within your asset register or whether it is one of several that are the same.
If the former applies, then simply navigate to the asset and invoke the standard activity creation form as described in the next section.
If the latter applies, then reference to a Generic Asset should be used so that a single standard activity can be applied to multiple like assets, thus reducing the data definition and ongoing data maintenance workload.
By using a generic approach, when assets are created from a generic one, the standard activities are automatically linked to the new asset.