Maritime Science On Life

AURA

Advanced Unified Risk Analysis

0:00 / 0:00
01

Opening view

AURA

Project animation

Begin with one question: what could go wrong?

AURA: following a cooling failure through seven risk methods

A risk study becomes useful when its assumptions, event definitions and evidence can be followed. AURA brings several analytical views into one workspace. This illustrated example starts with a simple physical question: what happens when a heat-producing unit loses the cooling flow it needs?

Start with the function, not the score

Consider an illustrative cooling arrangement with a main pump and a standby pump. Either pump can provide the required cooling duty on its own. During normal operation the main pump supplies flow; the standby pump is available if that supply is lost. The function being protected is continued cooling, rather than the operation of one particular piece of equipment. This distinction matters: a stopped main pump is a component failure, but it does not necessarily mean that the overall cooling function has failed.

The example therefore separates two outcomes after main-pump loss. If the standby pump starts and restores the required flow, cooling is available again. If the standby pump also fails to provide flow, cooling is unavailable within the stated model. Heating is a possible consequence only while heat input continues. These statements define a bounded teaching case. They do not establish actual pump capacity, transfer time, temperature response or the behaviour of an installed system.

Şekil 1. Korunan işlev soğutmadır. Ana pompanın kaybından sonra yedek akışın geri gelmesi ile iki yolun da kullanılamaması farklı sonuçlardır.Figure 1. Cooling is the protected function. After main-pump loss, restoring standby flow and losing both supply paths are distinct outcomes.
Figure 1. Cooling is the protected function. After main-pump loss, restoring standby flow and losing both supply paths are distinct outcomes.

Turn one problem into several precise questions

AURA presents HAZOP, FMEA, LOPA, FTA, ETA, PSA and BowTie as different ways to interrogate a study. Their value is not that seven methods produce seven independent confirmations. Each method organises a different question, and the answer must retain its relationship to the underlying scenario. A cause, a failure mode, a missing function and a consequence should not become interchangeable just because they appear on the same diagram.

HAZOP asks how a process can depart from its intended condition. In this case, main-pump loss is a cause; no flow in the main branch is the deviation; standby flow is then needed. FMEA asks what a component can fail to do and how that failure propagates. The illustrative standby-pump record follows shaft seizure through failure to start and absent standby flow to an unavailable standby path. Actual-flow monitoring is recorded as a control; a start test is a proposed action. These records do not establish that either has been verified in service.

Use the fault tree to expose the combination

The fault-tree question is deliberately narrow: which combination makes cooling unavailable? With either pump assumed sufficient, the two required conditions are main-pump loss and standby-pump failure. The top event is connected through an AND relationship. Main-pump loss alone is not enough; neither is an unavailable standby pump while the main pump continues to meet the duty. Naming both conditions makes the redundancy assumption visible instead of leaving it hidden in the word “backup”.

This is a logical statement within the example, not a numerical reliability result. Shared electrical supply, a blocked common suction, maintenance configuration and response delays would require additional modelling if relevant to an actual installation. Drawing two pump branches does not establish that their failures are independent. A reviewer should be able to challenge the boundary before anyone attaches a frequency or probability to the top event.

Read the event tree from the initiating event

The event-tree view begins after main-pump loss has been given. It asks whether standby flow is restored and follows the resulting paths. The successful branch describes restoration of a positive function; the failed branch describes failure to restore it. This is a different reading direction from the fault tree even though both views reference the same cooling arrangement. The starting condition must stay visible, otherwise a conditional branch can easily be mistaken for an unconditional system result.

AURA’s linked records help keep those identities aligned. A reference to the fault-tree event does not create another independent contribution to risk. Likewise, a branch labelled “restored” is not proof that a transfer has occurred quickly enough to prevent damage. Timing, capacity and acceptable operating limits remain questions for the study’s supporting evidence. The diagram makes a question inspectable; it does not answer every engineering question by itself.

Separate prevention, recovery and consequence control

BowTie places the cooling-loss event between threats and consequences. In this example, each pump-related threat path retains the condition that the companion pump is unavailable. That qualification prevents the picture from quietly contradicting the fault tree. The hazard is associated with the heat load, while loss of cooling is the central event. Continued heating is a possible downstream consequence if the heat source remains active.

A standby supply can help preserve or restore cooling. Cutting heat input or a high-temperature shutdown instead addresses the consequence when cooling is not available. These measures should not be described as performing the same function. In the LOPA view, high-temperature shutdown is a candidate protection measure only. Its eligibility, effectiveness and independence have not been assessed, so the demonstration gives it no independent-protection-layer credit and reports no calculated risk reduction.

