120 likes | 318 Views
New to RCT DCS component 3.4.1. K. Grogg, M. Grothe. Access Control. Domain: RCT Groups: RCT_expert, RCT_operator Users: clazarid, efron, grothe, grogg, jleonard, pamc, tgorski, weinberg All RCT people belong to RCT_operator Almost all actions are available to operators
E N D
New to RCT DCS component 3.4.1 K. Grogg, M. Grothe
Access Control • Domain: RCT • Groups: RCT_expert, RCT_operator • Users: clazarid, efron, grothe, grogg, jleonard, pamc, tgorski, weinberg • All RCT people belong to RCT_operator • Almost all actions are available to operators • Users grogg & grothe also belong to RCT_expert • Expert has a couple more buttons available for development • We select what buttons/fields are accessible by whom • You must log in to take control of the FSM and have access to certain buttons • Non-RCT people will be able to look at the information, but not take any action
How to log into DCS • On FSM page, or the RMC subpages, click the lock icon in the upper right • Enter your NICE login name and password If you change your password, it might not be updated in PVSS for up to 8 hours
Access to FSM requires Login Logged In: Control of FSM Power_ON/OFF available Access to Alarm Panel NOT logged in: No control of FSM Can’t Power_ON/OFF Cannot see Alarm panel
Operator vs Expert Expert Experts can define new commands Operator A couple other areas within the expert panel are available only to Experts
Alert System • Variables in PVSS, filled from RMC responses, can be set up to auto-generate a Warning or Fault alert when at an undesirable value • These alerts show up automatically in the Alarm Panel • Additional notification actions can be added, such as sending emails or SMS • Severity of alarm will be indicated • Need to decide which variables should have alerts, and which should also have notifications added to them
Alert System Setup • Currently using the monitoring script to send emails and SMS to Monika, Pam, Kira, Jonathan, Jessica, when a Fault occurs • Will be expanded to more variables and all shifters by using the CMS framework alert system • Users and alerts mechanism is in place, but does not appear to be ‘activated’ • CMS alert system is still in development • Needs to be discussed with central DCS and tested with fake alarms • Will have monitoring script email and SMS alerts in place as a backup for now
Alerts Currently Set Up (in principle) • Monitoring script sends email and SMS to Monika, Pam, Kira, Jessica if RMC sends a Fault – i.e., any subsystem Failed • Within CMS framework, alerts will be sent to Monika, Kira, Pam, Jonathan, Christos, Jessica, Marc • Alert notification texts from CMS alert framework: • _RDBArchive.dbConnection.connected DISCONNECTED: FALSE • Our component is not connected to the database and changes to values are not being stored (check Log to see if reconnected) • RMC/RMC1.alarm ALARM: TRUE • RMC 1 Alarm triggered; OR of AlarmStatusFans, AlarmStatusCrates, AlarmStatusSupplies • RMC/RMC2.ONLINE OFFLINE: FALSE • RMC 2 is OFFLINE (no communication) • RMC/RMC3.crateA.secovertwarn WARNING: 30 • RMC 3, crate A has at least one temperature above warning threshold for at least 30 seconds
To Be Decided • Are there any other variables that need alerts? • Are there more variables that need a notification action added to the alert (email/sms)? • The +5V, +12V, -12V analog voltages? • Current in Warning? • Eventually central DCS should have an “RMC script is running” variable to let us know if we are operating • What action should the shifter take in event of alert?