What does the tag ALB_BLDG1_L1_M47_DISPUMP1_RPM mean?
How do we overcome the challenges around deriving real value from data that is collected? The first step in turning data into information is creating context for the data.
Whether data is from an HMI/SCADA system (collected from PLC memory locations), time series and alarm and event data from a historian, or IIoT sensor data, industrial data is typically identified by a tag name. People that work with data everyday may understand how these “tags” correlate to signals coming from the plant equipment or other sensors. The problem is that set of people represents a small percentage of the people that could potentially get value from the data.
The answer is to create a mapping between the tag data and a representation of the machine, line, plant or enterprise – called an asset model. Any user who wants to know the value of any specific sensor (such as RPMs of a pump) can find the specific pump in the model and see the data values associated with the pump, RPMs in this example.
Asset modelling today includes the ability to create standard object types (think templates) that include the standard set of information associated with a type of equipment. Having standard object types (templates) that can be referenced for each similar piece of equipment further enhances users’ ability to understand the plant equipment. Comparison of the parameters associated with multiple examples of a given equipment type becomes simple.
So, what does ALB_BLDG1_L1_M47_DISPUMP1_RPM mean? Probably only a few people know the answer. However, almost everyone can understand what the RPM parameter for the discharge pump number one on Mixing Machine 2 in Building 1, Line 1 in Albuquerque means. And if they want to compare the behavior of Discharge Pump 1 and Discharge Pump 2 – no problem. Context makes all the difference.