Does the reporting module need to also have the tag historian licensed?

Our architecture design is set up to have three main gateways at three sites, they each have tag historian module and log data to their own SQL as well as to the other 2 using the historian splitter. then we have a "front end" gateway with perspective and the reporting module. This gateway doesn't have any PLC comms, it's just hosting the perspective views and the views get data through the gateway network. So now I'm trying to use a "Report". It works but only if I activate the 2 hour trial on the front end gateway, otherwise the values come back as "NA". The tag_history_query binding I am using as the data for the report is connected to the SQL database on the main gateway that is populated from the PLC data.

So why won't the reports work? Is this behavior as designed? It doesn't seem right because the reports should work with any database, I'm not trying to write data to it, just query it.

Tag history bindings and queries are part of the Tag Historian module, not the platform. You need the module both to push data into history, and to pull it out.

There's a query only version of the historian module you can get for front end gateways.

2 Likes