|Documentation||The definition of operator commands used for this infrastructure manager.|
|Children||designator (0..*), name (0..*), scope (0..*), textMessage (0..*)|
Elements may have different parent elements. As a consequence they may be used in different contexts.
Please, consider this as well as a user of this wiki as when developing this documentation further.
Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.
Introduced with version 3.2
Best Practice / Examples
The operator commands used for influencing the status of elements within the interlocking system can be predefined for a <specificInfrastructureManager> and referred to from any suitable element. The definition takes several parts of useful information.
- <name> - It contains the full name of the operator command in a given language.
- <scope> - It contains the additional information about the scope or the context where the command is used.
- <textMessage> - It contains any text message, which shall be displayed with the command, in a given language. The text may be of explanatory or warning type depending on the nature of the command.
- @acronym - The acronym or token of the command. This is mainly an abbreviation which is used in communication between the components and for display on HMI.
- @securityLevel - The nature of the command is defined whit respect to the safety affects in operation. Related with the level might be the functions of extra registration of the command and the use of special texts as defined in <textMessage>. Currently there are only two levels foreseen.
- normal - The normal level applies to any command which does not need special attention.
- vital - The vital level applies to any command where special attention is needed as the safety features of the interlocking are partly voided.