Recent Control & Safety Systems Discussions
Similar Posts
Access Problem to OPC HDA Server
Connect Delta-V PI Historian through OPC HDA protocal
Connect remotely to DeltaV OPC HDA server that runs on a machine with a Domain Controller role
Technical query for Automatic Start of OPC Mirror Services and Automatic Pipe activation when ever OPC Mirror computer is rebooted
OPC MIRROR on a external serveur
Share

OPC Licensing query - from external PI system (OPC HDA)

Hello. I am looking for a simple answer with regards OPC Licensing in DeltaV. I am looking to setup a PI OPC HDA interface from a corporate network PI system to a DeltaV Continuous Historian. The DeltaV server in question has approx 5000 points. The control engineer has provided a screenshot of the licensing summary. It is DeltaV version 9. There is licensing for OPC Mirror, OPC Remote services and OPC Server: 2000 data values. I know they have an OPC RNI with approx 200 points.

We will initially be loading 1000 tags in PI across the OPC HDA interface, with a view to eventually collecting all ~5000 tags. Does the "2000 data values" in the license file refer to the amount of points they are licensed to collect via OPC RNI, or does it refer to how much tags the PI OPC interface (essentially an OPC client) may sign up for (or is it a combination of both?).

We also currently only have one OPC interface, but would plan to setup PI OPC warm failover (which would mean both nodes are connected as clients). If there is restrictions on how many tags can be served from OPC, would this also require double the license count? Grateful if anyone could fill in the blanks for me as I am unable to get any answers internally! Many thanks.

Keilan Knight
  • chessley
    We use the PI OPC HDA interface to our Continuous historian (We're on v12 but used the same set-up back to v8), it doesn't require any special licenseing beyond the continous historian license. The catch is you can only have one third party HDA client connected at a time I'm not sure if there is a license avaiable to increase this limit.
  • Ray Emerson

    In reply to chessley:

    The DeltaV OPC History Server license scales the one-connection OPC HDA limit to up to 25 concurrent connections.
  • Keilan Knight

    In reply to Ray Emerson:

    Many thanks for the quick answers, looks like we are good then. Out of interest, what then does the "2000 data values" number refer to? It was reading this post that initially caused me alarm http://community.emerson.com/process/emerson-exchange/operateandmanage/deltav/f/50/t/2860 , specifically "providing you don’t exceed the OPC point count for the application station"
  • chessley

    In reply to Keilan Knight:

    the 2000 limit is your license limit for OPC DA points
  • Youssef.El-Bahtimy

    In reply to Keilan Knight:

    The thread you reference discusses OPCDA license count, not OPCHDA.

    Now regarding use of OPCHDA to essentially duplicate your DeltaV historian data in enterprise PI, I really like this idea and have posed it as a solution many times (as opposed to using OPCDA) but I would check with both OSI and Emerson, as I have been warned that using PI OPCHDA interface for many thousands of tags for near real time duplication to the enterprise historian may suffer performance issues.
  • Michael Moody

    In reply to Youssef.El-Bahtimy:

    It has been a few years since I used the OPC HDA connection, but I think it updates in chunks rather than real time based on scan class. The HDA is more sophisticated, but has pros and cons.

    I would definitely follow Youssef's advice to discuss with Emerson / OSIsoft if performance could be an issue.

    I'm not sure if practical for your system, but Emerson now offers the Advanced Continuous Historian that includes a PI to PI interface. May be worth consideration. I think v12 is required.
  • Ray Emerson

    In reply to Youssef.El-Bahtimy:

    The typical heuristic we follow is less than 2000 data values per instance of the PI OPC HDA interface. There are a couple of limitations in this architecture, such as the inability to use Auto-Point Sync functionality on the Enterprise PI side.

    I've also seen several instances in the past few year (KBA and hotfix released in October 2014) where recurring connections to the DeltaV OPC HDA Server can crash DVCH in such a way that the scanner continues running, but the recording process terminates. The subsystem retains a GOOD status in Diagnostics, but no data are being historized. Compared to the DeltaV OPC History Server, the Advanced Continuous Historian with a PI-to-PI connection to your Enterprise database may be a more robust solution for a comparable / lower dollar value. You'd need at least DeltaV 12.3.1 to roll this out.

This is the official online community site of the Emerson Global Users Exchange, a forum for the free exchange of non-proprietary information among the global user community of all Emerson Automation Solution's products and services. Our goal is to improve the efficiency and use of automation systems and solutions employed at members’ facilities by sharing our knowledge, experiences, and application information.

User Groups | World Areas | Community Guidelines | Legal Information | Privacy Policy | Contact Community Manager

Website translation provided by Website Translator

© 2015-2022 Emerson Global Users Exchange. All rights reserved.