Background: we have a solution where we log a OPC vt_date field to a local scada logfile in local time (i.e. GMT+1 / DST). This local logfile is read via OPC HDA interface into the PI data archive. This is than presented in asset framework as an attribute named date (the excel-type date (i.e. 45605,085938 = 9-11-2024 03:03:45 GMT). The problem is that the excel-type date is not human readable, and not useable in PIvision. Also I would like to see 'real' date and not just the GMT one. To correct this we came up with the following formulas in AF (no extra pipoint needed). 1 attribute is for the pipoint containing excel-type date named date, 1 extra hidden attribute (named dateconverted for example) with "A=|Date;[( A-25569) * 86400]" with value type datetime to convert from excel to epoch and 1 extra hidden string builder attribute with value type double (type conversion) named offset with "replace(Left(Right(Format(dateconverted, O, "nl-NL"), 5), 2),'0','');" (O beeing the datetype that includes the offset from GMT, we extract the offset and convert it to a double) This is than used in the final attribute (named DateTime) with formula "A=Offset;B=dateconverted;[B-(A*3600)" with value type datetime. This way we can work around the pipoint not beeing stored in UTC and we can show the date in pivision.. Hope this makes sense!