Services
The work spans from field inspection and measurement to advanced analysis and physics-based modelling – and back again via verification in operation. It is the chain as a whole that creates value, not individual parts of it.
Technical investigations and system analysis
Root cause identification of operational disturbances and performance problems. Based on inspection, measurement and reconstruction of real system behaviour.
Dynamic and model-based analysis
Physics-based models, transient analysis and scenario comparisons. Parameter studies, sensitivity analysis and what-if analysis for technical decisions.
Thermohydraulic process analysis
Analysis of cooling systems, heat systems, pumps, valves and pipework. Pressure drop, flow distribution, transient processes, operational cases and disturbances.
Resilience and preparedness analysis
Technical support for assessment of critical infrastructure, consequence analysis at disturbances and system robustness under varying load conditions.
Technical training and communication
Knowledge transfer via simplified models, simulators and documentation adapted to the recipient. Raises internal competence and reduces dependence on external support.
Prototype tools and analysis templates
Jupyter notebooks, calculation templates and visualisation tools that the customer can reuse. Concrete demonstration of the model-based working method.
Model fidelity – the right level for the right question
Not all analysis needs to be complex. The same question can be developed step-by-step from a simple web model to advanced thermohydraulic analysis without losing structure or comparability.
Interpretation
Most technical questions should begin at level 1 or 2 to quickly establish reasonable assumptions, bound the problem and identify which parts truly justify higher model fidelity. Escalation to level 4 or 5 should be driven by decision consequence, training realism, safety requirements or regulatory weight.
The CDS-100 demonstrator is an example of level 1 in practice. Open the demonstrator →
When does this fit?
- When a system behaves unexpectedly and the underlying cause is unclear
- When existing documentation is incomplete or outdated
- When changes require consequence assessment and robustness analysis
- When decisions require clear assumptions and traceable evidence
- When the organisation needs to improve its technical understanding of a system
Start an assignment
Briefly describe the system and the problem – and what type of deliverable is needed. Response with a proposed approach normally within 1–2 business days.