Multiple instances for Asset Analytics

Currently it is only possible to connect the Asset Analytics service to an AF server. It would be very useful if you could connect an Asset Analytics service to an AF database. This way you can create a "silo" of an Asset Analytics service and AF database. This silo can run on its own without impacting or being affected by other AF databases, resulting in a more robust, reliable system.

The "created" instances of the Asset Analytics services can all run on the same server or on different servers. If the services are running on the same box, they should be able to run with their own service account and connect to the PI system with that account and write data back using the service account, even if the pi buffer subsystem is enabled on the server (which is necessary if you are using a PI collective)

It should be possible to link an AF database with analytics to a specific AF Analytics server.

We have monthly patching cycles and we have a failover cluster setup for high availability. The analysis takes hours to complete backfilling after a restart for patching.

If we could assign an analysis service for certain AF databases, that could be a good workaround unless a load balancer like F5 can be supported which would be optimal. This will avoid analysis skipping issues which we see in the logs all the time. Anything we could do to isolate critical analysis from being impacted by not so critical analysis.

Being able to run Asset Analytics on different hosts could solve a problem with single systems spanning multiple time zones. By having an Asset Analytics server hosted in each time zone an enterprise operates in could mean that time zones/daylight savings/etc. are taken care of by the operating systems as they are clients to Asset Framework and PI data archive.

For example, if I have a calculation that is a 6am to 6am totalizer at the momment I have to be aware of what time zone the analytics service is running in and account for that. Sometimes this can be complicated, and it just adds more expense to the calculations than would be needed otherwise.

It would be useful to run multiple instances of Asset Analytics to assign "mission critical" calculations to a dedicated environment, while running non-critical calculations on another environment. This would allow the "mission critical" system to be more controlled to avoid stressing the environment.

we are also an Enterprise customer and we have been facing a lot of challenges with single instance of Analytics Service & Notification service. for a small scale system, analysis service works well but when system grows with thousands of assets (35K assets in our case) and analyses (140K Analyses in our case) the system starts to show signs of performance deterioration. all techsupport calls ends up providing gigs of logs files and service statistics and in the end we just hear the feedback of fine tuning our calculations. we have some very critical 10-20K analyses which we can't afford to loose for even 1 minute, but if analysis service goes down, it takes all 140K analyses with it including super critical ones as well.

Aveva/OSIsoft should definitely look into creating multi-instances of PI Analysis Services like PI-PI Interface so that we can group all critical analyses to 1 instance and do some load distribution. We have seen similar setup for PI Integrator for business analytics where we can configure up to 4 worker node services on 1 server machine.

Regards,

Gaurav A

Agree and Supported by EA Customer in Australia: User Voice on Behalf of EA customer: 1 AF server to 1 Analytics box gets 'way overloaded' even with allot of CPU thrown at it, why can’t we split analytics boxes to AF servers. Case alignment: closed case 710771 100% agree with this and voting on behalf of customer

In our case this is also critical. We have a database with 600 assets right now and each asset have around 14 rollup calculations. With this our server is using 30GB of memory and takes 1,5 hour to start and 7 hours to finish the first recalculation (after it starts). With the help of Rory (from OSIsoft) we reduced that to 30 minutes and 1,5 hours respectively using the Excluded functionality to remove some of the Rollup triggers (as there's no way to select individual triggers for Rollups) but this was just a test server. In our production server we will have 20000 assets, which will make the usage of Analysis for anything else very difficult. So, In our case ideally we would want to load balance all of those Rollup to split the load on different servers (this could be set by category or when you create the analysis) and one server to Event frames, another one for regular analysis, etc.

Wilson, We need to take a closer look at your system. It's not necessarily a good idea to just throw hardware and brute strength to solve every problem. Looking at your description, it should not take 1.5 hours to start. Which version of software are you running? We fixed a couple of issues that dramatically reduced start time with recent release(s). Do you have a lot of missing PI Points in your rollups? How often are your rollups being triggered? Are you in a situation where you're triggering more often that you think due to the rollups having so many inputs? You're welcome to email me directly, especially if you have a current tech support case.

In addition to resource usage, there are possible legal (international trade) or contractual (multi-tenant) concerns where having separate services with access to selected AF databases could make it easier to prove to the lawyers that there was no way for someone to have calculated data from pi server 'y' (on the same AF / Analytic server) and stored data on server 'x'

Stephen, to answer your questions: Which version of software are you running? A) We are running the latest version of everything (PI AF 2017R2 and Analysis 2017R2)   We fixed a couple of issues that dramatically reduced start time with recent release(s). A) Yeah, we know, the previous version wasn't usable. We noticed a lot of improvement on PI System Explorer as well as before it would take too long to even load an Analysis on it giving the amount of attributes we have.   Do you have a lot of missing PI Points in your rollups? A) No, we make sure we create all the points. But we had a lot of attributes that would not get a value (its optional manual data), so, we started using the Excluded functionality to remove those and it improved the overall performance as I mentioned above.     How often are your rollups being triggered? A) Our data flow is pretty slow. Around 2000 assets will have one data point each 10 minutes on average, but the other 18000 usually comes once in a day. And we would like to be able to subscribe to just some of the attributes to generate a rollup, but that is not possible in the current version, Rollups are set to monitor all in event based or you need to change to period, which is not ok to us.   Are you in a situation where you're triggering more often that you think due to the rollups having so many inputs? A) We didn't identify any problem with the data flow. As soon as the service start, it kind of behave ok, but we are still in the test phase and the data will start to flow in groups of assets, so, we may have a problem later, but as of now we didn't notice anything. But as stated before, if we could subscribe to just three or four attributes, in our case, that would be actually a better solution as we expect the data to come at the same time.

