A Review of the Event Analysis of Systemic Teamwork Methodology

More documents

Recommendations

Info

HFIDTC/WP1.1.3/10 Version 2/ 31 October 2005 1 Executive Summary This report describes a review of the Event Analysis of Systemic Teamwork (EAST) methodology (Baber and Stanton 2004) that was used to analyse C4i activity in the rail, air traffic control, energy distribution, military, police, fire service and naval domains. The EAST methodology and its component methods were analysed using a set of human factors (HF) methods and criteria designed to analyse the performance of the methods. The analysis was based upon the EAST applications undertaken as part of the Human Factors Integration Defence Technology Centre (HFI DTC) work programme (see application domains above). The methods review indicated that the EAST methodology is an exhaustive technique that is particularly suited to the analysis of C4i, team based and collaborative activity. The methods review also indicated that the outputs from the EAST methodology are extremely useful, offering a number of different analyses of, and perspectives on the scenario in question. Further, it was concluded that the EAST methodology is relatively simple to learn and apply. In terms of flaws in the EAST methodology, the review indicated that the method can be overly time consuming (although this reflects the complexity of C4i domains) in some instances (i.e. for larger, more complex tasks) and also that there may be issues with the reliability of the method in some instances. 1
HFIDTC/WP1.1.3/10 Version 2/ 31 October 2005 2 Introduction The event analysis of systemic teamwork (EAST) methodology (Baber and Stanton 2004) was developed as part of the HFI DTC work programme, and uses a combination of HF methods to form a framework for analysing command, control, communication, computers and intelligence (C4i) activity. With a view to the development of a generic model of C4i, EAST has been applied to a number of diverse C4i scenarios, across a number of different domains. The domains and scenarios in which EAST has been used to analyse C4i activity are presented in Table 1. Table 1 – EAST Analysis Domain Air Traffic Control National Air Traffic Services Energy Distribution National Grid Transco Fire Service Military Aviation E3D Navy HMS Driad Police Rail (Signalling) Scenario Holding Overflight Departure Approach Shift handover Barking switching operations Feckenham switching operations Tottenham return to service operations Alarm handling operations Chemical incident at remote farmhouse Road traffic accident involving chemical tanker Factory fire exercise #1 Factory fire exercise #2 General operation Air threat Surface threat Sub-surface threat Car break in caught on CCTV Suspected car break in Mobile phone robbery Detachment scenario Emergency Possession scenario Handback a Possession scenario Possession scenario EAST review In order to analyse the performance of the EAST methodology and its component methods, a review of the method was conducted based upon the applications described above. The review was based upon the same criteria that were used in the HF methods review (Salmon et al 2004a) that was conducted for the development of the EAST methodology. The criteria are outlined below: 1. Name and acronym – the name of the technique and its associated acronym. 2
Page 1 and 2: Analysing C4i Activity: A Review of
Page 3: HFIDTC/WP1.1.3/10 Version 2/ 31 Oct
Page 7 and 8: HFIDTC/WP1.1.3/10 Version 2/ 31 Oct
Page 55 and 56:
HFIDTC/WP1.1.3/10 Version 2/ 31 Oct
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
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:
show all

A Review of the Event Analysis of Systemic Teamwork Methodology

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

Delete template?

Save as template?