Wonderware Historian + Citect SCADA 2016

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".

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".