So, every PI system is concerned with taking data from items, things, and measurements that are important to you and getting them to you and the people around you. So, to start this off, let's say you own things out there like a building or you rent a building and you own equipment, like tanks or equipment that runs and uses electricity, such as a pump or something. There are things that you own and there are things about them that we want to know. Over here, there are people, including you and your peers, who want to know stuff. They want to see charts and be able to analyze things like the running time of the pump or its RPM. Maybe someone wants to see a spreadsheet report of the production data for a tank. Or perhaps someone wants to monitor the temperature of a building and receive a notification if it goes too high. These are the things we want to deliver about the things we own and are concerned about. So, how do we connect these things to each other? Well, there's one video on the servers and hardware that act as intermediaries, delivering the data to the PI system. However, in this video, I will discuss how we organize this in the PI system, specifically how we organize the database that represents the data and makes it available to end-users. This will be divided into three parts: PI assets, PI asset attributes, and PI tags. These three components are the building blocks for organizing data in the PI system. Let's start with PI assets, or more precisely, PI AF assets. The first step in representing this data is to take the items we have and represent them in our database, specifically the PI AF database. We...
Award-winning PDF software
Video instructions and help with filling out and completing Which Form 2220 Assets
