The initial setup was straightforward.

The deployment was greatly simplified when IBM acquired FileNet, which helps you install in batches. Previously, we relied on vendors to deploy for the whole development cycle. Now, I'm working for a bank, so everything needs to be done in-house.

It can be difficult to set up. This is true, especially for someone who doesn't know the product.

It's very important to have an understanding. It's a good product. However, you have to put in lots of time to really understand the platform and to have some skills.

The deployment itself takes several days. 

The maintenance can be done by one person, although it would be challenging. 

For me, now, the initial setup is easy. That said, in the beginning, it is very, very confusing as you have to build and install many, many other things before the actual installation of IBM software. However, when they changed the process engine applications, which were before .NET and now is Java, it became easier. Still, you have to read the documentation carefully in terms of the installation guide. If you do, everything will be fine especially if you follow the rules. At the outset, it was not very, very straightforward, however, I must say.

I was not involved in the installation process. We have a team of engineers who handled the initial setup.

When we installed it over top of our existing solution, overall, deployment took us eight days — four days for staging and four days until we were ready for production.

For Case Foundation alone, implementation takes no more than six days.

I think that the initial setup is usually okay if you just run the installation and use the default settings. You won't have any problems and it's easy, but there are a lot of technologies behind it. There is the verification server, IBM WebSphere or Oracle WebLogic. The database can be Microsoft SQL, IBM DB2, or Oracle, and they can be running either on Linux or Windows.

With so much technology that can be used in different configurations, if you aren't familiar with all of them then it could be hard. At the same time, the solution is versatile and can work well with many different technologies.

The initial setup is straightforward, but because the interface needs to be improved, it gets complex. You have to develop more and more, which involves some coding and development to ease it out.

The length of deployment depends on the requirements. If it is a small process, five to six nodes, it's a matter of one to two days. If it is a complex process and the rules are complex then it can take weeks.

The method of deployment depends on the customer's use case requirements.

If an organization does a base installation, it's not that complex to set it up. 

The problem is that instructions are not that easy to come by and not really available or very helpful if you can find them. 

To get the project running completely, meaning implementing an actual solution completely for a customer, that will depend on what the customer wants. This can be extremely complex for certain clients.

The main deployment may take one to two weeks, however, full implementation can be anywhere from three months to a full year.

The customer plays a big role in implementation. For example, at the beginning of the project, you do a business analysis with them and collect data. They approve the design and everything else after that. You may run into problems where the customer changes the design as the project rolls out. That extends the project drastically. 

The initial setup is somewhat complex and needs to be simplified. 

The setup and deployment were completed before I joined the company.

The initial setup is straightforward. Deployment takes one or two days depending on the environment.