Quite impressive for someone to read an incident report and actually implement the recommendations - so often they sit in a filing cabinet forever.
Quite impressive for someone to read an incident report and actually implement the recommendations - so often they sit in a filing cabinet forever.
That's not really true. There is a saying when it comes to transportation regulations, "Safety regulations are written in blood." That is, nearly all safety regulations are the result of analysis after a tragic accident.
Generally when I write a postmortem there is a long list of modifications that could solve the problem. However they all have different costs, different effectiveness, different specificity and may overlap in different ways. This means that the high-cost, highly-specific modification may not be worth implementing when a lower cost and very broad modification can cover that same class of problems (even if not quite as effectively).
As an example you may have two recommendations:
1. Queue the requests and add many retries so that if a problem occurs in the future the requests are not lost and the problem can be fixed or allowed to resolve itself.
2. Add a second implementation of the process using different technologies and dependencies and fail over to it if the first implementation fails.
If this specific type of request is not very latency sensitive 2 is likely not worth it even though it is an improvement over just doing 1. 2 might be the better solution as well however 1 would greatly mitigate not only the specific request that had a problem this time but all similar requests in the system so 1 is good to do even if 2 is done for the other types of request.
In the end I would say that both are good recommendations however the logical business choice is just to do 1.
https://en.wikipedia.org/wiki/SOLAS_Convention
SOLAS doesn't make a lot of requirements of recreational vessels but in practice you'll have a Digital Selective Calling VHF radio much like SOLAS requires a container ship to have, because either local laws require it or just it was really annoying without it as you can't talk to anybody. DSC has automated Mayday. So it's practical to teach children how to activate it at about the same age you teach them to make a 911/ 112/ whatever phone call. The radio will make Mayday radio calls, automatically giving its location (unless it doesn't know) and its identity, and explaining that there's a problem, but it doesn't know what the problem is. Somebody will come investigate, because SOLAS also made explicit what is obvious to most mariners, that you should always come help people. The ocean will definitely kill us if it gets a chance, so by the Golden Rule we should all pitch in to save others.
https://en.wikipedia.org/wiki/Digital_selective_calling
SOLAS also requires float-release EPIRBS which are beacons that a COSPAS/SARSAT satellite can see from space, and again transmit their identity, so a shore-based emergency response co-ordinator can see e.g. this beacon is registered to a medium sized power yacht named "Example", we don't know what's wrong with it, but its beacon is activated, so either it sank or its in trouble and the beacon was activated manually (or somebody fucked up). The owner's satellite phone doesn't answer, he gives a home number, his wife answered and said he's fishing with two friends, due back this evening.
Update that to 'the interwebs', and we are [still] sadly lacking.
/!totc