MAP-01-010 HFI Management Guide - Human Factors Integration ...

More documents

Recommendations

Info

Chapter 1 – HFI within Naval Capability Acquisition 1.1 Introduction to the Human Factors Integration (HFI) Guides Human Factors (HF) is the systematic application of relevant information about human capabilities, limitations, characteristics, behaviour and motivation to the design of products and systems, the procedures people use and the environment in which they use them. The term covers all biomedical and psychosocial considerations. This information serves as the basis for making design recommendations and for predicting the probable effects of various design alternatives. In addition, HF involves the evaluation of things that have been designed to ensure that they satisfy their intended objectives. In terms of military capability, whether a product will achieve its required level of operational effectiveness in the field depends not only on the technical performance of the hardware and the software that make up the system but the capabilities and limitations of the people who will operate and support it. Failure to address the people who are part of the system and the environment in which it will be operated can lead to an overall system that fails to achieve the expected levels of operational effectiveness or safety. Unless identified and addressed at early phases of procurement, solving problems in design is likely to be high cost and require: • Product redesign or modification • Increases in manpower numbers or a need for personnel with a higher level of skill • Additional training time or resources To address these problems MOD has established the Human Factors Integration (HFI) programme, which is reviewed as part of the Project Review and Assurance (PR&A) process for each project. The programme consists of a systematic process for identifying, tracking and resolving human related issues ensuring a balanced development of both technological and human aspects of capability, together with supporting tools and techniques. A fundamental concept within HFI is that people are an important part of the system and that system integration is key to achieving operational effectiveness. The HFI process is described in this document (ie MAP-01-010 ‘HFI Management Guide (STGP 10)’) and, with more detail, in MAP-01-010 ‘HFI Technical Guide (STGP 11)‘ [Ref 1]. HFI should also be seen as an integral part of the Systems Engineering approach. The systems concept is central to the implementation of HFI and the overall goal of both HF and HFI is to design an optimal system consisting of operator, equipment and the environment in which they operate. In order to provide flexibility of approach to IPTs, there is no, single, mandatory HFI process specified within DPA AMS guidance. However, formal HF input may be required to mandatory MoD processes, such as Safety Case development. The HFI guidance promulgated within MAP-01-010 and MAP-01-011 should be regarded as model processes and activities, representing current best practice. The need to undertake specific HFI activities, e.g. task analysis, and the extent to which such activities are required, should be decided on a project-by-project basis, with appropriate input from HF Specialists and stakeholders. There is no suggestion that all the activities detailed within the Guides are always necessary or justified. However, in order to provide accountability, the Nov 2006 Page 1-3 Issue 4
MAP-01-010 – HFI Management Guide (STGP 10) model process identified in the Guides should be used as a reference norm, with any departures from that norm being documented and justified in appropriate project documentation. The HFI Focus should therefore use the model process as a checklist, and fully justify any project-specific 'opt-outs'. Key HFI activities are also considered during the Maritime System Maturity (MSM) Project Review and Assurance (PR&A) process. Experience from a range of MoD acquisition projects, and also from many other large-scale industrial procurement programmes, shows very clearly that the timing of HFI activities and resulting outputs is a critical factor in successful Human Factors Integration. A classic problem is the HFI input is "Too Little, Too Late". The active involvement of HFI staff (HFI Focus and HFI professionals) in the early phases of a project is an essential requirement whilst key project decisions are being made. If Human Factors input is delayed until the latter phases of equipment design and selection, there may be relatively little value to be added. The Early Human Factors Analysis (EHFA) technique addresses this issue in part. Similarly, it is often thought by non-HF specialists that HFI activities are never complete. Whilst some HF activities are relatively self-contained and produce discrete outputs at defined phases in a project, it must be emphasised that many HFI activities require an iterative approach, in which system and equipment proposals, designs and their realisations are systematically and repeatedly examined to assess their effects on the human component of the system. The need for HFI continues on beyond the hand over of capability to the user, in that there is justification for HF involvement in the analysis of in-service data and user feedback on the adequacy of the delivered solutions. It is not only important to decide upon an appropriate set of HFI activities for a particular project situation, it is essential that these are satisfactorily communicated to all relevant parties. HFI activities will not happen as a matter of course. The various organisations involved in a typical capability acquisition chain may or may not have in-house HFI capability, HFI processes or adopt HFI practices. Where MoD requires a Supplier to undertake particular HFI activities, apply particular HFI processes or produce particular HFI outputs this must be clearly stated in contract documentation, and appropriate resources allowed for their procurement and associated management. To avoid nugatory effort and expenditure, appropriate efforts should be made to identify, take into account and possibly re-use HF deliverables produced for MoD under other contracts. Generally, in specifying HF requirements in contracts, emphasis should be placed on the form of deliverable required, rather than on how the deliverable should be achieved. A possible exception to this is where consistency of approach across a number of supply contracts is required. Nov 2006 Page 1-4 Issue 4
Page 1 and 2: THIS DOCUMENT IS THE PROPERTY OF HE
Page 3 and 4: MAP-01-010 - HFI Management Guide (
Page 9: MAP-01-010 - HFI Management Guide (
Page 61 and 62:
MAP-01-010 - HFI Management Guide (
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
ANNEX 3 - REFERENCES CONTENTS A3 Re
Page 157 and 158:
Annex 3 - References A3 References
Page 159 and 160:
Annex 3 - References [24] The Unite
show all

MAP-01-010 HFI Management Guide - Human Factors Integration ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?