Project Engineering
Project Engineering tests how instrumentation and control work is scoped, scheduled, costed, commissioned and handed over. The exam favours earned-value, interface and commissioning scenarios rather than generic project-management definitions.
Core rules and concepts
- The lifecycle runs from feasibility and front-end engineering through detailed design, procurement, construction, commissioning, operation and decommissioning. Deliverables include P&IDs, instrument index, loop drawings, I/O lists, cause-and-effect charts, datasheets and as-built records.
- Use a work breakdown structure and critical-path method. Float is the time an activity can slip without delaying the project; the critical path has zero float. Fast-tracking and crashing change risk, not just duration.
- Earned value uses planned value (PV), earned value (EV) and actual cost (AC). Cost variance CV = EV - AC; schedule variance SV = EV - PV; CPI = EV/AC; SPI = EV/PV. Negative CV means over budget; negative SV means behind schedule.
- Risk management records cause, event, consequence, likelihood, impact, owner and mitigation. Interface management is critical between civil, mechanical, electrical, process and vendor packages.
- FAT proves a system in the factory; SAT proves it in the plant. Loop checks, cause-and-effect testing, alarm testing and functional safety validation must be completed before handover. Punch-list items need owners and closure dates.
- Contracts allocate risk. Variations, extension-of-time claims and change control must be documented; verbal instructions are a common source of disputes.
Worked example
A package has PV = HK$500,000, EV = HK$400,000 and AC = HK$450,000. CV = 400,000 - 450,000 = -HK$50,000, so it is over budget. SV = 400,000 - 500,000 = -HK$100,000, so it is behind schedule. CPI = 0.889 and SPI = 0.800. The correct conclusion is not "the project is 80% complete"; it is that the work earned is only 80% of what was planned for this point.
Traps
Confusing EV with actual cost; treating float as free time; accepting verbal changes; starting commissioning before loop checks; and handing over without as-built drawings and validated cause-and-effect records.
Standards and Codes of Practice
Standards and Codes of Practice tests whether you can identify the governing document, apply the correct edition and distinguish a legal requirement from good practice. The exam expects working knowledge of the standards used in control, instrumentation and safety, plus Hong Kong legal instruments.
Core rules and concepts
- A regulation is legally enforceable; a code of practice is approved guidance that may be used as evidence of compliance; a standard is a consensus technical specification. "Shall" indicates a requirement, "should" a recommendation and "may" a permission.
- Key IEC standards include IEC 61508 and IEC 61511 for functional safety, IEC 61131-3 for PLC languages, IEC 62443 for industrial cybersecurity, IEC 61850 for substation automation, IEC 62061 and ISO 13849 for machinery safety, and IEC 60204-1 for electrical equipment of machines.
- Hazardous-area work uses the IEC 60079 series; enclosure protection uses IEC 60529 IP ratings. P&ID symbols follow ISA-5.1; alarm management follows ISA-18.2; HMI design follows ISA-101; batch follows ISA-88; enterprise integration follows ISA-95.
- Hong Kong instruments include the Electricity Ordinance Cap. 406 and its Code of Practice for the Electricity (Wiring) Regulations, the Engineers Registration Ordinance Cap. 409, the Buildings Energy Efficiency Ordinance Cap. 610, the Fire Services Ordinance and occupational safety and health legislation.
- Local law overrides a standard or a client specification. Edition and amendment matter: citing an obsolete edition can invalidate a design basis.
Worked example
A field enclosure is specified as IP65. The first digit 6 means dust-tight; the second digit 5 means protection against water jets from any direction. IP65 is not suitable for temporary immersion; IP67 would be needed for immersion under defined conditions. The reasoning is to decode each digit separately, then compare with the actual washdown or outdoor exposure, not to treat IP65 as a generic "weatherproof" label.
Traps
Citing IEC 61508 when IEC 61511 is the process-sector standard; treating "should" as "shall"; assuming CE or ATEX marking alone satisfies Hong Kong law; and using an outdated edition without checking amendments.
Professional Practice
Professional Practice tests how an engineer exercises judgement, documents decisions, manages interfaces and protects the public interest. The exam looks for a defensible process: identify the duty, assess the risk, act within competence, record the decision and escalate when necessary.
Core rules and concepts
- Work within your competence and current knowledge. Keep continuing professional development records and know when to seek specialist advice. A signature is a professional assertion, not an administrative formality.
- Maintain traceability: design basis, calculations, assumptions, vendor data, review comments, change requests and approvals. Configuration management applies to software, firmware, network settings and safety logic, not only drawings.
- Independent review and verification reduce self-approval risk. Safety in design requires hazard identification, risk assessment and ALARP reasoning; HAZOP, LOPA and SIL assessment are team activities with defined terms of reference.
- Interface management is a professional duty. Define battery limits, signal ownership, cause-and-effect responsibilities and commissioning roles between client, consultant, contractor and vendors.
- Site work requires permit-to-work, isolation, lockout/tagout and management of bypasses. Commissioning is a controlled transition, not an informal trial.
- Raise concerns promptly and in writing. If a safety issue is not resolved, escalate through the responsible engineer, client and appropriate authority rather than accepting a verbal assurance.
Worked example
During FAT, a vendor cannot show that a high-pressure trip function meets its specified SIL. The correct response is to raise a nonconformance, withhold acceptance of that function, request the safety requirements specification and verification evidence, and escalate the schedule impact. Signing the FAT "subject to later review" without a hold point transfers risk to the operator and weakens the audit trail. The reasoning: acceptance is a professional decision supported by evidence, not a favour to the vendor.
Traps
Acting outside competence; accepting verbal instructions without change control; signing off without reviewing evidence; leaving safety bypasses undocumented; and treating "not my scope" as a defence when you knew of the risk.
Ethics and Legal Responsibilities
Ethics and Legal Responsibilities tests the boundary between commercial pressure and professional duty. The exam expects you to know the HKIE Code of Conduct, the main Hong Kong legal instruments and the principle that public safety and honesty prevail over client convenience.
Core rules and concepts
- The HKIE Code of Conduct requires honesty, integrity, competence, objectivity, confidentiality and avoidance of conflicts of interest. Members must not misrepresent their qualifications or experience and must not accept work outside their competence without proper support.
- Public safety and health take precedence over commercial or contractual interests. If a client instructs work that creates an unacceptable risk, the engineer must refuse, document the advice and escalate as necessary.
- The Engineers Registration Ordinance Cap. 409 provides for registration of professional engineers. The Electricity Ordinance Cap. 406 and its wiring code govern electrical work; the Occupational Safety and Health Ordinance Cap. 509 imposes duties on employers and persons at work; the Prevention of Bribery Ordinance Cap. 201 prohibits corrupt gifts and advantages.
- Liability may arise in contract or tort. Negligence requires a duty of care, breach, causation and damage. Professional indemnity insurance is protection, not a substitute for competent practice.
- Confidentiality is not absolute: it can be overridden by legal obligation, court order or a serious risk to safety. Whistleblowing should follow approved channels and be evidence-based.
- Sustainability and fair dealing are part of professional ethics; do not mislead with unverified performance claims or plagiarised work.
Worked example
A client pressures you to energise a control system before safety validation because a deadline is at risk. The correct response is to refuse energisation for the safety-critical function, record the technical basis, offer a partial energisation plan for non-safety systems if it can be isolated, and escalate to the responsible officer. The reasoning: the Occupational Safety and Health Ordinance and the HKIE Code both require foreseeable risks to be controlled; a deadline does not create a legal defence.
Traps
Treating confidentiality as a reason to conceal a safety risk; accepting gifts that could influence judgement; signing outside your competence; and copying another engineer's work without attribution.