MAP-01-011 HFI Technical Guide - Human Factors Integration ...

MAP-01-011 – HFI Technical Guide (STGP 11)stakeholders. There is no suggestion that all the activities detailed within theGuides are necessary or justified. However, in order to provide accountability,the model process identified in the Guides should be used as a reference norm,with any departures from that norm being documented and justified in appropriateproject documentation. The HFI Focus should therefore use the model processas a checklist, and fully justify any project-specific 'opt-outs'.Experience from a range of MoD acquisition projects, and also from many otherlarge-scale industrial procurement programmes, shows very clearly that thetiming of HFI activities and resulting outputs is a critical factor in successfulHuman Factors Integration. A classic problem is the HFI input is "Too Little, TooLate". The active involvement of HFI staff (HFI Focus and HFI professionals) inthe early Phases of a project is an essential requirement whilst key projectdecisions are being made. If Human Factors input is delayed until the latterPhases of equipment design and selection, there may be relatively little value tobe added. The Early Human Factors Analysis (EHFA) technique addresses thisissue in part.Similarly, it is often thought by non-HF specialists that HFI activities are nevercomplete. Whilst some HF activities are relatively self-contained and producediscrete outputs at defined Phases in a project, it must be emphasised that manyHFI activities require an iterative approach, in which system and equipmentproposals, designs and their realisations are systematically and repeatedlyexamined to assess their effects on the human component of the system. Theneed for HFI continues on beyond the hand-over of capability to the user, in thatthere is justification for HF involvement in the analysis of in-service data and userfeedback on the adequacy of the delivered solutions.It is not only important to decide upon an appropriate set of HFI activities for aparticular project situation, it is essential that these are satisfactorilycommunicated to all relevant parties.HFI activates will not happen as a matter of course. The various organisationsinvolved in a typical capability acquisition chain may or may not have in-houseHFI capability, HFI processes or adopt HFI practices. Where MoD requires acontractor to undertake particular HFI activities, apply particular HFI processes orproduce particular HFI outputs, this must be clearly stated in contractdocumentation and appropriate resources allowed for their procurement andassociated management.To avoid nugatory effort and expenditure, appropriate efforts should be made toidentify, take into account and possibly re-use HF deliverables that have beenproduced for MoD under other contracts.Generally, in specifying HF requirements in contracts, emphasis should beplaced on the form of deliverable required, rather than on how the deliverableshould be achieved. A possible exception to this is where consistency ofapproach across a number of supply contracts is required.1.2 HFI Technical Areas for Naval Platforms and EquipmentThe procurement of Sea Systems ranges from the acquisition of new platformsand/or equipments to the provision of specific items of equipment for existingvessels. The procurement process itself may occur over a number of stages andNov 2006 Page 1-4 Issue 4