HKIE Professional Assessment - Logistics & Transportation Discipline common mistakes
HKIE Professional Assessment - Logistics & Transportation Discipline · Understand the traps and how to avoid them.
Answering a capacity or level-of-service question by quoting a single rule-of-thumb number (e.g. a fixed lane capacity or berth throughput) without stating the assumptions behind it, then failing to adjust when the scenario gives different heavy-vehicle percentages, grade, or dwell times.
Candidates memorise headline figures from undergraduate notes and treat them as universal constants, so they never surface the assumption set the number depends on and cannot adapt it to the scenario actually presented.
What to do instead
For every capacity or LOS answer, write the assumption line first: traffic composition, terrain, control type, dwell/ service time, and peaking factor. Then show the adjustment step explicitly (e.g. heavy-vehicle equivalence, grade correction, peak-hour factor). If you cannot justify an adjustment, state the base case and flag the sensitivity rather than presenting a bare number.
Producing a demand forecast as a single point estimate with no scenario range, no stated growth assumption, and no reconciliation against an independent check such as population, employment, or GDP drivers.
The four-step model workflow encourages candidates to run the mechanics (trip generation, distribution, mode split, assignment) and stop when a number appears, without interrogating whether the inputs and elasticities are defensible.
What to do instead
Always present a low/central/high range, name the key driver and its elasticity or growth rate, and cross-check the total against a simple independent indicator. State which input dominates the uncertainty. A forecast without a range and a sanity check reads as unfinished to an assessor.
Treating an intermodal or freight chain question as a single-mode problem - recommending a road solution where the scenario involves rail or barge legs, or ignoring container turnaround, empty repositioning, and terminal dwell in the cost and time calculation.
Candidates often specialise in one mode and default to it, and they under-weight the interface costs (handling, transfer, documentation) that dominate multimodal economics.
What to do instead
Map the full chain node by node before recommending anything: origin haul, transfer point, line haul, transfer point, final delivery. Quantify transfer cost and time at each interface, include empty equipment and dwell, and only then compare options. Explicitly identify which leg or interface is the bottleneck.
Describing an ITS or logistics IT solution by naming technologies (RFID, GPS, a control tower, a digital twin) without specifying the data flow, the decision it supports, the integration points with legacy systems, and the measurable outcome.
Vendor vocabulary is familiar and easy to reproduce, so candidates substitute technology names for system design and never demonstrate that they understand what the system actually does.
What to do instead
For each technology proposed, state: what data is captured, at what frequency and accuracy, which system consumes it, what decision or KPI changes, and how success is measured. Name at least one integration risk (interface standards, data quality, cybersecurity) and the mitigation.
Answering a port or airport planning question with a generic layout sketch or a list of facility types, without deriving the required number of berths, gates, or stands from throughput, vessel or aircraft size, service time, and acceptable waiting time.
Terminal planning is visually intuitive, so candidates draw rather than calculate, and they skip the queueing or occupancy arithmetic that actually determines capacity.
What to do instead
Start from demand (annual throughput, call size, seasonality), convert to peak-period arrivals, apply service time and an acceptable utilisation or waiting-time target, and derive the facility count. Show the queueing or occupancy formula used and test sensitivity to a longer service time or higher peak factor.
Presenting an economic appraisal or business case that lists benefits qualitatively or gives a benefit-cost ratio without stating the discount rate, appraisal period, base year, treatment of optimism bias, and which costs and benefits are included or excluded.
Candidates know a BCR is expected and produce one, but they treat the appraisal as a formality rather than a transparent accounting exercise, so the number cannot be scrutinised.
What to do instead
Tabulate costs and benefits by year, state the discount rate and appraisal period, convert to present values, and disclose inclusions, exclusions, and any optimism-bias or risk allowance. Show the sensitivity of the BCR to the discount rate and to the largest benefit line, and state the switching value at which the project fails.
Treating safety and regulatory compliance as a closing paragraph of generic assurances, rather than identifying the specific hazards, the governing regulatory regime, the risk-control hierarchy, and the residual risk owner for the scenario.
Candidates fear getting a regulation wrong and so retreat to vague statements, but vagueness scores nothing; the assessor wants structured risk reasoning even where the exact clause is uncertain.
What to do instead
Run a short structured risk process: hazard identification, likelihood and consequence, controls in hierarchy order (eliminate, engineer, administer, PPE), residual risk, and named owner. Cite the regime by name and purpose rather than quoting clauses, and state explicitly where you would verify the current requirement.
Offering sustainability measures as a checklist (electric vehicles, solar panels, modal shift) with no baseline, no quantification of emissions or energy saved, and no consideration of cost, grid or fuel-supply constraints, or lifecycle impacts.
Sustainability language is easy to generate and candidates mistake breadth of measures for depth of analysis, skipping the baseline-and-abatement arithmetic.
What to do instead
Establish a baseline (tonne-km or vehicle-km, energy intensity, emission factor), then quantify each measure's abatement and cost per tonne of CO2 avoided. Discuss lifecycle and supply-chain emissions where relevant, and state at least one constraint or rebound effect. Rank measures by cost-effectiveness.
Writing the project management section as a generic description of a methodology (phases, a Gantt chart, a risk register) without binding it to the specific project's critical path, procurement route, interface risks, stakeholder approvals, and contingency.
Candidates reproduce textbook project-management frameworks because they are safe, but the question is testing whether they can apply judgement to the particular scope, constraints, and approvals described.
What to do instead
Anchor every project-management statement to the case: name the critical path and the activity most likely to slip, the procurement and contracting route and why, the top three interfaces or approvals, and the contingency in time and cost with its basis. Show one decision you would take if a stated constraint tightened.
Discussing automation, analytics, or e-commerce logistics as futuristic possibility without addressing the operating model change, the failure modes of the technology, workforce and change-management implications, and the professional and ethical duties of the engineer recommending it.
Emerging-technology questions invite speculation, and candidates enjoy describing capability rather than confronting reliability, liability, data governance, and the human factors that determine whether deployment succeeds.
What to do instead
For each technology, state the current maturity and evidence base, the operating-model change required, at least two failure modes and their mitigations, the workforce transition, and the professional duty owed (public safety, transparency, data protection, avoiding overclaiming). Conclude with the conditions under which you would not recommend deployment.