Getting startedDeliver your first use case
Deliver your first use case
Give the pilot one operational decision, one accountable owner and one measure of success. An eight-to-twelve-week pilot is a useful planning window when the plant can supply representative data and a reviewer for inspection findings.
Customer guide · Updated 14 November 2026
#The six steps
| Step | Work to complete | Evidence to retain |
|---|---|---|
| 1 · Frame | Ask the decision owner what they do today, when they need the answer, and what happens if it arrives late. | A one-sentence use case, cadence, owner and baseline. |
| 2 · Map | Identify assets, signals, documents and maintenance records. Verify units, timestamps, asset IDs, data gaps and access. | An approved mapping and a list of missing inputs. |
| 3 · Qualify | Select representative operating periods. Agree normal conditions and which fault hypotheses the available signals can distinguish. | A reviewed baseline, exclusions and a field verification method. |
| 4 · Configure | Connect the approved source, map the asset, configure evidence and identify the queue or person receiving a request. | A source-to-screen check and a traceable test request. |
| 5 · Trial | Replay a historical period or simulator case, then observe live operation with the plant team. Review false alerts, missed cases and missing evidence separately. | A labelled trial log with the operator’s judgement and unresolved questions. |
| 6 · Accept | Compare the agreed metric with its baseline. Review exceptions and decide whether to extend, revise or close the pilot. | A signed result with scope, observation count and next owner. |
#Define a measure that survives review
For a fan-inspection pilot, measure the median elapsed time from a qualifying vibration deviation to a planner’s recorded inspection decision. Agree what counts as a deviation and which shifts are covered. Use the same start and end events for the baseline and trial. Report the case count and open cases alongside the median. If the pilot sees no qualifying events, report that and retain the replay results separately.
#When an ERP action is in scope
Name the ERP object, allowed fields, approving role and destination. Trial the action in the approved test environment. Verify the returned ERP identifier at the destination and confirm that a retry cannot create a duplicate. Treat a request as pending until the receiving system acknowledges it.