Asle Frantzen
My feedback
-
111 votesEVALUATING · 13 comments · Customer Portal & PI Square » Customer Portal Overall · Flag idea as inappropriate… · Admin →Asle Frantzen
supported this idea
·
-
1 voteAsle Frantzen
shared this idea
·
-
3 votesAsle Frantzen
supported this idea
·
-
7 votes0 comments · Customer Portal & PI Square » PI Square Online Community · Flag idea as inappropriate… · Admin →Asle Frantzen
supported this idea
·
-
9 votes0 comments · Customer Portal & PI Square » PI Square Online Community · Flag idea as inappropriate… · Admin →Asle Frantzen
supported this idea
·
-
2 votes1 comment · Customer Portal & PI Square » PI Square Online Community · Flag idea as inappropriate… · Admin →Asle Frantzen
supported this idea
·
-
13 votes2 comments · Customer Portal & PI Square » PI Square Online Community · Flag idea as inappropriate… · Admin →Asle Frantzen
supported this idea
·
-
12 votes2 comments · Customer Portal & PI Square » PI Square Online Community · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment Asle Frantzen
supported this idea
·
-
13 votes
An error occurred while saving the comment Asle Frantzen
commented
Hiding them would be great. Is it possible to add this to the Tools->Options dialog? Just a simple setup with the option to hide non-essential element tabs
Asle Frantzen
supported this idea
·
-
3 votes
An error occurred while saving the comment Asle Frantzen
commented
Yes, I think a clear and meaningful name of the database will benefit "everyone". I understand it's under the hood, to some extent, but keeping working titles and code names 10-15 years after a product launch isn't really necessary. And looking at the naming convention for databases in newer products, such as the PiIntegratorDb, it certainly makes it easier to deal with. Renaming a database for an important product such as PI AF isn't really for the faint hearted, I'm not sure if there's a KB article for it or not, but it's not really something people want to mess around with. Much better if OSIsoft introduces the change.
Asle Frantzen
shared this idea
·
-
111 votes7 comments · Customer Portal & PI Square » Customer Portal Overall · Flag idea as inappropriate… · Admin →Asle Frantzen
supported this idea
·
-
150 votesAsle Frantzen
supported this idea
·
-
13 votesAsle Frantzen
supported this idea
·
-
70 votes
An error occurred while saving the comment Asle Frantzen
commented
We monitor some buildings at different sites, and have climate sensors in each room. We want to display all temperature measurements from all rooms in a building in one trend, regardless of the number of rooms.
Some buildings have 20 rooms while others only have 3.
Today we're building the semicolon separated list of paths to the attributes using PI SQL, and appending that to the PI Vision adhoc trend URL, in order to accomplish our goal. Many steps for a simple task.
Asle Frantzen
supported this idea
·
-
2 votesAsle Frantzen
shared this idea
·
-
3 votesAsle Frantzen
supported this idea
·
An error occurred while saving the comment Asle Frantzen
commented
Hi Steve. Ben created this feedback item for me.
We're doing a project for a T&D company, and they have done a large IoT project together with some partners. The project aims to give extra insight in their switchgear operations with all the benefits of inexpensive, stand-alone sensor units, which can be retro-fitted to any circuit breaker, disconnector, earthing switch, etc.
Their transmission system is relatively stabile, resulting in not many switchgear operations. If one operation occurs at a circuit breaker, it could easily be a year until the next operation (or they could occur back-to-back for a few repetitions).
Once something happens, they record everything - and need to do it with precision. An operation may result in 10 000 values, and a whole motor current event may have a duration of 200 ms. This is my event frame!
In the case I reported to techsupport, I'm missing 11 out of 12 values occuring within the last millisecond of the event. That is, between 2019-11-27 14:26:33.0340000 and 2019-11-27 14:26:33.0349167. The latter timestamp is the end time I'm trying to set, but both PI System Explorer and AF SDK simply truncates everything less than 1 ms. Had it actually rounded the number up to .035 all my time series data would have been included, so that's what I'll be doing programmatically now.
-
4 votesAsle Frantzen
shared this idea
·
-
5 votes
An error occurred while saving the comment Asle Frantzen
commented
I have a scenario where I first need to look up a GUID and a timestamp from one table, this is done in my element. Both are table provided time series lookups The timestamp will "trigger" creating new event frames by using the step continuous method.
Once the event frame is created I will need to reference the GUID inside the EF, which in turn will be used to collect the time series data from another table. But since my GUID isn't a PI Point DR I will need to use String Builder to collect it, and with that I only have the value at the end of the event frame (which consequently is the start of the next EF), leaving me with the GUID of the next EF.
Asle Frantzen
supported this idea
·
-
41 votesAsle Frantzen
supported this idea
·
-
27 votes
Most software we deal with on a daily basis allows pasting of images, so this is an important feature to include.