Best Practices - Level 2

201: What Are Tasks

  • Keep in mind that expertise is designed for expert know-how that isnt documented in a manual. It is best to convert procedures to a task with multiple steps and in-depth detail. The more detail the better

202: How to create a task

  • Info-only steps are designed for what it states, steps that only show information. If there is a step that requires any type of action, then it should not be a info-only step. Keeping it a solved/not solved step will help teach the system.

203: Creating a task with observations

  • Implementing observations helps technicians as the systems will gather information from the user during sessions to better prepare themselves for a site visit.
  • Create variables in the data dictionary before using them in expertise (Covered in next section). This helps eliminate discrepancies between data dictionary and expertise which ensures the task will run the way the author intended it to.


204: How to Run a Session

  • Running a session through the app is the best way to complete a session. This allows for quick on-site input from the user such as status update or photo input.