I work for a software company that sells a process historian. We have a customer that is interested in us creating an integration between our product and Ignition.
I have been looking at the SDK documentation. It has been suggested by a technical support person that we may want to create our own custom Tag Historian module. Does this sound like a good approach? Are there other approaches?
If we create a custom Tag Historian module, will the user then use the normal Ignition configuration options to define what tags they want to historize and those tags will be passed to our module along with their data value changes? Or will we need to create our own tag configuration and read/subscribe to the tags the user wants to historize?
Also, if we create a custom Tag Historian module, will we need to support functions for reading historical data to the Ignition system or can it be “write-only”. If we have to support read functions are those SQL statements or some other defined interface?
Thanks,
Mark