Skip to Content
Once in a while clients need to expose data from a custom build data store to their xMII Server, this article describes the best practices for doing that. This article is also intended to support the 2.5.x and 4.0.x xMII UDSs and will most likely be supported in future connectivity products.  Though a custom xMII UDS can be developed (through negotiations with solution management), but the cost and schedule can make it OPC DA, OPC HDA and OLE DB.  OPC is standards organization that is “dedicated to interoperability in automation”. Although OPC has several standards we will focus on the ones that are currently accessible to the current line of xMII connectivity products. OPC Data Access, or simply OPC DA, is probably the most recognized and implemented set to standards in the OPC portfolio. OPC DA exposes current values as well as allows for writing values to the items (OPC uses the generic term ‘item’ were other automation vendors use the term ‘tag’, for this article I’ll use the term ‘item’). The namespace is also exposed so that other systems can see what information is on the server, xMII will use this data to create query templates, and though the OPC DA specification may say it is ‘optional’ but it is required by the xMII UDS, so implement it.  The OPC DA specification 2.05A specification is supported by the 2.5.x and 4.0.x versions of the xMII UDSs, the 4.0.x xMII UDSs also supports the 3.0 version of the OPC DA specification. It should be noted that the 1.0 OPC specification is not supported by the xMII UDSs. Any future connectivity products will most likely support both OPC DA 2.05A and 3.00, but 1.0 will remain unsupported.  OPC HDA, or OPC Historical Data Access, is another interface that can be used to connect to historical tag systems. Currently the xMII UDSs support the 1.20A revision of the interface only. The OPC HDA specification supports current and historical queries and writes, interpolated historical trends and statistical information, all of which can be accessed through the xMII OPC HDA UDS. Other interfaces are currently not exposed to the UDS for data retrieval.  OLE DB is probably the oldest supported database access interface in the Microsoft realm. Though it is older then ODBC, it is generally the lowest level interface a database system will expose, and in some cases the most efficient. It should be noted that the queries to the database need not be SQL or any other relational language (though most vendors have defined a SQL like language). If retrieval of non time series data is required, the OLE DB interface is the recommended extraction approach.  To summarize, if a client needs to access data in a custom or obscure data source into SAP xMII and that back end source is a Microsoft based operating system, then it is recommended that the parties involved create an interface to either OPC DA, OPC HDA or OLE DB, or a combination there of, to access this data. This will allow for the greatest integration with any future releases if xMII and the xMII UDSs.
To report this post you need to login first.

4 Comments

You must be Logged on to comment or reply to a post.

  1. Former Member
    I’ve found myself in a position where I need to utilise the OLE DB UDS to connect to PI as the standard PI UDS connector does not provide all the functionality I require.  (nothing too complicated, but things like filters on time based queries etc.)  Please refer to SAP log 0000519040/2007.
    I was under the impression that the PI UDS connector utilised the same API as that used for the PI Excel Add In, and that any functionality available in the Excel Add In would also be apparent when using the PI UDS connector.  Was my assumption incorrect? 
    Also, we are looking at purchasing a Honeywell Uniformance PHD historian (Release 210)  for one of our plants.  I’m assuming the OPC HDA connector will be able to connect to this historian successfully.  Is there anyone I can speak to to confirm this connectivity before we go ahead and purchase this historian? 
    (0) 
    1. Joanne,

      Though the xMIII PI UDS is designed to retrieve data from OSIsofts PI Historian, it was never intended to fully retrieve all of the query possibilities for PI. With that in mind, the PI OLEDB Provider delivered by OSIsoft is able to get to a lot more data that the xMII PI UDS can. If you need to translate an Excel Add-In function to a PI OLEDB query, you will need to contact your local PI expert or OSIsoft directly.

      Unfortunately your assumption that all connections to PI are the same is incorrect. There are 2 main low level interfaces to PI as well as a few higher level ones. Each level adds particular functionality dependant on that levels need. In your case the Excel Add-Ins add functionality that may not all be available to lower levels which is where the xMII PI UDS needs to access.

      As for your question regarding Honeywells PHD historian, we have some customers connecting to this server using the xMII OPC HDA UDS. The only issue that seems to come up in the method that the PHD implements quality information differently in the OPC HDA interfaces then the native PHD client tools, this is partly due to the OPC specification. We have not seen any other issues (though the customer base for PHD is much smaller then other tag based systems).

      (0) 
      1. Former Member
        Hello,

        We are on UDS version 2.5 – there is mention of a OLE DB UDS in 2.5 – is the UDS version 4 more robust for OLE DB..?

        Many thanks,

        Joseph Scott

        (0) 

Leave a Reply