Getting startedFirst use case worksheet
First use case worksheet
Copy this worksheet into the project record and complete it with the person who owns the decision. The examples illustrate a fan inspection pilot. Replace them with site-approved values before commissioning.
Customer guide · Updated 14 November 2026
#Worksheet
| Field | Example entry or question to resolve |
|---|---|
| Decision and owner | Should the planner request a vibration inspection before the next shutdown? Record the planner, backup and decision deadline. |
| Asset scope | Record the plant, area, equipment ID and bearing position. Cross-check the historian tag against the drawing and ERP asset record. |
| Evidence and context | List the vibration value and unit, source timestamp, sensor quality, fan speed, load and current operating mode. Name the owner of each input. |
| Decision rule | Document the approved comparison period and what warrants a review. Record how a technician can confirm or challenge the suspected cause. |
| User and destination | Record who sees the finding, who may request an inspection and which queue receives it. Name any external system where a separate write is authorised. |
| Exception and recovery | If a reading is stale, identify who checks the source. If a request fails, state who checks its destination before retrying. |
| Test and acceptance | Define the baseline, start and end events, trial dates and reviewer. Keep one labelled replay, one traceable request and any field-verified outcomes. |
| Support and handover | Record the configuration revision, asset owner, approved support channel, review date and decision on expansion. |
#Sketch the solution before connecting systems
Draw the source, asset mapping, user view, decision owner and destination on one sheet. Mark which connections read data and which can write. At each handoff, record the identifier that lets a reviewer follow the same machine or request into the next system.
#Commissioning review
Ask the operator to find the asset, the engineer to reproduce a finding and the planner to locate the request. Have the administrator demonstrate the relevant access boundary. Keep unresolved items with a named owner and a retest date.