We got help from Omada professional services to implement the solution. They were absolutely helpful and knowledgeable. We had senior resources from Omada who really knew what they were doing. Omada Identity's deployment took two months.

The company that was initially involved in implementation was Traxion from Holland. They were not prepared for the educational industry. Afterward, I learned from some colleagues in the field that they had already attempted to do an implementation with another organization, and they failed. Omada bailed them out there too.

I would rate Omada's implementation support an eight out of ten. There are always some glitches in an implementation. If you report a glitch and say that something is not going right, it is a completely different experience if you have to jump through seven hoops and wait three weeks, or it gets corrected the next day with the Omada team and the glitch is mitigated. It is a whole different experience.

From my end, there were three technicians, one product owner/project leader, one adviser from the cloud team, and one adviser specialist from the identity preparation team. All in all, it was a team of five people.

Omada offers two services: one for products and another for consulting. We've also had Omada available as a consulting service for the past 2 years.

The deployment is done partly by our staff and partly by an external implementer. We have, some persons responsible for the application side of the system we want to connect to, but the core team has five to eight people.

We opted for an external implementation partner for internal reasons, not because of Omada's services. Although, a 12-week deployment is possible.

Omada used a value-added reseller to do the implementation, and things went wrong there. They were not capable of doing SaaS implementations. They were capable of doing on-prem implementations. We were the first or second SaaS customers, and they were not capable of delivering the solution we requested in our tender, but we knew that Omada was capable of doing so. Omada then took over in March or April 2023, so the actual implementation started in March or April, and we went live in July 2023. At the end of February 2024, we are closing the activities from that go-live in July. For me, it was successful when we directly got it implemented from Omada. 

When Omada took over, there were no issues at all. They provided us with what we needed. The most important feature for us was the identity join check process for which we needed an improvement. It was quite a big improvement, but Omada fixed it with extra code, specially built for Avans.

I would rate Omada's implementation services an eight out of ten, and I would rate the third-party provider one out of ten for the effort.

We used Omada itself as an implementation partner. The consultants themselves were quite adept at handling the product. From a technical standpoint, they were definitely above average. From a project management point of view, we would have liked to see some improvements. This is from the perspective of a very large customer. The problem for us was handling an organization of our size. If I have to choose again, instead of Omada, I would choose an implementation partner who is more used to handling large enterprises. That was definitely a pain point for us.

It is quite a technical and difficult application to maintain. It is a standard solution, but some parts of the solution make it difficult to upgrade and maintain the solution. A very specialized skill set is required to operate and maintain it. You should either pay Omada or another consultancy firm to maintain the solution, or you should have internal resources for maintaining the solution. 

We have around 10 people who are directly involved in its maintenance. They are on the business side, such as for onboarding new applications, front-end problem-solving, and incident-handling, as well as on the operations side, such as for ensuring data validation, handling integrations, and things like that. 

One or two external people and three to four internal employees were involved in its implementation.

We had a project team of four. Omada had a project team of four. Omada was doing the work. We were only participating in workshops where we were being interviewed. We were kindly asked to keep our hands off the systems while they were working, but we are now continuing with a team of four people.

In terms of maintenance, the solution as such does not require any maintenance, but there are always changes. When you get new business applications that need to be managed, you need to make some changes. This year, we not only have a new ERP but also a new HR system, so when the world changes, you also need to change what has to be managed.

We had someone from our company, and we also took help from the vendor. We didn't use a third-party integrator. We got professional services from the vendor's organization.

We were supported by the Omada project team.

I worked side-by-side with the supplier. We have a very good connection with our supplier, Traxion. We see them more as a partner. We work well together, learning from each other.

We used Omada to help with the implementation.

My colleagues deployed the product in my organization.

We used consultants from Omada. Our experience with them was okay.

We provide deployment and post-deployment support. In a deployment scenario, there will be one or more implementation engineers along with an architect and project manager. Then, in the post-deployment support, we have architects and engineers.

They set up the environment, which makes it almost immediately available for us. Then, we can configure the solution for our customers' needs, as the customer wants, and as we think is best for our customers. That makes it flexible, so we do not have to make any big investments in terms of hardware.

We have a customer lead who is responsible for all contact with a given customer. We also have a project manager finishing the implementation process, then we have a couple of engineers and a solution architect. There are about five people who are involved.

Omada people came in on-premises and they helped with the installation, so it was a joint effort from the client and Omada. Our client takes care of the maintenance. They are enterprise size and use Omada on a daily basis. 

We had an integrator working with our in-house team. You can't do it all on your own. You need an integrator, but there are good integrators and poor integrators.