It is a stable solution. I rate it eight out of ten.

I rate the tool’ stability a six out of ten. Sometimes, the product is incorrect. We had some consistent technical issues. We fine-tuned and fixed them.

It is stable.

Stability has been perfect. We have never had any issues from downtime.

My impression is that it's excellent. I believe that BOARD does provide a very stable environment. Again, we haven't had any real issues.

No issues. The only issues we ran into were related to communication mistakes that we made. As long as we follow our change control process, the system is rock solid.

The solution is not very stable. Sometimes we work on Board and automatically get logged off for all the clients and developers working on it. One type of error titled service unavailable consistently appears in the red error box. The error box appears frequently, but we don't know why it is happening. Sometimes in our data flow, many cubes vanish, and after some time, it shows an error that our database is corrupted. After some time, if we open the exact procedure, those cubes are there. Sometimes the client is running a procedure, but that process doesn't run, but when we check as developers, that time it is running.

In the beginning, Board 11.2 was not stable, but after the patch was released, it became stable. Now it's really stable.

As I mentioned elsewhere, sometimes users are finding that the memory use is high.

Stability-wise, there are no issues. 

We do get some error messages in the client, messages that we have raised tickets about with their support team. They are just a warning, they are not corrupting, but they give end-users the wrong impression. We have started correcting those. Apart from that, there are no stability or performance issues.

Stability has been fantastic. We have not had any downtime. We are an on-premise user, so we are very dependent on our own systems and we have very reliable systems. 

I am interested in the future of turning over to the cloud and the challenge of what that performance will be like. Right now, it is a future endeavor that we have. In the industry that I belonged to, the healthcare industry, there are a tremendous amount of safeguards that we have to add, therefore everything is on-premise versus out in the cloud. 

No, The software is extremely resilient, and problems are only encountered through user error, which are often easy to fix.

It's outstanding, because I don't know of any issues that we've had.

Initially we did have issues with the BOARD crashing, but at that time I was fairly new. I will say that the services were meant to start after a few hours but that's the time where it briefly pauses and if anybody, by chance, was even trying to get into BOARD, it would lock them up. But that was fine. It was not really a stability issue. Our users did make a little bit of commotion, but eventually I explained it to them, and it was fine. Now it is pretty stable.

We have had some challenges with newer version of the rollout. We are looking forward BOARD 11 with its more refined functions.

It is pretty stable. The only issue that we seem to have is with the performance, which with version 11, it looks like they might have addressed it.

It wasn't because of BOARD, it was more because we have integrated it with our ERP system, and we have made changes in our ERP system without filtering those through to our BOARD software. So it wasn't BOARD, it was really a self-inflicted kind situation.

The platform has worked wonderfully for us. There haven't been any issues that I've seen with the platform. In fact, we're looking at - maybe in the next year, or next two years - integrating more into it, really expanding what we're currently using it for, which is just budgets; to look at it and see what else we can do with it. It's very customizable.

I have not seen any stability issues.

It's good. I feel it's stable in our client base, and I'm quite confident that the new version will increase the scalability.

The stability has been fine. We have an additional challenge because we have to integrate it not only with where we are pulling the data, but with our own technology, as if we are implementing three systems. This has been challenging, but we are slowly improving on it. Hopefully, future implementations will be quick. This downtime is mainly due to our learning curve.

We've had a few little issues. We adopted the cloud version, we were something of a guinea pig for them. They've had a few issues that they were able to work out. But overall, it's a few bumps here and there, but it seems to be working well now.

The stability is pretty good. We have used other systems, and it is on par with the big competitors out there.

No stability issues. Everything has been good.

We did have some downtime because there are only two staff members in my division. My managers continuously use it, except we do not have the time to continuously update it.

So far so good.

In development we have issues for which we have had to open tickets. It's part of the learning process. We don't know where exactly it's going wrong. It's not quite intuitive sometimes.

We haven't had any real issues with the stability. We've had one issue where they had to come in and fix something that kept needing restarting while we're developing, but we've not had that issue in a while.

It is pretty stable. 

I think the stability can be improved upon, but overall it is stable.

We've seen downtime from our side, that we did not design it the way that it was going to be used. But I also see that we have had to take away features because it was not supported in the way that we wanted it. We're using it in the client versus Web; in the client it works and in the Web it doesn't. So we had to pull certain controls off the screen.

We have not encountered any stability issues.

We've had no issues with stability.