FranzK
My feedback
-
14 votesFranzK
supported this idea
·
-
1 voteFranzK
shared this idea
·
-
89 votesFranzK
supported this idea
·
-
22 votes
An error occurred while saving the comment FranzK
supported this idea
·
-
25 votesFranzK
supported this idea
·
-
27 votesFranzK
supported this idea
·
-
51 votesFranzK
supported this idea
·
-
64 votes
We understand that for slow changing points, values might not change often and thus there is a need to collect values at certain time intervals as opposed to on change. However, scanning at frequent intervals leads to increased load on the server and thus can lead to performance degradation. We are discussing how best to solve this problem with PI Connector for OPC UA.
FranzK
supported this idea
·
-
133 votes
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.
An error occurred while saving the comment FranzK
commented
Hi Alison,
do you already have a release date for the follow up version? Do you have more details to the implemented snapshot-support? e.g. about the configuration options?
thanks and best regards
FranzAn error occurred while saving the comment FranzK
commented
This topic is already under Research/Evaluating. Is there a new status? It's really important to get this support. Use of additional tools like PI Cloud connect, PItoPI interface,... is not straightforward and not in scope of best practice for an state of the art IT Architecture.
An error occurred while saving the comment FranzK
commented
PI to PI in parallel is not a solution. i expect to have one tool to communicate from a local system to a global system. there should be a straight forward way to connect one PI System to another and not different combinations of tools. another reason, the communication from local to global should be secured (it's with the connector, but not with PI to PI). so the connector should be able to:
-communicate historical data based on archive
-communicate snapshots in real-time mode
-full AF/EF supportFranzK
supported this idea
·
-
9 votes
We have started developing a PI Adapter for RDBMS. Look for more updates on our progress in Q1 2021.
FranzK
supported this idea
·
-
15 votes
We are currently considering the future development of this functionality. Please share your use cases here.
FranzK
supported this idea
·
-
13 votes
We have started developing a PI Adapter for Structured Data Files. Look for more updates on our progress in Q1 2021.
FranzK
supported this idea
·
-
82 votes
This feedback item has been moved from the PI Connectors forum to the PI Adapters forum.
We are continuing to support the PI Connector for OPC UA with stability and security releases. However, for feature enhancements, we are considering them for the PI Adapter for OPC UA. We would like to hear more about your use cases for this functionality, so please share with us in the comments.
FranzK
supported this idea
·
An error occurred while saving the comment FranzK
commented
we also use WinCC and other scada systems. about what to collect/ not collect, there should be same filtering possible like in the scada system itself, so i want the possibility to filter on every attribute the scada system offers. Naming for event frame should also be possible. E.g. Asset_Alarmtext or Alarmtext_Messageclass,...
The eventframes should be built without using PI Tags (Tagrefference). The behaviour of the end of eventframe (end eventframe when alarm is gone or with quitting) should be configurable in the connector -
16 votesFranzK
supported this idea
·
An error occurred while saving the comment FranzK
commented
It's important to get this soon as possible. Base Requirement to the System Connector is to have identical Data on source and destination Data Archive. This only works with append. at the moment it works with replace (in my opinion a bug - the feature might be replace).
-
81 votesFranzK
supported this idea
·
-
8 votesFranzK
supported this idea
·
-
2 votes
We have started development work to include the ability to prefix AF Objects being sent by PI System Connector. We look forward to sharing more with you in early 2021 on the release of this feature.
An error occurred while saving the comment FranzK
commented
The use-case is as follows. we use the System connector to connect local PI Systems to one global PI System. as the local PI Systems already exist, it's hard to harmonize all configuration objects (e.g. Event Frame templates). in case there exist different objects with the same Name (e.g. Event Frame template with Name "Batch"), the different templates influence the one template on the global System with this Name (i think the last connected template will be transfered to the global System). a prefix for AF objects would avoid this behaviour.
FranzK
shared this idea
·
-
398 votes34 comments · PI Vision » Display Management / Displays Page · Flag idea as inappropriate… · Admin →
In the upcoming PI Vision 2021 release, this functionality is being added that will allow for offline management of PI Vision displays.
An error occurred while saving the comment FranzK
commented
Hi Ryan,
the status of this idea didn't change a long time. It's very important to us. Can you give us an update/timeline?
An error occurred while saving the comment FranzK
commented
is this a similar topic?
https://feedback.osisoft.com/forums/320517-pi-vision/suggestions/18689953-exporting-and-importing-of-displaysimportant is also how the requirement is implemented - e.g. what does the export-file look like? what data format is used - am i able to edit these files.
FranzK
supported this idea
·
-
36 votesFranzK
supported this idea
·
-
26 votesFranzK
supported this idea
·
i think this request is related to https://feedback.osisoft.com/forums/555139-pi-connectors/suggestions/41720188-implement-the-option-to-choose-between-append-or-r
So it might be useful to merge to get a better view about the need for this requirement.