When Planning and Implementing Asset Rules in ReadyWorks, teams should focus on establishing conditional states that trigger automated asset updates, notifications, and other critical actions based on asset attributes. Asset Rules allow for sophisticated orchestration across asset lifecycles, supporting seamless automation, effective management, and proactive handling of asset-related events.
Key Considerations for Planning and Implementing Asset Rules:
- Define Use Cases for Asset Rules:
• Identify Common Scenarios for Automation: Determine key asset management scenarios that benefit from automation, such as updating asset statuses, triggering notifications on asset condition changes, or sending alerts when thresholds are met (e.g., firmware updates, low stock levels). Understanding these use cases ensures rules align with the organization’s asset management needs.
• Set Specific Triggers Based on Asset Types: Different asset types may require unique triggers. For example, IT assets might trigger notifications for compliance updates, while facility equipment may have maintenance or operational triggers. Defining asset-specific rules tailors automation to asset type requirements and optimizes resource usage.
- Establish Rule Conditions and Cascading Options:
• Determine Conditions for Each Rule: Define conditions for each Asset Rule based on asset attributes, such as status, location, or operating system version. For example, set a rule to update the “Device Status” to “Offline” when an asset’s “MZ Field” is marked as “Screen 200.”
• Enable or Disable Cascading: Cascading allows multiple rules to run sequentially if conditions in one rule trigger conditions in another. This can support complex workflows where, for instance, a change in device status triggers additional updates or notifications. For performance optimization, only enable cascading when necessary to avoid processing delays.
• Configure Persistent Options for Conditions: Decide if the rule should process when all conditions are met at once or if pre-existing conditions can activate it. For example, setting Persistent = Yes ensures that even if one condition was pre-set on the asset, the rule still triggers when the remaining conditions are met in the update. Persistent settings can support more comprehensive, context-sensitive rules.
- Define Triggered Actions within Asset Rules:
• Configure Asset Attribute Updates: Set rules to update asset attributes automatically. For example, when an asset reaches a specific status or condition, the rule could change its “Device Status” to “Decommissioned” or mark it for maintenance. Such updates help maintain accurate, real-time asset statuses without manual intervention.
- Develop and Document an Asset Rules Configuration Guide:
• Consolidate Rules into an Instance Specific Reference Guide: Document each Asset Rule, including conditions, actions, asset types, cascading and persistence settings. A comprehensive Configuration Guide serves as a single source of truth, aiding troubleshooting, audits, and future updates.
• Include Use Case Context and Expected Outcomes: Document use cases and expected results for each rule, such as the actions taken when a device enters a specific status. This context helps stakeholders understand the purpose and benefits of each rule, supporting alignment across teams.
• Specify Dependencies and Impact on Workflows: If certain rules depend on other workflows or system attributes, note these dependencies in the Configuration Guide. For example, a rule that assigns assets to a Wave may depend on predefined Waves in the workflow system, and documenting this ensures consistency.
- Ensure Knowledge Transfer and Ongoing Documentation:
• Document Changes and Updates to Rules: Maintain a change log for rule updates, including modifications to conditions, actions, or persistence settings. A structured change log supports continuity, aiding future troubleshooting and adjustments.
By establishing a structured approach to configuring, testing, documenting, and maintaining asset rules, the Project Manager can ensure that ReadyWorks automates critical asset management functions effectively. Asset Rules enhance operational efficiency, support proactive management, and maintain consistency across the asset lifecycle, making them a powerful tool in the ReadyWorks deployment.