Wonderware Historian + Citect SCADA 2016

Hi,

We have a Citect SCADA 2016 installed on our server. We are now considering adding Historian. Our solution provider has talked us about the new powerful Wondeware Historian which should connect to Citect SCADA using a 'connector' tool. We have a choice of installing the Historian on the same machine or onto another one.

What would you recommend?

  • It really depends on how much capacity your hardware or host machine has. I'd recommend you have them on separate machines so they aren't competing for resources. But I have seen customers with small systems that have SCADA, Historian and MES on the same machine.
    There are no known co-existence issues between these products, so you should be fine either way you chose.
  • I would recommend a separate installation for the Historian in almost every case. It would be really unusual to see a case of the Historian installed on the same machine as the SCADA because for systems that size it would usually not be justifiable to add a historian.
    Make sure you understand some of the significant limitations of using the Wonderware Historian with Citect. There is no integration of any historian client functionality back into Citect (the Connector just pushes data out to Historian). The Connector is very slow and for larger systems can be a concern. The Connector does not support some of the more sophisticated (and useful) features of the Historian such as the storage options that allow more sensible collection of data (swinging door deadband, minimum storage rate, rollover) - I find this really limiting and frustrating. Not all log messages are sent through to the Historian A&E - you have to do customised stuff in Citect to make it actually log all operator actions to historian. No support for the hierarchical (equipment model) representation in Historian. Diagnostics is poor. Discrete and Stirng tags get created with Historian tagnames appened with ".Discrete" and ".String".
  • We are in the midst of a similar setup.
    What i recommend is not put historian on the SCADA system.
    you can put the Citect connector to wonderware (v3 with latest update) on the citect server or if you can
    install on another machine so that you can setup redundancy. you can specify the primary and secondary server in the settings. this provides redundancy to Citect but the collector itself is not redundant.
    Wonderware historian should be on another server with enough capacity for the historian history files.
  • Hi, 

    I am Trying the same with CItect SCADA 2018 R2 ,  I am connecting with Wonderware Historian using Connect tool and managed to get the Trends from.  How do we historise the Events and Logs.  

    Anyone found solutions for this setup?

    pls provide link or solution