Mode-switch

During normal run-time operations, a mode-switch can be accomplished with easy eXtended Operator Station (ezXOS). Using this interface, you can perform mode-switches by selecting the provided button.

Switching between two modes of operation is referred to as a "Mode-Switch".The ezXOS interface clearly shows which modes are currently active. As a Controller, you can view the underlying privileges; however, all you need to know to switch modes is the name of the mode to which the current should be changed.

For example, at 7:00PM, a mode-switch to something like the "Night Operating Mode"may be performed. At 7:00AM, another mode-switch to the "Day Operating Mode" would take place.

Clearly, it is important to decide on and configure the different operating modes and privileges at the time of system staging. It is expected that the configuration of privileges and modes will be set up once at the beginning of the project.

Notes: Mode-switching can be automated using jsh on a per project basis, since the underlying Controller command is the execution of an RPC against the RealTime Server.

If a mode switch is performed that changes the owning system of a recently commanded device (for example, an analog setpoint command), and that command has not completed, the command is not guaranteed to complete. Furthermore, the system may not generate an alarm or log an event when a command either succeeds or fails. If the recently commanded system is disconnected (for example, via a network disconnect or shutdown event) from the new owning system immediately after the mode switch, then a command-in-progress Tag or FlexTag may remain on the recently command point. A Controller would have to manually delete the Tag/FlexTag through the ezXOS Tag or FlexTag Summary, as appropriate.