Asset data becomes useful when engineers can connect it to a question they need to investigate. A changing trend, an unfamiliar operating pattern or a recurring concern can provide a practical starting point. We recommend bringing relevant process history, asset context and engineering judgement together in a reviewable workflow, with clear boundaries between observations, working hypotheses and decisions about action.
Frame the engineering question.
Begin with an asset and a question that engineering teams recognise. What changed? Under which operating conditions did it occur? What would the team need to compare? Define the investigation scope with the people responsible for the equipment, including the boundaries of their available information.
Separate the observed condition from the explanation being considered. Record what the team knows, what remains uncertain and which evidence could help. This provides a practical structure for reviewing historian trends, operator observations and maintenance information without presenting an early interpretation as an established conclusion.
Bring the history into context.
Identify the relevant signals, equipment relationships and operating periods for comparison. Ask whether engineers can see the source, timing and units of each value. Include contextual information the team considers necessary, such as operating mode, recorded events or recent changes that may influence their interpretation.
Use an agreed view to assemble the evidence for discussion. A historian or AVEVA PI application can form part of that scope where appropriate. Make gaps and assumptions visible, and give engineers a way to add observations that explain what the available data cannot resolve.
Make the review repeatable.
Define how findings move from investigation into an agreed decision. Who reviews the evidence? Who can request further checks? Who owns the next action? Keep responsibilities aligned with the organisation’s existing operating procedures, and record the reasoning that connects an observation to a proposed response.
Start with a focused application and review it with the intended users. Ask whether the information supports a clearer engineering discussion and what remains difficult to investigate. Use that feedback to refine asset context, integration priorities and the investigation workflow before extending it more widely.
Let the question guide the data, and the evidence guide the discussion.