FranzK
My feedback
-
71 votesFranzK
supported this idea
·
-
31 votes
An error occurred while saving the comment FranzK
shared this idea
·
-
196 votes
We understand and acknowledge the importance of this request. We are evaluating how to provide a homogeneous and unified experience for health information across all our connectors.
An error occurred while saving the comment FranzK
commented
Is there already an update to the Topic? it's important to monitor the Health Status of the PI System. This should not be done Manual checking the Website. with Performance counters or other possibilities to Access the Information, this could be done by Standard Monitoring Tools.
Also for example the Buffer capacity (similar to the Performance counter available for Buffer Subsystem) would be quite helpful. -
6 votesFranzK
supported this idea
·
-
2 votes
We are currently researching the addition of prefixing for AF Objects transferred by PI System Connector.
Tell us more about your use cases in the comments and I will continue to update you on our progress!
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
·
-
354 votes31 comments · PI Vision » Display Management / Displays Page · Flag idea as inappropriate… · Admin →
We are currently researching this item and evaluating it for a future release.
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
·
-
3 votesFranzK
supported this idea
·
-
34 votesFranzK
supported this idea
·
-
10 votesFranzK
supported this idea
·
-
3 votes
We would like to learn more about the different use cases for your independent data streams.
While PI System Connector can support the configuration of data collection from specific branches of a PI AF Database, it seems that there’s also a need expressed here to regarding the destination options which we would like to know more about.
An error occurred while saving the comment FranzK
commented
a use case might be to define flexible routing of data. e.g. on the local system we have different departments. this departments might be handled with different data sources. the departments need to access these data in dedicated AF databases on global side. so a flexible routing data-source to destination is needed.
Another use case is to differentiate data based on GMP-context. so there is a Destination for GMP Data and one for non-GMP Data -
2 votes
An error occurred while saving the comment FranzK
commented
For different use cases we want to use different AF Databases. With AF Transformer we are able to get AF Structures from one database to another. but at the Moment there is no way to move Event-Frames from one database to another. this is very important if you want to have the context of your data in all your AF Databases. For Example if you have a batch-event-Frame you Need this context also in other AF Databases.
FranzK
shared this idea
·
-
26 votesFranzK
supported this idea
·
-
4 votesFranzK
supported this idea
·
-
125 votes
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 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
·
-
3 votesFranzK
shared this idea
·
-
3 votes
-
2 votes
-
76 votes
-
2 votes
-
9 votes
Is there already an update to this Topic? I saw there 3 other Feedback Posts regarding logarithmic scale (e.g. für xy-plots).Maybe you should merge them.