Stephen, to answer your questions: Which version of software are you running? A) We are running the latest version of everything (PI AF 2017R2 and Analysis 2017R2)   We fixed a couple of issues that dramatically reduced start time with recent release(s). A) Yeah, we know, the previous version wasn't usable. We noticed a lot of improvement on PI System Explorer as well as before it would take too long to even load an Analysis on it giving the amount of attributes we have.   Do you have a lot of missing PI Points in your rollups? A) No, we make sure we create all the points. But we had a lot of attributes that would not get a value (its optional manual data), so, we started using the Excluded functionality to remove those and it improved the overall performance as I mentioned above.     How often are your rollups being triggered? A) Our data flow is pretty slow. Around 2000 assets will have one data point each 10 minutes on average, but the other 18000 usually comes once in a day. And we would like to be able to subscribe to just some of the attributes to generate a rollup, but that is not possible in the current version, Rollups are set to monitor all in event based or you need to change to period, which is not ok to us.   Are you in a situation where you're triggering more often that you think due to the rollups having so many inputs? A) We didn't identify any problem with the data flow. As soon as the service start, it kind of behave ok, but we are still in the test phase and the data will start to flow in groups of assets, so, we may have a problem later, but as of now we didn't notice anything. But as stated before, if we could subscribe to just three or four attributes, in our case, that would be actually a better solution as we expect the data to come at the same time.

Stephen, to answer your questions: Which version of software are you running? A) We are running the latest version of everything (PI AF 2017R2 and Analysis 2017R2)   We fixed a couple of issues that dramatically reduced start time with recent release(s). A) Yeah, we know, the previous version wasn't usable. We noticed a lot of improvement on PI System Explorer as well as before it would take too long to even load an Analysis on it giving the amount of attributes we have.   Do you have a lot of missing PI Points in your rollups? A) No, we make sure we create all the points. But we had a lot of attributes that would not get a value (its optional manual data), so, we started using the Excluded functionality to remove those and it improved the overall performance as I mentioned above.     How often are your rollups being triggered? A) Our data flow is pretty slow. Around 2000 assets will have one data point each 10 minutes on average, but the other 18000 usually comes once in a day. And we would like to be able to subscribe to just some of the attributes to generate a rollup, but that is not possible in the current version, Rollups are set to monitor all in event based or you need to change to period, which is not ok to us.   Are you in a situation where you're triggering more often that you think due to the rollups having so many inputs? A) We didn't identify any problem with the data flow. As soon as the service start, it kind of behave ok, but we are still in the test phase and the data will start to flow in groups of assets, so, we may have a problem later, but as of now we didn't notice anything. But as stated before, if we could subscribe to just three or four attributes, in our case, that would be actually a better solution as we expect the data to come at the same time.

Stephen, to answer your questions: Which version of software are you running? A) We are running the latest version of everything (PI AF 2017R2 and Analysis 2017R2)   We fixed a couple of issues that dramatically reduced start time with recent release(s). A) Yeah, we know, the previous version wasn't usable. We noticed a lot of improvement on PI System Explorer as well as before it would take too long to even load an Analysis on it giving the amount of attributes we have.   Do you have a lot of missing PI Points in your rollups? A) No, we make sure we create all the points. But we had a lot of attributes that would not get a value (its optional manual data), so, we started using the Excluded functionality to remove those and it improved the overall performance as I mentioned above.     How often are your rollups being triggered? A) Our data flow is pretty slow. Around 2000 assets will have one data point each 10 minutes on average, but the other 18000 usually comes once in a day. And we would like to be able to subscribe to just some of the attributes to generate a rollup, but that is not possible in the current version, Rollups are set to monitor all in event based or you need to change to period, which is not ok to us.   Are you in a situation where you're triggering more often that you think due to the rollups having so many inputs? A) We didn't identify any problem with the data flow. As soon as the service start, it kind of behave ok, but we are still in the test phase and the data will start to flow in groups of assets, so, we may have a problem later, but as of now we didn't notice anything. But as stated before, if we could subscribe to just three or four attributes, in our case, that would be actually a better solution as we expect the data to come at the same time.

