4 Replies Latest reply on Jul 17, 2018 2:58 PM by psehgal

    Online tutorial on end-to-end connectivity from source to AF Server

    psehgal

      I am looking for some tutorial that explains the complete flow from a source (could be simulated) to Pi Interface to Data Archive Server. Further how does the data get pulled or how often Pi Point get pulled to Asset Framework. If there is some simulated devices that send the data that would be great.

       

      Are the databases of Data Archvie and Asset Framework same or different (I mean SQL server DB or is it some internal DB).

        • Re: Online tutorial on end-to-end connectivity from source to AF Server
          rschmitz

          Hi Priya,

           

          Thanks for reaching out to us on PI Square. There are a lot of different sub-questions in this so I apologize if I miss one of them:

           

          • PI Point Data is updated in AF whenever the data is refreshed on the client. So the most common example is PI System Explorer - anytime you navigate from one element to another or hit the refresh button on the toolbar the data is updated.
          • The backend of the Data Archive and the AF Server are separate. The Data Archive is developed on OSI's proprietary archive file format whereas the AF Server is built on top of SQL Server.
          • As far as simulated data goes, everyone has their own solution to this problem depending on what data sources you plan on using. Probably the most common one I see if clients using Matrikon's simulation server, though if you're pulling data from SQL Servers perhaps it makes more sense to use something like the Northwind Database from Microsoft. Do you know what kind of Data sources you're going to have? Perhaps we could help identify one specific for your needs.

          Cheers,

          Rob

          2 of 2 people found this helpful
            • Re: Online tutorial on end-to-end connectivity from source to AF Server
              psehgal

              Hi Robert,

              Thanks for the reply. This is useful. One more question:

              • The backend of the Data Archive and the AF Server are separate. The Data Archive is developed on OSI's proprietary archive file format whereas the AF Server is built on top of SQL Server. --> How often does the data get pulled into AF Server from Data Archive?

               

              The overview video is having some problem and I cannot access it. I have seen multiple such videos and wanted to reconfirm my understanding. Here is the flow which I have understood - please let me know if I am correct:

              If I have a sensor/data source and it registers and sends the stream to the Interface Node (Pi Connector). Since the Data source can send data in various formats, Pi connector will convert these into the format understood by Pi Data Archive and then send the data stream  to Pi Data Archive. This will be stored in OSI's proprietary format.

              The administrator can setup a element hierarchy of his IoT devices/plant in AF server and map them to Pi Points or time series values stored in Data Archive. So, these streams of data will flow from OSI file (data archive) to AF Server and be stored in SQL. One can also have different types of attributes to elements which are derived, etc.

                • Re: Online tutorial on end-to-end connectivity from source to AF Server
                  Lal_Babu_Shaik

                  Hi Priya

                   

                  Data is not stored in SQL server. All the data coming from interface will be stored on PI Data Archive. Meta data and other relational mappings are stored in AF Server(SQL Database). As your build your hierarchy you add relations and mapping to the PI Points and only meta data is stored. When AF clients requests data it connects to PI Data archive to get data from PI Data Archive server.  AF allows you to define your own hierarchy and define your own derived attributes and calculations.

                   

                  Interface and connectors collect data from  data sources and sends to PI system based on instrument tag configuration i.e. item id on source system (dependent on source).  PI system process data based on point settings like exception and compression. Data is historised on PI Data Archive. Using AF you can map to PI points/tags and define your own hierarchy based on your requirement and add additional information like location, maintenance date and calculations in AF analysis which will store the meta data in SQL server but point data is coming from PI Data Archive.

                   

                  Please let me know in case of any queries.

                   

                  Thanks,

                  Lal Babu Shaik

                  2 of 2 people found this helpful