Create a stack that includes data about your assets, including data such as tag numbers, process areas, maintenance details and intervals, manufacturer, or warranty information. Additionally, create linked fields to other stacks such as asset-specific documentation that could be linked from a documentation stack. This is particularly helpful if several assets share some of the same documents, as a linked field will streamline the document referencing and version control over time.
It is often helpful to generate asset-specific tasks, especially for specific maintenance periods. Using automations, it is possible to create a recurring asset-specific maintenance task (or set of tasks on varying intervals) that are assigned to an individual or group and may be monitored by a supervisor or management group. Push notifications will inform relevant users of the addition and completion of these tasks.
Use topic-based conversations to have a focused discussion around a single asset, and easily follow-up or review conversation outcomes without need to scroll through unrelated discussion.
Use linked fields to tie assets to specific SOPs, drawings, manuals, or other technical data that is relevant to an asset. All documentation for that asset will be available without creating copies of the documentation for each asset.