Foreword |
|
xv | |
Preface |
|
xvii | |
Contributors |
|
xxi | |
|
|
xxv | |
|
|
xxvii | |
Part I Human performance |
|
1 | (98) |
|
|
3 | (14) |
|
|
|
3 | (1) |
|
|
4 | (1) |
|
How are errors classified? |
|
|
5 | (2) |
|
|
6 | (1) |
|
|
6 | (1) |
|
What are the causes of errors? |
|
|
7 | (1) |
|
Do errors lead to accidents? |
|
|
8 | (4) |
|
|
10 | (1) |
|
|
10 | (2) |
|
|
12 | (1) |
|
|
13 | (4) |
|
|
14 | (1) |
|
|
14 | (3) |
|
Memory and complex skills |
|
|
17 | (18) |
|
|
|
17 | (1) |
|
|
18 | (3) |
|
Skill-based, rule-based and knowledge-based performance |
|
|
21 | (2) |
|
Naturalistic decision-making |
|
|
23 | (1) |
|
Skilled long-term working memory |
|
|
24 | (2) |
|
|
26 | (1) |
|
Implicit memory and skilled performance |
|
|
27 | (1) |
|
Cognitive aspects of performance in the management of complex systems |
|
|
28 | (1) |
|
|
28 | (7) |
|
|
30 | (5) |
|
|
35 | (16) |
|
|
|
35 | (1) |
|
|
36 | (2) |
|
|
37 | (1) |
|
Vigilance and performance |
|
|
38 | (1) |
|
Work and task factors and vigilance |
|
|
38 | (6) |
|
The influence of workload |
|
|
38 | (1) |
|
|
39 | (1) |
|
|
40 | (1) |
|
|
41 | (2) |
|
Shifts, circadian rhythms and sleep disruptions |
|
|
43 | (1) |
|
Work environment influences on vigilance |
|
|
44 | (1) |
|
|
45 | (2) |
|
Vigilance characteristics and qualities in people |
|
|
45 | (2) |
|
|
47 | (2) |
|
Management-driven enhancement methods |
|
|
47 | (1) |
|
Training to enhance vigilance |
|
|
48 | (1) |
|
Technology-driven enhancement methods |
|
|
48 | (1) |
|
|
49 | (2) |
|
|
49 | (2) |
|
|
51 | (18) |
|
|
|
51 | (1) |
|
Situation awareness - a perspective |
|
|
52 | (4) |
|
The cognitive perspective |
|
|
52 | (2) |
|
The interactionist perspective |
|
|
54 | (1) |
|
A situated cognition perspective |
|
|
55 | (1) |
|
A situation awareness process model |
|
|
56 | (3) |
|
|
56 | (1) |
|
|
56 | (1) |
|
|
57 | (1) |
|
|
57 | (2) |
|
A system situation awareness model |
|
|
59 | (1) |
|
SAPAT-SA process analysis technique |
|
|
59 | (5) |
|
Stage I: identify system SA sources |
|
|
61 | (1) |
|
Stage II: preliminary hazard identification |
|
|
61 | (2) |
|
Stage III: identify hazardous interactions |
|
|
63 | (1) |
|
Stage IV: analyse hazardous interactions |
|
|
63 | (1) |
|
Stage V: interpret results and suggest safe design solutions |
|
|
64 | (1) |
|
SAPAT and safe interactions |
|
|
64 | (2) |
|
|
64 | (1) |
|
|
65 | (1) |
|
|
66 | (3) |
|
|
67 | (2) |
|
|
69 | (10) |
|
|
|
|
|
69 | (1) |
|
Control room team failures |
|
|
70 | (2) |
|
Defining the team and teamwork |
|
|
72 | (3) |
|
|
75 | (4) |
|
|
76 | (3) |
|
Training for control room tasks |
|
|
79 | (20) |
|
|
|
79 | (2) |
|
Relating training to the task |
|
|
81 | (3) |
|
|
81 | (2) |
|
Task analysis in human factors design |
|
|
83 | (1) |
|
Setting the criteria for performance |
|
|
84 | (2) |
|
Performance measurement in system design and development |
|
|
86 | (1) |
|
|
86 | (6) |
|
Aspects of skill and skill acquisition |
|
|
86 | (3) |
|
The instructional cycle in mastering operational skills |
|
|
89 | (1) |
|
|
90 | (2) |
|
The role of simulation in training for control room tasks |
|
|
92 | (4) |
|
|
92 | (1) |
|
Representing the system being controlled |
|
|
93 | (1) |
|
Providing simulation in practice |
|
|
94 | (2) |
|
|
96 | (3) |
|
|
97 | (2) |
Part II Methods |
|
99 | (88) |
|
Humans and machines: Allocation of function |
|
|
101 | (16) |
|
|
|
101 | (1) |
|
|
102 | (2) |
|
|
104 | (2) |
|
Mutual understanding and authority |
|
|
104 | (2) |
|
|
106 | (1) |
|
Designing for interaction |
|
|
106 | (1) |
|
|
107 | (3) |
|
Trust between operators and machines |
|
|
110 | (1) |
|
|
111 | (1) |
|
|
112 | (5) |
|
|
113 | (4) |
|
|
117 | (16) |
|
|
|
117 | (3) |
|
Skills required for task analysis |
|
|
117 | (1) |
|
A model of the task analysis process |
|
|
118 | (2) |
|
|
120 | (5) |
|
|
120 | (1) |
|
Selection of task analysis methods |
|
|
120 | (2) |
|
Selection of data sources |
|
|
122 | (2) |
|
Scenario selection and development |
|
|
124 | (1) |
|
|
125 | (3) |
|
Using existing data sources |
|
|
125 | (1) |
|
|
126 | (1) |
|
|
127 | (1) |
|
|
128 | (2) |
|
Hierarchical task analysis (HTA) |
|
|
128 | (2) |
|
|
130 | (1) |
|
|
130 | (1) |
|
Analysis of informational requirements |
|
|
131 | (1) |
|
Representation of task sequence |
|
|
131 | (1) |
|
Temporal requirements and workload |
|
|
131 | (1) |
|
|
131 | (1) |
|
|
131 | (1) |
|
|
132 | (1) |
|
|
132 | (1) |
|
Training and technology for teams |
|
|
133 | (18) |
|
|
|
|
|
133 | (9) |
|
Analysis; Identifying what needs to be trained |
|
|
134 | (2) |
|
Design: Identifying how to train team competencies |
|
|
136 | (1) |
|
Conduct: Training practice |
|
|
137 | (2) |
|
Evaluation: Evaluating the effectiveness and impact of the training |
|
|
139 | (1) |
|
What are the implications of team training for control room operations? |
|
|
139 | (3) |
|
|
142 | (3) |
|
GroupWare design considerations |
|
|
143 | (2) |
|
Designing for teams: An integrated approach |
|
|
145 | (3) |
|
|
146 | (1) |
|
|
146 | (1) |
|
|
147 | (1) |
|
Simulation-evaluation phase |
|
|
147 | (1) |
|
|
148 | (1) |
|
|
148 | (3) |
|
|
149 | (2) |
|
Naturalistic analysis of control room activities |
|
|
151 | (18) |
|
|
|
|
151 | (1) |
|
|
152 | (1) |
|
Tracking events through a fragmented environment |
|
|
153 | (5) |
|
The world beyond the image |
|
|
158 | (1) |
|
|
159 | (1) |
|
General and design issues |
|
|
160 | (3) |
|
|
163 | (6) |
|
|
164 | (1) |
|
|
165 | (4) |
|
Development of a railway ergonomics control assessment package (RECAP) |
|
|
169 | (18) |
|
|
|
|
|
169 | (1) |
|
|
170 | (4) |
|
Discussion of specific human factors issues |
|
|
174 | (5) |
|
|
174 | (2) |
|
|
176 | (1) |
|
|
177 | (2) |
|
Feedback of results to respondents |
|
|
179 | (1) |
|
General methodological issues |
|
|
179 | (4) |
|
Reporting of cognitive processes via questionnaires |
|
|
179 | (1) |
|
Field-based research vs. simulation |
|
|
180 | (1) |
|
Distinction between operator and control system |
|
|
181 | (1) |
|
|
181 | (1) |
|
Issues associated with longitudinal studies |
|
|
182 | (1) |
|
Guidelines and recommendations |
|
|
183 | (4) |
|
|
184 | (1) |
|
|
184 | (3) |
Part III Control roam design |
|
187 | (120) |
|
Control room mock-up trials |
|
|
189 | (18) |
|
|
|
189 | (1) |
|
Lack of `top down' approach |
|
|
189 | (1) |
|
Impact of increasing automation on control room operation |
|
|
190 | (1) |
|
Team working and job satisfaction |
|
|
190 | (1) |
|
Why do we need a control room standard? |
|
|
191 | (1) |
|
The structure of the control room ergonomics standard |
|
|
192 | (7) |
|
Part 1 - principles for the design of control centres |
|
|
193 | (1) |
|
Part 2 - principles for the arrangement of control suites |
|
|
194 | (1) |
|
Part 3 - control room layout |
|
|
195 | (2) |
|
Part 4 - layout and dimensions of work-stations |
|
|
197 | (1) |
|
Part 5 - displays and controls |
|
|
198 | (1) |
|
Part 6 - environmental requirements for control centres |
|
|
198 | (1) |
|
Part 7 - principles for the evaluation of control centres |
|
|
199 | (1) |
|
Case study: Railway signalling upgrade and control room ergonomics |
|
|
199 | (6) |
|
|
205 | (2) |
|
|
206 | (1) |
|
|
207 | (16) |
|
|
|
207 | (1) |
|
Functional requirements for alarm systems |
|
|
208 | (1) |
|
Designing individual alarms |
|
|
208 | (3) |
|
|
209 | (1) |
|
|
209 | (1) |
|
|
209 | (1) |
|
|
209 | (1) |
|
|
210 | (1) |
|
|
210 | (1) |
|
Design of alarm handling systems |
|
|
211 | (4) |
|
Measuring system performance |
|
|
215 | (4) |
|
|
219 | (2) |
|
|
221 | (2) |
|
|
221 | (1) |
|
|
221 | (2) |
|
Decision support in process control plants |
|
|
223 | (16) |
|
|
|
|
223 | (1) |
|
Human information processing |
|
|
224 | (1) |
|
Decision support for operators |
|
|
224 | (3) |
|
Situations for supporting the operator |
|
|
225 | (1) |
|
Types of decision support and roles of decision support systems |
|
|
226 | (1) |
|
Case-based reasoning as decision support |
|
|
227 | (2) |
|
A case-based reasoning approach for fault diagnosis |
|
|
228 | (1) |
|
|
229 | (1) |
|
The importance of the user interface |
|
|
229 | (5) |
|
|
230 | (1) |
|
Visual decision support for case-based reasoning approach |
|
|
230 | (1) |
|
Metaphors used in visualisation |
|
|
231 | (1) |
|
|
232 | (2) |
|
|
234 | (2) |
|
|
236 | (3) |
|
|
236 | (3) |
|
Train controllers, interface design and mental workload |
|
|
239 | (20) |
|
|
|
239 | (1) |
|
Mental workload and related factors |
|
|
240 | (2) |
|
Identification and analysis of specific workload sources |
|
|
242 | (9) |
|
Task 1: Issue train order (TO) or authority (ASW) |
|
|
243 | (2) |
|
Task 2: Establish authority queue (ASW only) |
|
|
245 | (1) |
|
Task 3: Fulfil train order (TO) or relinquish authority (ASW) |
|
|
246 | (2) |
|
Task 4: Report location - field |
|
|
248 | (1) |
|
Radio transmission problems and ASW alarms |
|
|
249 | (2) |
|
Different dimensions of controller workload |
|
|
251 | (2) |
|
Overall differences between TO and ASW in workload dimensions |
|
|
253 | (1) |
|
Quantifying overall workload |
|
|
254 | (1) |
|
Future monitoring of ASW workload levels |
|
|
254 | (2) |
|
Possible indicators of imminent `overload' |
|
|
255 | (1) |
|
Implications for interface design |
|
|
256 | (3) |
|
|
256 | (1) |
|
|
257 | (2) |
|
Power generation: The advanced control desk |
|
|
259 | (14) |
|
|
|
|
259 | (2) |
|
The integrated operator interface |
|
|
261 | (1) |
|
From business to plant and back |
|
|
261 | (2) |
|
The key system interfaces |
|
|
263 | (3) |
|
Electronic dispatch and logging (EDL) |
|
|
263 | (1) |
|
Start-up management system (SMS) |
|
|
264 | (1) |
|
Integrated load monitoring (ILM) |
|
|
265 | (1) |
|
Operational information system (OIS) |
|
|
266 | (1) |
|
The transition from hard desk to `soft desk' |
|
|
266 | (6) |
|
Philosophy and physical layout |
|
|
267 | (1) |
|
Navigational considerations |
|
|
268 | (1) |
|
|
269 | (3) |
|
|
272 | (1) |
|
|
272 | (1) |
|
Human-centred design for railway applications |
|
|
273 | (20) |
|
|
|
|
273 | (1) |
|
|
273 | (2) |
|
Case study 1: Training wrong behaviours |
|
|
275 | (2) |
|
Case study 2: Low frequency high impact events |
|
|
277 | (5) |
|
|
277 | (1) |
|
|
278 | (1) |
|
Two-channel safety approach |
|
|
278 | (1) |
|
Initial approach: piggyback interdiction signal |
|
|
279 | (1) |
|
Driver's eye view of the initial approach |
|
|
279 | (2) |
|
Critical review of the approaches taken |
|
|
281 | (1) |
|
|
281 | (1) |
|
Case study 3: Controlling speed on TGV Nord |
|
|
282 | (1) |
|
Case study 4: Dispatching and train graphs |
|
|
283 | (2) |
|
|
283 | (1) |
|
Static information and timetables |
|
|
284 | (1) |
|
Computer control with paper supervision |
|
|
285 | (1) |
|
Case study 5: The impact of the systems model on operational communications |
|
|
285 | (5) |
|
Definition of system databases |
|
|
286 | (2) |
|
Implementation of systems integration |
|
|
288 | (1) |
|
|
289 | (1) |
|
|
289 | (1) |
|
|
290 | (3) |
|
|
290 | (1) |
|
|
291 | (2) |
|
Integrated platform management system design for future naval warships |
|
|
293 | (14) |
|
|
|
|
293 | (1) |
|
Demands of the twenty-first century |
|
|
294 | (1) |
|
|
295 | (1) |
|
|
296 | (2) |
|
|
297 | (1) |
|
Integrated platform management system |
|
|
297 | (1) |
|
|
298 | (1) |
|
|
298 | (2) |
|
|
300 | (3) |
|
|
300 | (1) |
|
|
301 | (1) |
|
|
301 | (2) |
|
Integrated platform management system |
|
|
303 | (3) |
|
|
306 | (1) |
|
|
306 | (1) |
Index |
|
307 | |