Pro
5 min
CCST 39 — Change Management (Revision Tracking)
ccstdocumentationrevisionchange-management
Ready to build this?
Sign up free — no credit card required. This scenario requires the Pro plan.
Sign up to play this scenario →Already have an account? Log in
Briefing
A drawing shows the original logic for ALARM_RELAY (FAULT_A OR FAULT_B). A revision adds FAULT_C. Update the rung to match the revised drawing and describe the change.
Objectives
- Update ALARM_RELAY to include FAULT_C
- ALARM_RELAY := FAULT_A OR FAULT_B OR FAULT_C
- Document the change reason in a comment
Hints
- Simply add FAULT_C to the OR expression
- Comment: (* Rev 1.1: Added FAULT_C per ECO-0042 *)
I/O Table
Inputs
FAULT_AFault A
BOOL · %I0.0
FAULT_BFault B
BOOL · %I0.1
FAULT_CFault C (new)
BOOL · %I0.2
Outputs
ALARM_RELAYAlarm relay
BOOL · %Q0.0
Your program will be tested against:
All test cases run automatically when you submit. Assertions are hidden until you pass.
- #1Fault C triggers alarm
Fault C triggers alarm
- #2No alarm when all clear
No alarm when all clear
Related scenarios
Ready to build this?
Sign up free — no credit card required. This scenario requires the Pro plan.
Sign up to play this scenario →Already have an account? Log in