AdminStephen Kwan
(Product Manager, OSIsoft)
My feedback
-
25 votes
-
1 vote
Which version are you using?
-
1 vote
Can you help me understand how this would be different than the current "Evaluate" button that you can use to evaluate the expressions immediately?
-
7 votes
You can do that with currently shipping software. Just configure an attribute with a Formula Data Reference and a %StartTime% or %EndTime% substitution parameter.
This would not work if you wish to write the start and end time to a PI Point.
If I have misinterpreted your needs, please let me know.
Can you provide some example use cases?
-
1 vote
This is problematic as you can have more than one AF attribute that is referencing the same PI Point within a given Element. In addition, if you use indirect reference within the configuration of a PI Point Data Reference attribute, this becomes even more confusing.
On thing you might consider doing is if you only want to work with PI Point names, is to simply name your attribute the same as your PI Point name. In general we don't recommend this as you would then not be using your AF as effectively as possible.
-
5 votes
With the introduction of the new Notifications, the prefer way to view the notifications history is via PI Vision. Have you considered doing that?
-
100 votes
Thanks for your feedback. We're looking at your Usecase1 right now via tech support escalation. As to Usecase3, the upcoming release should help you if your CPU is not being fully utilized. We'll reach out to you via your existing tech support case (Usecase1).
In response to Wilson Laizo Filho, "We had before, but we shouldn't have any..."
Wilson,
I started writing a long reply back to you but then I realized that we may not be talking about the same thing. Is your startup time slow, meaning when you restart PI Analysis Service? Or do you mean something else like the rollup analysis takes longer to complete than what you would like?
--
Steve KwanIn response to Wilson Laizo Filho, "Hi Steve, in my case I'm using 2017R2. I..."
Hi Wilson,
Thanks for the info. I'm curious if you have missing PI Points in your rollups?
--
Steve KwanIn response to Wilson Laizo Filho, "Hi Steve, of course I don't know the int..."
Hi Wilson, which version are you using? The 2017 R2 and 2018 releases both have a lot of improvements to: 1) help identify the root cause of lags and 2) remove several bottlenecks. In addition, the 2018 release has a nifty feature that when you do a Preview (and also Evaluate) PI System Explorer gives you additional information on how long an execution took.
I'm not disputing that scaling out PI Analysis Service would help in some instances, but I want to make sure we understand the real reason behind any lag. If signups are slow, then is it possible the PI Data Archive is over-worked? In that case, multiple instances of PI Analysis Service make cause additional issues with your (overall) PI System as a whole. Often times, what we find is that users can remove a lot of lag by ensuring they don't unnecessarily tax their PI System. For example, do you have missing PI Points in your inputs such that you're causing excess round trips to query for a PI Point? Are you doing year-to-date summaries with every execution cycle? Are you repeated doing a sub-calculation when you can just do it once and reference it as a "Variable"?
Not trying to avoid the problem, but rather I'm interested in making sure we solve the right problem.
--
Steve KwanIn response to Lal Babu Shaik, "We have configured all calculations in A..."
If by adding RAM and CPU provide no significant change, then it's likely that the bottleneck is not with PI Analysis Service. If that were the case, I don't necessarily think that multiple instances of PI Analysis Service would necessarily remove the bottleneck. Do you know why your calculations are lagging for 12 hours? Do you have a very large dependency chain such that you're being blocked by an expensive analysis? Are you doing large summaries that is taking a long time? Are you triggering faster than the end-to-end calculation time of your analyses? I would suggest that you call tech support so they can help you pinpoint the problem.
--
Steve KwanAnalytics High Availability is implemented via Windows Server Failover Clustering. When one PI Analysis Service fails, WSFC reroutes to the other PI Analysis Service. Currently there can only be one PI Analysis Service instance per AF Server.
Wilson,
We need to take a closer look at your system. It's not necessarily a good idea to just throw hardware and brute strength to solve every problem. Looking at your description, it should not take 1.5 hours to start. Which version of software are you running? We fixed a couple of issues that dramatically reduced start time with recent release(s). Do you have a lot of missing PI Points in your rollups? How often are your rollups being triggered? Are you in a situation where you're triggering more often that you think due to the rollups having so many inputs? You're welcome to email me directly, especially if you have a current tech support case. -
2 votes
In order to accomplish this, there would need to be a way to store the information - i.e. when you identify a critical point, the fact that it's identified has to be recorded and stored so that when the next person accesses these points, the information is available. In a way, this is metadata that arguably should be stored in the AF database. I'm curious why you consider using AF as a workaround. Can you elaborate?
-
1 vote
Have you tried using PI Builder?
-
1 vote
The CreateConfig option is the same as if you right-click the element in PI System Explorer and selecting Create or Update Data Reference. Is that something that would suit your needs?
What are you trying to update with the attributes? Are you using the utility to do a CreateConfig, Repair, or ReplacePIServer?
-
2 votes
Have you considered using PI AF for this?
-
3 votes
Which version of AF are you using? In recent versions, we allow you to search by individual analysis templates in the management plugin and we also allow you to perform element searches that includes Descendants.
-
1 vote
For Step Continuous, we currently support Integer, String and Enum. This is shown in the configuration UI. Does this satisfy your needs?
-
2 votes
If you right-click on the white space beneath to add a row, it is added to the end. If you don't have a row already highlighted and press the New button, a row is added to the end. However, it is noted that the behavior is inconsistent and we'll look at fixing this in a future release.
-
5 votes
Hi, how would you envision being able to configure this? Would you want all the EF's based on a single template or multiple EF templates? In essence do you envision wanting what would be a report on all notifications tied to a single notification rule or multiple notification rules? Would you possibly want this at a database level or system level?
-
3 votes
Since PI System Explorer is not a real time client, i.e. you need to refresh it to get updates, it's really not a good place to provide this information, especially if the problem is transient in nature. For example, if the notification is rejected by the end point unexpectedly once in a while, I would not expect users to sit in front of PI System Explorer and continuously hit Refresh to catch this information. What's the best way to expose this information for it to be useful?
-
2 votes
I have reviewed your case# 939560. Based on the information in the case, having individual MSI's would not have helped you. Can you elaborate on your request and your specific use cases?
-
14 votes
Looks to me there are two specific use cases here: 1) you have analyses that do not need to run more often than weekly - i.e. longer than what is permitted right now (daily), 2) you have data that is supposed to arrive at a specific time, but sometimes they don't and you want to re-calculate at a later time at which point you know for certain you have all the data you need for the calculations.
Did I get that right? Are there any more use cases?
Please describe use case in more details. Are you trying to handle late arriving data?
If you're trying to handle late arriving data, we're researching auto-recalculation for the 2017 R2 release.
-
1 vote
This will be available in the next release, AF 2018 SP2.
--
Steve Kwan -
4 votesAdminStephen Kwan
(Product Manager, OSIsoft)
supported this idea
·
AdminStephen Kwan
(Product Manager, OSIsoft)
shared this idea
·
This current suggestion is NOT the same as meierke1 reference.