|
Content
Human Factors Integration (HFI) Issues LogWhat is an HFI Issues Log?An HFI Issues Log is a tool used to identify and record issues and constraints. The main purpose of the HFI issues log is to outline the impact of each issue, prioritise them and propose a strategy for resolution. The HFI issues log is a live document throughout the project. What are the Components of the HFI Issues Log?
How should an Issues Log be developed?Issues should be identified throughout the acquisition process. However, different stages will provide different types of information. During early stages the issues log will rely on stakeholder consultation and human factors analysis (e.g. task analysis, workload analysis, target audience description, human reliability analysis). At later stages the issues log will rely on trial results, and later from feedback following operational work ups. At early stages of the acquisition process, issues are gathered relating to each acquisition or system option (a matrix of options vs. human factors integration domains could be used). Each issue should be given a unique reference number and a detailed description. The issue is assessed for the likely impact on cost, time-scale, safety or system effectiveness. It is useful to sub-divide issues into:
What impacts an HFI Issues Log?The following topics are required to compile an HFI Issues Log: Does the HFI Issues Log affect any other processes?The following lists the dependencies associated with a Human Factors Integration Issues Log, and relevant issues should be placed in the following documents:
When should a HFI Issues Log be produced?The HFI issues log should be produced at the start of a project, and incorporated into the Initial Gate Business Case. This will be carried forward through the rest of the acquisition process. The human factors issues are fed into the Project Issues or Risk Registers. Further Information can be found in the HFI Process booklet [PDF]
Change History
Change History
|