Loading…

DTP2 control room operator and remote handing operation designer responsibilities and information available to them

The purpose of the Divertor Test Platform 2 (DTP2) is to demonstrate the proof-of-concept level operations of ITER divertor maintenance devices, by remotely handling them from a dedicated control room. In order to verify safe and reliable remote handling (RH) maintenance operations, it is vital to r...

Full description

Saved in:
Bibliographic Details
Published in:Fusion engineering and design 2011-10, Vol.86 (9), p.2078-2081
Main Authors: Aha, L., Salminen, K., Hahto, A., Saarinen, H., Mattila, J., Siuko, M., Semeraro, L.
Format: Article
Language:English
Subjects:
Citations: Items that cite this one
Online Access:Get full text
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary:The purpose of the Divertor Test Platform 2 (DTP2) is to demonstrate the proof-of-concept level operations of ITER divertor maintenance devices, by remotely handling them from a dedicated control room. In order to verify safe and reliable remote handling (RH) maintenance operations, it is vital to repeat them equally every time. The operations shall be validated and restored beforehand by RH operation designers. During the actual operation the control room operators are following predefined operation sequences. After time passes, even the validated operation details will change and the sequences improve, but these changes should not be done during the actual operation. It is fundamental from safety perspective that the control room operator will not be able to make unintentional actions. Hence, during the operation the irrelevant information shall not be available to him. Also the software functionality available for other purposes than executing the operation shall be made invisible. Therefore, making careful user interface design is certainly relevant when designing control room sub-systems. In this paper, we introduce the current control room sub-systems used at the DTP2.We suggest utilizing user groups and user-centered design in the software development and implementation done in user group fashion is described.
ISSN:0920-3796
1873-7196
DOI:10.1016/j.fusengdes.2011.03.040