Re: [SystemSafety] Language issues, control systems

From: ECHARTE MELLADO JAVIER < >
Date: Mon, 27 Apr 2015 16:08:05 +0000


Maybe you can transfers an SRAC (application condition) to the specific projects in order to evaluate (or check) the translation with the Final User or Client. Sometimes it is difficult to translate railways terminology.

Even in the former language it is not easy to understand or change between different operators. For example, in the Signaling Control Center in Spain we use “comando especial” (special command….) to designate commands that needs double confirmation (most of them safety related). I have never understood the word “special”….maybe, they do not want to use “safety command” (because the Control Center is some sort of PC… being difficult to demonstrate a SIL…never ending story…).

Enviado el: lunes, 27 de abril de 2015 11:51 Para: systemsafety_at_xxxxxx Asunto: [SystemSafety] Language issues, control systems

Dear all,

I was wondering if anybody has any experience with SIL certifications where the final product should be usable in two different languages. For example, a centralized control system of any type, SCADA, etc. My question is if there are any potential hazards associated with an incorrect translation, what would be the best way to go about mitigating them? Would it be valid, for example, to use two translators and then cross-check the resulting translations, analyzing inconsistencies? The translations would be for the commands available on the HMI.

Really what I am trying to determine is the most common way of dealing with this issue during SIL certifications, as there may be more than one. That is, can it be considered as part of the generic product (no, I suspect), should it be considered as part of the specific application, can it be considered a SRAC, should it be dealt with during FAT…..? I work in the railway industry, but I imagine that this could be an issue in any industry where control systems are used. Thanks in advance.

Kind regards,

Myriam.



The System Safety Mailing List
systemsafety_at_xxxxxx Received on Mon Apr 27 2015 - 18:08:15 CEST

This archive was generated by hypermail 2.3.0 : Tue Apr 23 2019 - 01:17:07 CEST