Simulation represents process behaviour through a model and a set of assumptions. It enables design or operating scenarios to be evaluated and shows how system conditions and constraints influence the results.
A model's complexity should reflect the question it is intended to answer. Its development requires input data, reference conditions and validation criteria to be identified.
Results are interpreted within the study's range and assumptions. Documenting these conditions supports comparison of alternatives and updates to the analysis as information changes.
The scope is defined according to asset condition, project stage and available information.
The system scope is defined and information reviewed to build a consistent representation. Comparison with data or references enables its usefulness to be assessed.
Balances enable the comparison of configurations and representative loading conditions. The study connects properties, equipment and utilities, with documented assumptions about the behaviour of each part of the process.
Where behaviour over time matters, the model incorporates system responses and interactions. Its scope and validation must be appropriate to the intended assessment, without replacing design verification.
Deliverables are agreed when the service is defined. The bases used, results and outstanding checks are documented so that the information can carry through to the next stage.
An initial review confirms what information is available and what needs to be completed. To prepare for that discussion, it is useful to have:
Explore the services that complement this scope.