Answers are grounded in this paper and cite their sources.
Procuring an engineer-to-order training simulator requires close coordination between software development and the procurement of specialized hardware. Although the House of Risk method ranks mitigation actions, it does not identify which actions are prerequisites for others. This study aimed to identify the main sources of risk and determine the order of mitigation actions for the procurement of one simulator at PT XYZ. The case study drew on assessments by three project experts and data from 14 monthly progress reports. The Supply Chain Operations Reference model was used to map procurement activities. The House of Risk method quantified aggregate risk potential and ranked actions by their effectiveness-to-difficulty ratios. Interpretive Structural Modeling then mapped dependencies among actions. Five of eleven risk agents accounted for 86.18% of total aggregate risk potential. Poor coordination between programmers and users contributed the largest share (34.39%). Of nine mitigation actions, staged model acceptance testing ranked first (6,561), followed by user acceptance testing (5,832). The hierarchy identified user acceptance testing as foundational. These findings guide project teams in agreeing on user acceptance criteria at project initiation and using those criteria to define design specifications, set milestones, and validate the model.
No takes yet. Share an insight, caveat, or question.
Hapsari et al. (2026) studied this question.
Synapse has enriched 10 related papers. Consider them for comparative context: