By Mustafa Al-mosawi
There are few things I enjoy more than seeing the light go on in someone's mind, and the are few better places to see this than at an OPC Training Workshop. A student asked a very good question, and a few days later, when visiting a customer site, the same question came up again. So – here I am blogging about it.
The question asked both times was this: How do I access the data files/tables on your HDA Historian?
Some of you are probably chuckling under your breath. But these are very smart people—experts with a wide variety of technology. So why the disconnect? OPC-HDA wasn't something they were familiar with. So if you don't think that's a funny question, here are two answers for you: one short, one long.
Short answer: You don't. You don't. Need. To. That's the point. Any HDA tool will get you all the access to the archived data you need.
Long answer: You don't. You don't. Need. To. The whole point of the OPC HDA standard is to remove the need to understand deeply how the data is archived, accessed or organized. I can store my data in a single file or fifty-thousand. I can store them as csv, xls or DAT files. I can store them with an advanced configuration database with advanced lookups or in one giant, long, insanely over-indexed table. I can store the data however I want. HDA makes no restriction about which mechanism I should choose. The OPC HDA server's job is to make that invisible to you, whichever archive you choose.
That's the theory anyway. In reality, not all HDA servers or archives are created equal.
Archive structures are defined by good engineering, design constraints and project requirements. Choosing poorly can have implications related to security, reliability, auditability and availability of the data. Ultimately, whichever archive you or your vendor choose, the HDA server needs to understand the database schema, or the file structure. The HDA server is responsible for figuring out which files to open, how to structure the query, and for packaging them up so any OPC HDA client can understand the answer. The HDA server is almost always separate from the archive—just as the OPC DA server is almost always separate from the device.
Like DA, HDA frees you to pick and choose whatever tool to access the data from your historian. That's how OPC Excel Reporter and OPC Easy Trender work with any historian on the market, and how OPC Desktop Historian works with any HDA tool.
So instead of database schemas and file structures, gain knowledge about your processes and equipment performance from a wider variety of data sources with a greater selection of tools. That's the power of OPC.
Mustafa Al-mosawi, BSc, is Matrikon’s product manager for Matrikon Analytics. He has 8 years experience in design, development, commissioning and testing of industrial software products. Mustafa previously worked in the nuclear industry as a business and systems analyst with Ontario Power Generation-supporting next generation initiatives. Prior to his current role, he was a senior product designer for the Matrikon Suite of products, including Operational Insight, Alarm Manager, and TaiJi PID.
