When an engine malfunction occurs during a flight, the FMS (Flight Management System) aboard the Boeing 767 or Discovery, doesn't shutdown all engines and systems. But instead it deals with it, allowing the aircraft to continue on its current flight path and altitude.
More importantly, the pilots/astronauts decide on whether to continue the flight or look for a safe landing site and send a May Day signal (such as "Huston we have a problem").
All mission critical systems ( and Trading platforms are critical to us) have to deal with exceptional conditions.
1. An order rejection is an exception (exceptional condition) but not a reason to terminate the process (Strategy). Leaving me with an open position, while before the 'faulty' order, I had a perfectly healthy Stop order.
2. Handling an exception should be finding a safe landing (not crash). A safe landing in this context is to continue. Although the current Stop loss might not be ideal, but it is MUCH better than a killed strategy which left a completely naked order.
If FMS were implemented this way, aircrafts would be falling from the sky every minute.
3. Countless times when this occurred, there was a valid Stop Loss/Trailing Stop in place.
One faulty order, bang, I find myself in a very, very bad position.
Ignoring the exception would have been (am not suggesting this, but would prefer as it is less damaging than the implemented 'non-solution') less painful.
4. Would you, pretty please, provide me with a solution (be it temporary), to deal with this damaging (hard cash wise) situation more efficiently.
One thing that keeps me here, is that you do try and solve your customer's problems. I and most of us do appreciate that. And we also know that even the FMS on Discovery isn't perfect, but it preserves the lives of the astronauts and passengers.
Cheers,
Obi
Comment