Şekil 2. Akışı geri getirmek ve ısı girdisini kesmek farklı işlevlerdir. Aday durdurmaya bu örnekte bağımsız koruma katmanı kredisi verilmez.Figure 2. Restoring flow and removing heat input perform different functions. The candidate shutdown receives no independent-protection-layer credit in this example.
Figure 2. Restoring flow and removing heat input perform different functions. The candidate shutdown receives no independent-protection-layer credit in this example.

Preserve uncertainty when connecting the study

The PSA view follows selected qualitative paths, including restored standby cooling with or without temperature monitoring and a no-flow path followed by protective shutdown of heat input. Some branches are deliberately omitted. The purpose is to show how selected event and function records can be connected, not to claim that all possible outcomes have been enumerated or that a complete probabilistic model has been solved.

A useful review asks what changes when a shared assumption changes. If the standby pump cannot meet full duty, the original function definition needs revision. If both pumps share a vulnerable supply, the cause model needs another look. If shutdown is only proposed, a report should preserve that status. Connections between methods are valuable when they carry those qualifications forward, rather than making an incomplete record appear settled simply because it is reused.

From a diagram to a reviewable work product

The intended work product is more than a picture. It includes a defined system boundary, named events and functions, method-specific records, links between those records, and actions that can be checked. A proposed standby-chain test, for example, should remain traceable to the failure it is meant to investigate. Reporting can then bring the scenario, assumptions and open questions together so another reviewer can understand why a branch or barrier appears.

In a review meeting, the physical arrangement can be read first, followed by a comparison of event names across methods. If one record says “main-pump loss” and another says “cooling loss”, the difference needs an explanation: they are not the same event. The next step is to identify proposed tests and unassessed conditions. This sequence puts study consistency ahead of the diagram’s appearance and keeps missing evidence visible.

AURA’s current foundation includes multi-method workspaces, calculation and visual reporting components, together with study, experiment and learning surfaces. The film is an illustrative, authored explanation using synthetic study content. It is not a physical cooling simulation or evidence of field reliability. The next meaningful step for an engineering application would be to replace illustrative assumptions with appropriate system evidence and complete the outstanding reviews. The software helps structure that work; confidence still depends on the quality and scope of the evidence.

AURA özgün arayüzünde, sentetik soğutma çalışmasının yöntem kayıtlarını bağlayan çalışma haritası.The native AURA study map linking method records in a synthetic cooling study.
The native AURA study map brings method records and links together in a synthetic “Cooling Water Reliability” example. This separate interface example is not a live execution of the two-pump illustration above or field evidence. The interface is in English.

Select the image to open it at full size.

Original Work Record
Work
AURA: following a cooling failure through seven risk methods
Author
yönetici
Recorded (UTC)
2026-11-15T04:13:54.246Z
Version
11
SHA-256
04900e49b910509f595a80debe0c179f8e2ef1348dc8fef7f38166bcdebc5ff8

Credit the author and source when quoting or using this work.

Image records in this work

Kullanıcıya ait proje görsel sunumu · aura-optical.svg

Author
yönetici
Recorded (UTC)
2026-10-18T22:46:27.085Z
Version
1
SHA-256
61bffc67876433bc9ced1bddcc25fd92d1f478eb2d1d1183dfe74aee36da770a

Kullanıcıya ait proje görsel sunumu · aura-functions.tr.svg

Author
yönetici
Recorded (UTC)
2026-10-18T22:46:11.807Z
Version
1
SHA-256
073ea7ce1cc4a1b0d097ab8936a8dda7bc072c1368779fb599e37af5c771ed87

Kullanıcıya ait proje görsel sunumu · aura-functions.en.svg

Author
yönetici
Recorded (UTC)
2026-10-18T22:46:11.172Z
Version
1
SHA-256
993e4bfff7fb21b46ae8a8845261175c3b55e8a61b17b4ed6f231e252fd33bee

Kullanıcıya ait proje görsel sunumu · aura-barriers.tr.svg

Author
yönetici
Recorded (UTC)
2026-10-18T22:46:10.810Z
Version
1
SHA-256
adbd09475e688c3f69a8c3ea9eb7b6f4c0426e1f3b9c3ea3156cd7fa253d9eb7

Kullanıcıya ait proje görsel sunumu · aura-barriers.en.svg

Author
yönetici
Recorded (UTC)
2026-10-18T22:46:09.903Z
Version
1
SHA-256
e744d6439223b32dc161c89bf287428d230b1b78523b3e07529bc306f1d0a1f4

