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 reliability of the technique is questionable. Different analysts may interpret the OSD symbols differently. Related methods Various types of OSD exist, including temporal operational sequence diagrams, partitioned operational sequence diagrams and spatial operational sequence diagrams (Kirwan & Ainsworth 1992). During the OSD data collection phase, techniques such as observational study and interviews are typically used. Task analysis techniques such as HTA are also used during the construction of the OSD. Timeline analysis may also be used in order to construct an appropriate timeline for the task or scenario under analysis. Additional analyses results can also be annotated onto an OSD, such as CDA and comms usage diagram. The OSD technique has also recently been integrated with a number of other techniques (HTA, observation, co-ordination demands analysis, comms usage diagram, social network analysis and propositional networks) to form the event analysis of systemic teamwork (EAST) methodology (Baber et al 2004), which has been used to analyse C4i activity in a number of domains. Approximate training and application times The training time associated with the OSD methodology is low. However, the typical application time for the technique is high. The construction of an OSD can be a very time consuming process, involving many re-iterations. A typical OSD normally can take 12 + hours to construct. Reliability and validity According to Kirwan & Ainsworth (1992), OSD techniques possess a high degree of face validity. The intra analyst reliability of the technique may be suspect, as different analysts may interpret the OSD symbols differently. Tools needed When conducting an OSD analysis, pen and paper could be sufficient. However, to ensure that data collection is comprehensive, it is recommended that video or audio recording devices are used in conjunction with the pen and paper. For the construction of the OSD, it is recommended that a suitable drawing package, such as Microsoft Visio is used. The WESTT software package can also be used to automate a large portion of the OSD procedure. WESTT constructs the OSD based upon an input of the HTA for the scenario under analysis. Example The following example is an extract of an OSD of an energy distribution scenario (Salmon et al 2004b). The task 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. 63
HFIDTC/WP1.1.3/10 Version 2/ 31 October 2005 Observational data from Barking substation and the NOC control room was used to conduct a HTA of the switching scenario. A HTA was then created, which acted as the primary input into the OSD diagram. Total co-ordination values for each teamwork task step are also annotated onto the OSD. The glossary for the OSD is presented in Figure 3-16. An extract of the HTA for the corresponding energy distribution task is presented after Figure 3-16. The corresponding extract of the OSD is presented in Figure 3-17. The operational loading figures are presented in Table 24. Table 24 - Operational loading results Agent Operatio n Receive Transport Decision Delay Total NOC 98 40 138 SAP 223 21 19 1 264 WOK 40 10 50 REC 15 14 29 The operational loading analysis indicates that the senior authorised person (SAP) at Barking substation has the highest loading in terms of operations, transport, and delay whilst the network operations centre (NOC) operator has the highest loading in terms of receipt of information. This provides an indication of the nature of the roles involved in the scenario. The NOC operators role is one of information distribution (giving and receiving) indicated by the high receive operator loading, whilst the majority of the work is conducted by the SAP at Barking, indicated by the high operation and transport loading figures. 64
Page 1 and 2:
Analysing C4i Activity: A Review of
Page 3 and 4:
HFIDTC/WP1.1.3/10 Version 2/ 31 Oct
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16: HFIDTC/WP1.1.3/10 Version 2/ 31 Oct
Page 65: HFIDTC/WP1.1.3/10 Version 2/ 31 Oct
Page 113: HFIDTC/WP1.1.3/10 Version 2/ 31 Oct
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?