The Human View Handbook for MODAF: Part V – Appendices

The Human View Handbook
Part 5: Appendices
Risk influence
factor
of manpower and
skill levels
8 Extent of HF
problems in
predecessor
systems
Explanation
availability and requirements, and skill needs – potentially
requiring manpower planning, recruitment, and/or training
activities.
Extent of HF problems in existing systems, giving an indication
of the amount of design change required to overcome them and
assess improvements. 5%
9 Scope of effects The extent to which the new product/system affects related
system design areas through the consequences of changes
required. For example, new technology such as NEC information
networks may require new organisational and information flow
structures, re-training, re-recruiting, new maintenance
schedules, new documentation. The lifetime of the
product/system may come into the equation here.
10 HFI design scope
in relation to
project focus
If the purpose of the project is the design of a new user
interface only (e.g. for an existing helicopter), then the HFI
effort is proportionally much higher than, for example, the
design of an entire new helicopter (where, for example,
ensuring technical airworthiness will take on a much larger
proportion than HFI activities).
11 Level of novelty The extent to which the newly designed working system is novel
(e.g. first-of-a kind) and produces sources of uncertainty (e.g.
novel technology, new task and operating conditions, new
organisational constraints). This affects design, implementation,
and operation.
12 Number of design
constraints
13 Project
uncertainty
14 Product purpose
directly fulfils a
Human Factors
need
15 Absence of
conducive design
organisation
conditions
The extent to which the design process needs to conform with
external limitations that require optimisation of operational
variables (e.g. need to comply with safety regulations, need to
follow specific design standards).
Amount of (not yet) available understanding of operational
needs and system requirements (e.g. agreements on operational
concepts, understanding of user constraints, definition of tasks
and expected task performance, clarity of high-level humanequipment
interface requirements, envisaged use of
technologies).
Technology Readiness Levels may be referred to here.
The purpose of the design is in itself fulfilling a user need, i.e.
support to humans is the objective of the project (e.g.
transporting them, housing them, providing them with
information).
The ease with which an effective HFI process can be integrated
depends not only on the acceptance level of HFI, but also on the
presence of conducive processes such as an iterative design
process, efficient project management, effective
communication, documentation, and information sharing
processes.
Weight
5%
10%
5%
5%
10%
5%
5%
Severity Rating
0 - None
1- Very Low
2 - Low
3 – Medium
4 - High
5 – Very High
page 20