rpalmen
My feedback
-
20 votes
An error occurred while saving the comment rpalmen
supported this idea
·
-
16 votesrpalmen
supported this idea
·
-
99 votesrpalmen
supported this idea
·
-
22 votesrpalmen
supported this idea
·
-
14 votesrpalmen
supported this idea
·
-
140 votesEVALUATING · 17 comments · PI Server » Analytics & Calculations · Flag idea as inappropriate… · Admin →rpalmen
supported this idea
·
-
6 votes
An error occurred while saving the comment rpalmen
commented
I think this is already implemented (at least in PI Vision 2019)
-
5 votesrpalmen
supported this idea
·
-
9 votesrpalmen
supported this idea
·
-
128 votes
Update: PI System Connector 2.3.0.1 is not available at this time due to an issue identified with this version. We are working quickly to provide an updated version that resolves this issue.
Original Post: I’m really excited to announce that PI System Connector 2.3.0.1 is now available with snapshot support for PI Points that have compression disabled/off (on the source system). I cannot wait to hear your feedback on this latest version. Head over to https://my.osisoft.com/ to learn more about 2.3.0.1.
We will be keeping this feedback item alive as we continue to work on the next release of PI System Connector. The next release is expected in early 2021, and will expand upon the snapshot support introduced in 2.3.0.1 by adding configuration options and snapshot support for compressed PI Points.
An error occurred while saving the comment rpalmen
commented
Now we need to support multiple tools to sync systems: PI2PI and System connector. Moving to a single tool will reduce overall ownership cost.
rpalmen
supported this idea
·
-
32 votesrpalmen
supported this idea
·
-
7 votes
An error occurred while saving the comment rpalmen
commented
rpalmen
shared this idea
·
-
40 votesrpalmen
supported this idea
·
-
5 votesrpalmen
shared this idea
·
-
3 votes
An error occurred while saving the comment rpalmen
commented
Dealing with the same problem again...
It appears that the cleanup creates one huge transaction to perform the cleanup. If there is a large backup you need ridiculous amounts of logspace to buildup the transaction. At the moment performing a cleanup, and for a audit log of 110Gb i'm already at a logspace of 75Gb
With smaller transactions this would be more efficient.rpalmen
shared this idea
·
-
277 votes
Reopening this suggestion to collect additional feedback.
An error occurred while saving the comment rpalmen
commented
Now that Matlab is off the table, any new directions for extensibility of Analytics?
An error occurred while saving the comment rpalmen
commented
I appreaciate the step back! While Matlab provides scaleability performance and capabilities on the high-end of the spectrum, there is still a demand on the lower end.
I do understand the complexities and pitfalls involved (remember Custom DR's), but there should / could be a midway, just like PI Vision seems to strike a midway with it's extensibility. E.g. leaving the data delivery to the custom function to the analysis service, but having the capability to use e.g. C# to implement custom functions within that limited frame.After all we don't want to go back to the days where we open, render and parse Excel files in an ACE module...An error occurred while saving the comment rpalmen
commented
Let me add a current example where we use a custom C# calculation engine for.
For each batch, and during the batch at every change of the batch phase, we need to calculate the operating window for a number of key process parameters. We trigger the engine based on signups to BatchID and PhaseID. On every change, we lookup some process data, and some AF table, calculate our operating window limits (data series using future data) and write those back to PI Points.An error occurred while saving the comment rpalmen
commented
i think this request is more specific on the external calculation: https://feedback.osisoft.com/forums/555148-pi-server/suggestions/17219900-extensible-analytics
An error occurred while saving the comment rpalmen
commented
I'm a bug fan of AF, yet every decent project i needed to create my own external calculation engines for more complex business logic. I've used SQLserver, OLEBDEnt and linked AF tables, or custom C# engines.
In all cases i would at least get rid of all the technical plumbing of management, scheduling, security, etc., just like the ACE scheduler was.So mechanisms to trigger custom logic, supply the data and provide access, and send back the data to AF.
If needed, i can supply specific examples i've built for customers.
An error occurred while saving the comment rpalmen
commented
This request could go a long way, so maybe this option solves the request in a more broad sense:
https://feedback.osisoft.com/forums/555148-pi-server/suggestions/17219900-extensible-analyticsrpalmen
supported this idea
·
-
23 votes
An error occurred while saving the comment rpalmen
commented
In response to Stephen Kwan, "Based on your description, it is possibl..."
Not for this item yet. I did for another client, so i'm quite up-to-date with the release notes.
We are planning an upgraden soon though.An error occurred while saving the comment rpalmen
commented
In response to Stephen Kwan, "AF 2018 SP2 will have programmatic acces..."
In this case it's not a problem that i have lagging issues, skipped count is 0 on an evaluationcount of >1B. However i have missed Evaluations as i am missing data points that preview/backfill does reproduce and i can't find the reason why. The parameters don't tell me why one specific analysis fails once every thousand evaluations or so and that's where one would need tracing.rpalmen
shared this idea
·
-
8 votesrpalmen
supported this idea
·
-
1 voterpalmen
shared this idea
·
-
2 votesrpalmen
supported this idea
·
Being able to write to the starttime of the EventFrame is at least one of the key things required for proper trending