ISA CCST Level II common mistakes
ISA CCST Level II · Understand the traps and how to avoid them.
When a question describes a transmitter with a 4-20 mA output reading low at the DCS, the candidate immediately blames the DCS input card or the loop wiring and skips checking the calibration record, zero/span trim history, and the reference accuracy of the test standard used at the last bench calibration.
Candidates memorize loop troubleshooting flowcharts and treat calibration as a separate topic. Exam items deliberately blend the two, and the most probable root cause is often a drifted sensor, an incorrect LRV/URV entry, or a calibration performed with an out-of-tolerance standard, not a wiring fault.
What to do instead
For any measurement discrepancy, work the chain in order: process tap and impulse lines, sensor/transmitter, signal loop, input card, then scaling in the control system. Before choosing a hardware fault, ask whether the indicated value is consistent with a calibration error and whether the last calibration used a traceable standard within the required test-accuracy ratio. Practice items that require naming the calibration root cause, not just the wiring root cause.
The candidate calculates allowable calibration tolerance by taking a fixed percentage of span (for example 0.5 percent of span) without combining the reference accuracy, the ambient temperature effect, the static pressure effect, and the test-standard uncertainty, and without checking whether the specification is expressed as percent of span or percent of reading.
Percent-of-span and percent-of-reading look similar in a word problem but give very different tolerances at low readings. Candidates also forget that the test standard must typically be several times more accurate than the device under test, so the standard's own error must be folded into the uncertainty budget.
What to do instead
Write the tolerance as an explicit sum: reference accuracy plus temperature effect plus static pressure effect plus standard uncertainty, each converted to the same units and the same basis (span or reading). State the basis in your scratch work every time. Drill problems where the reading is near 10 percent of span so the percent-of-reading versus percent-of-span distinction changes the answer.
During a five-point calibration check, the candidate treats as-left and as-found data as interchangeable, records only the as-left values, and does not flag that a device found out of tolerance requires documenting the as-found condition before adjustment.
In a plant, technicians often adjust first and record afterward because the goal is to get the loop back in service. Exam items test whether the candidate understands that as-found data is the evidence used to decide whether historical product was affected and whether a recall or impact assessment is needed.
What to do instead
Always record as-found (five points up and down, including hysteresis) before touching zero or span, then record as-left after adjustment. When an item asks what to do with an out-of-tolerance as-found result, the answer includes documenting it and initiating an impact assessment, not simply recalibrating and moving on.
The candidate answers a preventive-maintenance scheduling question by choosing the most thorough option (for example, calibrating every device on a fixed annual interval) rather than the option that matches the documented maintenance strategy, criticality, and manufacturer or site interval basis.
Textbook instinct says more maintenance is better. Exam items reward matching the interval to the documented basis, the device's observed drift history, and its safety or product-quality criticality, and they penalize blanket intervals that ignore criticality ranking.
What to do instead
When an item involves interval or scope, identify the driver first: regulatory requirement, manufacturer recommendation, historical drift, or criticality ranking. Choose the answer that cites that driver. Reject answers that apply a single interval to all devices regardless of service or criticality.
Faced with a control valve that hunts or a positioner that will not settle, the candidate replaces the positioner or the I/P converter in the answer instead of first checking supply air pressure and quality, actuator bench set, stem packing friction, and mechanical linkage or feedback alignment.
Electronics are easy to blame and easy to swap. Most valve hunting in practice traces to air supply, packing friction, or linkage, and the exam expects the candidate to exhaust mechanical and pneumatic causes before condemning the instrument.
What to do instead
Adopt a fixed order for valve problems: air supply pressure and dew point, filter regulator, I/P output, positioner feedback linkage, packing friction and stem travel, then actuator bench set versus spring range. Practice writing that sequence from memory and pick the answer that follows it.
The candidate diagnoses an intermittent or noise-related fault by choosing to replace the transmitter or the cable, rather than first verifying grounding and shielding practice, checking for a ground loop, and confirming the shield is terminated at one end only.
Intermittent faults are uncomfortable, so candidates jump to the component swap that feels decisive. Exam items often hinge on the single-point shield ground rule, separation of signal and power routing, and the difference between a true ground loop and a single-ended shield.
What to do instead
For noise or intermittent analog signals, list the checks in order: shield grounded at one end, signal cable separated from VFD and power feeders, transmitter housing grounding per manufacturer, loop power supply within range, and terminations torqued. Choose the answer that names the specific grounding or routing defect rather than a parts replacement.
On a loop-check item, the candidate selects the step of simulating the transmitter output at the marshalling panel but omits verifying the final element stroke, the DCS graphic and alarm setpoints, and the control system scaling end to end.
Candidates think of loop check as proving the signal gets from field to control room. A complete loop check proves the entire path including the final control element, the operator interface indication, and the configured ranges and alarm limits.
What to do instead
Memorize the loop-check scope as sensor to final element: inject at the sensor or simulate at the transmitter, confirm the input card reading, confirm the HMI value and engineering units, confirm alarm and trip setpoints, then stroke the valve or drive the final element and confirm feedback. When an item lists partial scopes, reject the one that stops at the input card.
During commissioning, the candidate answers a question about a trip or interlock by saying to bypass it to allow continued commissioning, rather than describing the managed bypass procedure with authorization, logging, time limits, and removal verification.
In the field, bypasses are routine and informal. Exam items test whether the candidate knows that a bypass is a controlled activity with documented approval, tracking, and a verified return to service, and they penalize answers that treat bypass as a casual convenience.
What to do instead
For any interlock or trip question during commissioning, include four elements in your reasoning: written authorization, bypass log entry with tag and time, compensatory measures or restricted operation, and verified removal with a functional retest. Select the answer containing those elements.
Given a scope with a fixed milestone date, the candidate picks the schedule answer that compresses every task equally, instead of identifying the critical path, the float on non-critical activities, and the dependencies that actually govern the end date.
Candidates treat schedule compression as a uniform percentage reduction. Exam items reward recognizing that only critical-path activities shift the completion date and that crashing non-critical tasks adds cost without schedule benefit.
What to do instead
Before answering any schedule item, sketch the dependency chain and mark which activities have zero float. Direct compression, resequencing, and resource additions only at critical-path activities. Eliminate answers that shorten tasks with visible float as the means of recovering the end date.
The candidate answers a documentation or turnover question by choosing to hand over the as-built drawings and move on, omitting the calibration certificates, loop folders, configuration backups, test records, and the punch-list closeout evidence that the owner actually needs.
Drawings are the most visible deliverable, so they dominate the candidate's mental model of turnover. Exam items test the full turnover package and the traceability requirement that each instrument's records can be retrieved by tag.
What to do instead
Build a turnover checklist by tag: datasheet, calibration certificate with as-found and as-left data and standard traceability, loop check sheet, configuration backup, and punch-list closure record, plus as-built drawings. When an item asks what completes turnover, choose the answer that includes records traceable to each tag, not drawings alone.