You do need to have some third-party assistance. A consultant needs to assist with the setup. 

We handle the installation ourselves. I handle it mostly on my own. 

For deployment, you first need to install DataStage on the desired server. Then, you have to take a backup of the development and deploy it on the server. After importing, you need to execute and schedule it through your job application.

People required for the deployment depends on the scenario. Sometimes, one person is more than enough for deployment.

We do the deployment with our own team for the client, but the implementation can change depending on the client needs. When the client has specific things that need to be resolved for their situation or they want to install and to implement additional products to integrate with the base solution, that affects the rollout. It's especially true during the implementation stage. The implementation team can begin with as little as one person and it can end up as a team of five, six, or seven members depending on complexity and needs for rapid deployment. It also depends on whether the product is going to be used throughout the company. There are a lot of customers who deploy globally or selectively because they may have a strategy already in place for certain solutions that they may not want to change. For example, they may already have ETL processes being used without DataStage and it may not make sense to convert these processes.

We handled the implementation ourselves.

The initial setup can be handled in-house. 

Both vendor and in-house team implementations:

IBM has top-notch support and tool services along with other partners as well. Depending on the partner, this can go from installation and configuration to solution development, etc.)

Most in-house teams that I have seen tend to have have good developers, but not always good architects. Like most every data integration project, if you do not have a strong architecture, your solution will eventually fail.

The installation required assistance from an expert from IBM.

I implemented it myself. In terms of maintenance, a particular version might not require any maintenance. There could be bug fixes and minor versions going in for some versions.

We use an integrator to assist with implementation.

Three to four years ago, they decided to start a new data warehouse project. They were working with another Ukrainian company, which engineered this solution. However, the solution hadn't made it to production because of some problems between the understanding of IT and business. They tried to move it to production several times. After that, they decided to do some technical audits for this solution. They& asked us to come and see the solution, then write the audit report, which we did. Then, they asked us what to do with these problems, and this is when we began to help them.

All the components were already in place. We changed it a bit, tweaked the ETL processes, and changed some structures in the data warehouse. This solved the current needs of their business. 

The deployment is continuous. We are working on this project currently. It should take another year. At the moment, we have some Agile processes, in which we are finding new business needs. We try to understand them, then deploy the current user story.

It was setup by an outside vendor.