Laine
My feedback
-
1 voteLaine
supported this idea
·
Laine
shared this idea
·
-
43 votesLaine
supported this idea
·
-
29 votesLaine
supported this idea
·
-
139 votesLaine
supported this idea
·
-
37 votesLaine
supported this idea
·
-
62 votesLaine
supported this idea
·
-
54 votesLaine
supported this idea
·
-
10 votesLaine
supported this idea
·
-
13 votesLaine
supported this idea
·
-
52 votesLaine
supported this idea
·
-
6 votesLaine
supported this idea
·
-
2 votesLaine
supported this idea
·
-
25 votesLaine
supported this idea
·
-
19 votes
Currently interviewing customers – if you would like contribute to the research on how this should best work, I’d be happy to discuss – please email Dave at dcasazza@osisoft.com.
-
11 votes
We have a third party application that processes our individual plant locations’ environmental data and it requires a 00:00 timestamp. Each local location’s PI server sends data to the corporate PI server which is Central Time and the third party application then consumes the data. The 00:00 timestamp does not pose an issue for the local PI servers that are also Central Time, however in this particular case the local PI Server is Mountain Time an hour behind Central. Being the tags are from AF analyses I do have the option to adjust the timestamp relative to trigger time for some of the tags but this may not always be the case; plus the local locations also use the data and desire a 00:00 timestamp as well.
I will eventually have issues with Eastern sites which are an hour ahead of Central.
Are there any other options (interface/ tag configuration) other than adjusting the AF timestamp relative to trigger time to force the timestamp to be 00:00 central time which would be 22:00 for the previous day which would not work for local usage