What is an acceptance test in the context of RPS/NANTeL, and what does it typically include?

What is an acceptance test in the context of RPS/NANTeL, and what does it typically include?

• A. Relaxed testing after deployment
• B. No tests required if design looks good
• C. Formal demonstration that the system meets design requirements before operation; includes functional tests, fault-condition simulations, and verification of correct trip behavior
• D. Only vendor sign-off is needed

Answer: (C)

Acceptance testing is a formal demonstration, before the system goes into operation, that it meets the defined design requirements and will perform its safety functions as intended. In the RPS/NANTeL context, this means showing through documented procedures that the protection system operates correctly, responds to inputs as specified, and maintains proper protection behavior before it is allowed to run in production. The process typically includes functional tests to verify each function and interlock acts as designed, fault-condition simulations to confirm correct responses under abnormal or degraded conditions, and verification that the trip logic delivers the correct, timely trip behavior when the design criteria are met while avoiding unnecessary trips. This evidence-based check ensures the system is ready for operation and is not just a post-deployment or vendor-signoff activity.

Acceptance testing is a formal demonstration, before the system goes into operation, that it meets the defined design requirements and will perform its safety functions as intended. In the RPS/NANTeL context, this means showing through documented procedures that the protection system operates correctly, responds to inputs as specified, and maintains proper protection behavior before it is allowed to run in production. The process typically includes functional tests to verify each function and interlock acts as designed, fault-condition simulations to confirm correct responses under abnormal or degraded conditions, and verification that the trip logic delivers the correct, timely trip behavior when the design criteria are met while avoiding unnecessary trips. This evidence-based check ensures the system is ready for operation and is not just a post-deployment or vendor-signoff activity.