The stability of the system has significantly improved compared to earlier years when occasional issues arose, causing disruptions.

Stability, particularly with Linux hosting of Intranet Server, is consistently good. Most cases of stability problems traced back to incorrect data, such as schedule dates that are impossible in the real world. Identifying and fixing bad data resolved stability issues about 80% of the time. In one or two cases since 2002, a Planisware update (patch), in one incident received within twenty-four hours after reporting, remedied incorrect data handling.

There are some bugs in the solution, but they are not those critical ones, or they are not the showstopper ones.

I rate the stability of Planisware an eight out of ten.

1. Distinguishing between software stability and issues arising from data integrity is beneficial. Poor data can and will impact performance so greatly that the software becomes suspect. As an illustration, a custom module may falsely discriminate between a string that ends with one or more trailing blanks and the actual string itself. The underlying Planisware software is performing normally, yet it appears to end users that configuration itself is unstable.

It is very stable. 

I have customers who have been using it for more than five, or seven years and are very happy with the availability. Some of them are also moving to a SaaS environment.

There are a lot of bugs, and the stability of the system has been a problem for a year and a half. It is not really stable.

We worked hard on building a solid and generic data model, which has allowed us to avoid major stability issues.

I have found the stability to be good.

I did not encounter any stability issues.