A Review of the Event Analysis of Systemic Teamwork Methodology

More documents

Recommendations

Info

HFIDTC/WP1.1.3/10 Version 2/ 31 October 2005 The observation step is the most important part of the EAST procedure. Typically, a number of analyst(s) are used in scenario observation. All activity involved in the scenario under analysis should be recorded along an incident timeline, including a description of the activity, the agents involved, any communications made and the technology involved. Additional notes should be made where required, including the purpose of the activity, any errors made and also any information that the agent involved feels is relevant. Step 5: Critical decision method Once the scenario under analysis is complete, each ‘key’ (e.g. scenario commander, agents performing the component tasks etc) involved should be subjected to a CDM interview. This involves dividing the scenario into key incident phases and then interviewing the agent involved using pre-defined probes. A CDM interview should be conducted for each incident phase. Step 6: Transcribe scenario data Once all of the scenario data is collected, it should be transcribed in order to make it compatible to the EAST analysis phase. An event transcript should be constructed. The transcript should describe the scenario over a timeline, including descriptions of activity, the agents involved, any communications made and the technology used. In order to ensure the validity of the data, the scenario transcript should be reviewed by one of the SME’s involved. Step 7: Re-iterate HTA The data transcription process allows the analyst(s) to gain a deeper and more accurate understanding of the scenario under analysis. It also allows any discrepancies between the initial HTA scenario description and the actual activity observed to be resolved. Typically, C4i activity does not run entirely according to protocol, and certain tasks may have been performed during the scenario that were not described in the initial HTA description. The analyst should compare the scenario transcript to the initial HTA, and add any changes as required. Step 8: Co-ordination demands analysis The CDA involves extracting teamwork tasks from the HTA and rating them against the associated CDA taxonomy. Each teamwork task is rated against each CDA behaviour on a scale of 1 (low) to 3 (high). Total co-ordination for each teamwork step can be derived by calculating the mean across the CDA behaviours. The mean total co-ordination figure for the scenario under analysis should also be calculated. Step 9: Construct comms usage diagram The CUD is used to represent communication between the agents involved in the scenario and also to analyse the comms technology utilised. The scenario transcript is used as the input to the CUD. Step 10: Conduct social network analysis 7
HFIDTC/WP1.1.3/10 Version 2/ 31 October 2005 The SNA is used to analyse the relationships between the agents involved in the scenario under analysis. Using the scenario transcript, the analyst should firstly construct an agent association matrix, which presents the links between the agents and also the frequency of communications between the agents. An example association matrix is presented in Table 6. From the association matrix, a social network diagram is constructed and agent centrality, sociometric status, and network density are calculated. It is recommended that the Agna SNA software package is used for the SNA phase of the EAST methodology. Step 11: Construct operation sequence diagram The OSD represents the activity observed during the scenario under analysis. The analyst should construct the OSD using the scenario transcript and the associated HTA as inputs. Once the initial OSD is completed, the analyst should then add the results of the CDA to each teamwork task step. Step 12: Construct Propositional networks The final step of the EAST analysis involves constructing propositional networks for each scenario phase identified during the CDM interviews. In order to construct the propositional networks for each phase, a basic contents analysis should be conducted using the associated CDM outputs. Knowledge objects are defined as knowledge, information, artefacts and actions. Each knowledge object should have a corresponding node in the propositional network. Next, the links between the nodes should be specified. To do this, the analyst should specify any links between the knowledge objects within the propositional networks, using the following links taxonomy; Example • Has • Is • Causes • Knows • Requires • Prevents The following example is taken from an analysis of a switching scenario drawn from the civil energy distribution domain (Salmon et al 2004b). The scenario took place at Barking 275Kv, 132Kv and 33Kv substations and the National Grid Transco (NGT) Network Operations Centre (NOC) in Warwick. The scenario under analysis involved the switching out of three circuits (SGT5 and SGT1A and 1B) at Barking 275Kv, 132Kv and 33Kv Substations. Circuit SGT5 was being switched out for the installation of a new transformer for the nearby channel tunnel rail link and SGT1A and 1B were being switched out for substation maintenance. The observation focussed upon four main 8
Page 1 and 2: Analysing C4i Activity: A Review of
Page 3 and 4: HFIDTC/WP1.1.3/10 Version 2/ 31 Oct
Page 9: HFIDTC/WP1.1.3/10 Version 2/ 31 Oct
Page 61 and 62:
HFIDTC/WP1.1.3/10 Version 2/ 31 Oct
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

Create successful ePaper yourself

Delete template?

Save as template?