80 of 124  Construction of Giresun Wastewater Treatment Plant  Tender Dossier Volume 3 Employer’s Requirements  Section 8: Electrical Works  8.19.5 Engineering with Multiple User  8.19.6 Security  8.19.7 Operator Screens  Number of graphical displays to be used will not be restricted by software. Graphical pages will be resized notwithstanding with resolution where pages are formed or configured  or whether vector or bitmap graphs are used and without closing operator interface, without  8_Vol3_d4.3_Section 8 electrical works_en_GIR.rev8.doc  Access of unauthorized personnel to operation system should be able to be prevented. There should be mechanism in software for limiting access for individual user or user groups to access  to different areas of plant. Maximum 255 different plant areas should be able to be identified. It should be able to assign each graphical object to plants area also identify privilege level whether  authorization is granted for operator entry or whether object is visible or whether existing user in  certain plant areas will rely on certain privilege level. Access of unauthorized people to operation  systems should be able to be prevented. Ctrl, Esc, Ctrl Alt Del and similar windows hot keys should be  able to be disabled for preventing unauthorized access for operator. It should be able to define minimum 8 privilege level. Software should control user who logged in to  have correct privilege level in all functions. If user does not have correct privilege level for function or  object, it should be able to display message informing operator due to inadequate right. Request for one user to shut down system will not lead shut down in system, system should switch to  read only security status. Operator interface should be able to work integrated with windows firewall. Software should support  Operator interface users which are identified in a windows domain. Operator interface users should be  able to add, remove and provide access to Operator interface roles over windows domain server  without requiring to make change in Operator interface configuration. Identity information for  windows users whose identities are verified should be taken into cache memory securely in Operator  interface node for allowing to log in Operator Interface node in the event that control device is  unavailable in domain. Valid windows user should be able to open Operator Interface session  automatically and entering identity information again should not be necessary. Both internal operator  interface and windows users should be able to use. Software should be able to group users according to their roles. Roles should be identified clearly and  should be configured according to privilege levels and plant section. Security should be completely integrated to operator interface software for allowing access to any part  of system for users which have suitable security level. Security in server should be controlled and  passwords should be encoded. Operator interface should support double signature property, operations which have major importance  should not be operated without having approval from 2$^{nd}$ person. CMS software should support server-user structure in terms of engineering. Multiple engineering users  should be able to connect same engineering server at the same time and should be able to perform  activities such as commissioning, maintenance and failure tracking. Logic, visual or system  configuration changes which were made by engineering users should be recorded for security and  traceability. Thereby all changes which can be made in programs will be recorded. Engineering users  which are connected to same network should be able to make all operations as if they are in same  engineering server without having any restriction.