Historian Creating History Blocks in the future

I have an issue where my Historian has created 3 History blocks 4 months in the future.

It is storing a reasonable amount of valid process data there.

All platforms seem to have the correct time on them.

The Historian looks like it is struggling to manage this data and is responding poorly to data queries.

What would be the reason it stores data so far into the future.

AFAIK the time stamp of a Historized tag is determined at source on the application server where the data originates.

The Historian merges the data from all platforms and then stores the data into the appropriate block for the day.

Does anyone have any idea why this could be happening?

Thanks

Richard

Parents Reply
  • So it's typically one of two things - the data source (PLC) is not providing the right time and PLC is a type that can propagate the VTQ information, as opposed to the OI server providing the time stamp.

    The other thing it could be is time zone settings as the data is normally stored in UTC.  Sometimes people will mess up the timezone, but put the same time, so the offset in UTC ends up being wrong. 

    4 months though?  that seems very specific given now that we have another user mentioning it below.  I'd call in to support. 

Children