A different team handled the implementation. 

We needed developers and most of the delivery team. It's not like maintenance is extensive, but server maintenance is necessary, especially when it's deployed in the cloud. 

So, maintenance involves checking server speed and memory usage. Besides that, there's nothing else in terms of maintenance with the tool.

It was mostly done by our team, but there was some collaboration with the vendor.

In terms of maintenance, we are responsible for doing the upgrades. In the last five years, I have seen two upgrades. We had two or three patches this year, and every two or three years, we have an upgrade. The last upgrade was probably two years ago, and we are scheduled for an upgrade next year.

Our deployment of the solution was done by a third-party.

We are involved in the integration of everything.

Archer is responsible for the maintenance of the solution.

We hired a consultant to help us out with the deployment. After it was complete, we gave him a job and he came to work for us. Because it was so complex, we didn't have the resource in terms of someone to actually understand the tool because of how complicated it was to build it from scratch to match our organizational structure. It takes time for someone to understand the entire company, and since the integrators did that within the year, it was easier for us to bring him on board and then train people along the way.

A third party implemented the solution for us. 

I used a vendor team.

One person is required to set up the solution. The solution must be maintained. 

I did not have to consider using an outside vendor for the installation and I was able to complete the install by myself with the help of the documentation.