we use SKF @ptitude for vibration monitoring, and I wonder if anyone has set up a PI OPC interface for this software and what the best way to collect the historical data from the system is. OPC HDA, SQL interface, ...
Can you double check if your @ptitude implementation includes an internal OPC UA Server?
OSIsoft OPC UA Interface should be released in the future, so perhaps a direct connect will be possible eventually.
I have done this several times so it is possible although not easy. We used the OPC interface in both instances.
Setting up the OPC interface is fairly similar to a standard install. Where we ran into the most issues is the tag mapping between SKF and PI.
For a typical OPC interface you can use an OPC client to expose the tag names in a control system and use that as the instrument tag when configuring your PI tag list. This does NOT work for SKF systems. SKF uses a MS SQL Server database to store the hierarchy and tag information. In order to determine the "instrument tag" you must find the table in SQL server that holds this data and generate queries that recreate the SKF hierarchy to determine the rows in the table that contain the tag name (see query below).
I have done this twice and in both cases the table structure was completely different for each SKF system. In one system the table that I needed for the mapping was named NODE. In the other instance it was TREEELEM. My general process would be to copy the table and import it into a test database and write a query to determine the SKF hierarchy something like:
select n.TREEELEMID, n.NAME, n.HIERARCHYID,
n6.NAME as ParentLevel6,
n5.NAME as ParentLevel5,
n4.NAME as ParentLevel4,
n3.NAME as ParentLevel3
from TREEELEM n
inner join TREEELEM n6 on n.PARENTREFID = n6.TREEELEMID
inner join TREEELEM n5 on n6.PARENTREFID = n5.TREEELEMID
inner join TREEELEM n4 on n5.PARENTREFID = n4.TREEELEMID
inner join TREEELEM n3 on n4.PARENTREFID = n3.TREEELEMID
where n4.NAME is not null
and n4.NAME <> 'NULL'
and n3.NAME = 'Hierarchy'
and n4.NAME <> 'IMx Devices'
and n.REFERENCEID = 0
order by n.TREEELEMID
From this you can determine what the tag is in SKF. In this particular SKF instance there was an Access database which we would populate with the tag mapping. For the other SKF instance there was no Access DB and populating the instrument tags in the PI attributes was all that was needed.
and thank you for your consideration.
We have set up the PI Interface for OPC DA to 16 different instances of SKF @titude and it is all working very well.
On the SKF side they have an OPC DA wrapper, so we use that now but may look for the possibility to use OPC UA directly in the future. But it is not on our top priority list right now. :-)
That would be great if SKF would adopt the OPC UA protocol. The OPC DA wrapper provided when i was on this project was not very elegant. Sounds like it may have since improved.
they have adopted the UA protocol. That is their standard way of delivering data.
They provide the DA wrapper on top of it for customers like us, who have not adopted UA yet.
Retrieving data ...