The deployment can be done in-house.

The initial setup was done both in-house and with help from a third party. We hired an expert to onboard us. Then, when we were done with the knowledge transition, we created a team to manage the deployment and everything else. This is another reason why TIBCO BusinessWorks is problematic. You need separate expert teams for configurations, deployment, and everything else. A developer cannot do any of that.

We now have a maintenance team of 10 people for TIBCO BusinessWorks. The solution requires daily maintenance. This is because some of our applications are critical and sensitive and we do not want to run into any disruptions or have any negative impact on the business. We have people monitoring usage daily, 24/7. 

We implemented this solution through an in-house team. 

We have vendors as well as an in-house team.

It requires basic maintenance. If APIs are taking more time, we need to fine-tune that. If they are not responding, we need to look into that. It depends on how it is implemented and deployed in the environment and whether we need to fine-tune the environment. We have a tool called TIBCO Hawk. It is a monitoring tool that gives us some kind of idea about whether the service is up or down. If it is down due to some reason, we can set a rule to autostart.

We deployed the solution in-house.

We implemented through an in-house team. 

The implementation was completed in-house.

We handled the implementation ourselves.

I deployed it myself. We have a 10 member deployment team that follows a sprint cycle. They include DevOps people, administrators, and others.