Özgün proje sunumu ve doğrulanmış ekran kaydı · aura-study-map.webp

Author
yönetici
Recorded (UTC)
2026-10-18T22:45:35.136Z
Version
1
SHA-256
1da7cce947a5071fa4ffffb5b26b61db77cd37e5dd482dd0c10c0e9c5a825b26

Özgün proje sunumu ve doğrulanmış ekran kaydı · aura-event-tree.webp

Author
yönetici
Recorded (UTC)
2026-10-18T22:45:51.935Z
Version
1
SHA-256
7a11982443fb87e23e491bd6faf313ca42e7e6c2a4afd8adb7be0b550345c78c

Özgün proje sunumu ve doğrulanmış ekran kaydı · aura-fmea-detail.webp

Author
yönetici
Recorded (UTC)
2026-10-18T22:45:49.151Z
Version
1
SHA-256
0c141cdb0858bf34879fe347f18f3c5f61ed2aed45f043ca664edb9807f8007a

Özgün proje sunumu ve doğrulanmış ekran kaydı · aura-linked-methods.webp

Author
yönetici
Recorded (UTC)
2026-10-18T22:45:49.848Z
Version
1
SHA-256
b47af21b4401fe877abc8a8477e647315b1b4da976d24851ee0b772fe904af4c

Özgün proje sunumu ve doğrulanmış ekran kaydı · aura-study-map.webp

Author
yönetici
Recorded (UTC)
2026-10-18T22:45:47.293Z
Version
1
SHA-256
8aad19e647a2b02f148547cd48f91d187d35b5bffe107ada38323a95e3a76570

Özgün proje sunumu ve doğrulanmış ekran kaydı · aura-workspace.webp

Author
yönetici
Recorded (UTC)
2026-10-18T22:45:47.088Z
Version
1
SHA-256
ea16d9c42daf755db6e194d7c3898d200e0d65fd804e6967998146c3897fa1e9

Özgün proje sunumu ve doğrulanmış ekran kaydı · aura-event-tree.webp

Author
yönetici
Recorded (UTC)
2026-10-18T22:45:38.669Z
Version
1
SHA-256
8434ff51502df972b8d151b608482ab5594a263f0704b68746763d3d49f42c3c

Özgün proje sunumu ve doğrulanmış ekran kaydı · aura-fmea-detail.webp

Author
yönetici
Recorded (UTC)
2026-10-18T22:45:36.059Z
Version
1
SHA-256
86484624443a81cde9882af2e15df47aabfcb609be6c6e25552be965e0d424a8

Özgün proje sunumu ve doğrulanmış ekran kaydı · aura-linked-methods.webp

Author
yönetici
Recorded (UTC)
2026-10-18T22:45:36.673Z
Version
1
SHA-256
b59dae3844c8aae010adb5a447913886998e441d123bf5e2860eb81bd95cd435

Özgün proje sunumu ve doğrulanmış ekran kaydı · aura-workspace.webp

Author
yönetici
Recorded (UTC)
2026-10-18T22:45:35.064Z
Version
1
SHA-256
abf011fffdba7d16d5ca3df28c5a68f41c2f876211943b14d278c709012d623a

Kullanıcıya ait proje görsel sunumu · aura-original.svg

Author
yönetici
Recorded (UTC)
2026-10-18T22:46:18.326Z
Version
1
SHA-256
4e33a9e77041bd43bc222878b39926b1ca0454cdcc116e20da77dc8f9b4b809b

Kullanıcıya ait proje görsel sunumu · aura-transparent.svg

Author
yönetici
Recorded (UTC)
2026-10-18T22:46:19.831Z
Version
1
SHA-256
6cc842f9558b8bd4f7ff3398fea7b1d2cf942ad3a75a206ba386ad5482d1830d

Özgün proje sunumu ve doğrulanmış ekran kaydı · aura.png

Author
yönetici
Recorded (UTC)
2026-10-18T22:46:05.153Z
Version
1
SHA-256
e21c4ac155f2d27c10c3af5fa9187a4f3c0f299e7febe229400f27fb177461d7

Özgün proje sunumu ve doğrulanmış ekran kaydı · aura.webp

Author
yönetici
Recorded (UTC)
2026-10-18T22:46:04.905Z
Version
1
SHA-256
ce94b6f9fc15de47626638af2ca117aef24a55ce1422da9bfb26a703fb53ee2e

Edited native-view sequence · illustrative data