• Replies 5 replies
  • Subscribers 585 subscribers
  • Views 342 views
  • Users 0 members are here
Options
Related

Operator Logs to SQL

Mike

Has Citect (PlantSCADA) setup anyway to have defauts to log operator actions robustly and completely? 

Most mainstreams SCADA;s now have this capability, however with CitectSCADA/PlantSCADA you can build up your own SuperGenies hence it seems the only way is to build this in is as you build each SuperGenie.  Whilst this is flexibible, it is also problematic as it has to be tested to every action...... 

Is it possible to log all data written to tags by reading a queue or something??  Even  if you could would the logging necessarily make sense?

My experience is this is not possible, but want to check with the wider community.

Anyone got any great examples of operator action logs, ie who did what and when... 

Regards,

Mike

Parents

  • There is no open-box log device in type of SQL but it is possible for you to set it up yourself.

    You could refer to the following KB article for how-to set up a device of SQL-DEV type.

    https://softwaresupportsp.aveva.com/#/knowledgebase/details/000029969?lang=en_us

    Write a your own Cicode function to decide what needs to be logged.

    Then in configuration of the security roles, call your function in Entry Command and Exit Command for capturing user sign in/out activities. 

    Similarly, you can log other messages into this log device, such as tag write operations. For example, use cicode function TagSubscribe with a callback function. When the value of the subscribed tag changes, the callback function will be fired. Then you get the value and log it along with other info into the device.

    Hope this would help.

Reply

  • There is no open-box log device in type of SQL but it is possible for you to set it up yourself.

    You could refer to the following KB article for how-to set up a device of SQL-DEV type.

    https://softwaresupportsp.aveva.com/#/knowledgebase/details/000029969?lang=en_us

    Write a your own Cicode function to decide what needs to be logged.

    Then in configuration of the security roles, call your function in Entry Command and Exit Command for capturing user sign in/out activities. 

    Similarly, you can log other messages into this log device, such as tag write operations. For example, use cicode function TagSubscribe with a callback function. When the value of the subscribed tag changes, the callback function will be fired. Then you get the value and log it along with other info into the device.

    Hope this would help.

Children
No Data
© 2024 AVEVA Group Limited or its subsidiaries. All Rights Reserved.