What is our primary use case?
The hospital's internal network is used for communications between staff, including emails and direct point-to-point access. One of the most challenging features of the network is its ability to facilitate live video communications between staff in different parts of the world that can view operations live. We use Aruba Wireless to help facilitate the three requirements of always on-time, on-live, and on-direct. In certain cases, I have to communicate with another surgery room, whose call may be back to back or parallel in that same venue.
What is most valuable?
The most useful feature of this product is the configuration that allows us to have several areas covered with one unit. However, when we have to make maintenance to that unit, the other units can go back and support the one that we have in maintenance. This back-to-back service or this come-alone service is the best thing for us. If I have to remove the unit that we have in surgery, I know that another unit or two can take its place.
What needs improvement?
The most important thing that needs to be improved is the internal web feature. This allows all our units to use this as an internal GPS to locate somebody or some elements. However, the problem is that they need another unit different from the 535. This point is not good because we put that on this unit, and changed it from 515 to 535. For this unit, just to enable the possibility of locating equipment, we have very expensive equipment in the hospital and we put a GPS stack, so the system can track. We put them in all the time, but we need another unit to make it functional. Aruba can improve this by including the GPS stack in each unit. This would reduce our maintenance work.
Aruba Wireless needs to provide more visibility into the differences between their models so we can better understand them. The changes between the 515 and the 535 are just scalable in one step; We don't feel that one unit is going to be better in so many ways. Instead, it is just one change. The scale from one model to another is very short and because of this we are going to try to save money, we're going to pick up the lowest model because the newer model, doesn't have many additional features.
The bad things about the product are the price, the information about the product, and the time it takes to deliver the product.
For how long have I used the solution?
I have used the solution within 12 months.
What do I think about the stability of the solution?
The heat map is already running and it is very stable. There are no issues with the corners of the building, except for the sign, which I think is covered well. I give the stability of the solution a nine out of ten.
What do I think about the scalability of the solution?
I give the scalability of the solution a nine out of ten.
How are customer service and support?
As we had to present our submission or change a model to another, the technical support was very bad. The work I have to do to research the difference between the models and compare them is all manual. When we asked the factory, what the differences between the models are and what is going to be the advantage from one another. The training can't support me. I have to do all the research myself. We asked the representative, and we had conversations with the factory, and nobody tells us it is a small change, instead they say it was a software issue. When we have to present the submission, the presentation has to be very complete with all the technical information, with all the features and we have to say this is a processor that works in this area, this works at this speed. The technical support could not help with any of our required information.
How would you rate customer service and support?
How was the initial setup?
The initial setup is very easy because we change all the models. We have around 1,000 units and we changed all of them in one week.
What about the implementation team?
The implementation is completed in-house by our team for our customers.
What's my experience with pricing, setup cost, and licensing?
Aruba Wireless is expensive. The balance between quality and price is there, but the cost is still high.
I give the cost of the solution a seven out of ten.
What other advice do I have?
I give the solution a nine out of ten.
Eight IT people are required for the maintenance of the solution.
The first thing I'm going to do is check all the features to make sure they meet our requirements. The step from one model to another is very important. There are little changes, and we have to review a lot to know the difference between the models, and what the major advantage between them are. In PeerSpot, we've seen the difficult differentiation, but the compliment of the functionality, how does it work, what is the benefit that I get with each model in the field? What is the difference between the software, and the versions? Is it throughput out? It's a factor that we need to consider. It doesn't address the major concerns, and I check every single specialized page and I don't see anybody saying, "Okay, five megabytes is a huge improvement in throughput out."
Which deployment model are you using for this solution?
On-premises