Stephen, to answer your questions: Which version of software are you running? A) We are running the latest version of everything (PI AF 2017R2 and Analysis 2017R2)   We fixed a couple of issues that dramatically reduced start time with recent release(s). A) Yeah, we know, the previous version wasn't usable. We noticed a lot of improvement on PI System Explorer as well as before it would take too long to even load an Analysis on it giving the amount of attributes we have.   Do you have a lot of missing PI Points in your rollups? A) No, we make sure we create all the points. But we had a lot of attributes that would not get a value (its optional manual data), so, we started using the Excluded functionality to remove those and it improved the overall performance as I mentioned above.     How often are your rollups being triggered? A) Our data flow is pretty slow. Around 2000 assets will have one data point each 10 minutes on average, but the other 18000 usually comes once in a day. And we would like to be able to subscribe to just some of the attributes to generate a rollup, but that is not possible in the current version, Rollups are set to monitor all in event based or you need to change to period, which is not ok to us.   Are you in a situation where you're triggering more often that you think due to the rollups having so many inputs? A) We didn't identify any problem with the data flow. As soon as the service start, it kind of behave ok, but we are still in the test phase and the data will start to flow in groups of assets, so, we may have a problem later, but as of now we didn't notice anything. But as stated before, if we could subscribe to just three or four attributes, in our case, that would be actually a better solution as we expect the data to come at the same time.

Stephen, to answer your questions: Which version of software are you running? A) We are running the latest version of everything (PI AF 2017R2 and Analysis 2017R2)   We fixed a couple of issues that dramatically reduced start time with recent release(s). A) Yeah, we know, the previous version wasn't usable. We noticed a lot of improvement on PI System Explorer as well as before it would take too long to even load an Analysis on it giving the amount of attributes we have.   Do you have a lot of missing PI Points in your rollups? A) No, we make sure we create all the points. But we had a lot of attributes that would not get a value (its optional manual data), so, we started using the Excluded functionality to remove those and it improved the overall performance as I mentioned above.     How often are your rollups being triggered? A) Our data flow is pretty slow. Around 2000 assets will have one data point each 10 minutes on average, but the other 18000 usually comes once in a day. And we would like to be able to subscribe to just some of the attributes to generate a rollup, but that is not possible in the current version, Rollups are set to monitor all in event based or you need to change to period, which is not ok to us.   Are you in a situation where you're triggering more often that you think due to the rollups having so many inputs? A) We didn't identify any problem with the data flow. As soon as the service start, it kind of behave ok, but we are still in the test phase and the data will start to flow in groups of assets, so, we may have a problem later, but as of now we didn't notice anything. But as stated before, if we could subscribe to just three or four attributes, in our case, that would be actually a better solution as we expect the data to come at the same time.

Stephen, to answer your questions: Which version of software are you running? A) We are running the latest version of everything (PI AF 2017R2 and Analysis 2017R2)   We fixed a couple of issues that dramatically reduced start time with recent release(s). A) Yeah, we know, the previous version wasn't usable. We noticed a lot of improvement on PI System Explorer as well as before it would take too long to even load an Analysis on it giving the amount of attributes we have.   Do you have a lot of missing PI Points in your rollups? A) No, we make sure we create all the points. But we had a lot of attributes that would not get a value (its optional manual data), so, we started using the Excluded functionality to remove those and it improved the overall performance as I mentioned above.     How often are your rollups being triggered? A) Our data flow is pretty slow. Around 2000 assets will have one data point each 10 minutes on average, but the other 18000 usually comes once in a day. And we would like to be able to subscribe to just some of the attributes to generate a rollup, but that is not possible in the current version, Rollups are set to monitor all in event based or you need to change to period, which is not ok to us.   Are you in a situation where you're triggering more often that you think due to the rollups having so many inputs? A) We didn't identify any problem with the data flow. As soon as the service start, it kind of behave ok, but we are still in the test phase and the data will start to flow in groups of assets, so, we may have a problem later, but as of now we didn't notice anything. But as stated before, if we could subscribe to just three or four attributes, in our case, that would be actually a better solution as we expect the data to come at the same time.

Analytics High Availability is implemented via Windows Server Failover Clustering. When one PI Analysis Service fails, WSFC reroutes to the other PI Analysis Service. Currently there can only be one PI Analysis Service instance per AF Server.

Stephen, I am currently working with a customer who would like to see this functionality.  The High Availability isn't the same as what they are looking for.  I would love to discuss further with you.  I am currently on a long term engagement with them to make their existing calculations more efficient, but they will likely still need more than one analytics server in the end.

I completely agree with Wilson. Bringing a first of our 40 plants on our AF Server we already fought a lot of performance issues with PI Analysis. I have no good feeling about setting 39 more customers up on the same AF Server. Also for such a Setup - with just one analytics Service, performance issues of one customer will have Impact on calculations of other plants and managebility gets worse with every new plant. How are you supposed to know which calculations may cause errors when 80 different people create calculations in different AF databases.