Offline Display Management: Allow PI Vision displays to be imported and exported
There is a need to be able to export and import PI Vision displays so that displays can be managed offline. This would allow transferring displays between systems that are not connected, taking backups of displays, versioning displays, sharing displays with customers, vendors, and third-parties, etc.
We are currently researching this item and evaluating it for a future release.
Hi Franz - offline display management is an area we were evaluating for PI Vision 2020 but ultimately something that will not be included as part of that release. However, we are still evaluating it and considering it towards a future PI Vision release.
the status of this idea didn't change a long time. It's very important to us. Can you give us an update/timeline?
As a PI Developer this is a critical tool. Right now this involves creating an SQL Script Schema and Data, then editing the script to fix server and database names. The re-importing oat the customer site. Finally using PI Display Manager to move it from one database to another on the site. All while being careful not to overwrite any of the customer work. This process is unmanageable
Dan Lopez commented
Here's a great security-minded use case as well:
We exchanged in PI World in goteborg on the subject and we are very interested in this feature to change mapping of attrbute more easily, copy screen site A to site B. Thank you
When displays are built in an offline PI-Dev environment, it is not possible to be able to connect this machine to a customers production environment in order to copy displays from one PI Vision system to another. The previous method of mounting a SQL Server database was better. A different method should be permitted such as exporting/importing in XML format.
Pedro Campos commented
Create a tool to import and export PI Vision display from one PI Vision to Other.
Several times, as System Integrator, we would like to create a view on System Integrator's PI Vision and then export to Client's PI Vision.
Work on this feature has not been started, so it will not be included in PI Vision 2019. If this item gets planned for a release or if development work on this item starts, we'll update the status of this item to reflect that. If you'd like to see all requests that will be included in PI Vision 2019, you can filter by the status of 'Started / In Development', all items that are being worked on for the 2019 release will mention PI Vision 2019 in the status notes.
Great to hear it is being evaluated! Is it going to be included in the upcoming PI Vision release?
The only distinction is that the web site Name in AF. Currently, I've got to require the provision pages for one web site, save them as another name, and remap the new web site for all division displayed points. an awfully time intense task. this is often contrary to OSIsoft template/pattern produce and use philosophy.
Rick Smith Jr commented
In response to Ryan McErlean, "Richard, If the sites are identical and..."
Our company does not have the luxury of having sites even remotely similar to each other, so the OSISoft tool does not help much... I end up recreating all my displays at the new site. Even if it were easy to use the tool (and it is not), then we still have to find someone with privileges to connect to two Vision databases are the same time.
If the sites are identical and have the same AF structure you should be able to swap the site name natively in PI Vision by swapping to root asset for the display. This would allow you to either reuse the same display(s) for all sites, or swap the root asset and then save as to create distinct displays for each site without having to manually remap the symbols. You can swap the root asset in a few different ways, for example with the asset dropdown list, with navigation links, URL parameters, etc. Documentation for using the asset list in this way can be found here: https://livelibrary.osisoft.com/LiveLibrary/content/en/vision-v2/GUID-DC4D3A7B-94C9-43C1-9AA2-1846D7F66391
If you'd like any additional information on this topic please let me know.
What I would like to see is a feature where you can change the AF linkage for a mapped point in PIVision. I have several sites that are identical. The only difference is the Site Name in AF. Currently, I have to take the PIVision pages for one site, save them as another name, and remap the new site for all PIVision displayed points. A very time consuming task. This is contrary to OSIsoft template/pattern create and reuse philosophy. Ideally, we would have the ability to export, change the path(s), and reimport.
Now when PI Vision 4.x release is postponed until further notice is this option going to be available in the PI Vision 3.4 release?
important 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.
A "XML Export" (or some export to file) would be wery usefull when developing displays you (we) want to distribute to customers.
If you develop a product using standard OSIsoft tools you should definitely be able to transfer it to other systems not connected to your own network on any product.
Now when we deploy solutions we have to manually create the displays again, and again and again for every customer making the deployment time consuming.
Many companies are starting to talk about sharing data for a more global/community development/improvement of processes. Sharing displays across partners should be easy, so this doesn't just affect us as an integrator but all companies that want to share information and all partners who want to utilize PI Vision as the core visualization tool.
If we have 10 displays that we need to setup when delivering a product we don't need that many customers to argue that making our own visualization tool instead of using PI Vision just because the deployment time is unnecessary high.
10 a bit complex displays would take around 50 hours to deploy (3-7 hours for each display) so with 10 customers you have 500 hours to make a different visualization tool. (500 hours is't much if you need the capability that PI Vision has but when pushing a product you can focus on just what's intended with your product)
There has to be another way of exporting the display as a file ( modify the configuration within the file) then importing the same into the other server. This is not a hard thing to do, we must have a feature like that. The moment the Display Utility is virtually useless. It can be a very simple solution.
Please, No PI web API as suggested by the OP. This requires Kerberos Authentication which is also not possible in a Cross domain environment,
Agreed, more flexibility is required to be able import/export display from one environment to another. Cross domain (untrusted) does not currently seem to be possible, which limits the tools benefits.
Also core database actions such as a database back up can be restricted to only certain roles/ functions (e.g. DBA) within an organization and currently this seems to be an automatic function of the tool with no way to turn it off.
I agree, (OSIsoft - we have a tool which handles this internally already, happy to discuss its functionality)