Start with the decision, not a catalogue of studies.
A brownfield review can quickly expand into a long list of technical questions. Some will be necessary; others may have little bearing on the next decision. Before defining the review team, write down what the owner needs to decide and what would make that decision better informed. A review to understand a constraint is different from a review to select a modification or prepare for a shutdown.
1. What is the operating problem?
Describe the problem in the language of the asset and its operators. What is happening, under which conditions, and with what consequence? Distinguish observations from explanations. A suspected cause is a hypothesis to examine, not a conclusion to put into the brief. The first output should be a shared problem statement that the operational and technical teams recognise.
2. What evidence is available?
Map the information that could help: operating history, drawings, maintenance records, previous studies and the knowledge held by the site team. Record gaps and uncertainty. The initial task may be to establish whether the available information supports a specialist assessment, rather than to request a solution immediately.
3. Which constraints shape the options?
List the conditions that the review must respect. These could include access, operating windows, interfaces with existing equipment, commercial commitments and the owner’s approval process. A technically interesting option is not automatically practical. Bringing constraints into the brief helps the specialists focus their work.
4. Who needs to contribute and review?
Identify the disciplines and experience needed for the question being asked. Clarify the roles of the owner, operator, specialist and any other party whose input is essential. Define who can provide information, who reviews the findings and who has authority to accept the output. Attendance on a project is different from responsibility for its decisions.
5. What will a useful output look like?
Agree the form of the result before the work begins. It may be a ranked set of options, a list of unresolved assumptions, a recommendation for further study or a scoped implementation plan. State the evidence needed and the limits of the review. This gives the client a basis for judging whether the engagement has answered the original question.
Make the brief a working document.
A good brief can be concise. It should connect the problem, decision, evidence, constraints and responsibilities. It will evolve as information improves, but changes should be visible and agreed. The aim is to give specialist expertise a clear purpose and a useful destination.
This perspective is a scoping aid. It is not a project-specific technical assessment.
Discuss an asset performance challenge