Approach
The work follows a coherent method chain – from field analysis and system reconstruction to model-based analysis, concrete actions and verification in real operation. Each step builds on the previous, with the aim that the solution works in practice, not only in the calculation model.
Assignments are always scoped with regard to confidentiality and conflicts of interest.
How Antranova works
- Understand the system, the problem and the operating conditions.
- Collect and review available data, documents and observations.
- Identify possible root causes and critical dependencies.
- Analyse the interaction between subsystems and operating sequences.
- Assess improvement alternatives and technical consequences.
- Deliver clear decision support with conclusions and recommendations.
The goal is not to produce more documentation than necessary. The goal is to reduce uncertainty and give the customer technical support they can act on.
The method chain
Not all steps are always necessary – the assignment defines which phases are relevant.
Field analysis
Inspection, measurement and understanding of the system's real behaviour. Thermography, flow measurement, pressure and temperature – depending on what the system requires.
System reconstruction
Recreation of the system's structure and function based on observations, measurements and images. Does not require complete documentation – it is often missing or outdated.
Analysis and modelling
Physics-based models for analysing dynamics and causal relationships. Python, OpenModelica or more advanced thermohydraulic tools – chosen based on the requirements of the question.
Action development
Identification of solutions that are technically correct and practically implementable – taking the plant's actual conditions into account.
Implementation
Support or leadership during implementation of changes. Technical grounding in the full chain aims to reduce the risk that something is lost in execution.
Verification and start-up
Confirmation of function in real operation. The system is measured and compared to expected behaviour before the assignment is closed out.
Training
Knowledge transfer to the organisation via simplified models, simulators and documentation. Raises internal competence and reduces dependence on external support.
Principles
- System understanding before model: a system must be understood in its real context before it is modelled. The model is a tool – not an end in itself.
- Traceability: inputs, assumptions, method and versions are documented so that results can be checked and repeated.
- Verification in operation: solutions are confirmed to work in the facility they are intended for – not only on paper.
- Appropriate detail level: not all analysis needs to be complex. The right level of detail for the question saves time and increases credibility.
- Concrete actions: the end result must be implementable – not just a report with conclusions.
Tool chain
Field tools
- Multimeter – electrical and operational status
- Thermography – temperature and energy flows
- Laser distance meter – geometry and layout
- Inspection camera – internal verification
- Flow measurement – critical system parameter
- Pressure and temperature measurement
Analysis tools
- Level 1 – HTML / JavaScript for browser-native demo studies and rapid concept exploration
- Level 2 – Python / NumPy / SciPy / Jupyter for quantitative studies, parameter sweeps and sensitivity analysis
- Level 3 – OpenModelica / Modelica for multi-domain modelling, control integration and system studies
- Level 4 – simulator platforms such as JADE, SimExec, 3KeyMaster and Orchid for real-time execution, training and scenario verification
- Level 5 – RELAP5-3D, TRACE and CATHARE for safety-critical and regulator-sensitive thermohydraulic analysis
Software names are given as references to experience. The names belong to their respective rights holders. Delivery within an assignment requires that the customer provides a license, or that another tool is used.
Frequently asked questions
What information is needed to start?
Ideally: a description of the system, the problem or question, available measurement data and desired deliverable format. Incomplete documentation is normal – the field analysis is precisely there to supplement it.
Can you work in a plant without complete documentation?
Yes. System reconstruction based on observations, measurements and images is a core competence – not an exception.
Can you work under confidentiality?
Yes. Details are anonymised as needed and the deliverable is structured so that sensitive information is separated from general methodology.
What do I get at the end?
Normally: concrete action proposals, traceable documentation (report/appendices), and if relevant, a reproducible analysis package. For training assignments, simplified material or a simulator is also included.