"The loss of the program can be caused by many ways: competent engineer who missed out some thing by error, earth fault which can corrupt the data, loop card failed, using the internal reset button while the memory is open, and many others depending upon the makes..."
All the above will be noticed either by fault warning or by proper testing after work being carried out.
I can see where you are coming from, but I think you are going too far.
In this case had the weekly tests actually been carried out?
Regards
John.
Yes the incident happened between two successful weekly bell tests, and we still doing our weekly bell test too on behalf of the customer, the investigation is now going on by checking the 'Event Log' to find out the last minutes the 'Device Log' was in the panel and what caused the program to be lost. Also, I agree it could be the last engineer's error ... and in that case he should be hanged up if you want...:O. But
My concern is more about, BLOCKING OFF the way to any sort of mistakes that could cause such incident; the program was lost while the system still displaying 'Systems Healthy', it is just further future measures, and it is not really IMPOSSIBLE to find out a cost affective way to double secure the program from being lost without any warning message left.

I am aiming to set a warning message in the panel saying i.e. 'Panel Healthy, Device Log Required' with a beeping, in which the message would not be cleared out without uploading back the 'Device Log' I do not think I am going that far...if it is for safety reason
Thanks