HKIE Professional Assessment - Control, Automation & Instrumentation Discipline common mistakes
HKIE Professional Assessment - Control, Automation & Instrumentation Discipline · Understand the traps and how to avoid them.
When sizing a control valve, the candidate selects the valve on the normal flow rate alone and never checks it against the maximum and minimum flow cases, so the chosen trim is either too large (running near shut-off at minimum flow, causing poor control and cavitation/flashing damage) or too small (unable to pass the design maximum, and choked flow at maximum).
Candidates memorise the Cv equation and apply it once to the normal condition, treating valve sizing as a single-point calculation. They forget that a valve must control over the whole operating envelope and that the installed characteristic changes with pressure drop ratio. Under exam time pressure they skip the rangeability check.
What to do instead
For every valve-sizing question, tabulate three cases (minimum, normal, maximum flow) with the corresponding pressure drops, compute required Cv for each, and then select trim so that the normal case sits around 60-80% travel with the valve not operating below about 10-20% or above about 90%. State the rangeability and check against the valve's published rangeability. Also check cavitation index and flashing at the worst case, and state whether an anti-cavitation trim or downstream pressure recovery consideration is needed.
The candidate writes a safety function narrative and quotes a SIL target without showing the quantitative route: no PFDavg calculation from subsystem architecture, no proof-test interval, no diagnostic coverage, no common-cause beta factor, and no verification that the achieved SIL meets the target.
Candidates learn SIL as a label attached to a loop ('this is a SIL 2 loop') rather than as an outcome of a reliability calculation under IEC 61508/61511. They confuse SIL target (from risk assessment) with SIL achieved (from hardware and proof-test design), and they underestimate how much the proof-test interval and diagnostic coverage dominate the result.
What to do instead
Structure every functional-safety answer as: (1) hazard and risk assessment giving the required SIL; (2) safety requirements specification; (3) loop architecture with sensor, logic solver and final element subsystems; (4) PFDavg per subsystem using the simplified equations for the chosen architecture (e.g. 1oo1, 1oo2, 2oo3), including proof-test interval T1, diagnostic coverage DC, and beta factor for common cause; (5) summation and comparison with the target band; (6) statement of systematic capability and any architectural constraints. Show the numbers even when approximate, and state the assumptions explicitly.
In PLC/SCADA questions the candidate describes the control logic only at the level of 'the PLC opens the valve when the level is low' and omits the I/O list, signal types, scan-cycle implications, fail-safe state, interlocks, permissives, alarm and trip setpoints, and the operator interface behaviour.
Candidates treat automation questions as conceptual rather than as engineering deliverables. They have not practised producing the artefacts a real project requires (I/O schedule, cause-and-effect matrix, functional design specification), so they answer at the level of a narrative description and lose the marks allocated to detail and completeness.
What to do instead
Answer automation questions in the form of a mini functional design specification: input and output list with tag, signal type (4-20 mA, discrete 24 V DC, RTD), range and fail state; control narrative with normal, upset and shutdown sequences; interlock and permissive list; alarm and trip setpoints with deadband; scan time and any fast-task requirement; HMI display and operator action; and the fail-safe position of every final element. Where relevant, produce a small cause-and-effect matrix in text form.
The candidate treats fieldbus selection as a preference question ('use Profibus because it is common') and gives no comparison of determinism, cycle time, diagnostics, power and segment budget, cable length and topology limits, or device interoperability, and does not consider the effect of the network on the control loop and on safety functions.
Fieldbus is often studied as a list of protocol names and speeds rather than as an engineering selection with quantified constraints. Candidates do not know the physical-layer budgets (segment length, number of devices, spur lengths, termination, power conditioner sizing) and cannot therefore justify a choice.
What to do instead
For any network selection question, build a comparison table across the candidate protocols covering: topology supported, maximum segment and total length, maximum devices per segment, data rate versus cable length trade-off, determinism and jitter, intrinsic-safety and power budget (for example Foundation Fieldbus and Profibus PA segment current and voltage drop), diagnostic capability, device interoperability and certification, and suitability for safety functions. Then state the selection criteria ranked against the project's actual requirements and justify the recommendation.
When asked about control-loop performance the candidate tunes or describes a PID in the abstract and never identifies the process dynamics: no dead time, no process gain, no time constant, no distinction between self-regulating and integrating processes, and no discussion of valve and transmitter dynamics in the loop.
Candidates memorise tuning rules (Ziegler-Nichols, Cohen-Coon) and apply them without checking the assumptions behind them, particularly the dead-time-to-time-constant ratio. They also forget that the final element and the measurement are part of the loop, so a well-tuned controller on a sticky valve or a slow transmitter still performs badly.
What to do instead
Always begin with a process characterisation: gain, dominant time constant, dead time, and the dead-time ratio. State whether the process is self-regulating or integrating and whether it is inverse-acting. Then select the controller structure (P, PI, PID, feedforward, cascade, ratio) with justification, choose tuning based on the dead-time ratio (conservative for high ratios), and explicitly discuss the contribution of valve stiction, dead band, transmitter damping and sampling period to achievable performance. Where relevant, mention lambda tuning for robustness.
The candidate answers instrumentation questions with a sensor name only and omits the full measurement chain: accuracy, repeatability, drift, rangeability, turndown, response time, installation effects (straight runs, impulse lines, thermowell immersion, earthing and shielding), calibration traceability, and the effect of the process environment on the reading.
Candidates revise sensor principles (thermocouple versus RTD, orifice versus Coriolis) but not the installation and uncertainty analysis that determines whether the measurement is fit for purpose. They also confuse accuracy with resolution and repeatability, and forget that an uncalibrated or badly installed instrument has no defensible accuracy claim.
What to do instead
Answer in measurement-chain form: sensor principle and why it suits the fluid and range; specified accuracy, repeatability and drift with the reference conditions; total uncertainty including transmitter, installation and calibration standard; installation requirements (upstream and downstream straight lengths, thermowell immersion length versus velocity, impulse line slope and filling, shielding and earthing for low-level signals); calibration interval and traceability to a recognised standard; and the failure mode and diagnostics of the device. Quantify wherever the question gives data.
The candidate discusses industrial cybersecurity purely in terms of a firewall and antivirus, and does not apply a zone-and-conduit model, does not address the OT-specific constraints (availability first, patching windows, legacy devices), and does not connect the security architecture to the safety and control functions it protects.
Candidates carry over IT security habits and terminology and do not know IEC 62443 concepts such as zones, conduits, security levels, the difference between the asset owner and the integrator, or the practical reality that many controllers cannot be patched and must be compensated for by segmentation and monitoring.
What to do instead
Structure security answers using IEC 62443: define zones by function and criticality, define conduits between zones with the protocols and direction of flow permitted, assign target security levels, and then select controls (segmentation, unidirectional gateways, allow-listing, account and remote-access management, logging and monitoring, backup and recovery, patching policy with compensating controls for unpatchable assets). Explicitly state the availability-first principle and how each control affects the safety instrumented system and the control loop. Mention the security lifecycle and the assignment of responsibilities between asset owner and system integrator.
In building automation and environmental control questions the candidate describes the plant conceptually and omits the psychrometric and load calculations, the control sequences (economiser, staging, reset schedules, deadband and setpoint reset), the sensor placement and calibration requirements, and the interaction between the HVAC control and the fire and life-safety systems.
Candidates treat building controls as a soft topic and do not practise the numerical psychrometric work or the standard sequences of operation. They also underestimate the coordination requirements between BMS and fire alarm, smoke control and lift homing, which is where many real failures and many exam marks lie.
What to do instead
For building-services questions, work the load and psychrometric numbers (supply air temperature, coil leaving condition, humidity control), then write the sequence of operation in numbered steps with setpoints, deadbands and staging delays. Specify sensor location and accuracy (e.g. averaging duct sensors, return-air versus room sensing, CO2 for demand-controlled ventilation). Finally, describe the interfaces to fire alarm and life safety: smoke control mode, fan shutdown, damper positions, lift homing, and the priority hierarchy in the BMS so that fire mode overrides normal control.
The candidate answers professional-practice and ethics questions with general statements about integrity and safety, without citing the specific obligation, the applicable code or ordinance, the reporting route, or the consequences for the engineer and the public, and without recognising a conflict of interest or a competence limit when one is present.
Candidates treat the professional-practice section as common sense and do not study the Engineers Registration Ordinance, the HKIE code of conduct, the disciplinary process, or the statutory framework for occupational safety and for building services. They also hesitate to state a firm position when the scenario clearly requires one.
What to do instead
Prepare a short, memorised framework for ethical scenarios: identify the duty owed and to whom (public safety first, then employer, then client); identify the applicable legal and code obligations by name (Engineers Registration Ordinance and the disciplinary provisions, HKIE code of conduct, Occupational Safety and Health Ordinance, Factories and Industrial Undertakings regulations, Buildings Ordinance and allied regulations); state the action required (escalate, document, refuse to certify, report to the authority); and state the consequence of inaction. Where competence is exceeded, say so and recommend referral to a qualified specialist. Practise writing a clear position in the first sentence rather than hedging.
The candidate presents a project plan as a list of activities with no logic, no critical path, no interface and hold-point management, no consideration of procurement and construction lead times, and no risk register; and treats standards compliance as a document to be produced at the end rather than as a thread through design, procurement, installation, commissioning and handover.
Candidates study project engineering as vocabulary (WBS, Gantt, FAT, SAT) without practising the integration. They also do not know which standards govern which deliverable (e.g. IEC 61511 for the safety lifecycle, IEC 62443 for security, local regulations for electrical and building works) and therefore cannot place compliance activities at the right point in the schedule.
What to do instead
Answer project questions with a structured lifecycle: concept and feasibility, front-end engineering, detailed design, procurement, factory acceptance test, installation, site acceptance test, commissioning, performance test, handover and close-out. For each phase state the deliverables, the hold and witness points, the standards invoked, and the responsible party. Add the critical path and the long-lead items, an interface register (civil, electrical, mechanical, process, IT), and a risk register with mitigation. Show where functional safety verification, security assessment and statutory approvals fall in the schedule.