1 of 1 people found this helpful
I'm assuming that you are talking about the Advanced Continuous Historian offer in DeltaV which includes PI System technology. In this system, the interfaces and configuration are managed by DeltaV utilities. The licenses does not allow for OSIsoft provided clients (PI ProcessBook, PI Datalink, etc.) or third party apps to connect to this system.
The recommended architecture for customer who are using DeltaV and want to use applications that are not available in DeltaV is to have a site PI System that will sync automatically with the Advanced Continuous Historian and DeltaV and will provide full PI system functionality.
Finally, the Advanced Continuous Historian, while using PI system technology is provided, licensed and supported by Emerson. EMerson will be able to provide you more details on the apps the supported in that environment.
Thanks for your swift response.
May i know, how does the site PI System can sync automatically with Advanced Continuous Historian? Is it through PI-PI interface?
We use the DeltaV Smart Connector interface from OSI. This provides the OPC interface between DeltaV and your site PI system. We usually load the interface on the ACH machine. There are security modifications required on the Emerson side as they use a canned security model.
The interface keeps PI synched with the ACH and any new tags/changes made in DeltaV are automatically reflected in the site PI server and the site AF server thru XML.
DeltaV and their historian - an never ending (funny?) story. Unfortunately I have to deal with an version of DeltaV where they tried to create their own historian (which was said to be much better then PI *lol*)
For older versions I know that there were some restrictions.
May I ask which version of DeltaV we are talking about? I hab last year a talk with my OSI key accounter and he said that in the current version (12.3 I think) the embedded PI Server acts like every normal PI Server and could be interfaced by any OSI application.
Could this be clarified?
So here is more information about the current offering of Emerson. There has been many options and change, so I will not do the history here.
So an Emerson DeltaV customer has two choices of historian for DeltaV, they can either use the base continuous historian (created by Emerson) or use the Advanced Continuous Historian (Use the PI System technology). Both of these products are provided and supported by Emerson. As mention, earlier, the Advanced Continuous Historian does not allow OSIsoft provided client tools or third party tools to connect, unless they are provided by Emerson.
User/Customer that want the full functionality of a PI System should acquire a PI System. Emereson can resell what we they refer too as a Site PI System, Which is in facts a full PI System, but sold trought Emerson. OSIsoft can also provide this system or a cusotmer can use the PI System they might already have. This system allow for every interfaces, client tools, third party, etc, as it is a full PI System.
The nomenclature, options and different version can be confusing, so when discussing with a customer, please ensure to know a DeltaV customer, please ensure to know to what system they are refering to, and I will add, which version of DeltaV, since older version of DeltaV have different options. Hope this helps.
The Delta-V version they were about to migrate to is Delta-V v12.3.1. We need to add an Enterprise PI server above the embedded PI for this version of DeltaV.
So, my question here is: Can we use PI-PI to get data from embedded PI to another Enterprise PI server?
Not sure if the above provided DeltaV version is sufficient to answer this question. Please let me know if you need more information on this.
Thanks in advance
Usually, the PI OPC interface is used to get data from the Advanced Continuous historian. The PI OPC interface is provided as part of the DeltaV smart Connector bundle.
Thanks for all your inputs.
I'm waiting for a discussion with my client to get all the required version information.
The Smart connector version is 188.8.131.52.
Long ago... I would import the tags with Tag Configurator... paste tagnames into sourcetag, prefix the tagnames, change location fields to fit with pitopi, and export to a target server. We had a choice of pitopi or opc, until Emerson changed embedded historians, then we switched to OPC interface.
Nowadays, the Smart Connector makes it easy (once you get it configured). It will "read" the new points in DeltaV, as they are created/ downloaded to controller...