Pro
12 min

CCST 24 — Safety Category Levels

ccstsafetydual-channelcategory3PLd

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

CCST 24 — Safety Category Levels scenario preview

Briefing

Write a dual-channel E-stop circuit: two NC contacts ESTOP_CH1 and ESTOP_CH2 must BOTH be open to drop the output (Category 3 / PLd pattern). A discrepancy latch CHANNEL_FAULT fires if one is open but not the other.

Objectives

  • SAFE_OUTPUT requires both channels to be de-energised to shut down
  • CHANNEL_FAULT latches if CH1 ≠ CH2 for more than one scan
  • Normal run: SAFE_OUTPUT := NOT ESTOP_CH1 AND NOT ESTOP_CH2 (both NC: both TRUE at rest means safe)

Hints

  • Safe when ESTOP_CH1 AND ESTOP_CH2 are both TRUE (NC contacts at rest)
  • CHANNEL_FAULT := ESTOP_CH1 XOR ESTOP_CH2 (simplified — real systems use timers)

I/O Table

Inputs

ESTOP_CH1

E-stop channel 1 (NC, TRUE=safe)

BOOL · %I0.0

ESTOP_CH2

E-stop channel 2 (NC, TRUE=safe)

BOOL · %I0.1

Outputs

SAFE_OUTPUT

Safe output

BOOL · %Q0.0

CHANNEL_FAULT

Channel discrepancy fault

BOOL · %Q0.1

Your program will be tested against:

All test cases run automatically when you submit. Assertions are hidden until you pass.

  1. #1Safe when both NC contacts closed

    Safe when both NC contacts closed

  2. #2Both trip drops output

    Both trip drops output

  3. #3One channel discrepancy flags fault

    One channel discrepancy flags fault

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

Job-readiness and assessment field guide

CCST practical 024 alarm-response assessment: readiness checklist

Direct answer

The candidate can identify the initiating condition, separate alarm state from process cause, select a discriminating test and prove normal return.

Written for controls-technician candidates diagnosing an abnormal process indication without treating acknowledgement as repair.

a supervised controls-technician practical assessment bench with representative instruments, motor controls and retained diagnostic evidence while studying alarm evidence, first-out condition, acknowledgement and cause-based recovery
System map / 02

NODE 01observable

Role scope

Process variable, alarm threshold and priority, quality, delay, first-out record, acknowledgement, shelving boundary, trip relationship and reset permissive.

NODE 02observable

Skills map

Physical abnormal condition through instrument, controller evaluation, alarm server, operator display, response action and independent process recovery.

NODE 03observable

Core exercise

A controlled threshold crossing creates one timely alarm with correct identity, quality, priority and return-to-normal evidence.

NODE 04observable

Stretch case

Bad quality, chatter, multiple alarms, delayed scan, stale timestamp, acknowledgement while active, suppressed alarm, controller restart and recurrent cause.

NODE 05observable

Troubleshooting

A process, instrument, quality, threshold, logic, timestamp, alarm-state, operator-action or recovery mismatch.

NODE 06observable

Portfolio evidence

The response aligned with approved alarm philosophy, operating procedure and independent protection review.

Answer surface / 07

What is the difference between acknowledging and clearing an alarm?

Acknowledgement records operator awareness; clearing or return to normal means the detected condition is no longer active according to its configured rules.

Why preserve the first-out alarm?

The earliest credible deviation can identify the initiating boundary while later alarms may be downstream consequences of the same event.