Source linkage: DeltaV Source - Batch Executive Source

Within the settings of the batch historian (DeltaV Historian Administrator's interface) there is a possibility to link a DeltaV Source with a batch executive source. Through the help and books online I understand that it is possible to link de batch historian and the process historian. This would be very usefull for troubleshooting when something went wrong. I've linked to sources, but I do not see any changes in the logging. There is no difference in the process history view or in the batch history view. Where can you find or see the combined logs?

1 Reply

  • Jeroen,

    The process of creating source linkage does not actually aggregate the data.  It simply places a record in the batch historian that denotes the data should be associated.   That reference is then used by a batch historian client.

    In the case of alarm and event data, the chronicle must be set as an input to the batch historian.  The tables in the batch historian which store chronicle data are then available for union with items from the batch hiearchy tables via the Source linkage view. For continuous process data, this data resides in a different database.

    You could (I'd like to!) build a client that aggregates Batch/Chronicle/Continuous data via SQL and OPCHDA which utilizes the source linkage. This client could use the source linkage definitions to pull the three data sources cohesively,  based on time and equipment.  Of course, if you were inclined to do this, you'd probably be inclined to build the source linkage definition into your client directly.