Dependency

Dependencies: Driving Context-Aware Guidance

Dependencies are critical data points associated with assets, scanned QR codes, or information collected through real-time observations. Their primary function is to filter and display the most relevant tasks, steps, step instructions, and resources based on the specific context of the machine or the current situation.

How Dependencies Filter Content

By utilizing dependencies, you ensure that a technician only sees information that is applicable to the task at hand:

• Task Visibility: You can set dependencies at the task level so they only appear under specific conditions. For example, a maintenance task might only show up if an asset has a specific option installed.
• Step Logic: Individual steps within a task can depend on asset data or information collected earlier in the process, such as specific symptoms or sensor readings.
• Targeted Instructions: Step instructions often use dependencies to provide direct links to the exact section of a manual that corresponds to that specific asset model.
• Asset Data Points: These variables often include the machine model, configuration details, or optional add-ons.

Configuration and Logic

Setting up dependencies allows authors to create complex, non-linear diagnostic paths:

• Accessing Configuration: To manage these rules, navigate to the Configuration menu. You will typically find pre-existing dependencies in a dropdown menu based on previous usage or you can create new variables manually.
• Expertise Variables: In InSkill, "Expertise" refers to the variables used within tasks. When adding a dependency, you can incorporate one or more of these variables.
• Asset Integration: If a variable is associated with an "asset," it will appear automatically as a selectable item.
• Advanced Logic Trees: For sophisticated workflows, you can create groups of dependencies and utilize AND and OR logic functions to define exactly when content should be associated.