MAl
My feedback
-
51 votes
At this time, this item is not currently scheduled for a release of PI Vision. If this changes, this item will be updated to reflect the current status.
MAl
supported this idea
·
-
47 votes
-
57 votesMAl
supported this idea
·
-
8 votesMAl
supported this idea
·
-
13 votesMAl
supported this idea
·
MAl
commented
Unfortunately OSIsoft decided to abandon ProcessBook and the possibility of getting Event Frames in it (what a pity!).
I also wish we could give users the ability to reuse quickly their own displays made with PI BatchView but, on the base of my understanding , at the current time there is no hope: PI Batch data are not visible in PI Vision and they cannot be automatically migrated to EF. So every site should be charged first for a migration plan from [PI MDB,Batches] to [PI AF,Event Frames], and then should work on recreating the same or similar BatchView displays.
In my opinion a sort of add-on in PI Vision making PI Batch data as visible would be appropriate: the possibility of migrating PI ProcessBook displays should also include the ones containing PI BatchView symbols and the visibility to relative data.
-
179 votesMAl
supported this idea
·
-
11 votesSTARTED / IN DEVELOPMENT · 0 comments · PI Interfaces » Batch Interfaces · Flag idea as inappropriate… · Admin →MAl
supported this idea
·
-
1 voteMAl
supported this idea
·
-
1 voteMAl
supported this idea
·
-
29 votesMAl
shared this idea
·
-
23 votesMAl
commented
Interesting idea the one of the AF, even if I have some doubt about how reliable could be the Windows authentication: PI interface node and PI server are normally segregated by firewalls and not in the same domain. In similar cases (i.e. when using a PI EMDVB interface to Event Frames) we happened to get some inexplicable unauthorized errors that later disappeared again inexplicably. Today (with PI MDB) we set easily a PI trust and just open port 5450/tcp.
MAl
supported this idea
·
-
11 votesMAl
supported this idea
·
-
4 votesMAl
supported this idea
·
I perfectly agree. I think a dedicated section menu inside PI System Explorer would be appropriate. Maybe configuration should be saved inside AF database instead of .ini files.