Energy, Sustainability, Decarbonisation and Circular Economy
Scope
This domain tests energy accounting, heat integration, and decarbonisation reasoning. Expect pinch analysis, energy efficiency, CO2 scopes, emissions factors, and circular-economy choices. The exam favours a defensible number over a sustainability slogan.
Core rules
- Energy balance first: enthalpy in equals enthalpy out plus losses plus useful output. Efficiency is useful output divided by energy input; define the boundary.
- Pinch analysis: with a minimum approach temperature, construct hot and cold composite curves. The overlap gives minimum hot and cold utility targets. Heat recovery increases as Delta T_min falls, but exchanger area and capital cost rise.
- CO2 accounting: Scope 1 is direct combustion or process emissions; Scope 2 is purchased electricity and steam; Scope 3 is the value chain. Use consistent emissions factors and state whether location-based or market-based.
- Decarbonisation options include efficiency, fuel switching, electrification, renewable power, hydrogen, CCUS, and circular feedstock. Each has a cost, availability, and system-boundary question.
- Circular economy means design for reuse, recycling, and recovery. Avoid downcycling and account for energy and material losses.
Worked example
A site imports 2,000 MWh of electricity per year. Using an emissions factor of 0.7 kg CO2/kWh, Scope 2 emissions = 2,000 x 1,000 x 0.7 = 1,400,000 kg = 1,400 t CO2/yr. If the site instead generates the same electricity from natural gas at 40% efficiency, fuel energy is 2,000 / 0.40 = 5,000 MWh. At an illustrative 0.20 t CO2/MWh fuel, direct emissions are 1,000 t CO2. The comparison must also include the purchased electricity factor and any heat recovery. The lower number is not automatically the better option.
Traps
- Mixing kW and kWh, or thermal and electrical energy.
- Claiming renewable electricity without matching certificates and boundary.
- Quoting a carbon factor without its year, geography, and basis.
- Treating energy recovery as free. It requires area, pressure drop, and capital.
Sustainability claims need a boundary, a baseline, and a unit. Without these, they cannot be audited or compared.
Project Engineering, Economics, Contracting and Engineering Management
Scope
This domain tests whether you can frame a project commercially: cost estimate class, cash flow, NPV, contract strategy, schedule, and change control. The exam looks for judgement about risk allocation, not just arithmetic.
Core rules
- Capital cost estimate classes run from order-of-magnitude to definitive. Accuracy improves with engineering definition. Contingency covers identified uncertainty; it is not a slush fund.
- NPV discounts future cash flows at the cost of capital: NPV = sum of CF_t/(1+r)^t minus initial capex. IRR is the discount rate giving NPV = 0. Payback ignores time value and later cash flows.
- Contract types: lump-sum turnkey transfers cost risk to the contractor at a price; reimbursable keeps risk with the owner but needs controls. EPC, EPCM, and alliance models allocate design, procurement, and construction risk differently.
- Schedule: the critical path determines duration. Float is not spare time to be consumed casually. Change control needs scope, cost, schedule, and risk impact before approval.
- Working capital, escalation, taxes, and currency are part of the economics. Omitting them flatters the project.
Worked example
A project has capex 10.0 million at t = 0 and net cash inflows of 3.0 million per year for five years. At a 10% discount rate, the annuity factor is 3.791. NPV = -10.0 + 3.0 x 3.791 = +1.37 million. The project clears the 10% hurdle by 1.37 million in present-value terms. Payback is 3.33 years, which looks attractive but ignores later years and time value. If inflows were 2.5 million, NPV = -10.0 + 9.48 = -0.52 million, so the project would destroy value at the same hurdle rate.
Traps
- Discounting nominal cash flows at a real rate, or vice versa.
- Including sunk costs in incremental cash flow.
- Comparing IRR across projects of different scale and duration without incremental analysis.
- Accepting a lump-sum price without checking specification and exclusions. The lowest bid may carry the largest change orders.
Engineering management is risk management. The contract, schedule, and estimate must tell the same story.
Professional Practice, Ethics, Statutory Duties and Code of Conduct
Scope
This domain tests the engineer's statutory and ethical duties: public safety, competence, honesty, confidentiality, conflicts of interest, and compliance with the law. The exam favours a clear duty hierarchy over client convenience.
Core rules
- The safety, health, and welfare of the public come first. If a design or operation is unsafe, the engineer must not certify it, even under commercial pressure.
- Work only within competence. If you lack expertise, seek it, supervise it, and record the basis of decisions.
- Declare conflicts of interest, financial interests, and gifts. Do not accept inducements that could influence judgement. The Prevention of Bribery Ordinance (Cap. 201) makes corrupt transactions an offence.
- Confidentiality is real but not absolute. Legal disclosure, safety risk, and regulatory duty can override it. Do not conceal a known hazard behind a confidentiality clause.
- Keep records, sign only what you have checked, and respect the limits of professional registration. The HKIE code and the Engineers Registration Ordinance (Cap. 409) frame discipline and registration.
- Whistleblowing on a serious safety risk is a professional duty, not disloyalty. Use the internal channel first where it is effective, then the regulator.
Worked example
An engineer is asked to approve a pressure vessel design from a supplier in which the engineer holds shares. The design also has an unresolved fatigue calculation. The correct response is to declare the interest, withdraw from the approval, and escalate the technical gap to a competent independent reviewer. Signing with a verbal caveat is not adequate. The conflict undermines the objectivity of the approval, and the technical gap is a safety issue. The duty is to protect the public and the integrity of the engineering record, not to preserve the commercial relationship.
Traps
- Treating client loyalty as superior to public safety.
- Using industry practice to justify a known non-compliance.
- Accepting a gift or hospitality that creates a sense of obligation.
- Signing drawings or reports outside your competence because a senior colleague is unavailable.
Ethical failures are rarely dramatic. They usually begin with a small compromise that is never recorded. Record the decision and its basis.