Procedure

Prior information

Context of use analysis and task analysis should be used to identify the task structure and demands, the knowledge needed to perform the tasks, environmental constraints, functional and safety requirements, and any other relevant issues.

Mandatory allocation

Mandatory allocation can be identified from the task model, e.g.

• Allocate functions to humans when there are technical limitations, ethical constraints, or safety considerations.
• Allocate functions to machines when task demands exceed human capabilities or when the system must be operated in a hostile environment

Provisional allocation

Permanently allocate tasks based on factors such as task criticality, cost, training or knowledge requirements, or task unpredictability.

Dynamically allocate tasks based on factors such as human workload, the need for cognitive support, individual differences in users, changing capacity of the user, or organisational learning.

Jobs must be designed from the tasks based on factors such as responsibility, task variety, interference between and within tasks, communication between users, and individual capability.

Evaluation

The provisional allocations and jobs should be evaluated based on factors such as: safety, system performance, usability, cost, job satisfaction and human well-being, acceptance by users, management and society and social impact. The evaluation findings should be used to review and revise the provisional allocations which should then be re-evaluated.

(This procedure is based on Sujan & Pasquini, 1998.)

Materials Needed

Paul Fitts (1951) published an early list of functions (the Fitts' list) that were performed better by humans and functions that were performed better by machines. As technoogy has improved, the function allocation lists have been upgraded to take advantage of new machine capabilities like new sensors, advanced software, and better intelligence.

Common Problems

• Users of an automated system may rely too heavily on automation and fail to monitor the system adequately.
• Where there is dynamic allocation of functions between software and people (autopilots or crash avoidance systems in cars) when does the software allow the person to override the automation? Does the system know when someone is fatigued or when the driver is an expert?

Next Steps

The prototypes produced for evaluation of task allocation can be included as part of the iterative design process. This is followed by implementation.