What is a 'proof-test' and why is it important for NANTeL?

What is a 'proof-test' and why is it important for NANTeL?

• A. A casual demonstration to show the system looks correct.
• B. A formal verification that the system would respond correctly to design-basis events.
• C. A random software update audit.
• D. An operator walkthrough of the UI.

Answer: (B)

A proof-test is a formal verification that the protection system would respond correctly to design-basis events. It’s not just a quick check; it uses defined test conditions that simulate the events the plant must be ready to handle and then verifies that the system trips or accepts as required, with alarms and interlocks behaving as specified. In NANTeL, this kind of testing provides objective, documented evidence that the protection logic and hardware will perform correctly under those critical scenarios, even after changes or maintenance. It helps ensure safety and regulatory compliance by catching misconfigurations, software errors, or hardware faults before an actual event occurs. A casual demonstration won’t prove the necessary correct responses to design-basis events, a random software update audit checks updates rather than protection behavior under DBEs, and an operator UI walkthrough focuses on appearance or operation of the interface rather than the protective function.

A proof-test is a formal verification that the protection system would respond correctly to design-basis events. It’s not just a quick check; it uses defined test conditions that simulate the events the plant must be ready to handle and then verifies that the system trips or accepts as required, with alarms and interlocks behaving as specified. In NANTeL, this kind of testing provides objective, documented evidence that the protection logic and hardware will perform correctly under those critical scenarios, even after changes or maintenance. It helps ensure safety and regulatory compliance by catching misconfigurations, software errors, or hardware faults before an actual event occurs. A casual demonstration won’t prove the necessary correct responses to design-basis events, a random software update audit checks updates rather than protection behavior under DBEs, and an operator UI walkthrough focuses on appearance or operation of the interface rather than the protective function.