Real Time Snapshot Support

PI System Connector: Need real time snapshot data support for the PI System connector.

133 votes

AdminTodd Brown (Product Manager, OSIsoft) shared this idea · November 09, 2017 · Flag idea as inappropriate… · Admin →

IN DEVELOPMENT ·

AdminAllison Muraski (Admin, OSIsoft) responded · March 23, 2021

PI System Connector with configurable snapshot support is coming soon! In order to provide you with the latest and most secure PI Connector, the timeframe for this release is being extended to May. Be assured that we are working diligently to provide you with much anticipated features as quickly as possible.

Show previous admin responses (6)

IN DEVELOPMENT ·

AdminAllison Muraski (Admin, OSIsoft) responded · December 10, 2020

The issue identified with PI System Connector 2.3.0.1 has been resolved, and PI System Connector 2.3.1.1 is now available with snapshot support for PI Points that have compression disabled/off.

We are still on track for a follow up release in Q1 2021 that will expand upon the snapshot support introduced in 2.3.1.1 by adding configuration options and snapshot support for compressed PI Points.

IN DEVELOPMENT ·

AdminAllison Muraski (Admin, OSIsoft) responded · October 07, 2020

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.

IN DEVELOPMENT ·

AdminAllison Muraski (Admin, OSIsoft) responded · September 09, 2020

I know a lot of you are really excited about snapshot support for PI System Connector, so I wanted to offer you an update on our release plans.

Q4 2020 – You can expect to see a PI System Connector release introducing snapshot support for PI Points with the compression attribute set to zero (on the source system).

Early 2021 – You can expect to see a PI System Connector release that will expand on the Q4 release by adding snapshot configuration options and snapshot support for PI Points with the compression attribute not set to zero (on the source system).

IN DEVELOPMENT ·

AdminAllison Muraski (Admin, OSIsoft) responded · August 24, 2020

The next release of the PI System Connector will support sending snapshot values for PI Points with the compression attribute set to zero. This release is expected before the end of the year.

In addition to this the basic functionality of this initial release, we are currently evaluating expanding snapshot support for compressed PI Points in a subsequent release.

Please continue to follow this item for updates on PI System Connector snapshot support.

PLANNED ·

AdminAllison Muraski (Admin, OSIsoft) responded · June 17, 2020

We will soon be moving forward with the addition of Snapshot support for PI System Connector. I look forward to continuing to update you once we move from planning to active development work on this enhancement.

In the meantime, please continue to share your comments regarding Snapshot support for PI System Connector here.

EVALUATING ·

Abbas Saboowala responded · February 25, 2019

This item is under technical review. Currently, support for collecting Snapshot data can be achieved via PI to PI interface and should be considered for achieving this specific functionality.

30 comments

An error occurred while saving the comment

mbailey commented · July 25, 2019 13:46 · Flag as inappropriate

PI to PI and APS is still not meeting our requirements. While OSIsoft says this is the solution, its not a good one. PI APS processes tags one at a time. Startup time for PItoPI is also slow. APS and PItoPI is not multithreaded. The APS syncing for a large amount of tags is not meeting our need. Because the Connector still does not meet our requirements, we've had to add many (currently 14) interfaces which is very difficult to manage across multiple servers at multiple locations. Anytime we have PI to PI or APS talking to systems at other locations (for disaster recovery) latency causes the startup time and sync times to take hours. Not an acceptable high availability solution.

Submitting...
mbailey commented · January 14, 2019 12:53 · Flag as inappropriate

With 47 votes you would think the folks would listen to what we need. I have not been impressed with how slow this connector has been moving. APS and PItoPI are not working for us. Syncing a collective across a few states, causes latency issues and the sync process takes 24 hours currently.

Submitting...
Joshua Duncan commented · January 14, 2019 09:41 · Flag as inappropriate

In response to Matthew Bailey, "We need this as well. We have a project ..."
I wouldn't get your hopes up. I received an update on this on January 4, 2019 from a connectors product specialist at OSI. He reached out to the product manager for System Connector and they have decided not to support snapshot data collection with PI System Connector. On hearing this news my org has decided to remove System Connector and go with PItoPI/APS instead. The PI System Connector seems like a half-baked solution right now. I've heard from OSI that it should not be seen as a PItoPI replacement (see here) but instead should be seen as a solution for migrating AF DB structure from one AF environment to another. However, as of now, System Connector doesn't support migrating Analyses or Notifications. I have to say that System Connector seemed to handle PI tag creation/updates a lot more seamlessly than APS but also there was much less control and customization. With time I'm sure System Connector will become a solid product but seems lacking as of now.

Submitting...
mbailey commented · January 11, 2019 16:44 · Flag as inappropriate

In response to Matthew Bailey, "We need this as well. We have a project ..."
I should add that we have been waiting for the connector to meet these requirements for 4 years!
Essentially we want two collectives ( a source and destination) to be the same.

Requirements
- Send PI data even if it's not in AF.
- Send real-time snapshot data. It seems really useless for us to be able to only send archive data. Users using the destination system don't get the real-time or accurate values? A breaker is closed, but the users see's it open? Not making sense.
- If a tag name is changed on the source collective, it should update on the destination side.
- Should be much faster then PI to PI and APS (multi threaded), should work better across two locations where latency comes to play.
- Should be easier to configure then PItoPI and APS

Submitting...
mbailey commented · January 11, 2019 14:22 · Flag as inappropriate

We need this as well. We have a project on hold until this is done.

Submitting...
Joshua Duncan commented · January 09, 2019 12:10 · Flag as inappropriate

I heard that this feature is in the works. Is there a tentative timeline for this? Like everyone else here, I agree that this is a very necessary feature.

Submitting...
Trent Huhn commented · September 24, 2018 18:27 · Flag as inappropriate

Another vote for this functionality. We replicate data from remote site PI servers to a central enterprise server - having snapshot data available here to trigger real-time alarms is critical. Without this functionality, we are unable to implement PI System Connector at this time.

Submitting...
Laurie Dieffenbach commented · September 04, 2018 10:47 · Flag as inappropriate

Another example: One of my customers has a situation where manually entered data or KPIs are calculated on a daily basis, or even hourly. The snapshot value won’t get to our central server till the next hour/day/etc. I don’t think there is a way to force the value to automatically go from snapshot to archive. PI always needs the current value and the previous value to decide if it needs to archive. Therefore, they need the snapshot value to be included in the PI System Connector.

Submitting...
Fabiano Batista commented · April 19, 2018 10:43 · Flag as inappropriate

This idea is very important, Tood. Thanks for sharing.

I would like to mention is a typical use:

- Daily KPIs are calculated at the source system, and they should be available immediately on the destination server as soon as they get calculated in the source.

Unfortunately, with the current implementation of PI System connector, we see a lag of 1 day between the last daily result available in the destination PI System and the one available in the source PI System. One of my customers is having this issue right now.

Submitting...
fburrows commented · January 30, 2018 14:26 · Flag as inappropriate

A must have if replicating to an enterprise server that is then used as the primary source of data for end users.

Submitting...