OpenText Extended ECM's setup is complex in terms of the integration side and how long it takes to perform an upgrade.

I am not involved in the setup piece. I am the bridge between IT and business users.

The solution’s initial setup is a little complex.

Its initial setup was complex. Each implementation is different, but the most important thing is to gather the right stakeholders from the beginning of the project. Make sure that you are asking the right questions to collect business requirements correctly, and then you have to control the scope. To be able to complete the project, you have to control the scope of the project.

The initial deployment was complex, considering the infrastructure requirements. We need databases, servers, high availability, disaster recovery, front-end and back-end servers. The initial setup can get really complicated, and it takes time.

Our implementation strategy always starts with a lower environment. We make it a copy of the production environment. We start with the database applications, going by the prerequisites and OpenText documentation provided. Then, we deploy the application and start with the configuration, like building the structures, categories, attributes, search, and search forms. It's complicated, and it's a lot of steps to do.

The product's deployment is complex because of the integration and the time to complete an upgrade. Our implementation strategy focused on minimizing the impact on the end customer. 

It was fairly complex because we ended up using a couple of different modules to help us out. We built the workflow and a lot of custom reports. It was definitely some work to get them up and running and to get there, but I would not necessarily call it a con because it would be naive to ever think that you can just flap something down and have it work great for anybody. There is going to be some configuration, and there is going to be some tailoring to make it work for not just your organization but also the individual department. There was a decent amount of work to get it there and to get it to work well for them.

We even did a couple of different stages. We started off using something a little bit more basic to help them manage their process, which we eventually upgraded to a full-fledged workflow. We did it in stages because it was just too much to undertake all at once. They are busy from February until April, so we have this small window to roll things out and implement new changes. We stepped up over two or three years. In year one, we just cared about getting their documents digital in there and giving them some minimal tools to track the process. We refined that. In year two or three, we made that an actual workflow, so it did take a couple of years to get there. It was not simple, but we did it. You need to build that roadmap or that plan and keep iterating it.

I was initially involved in the very first parts of deployment, but then I got out and was focused on the legacy solution. Now that we are more ready to move the legacy solution into the new solution, I am coming back to the project. So, I was not super involved, and even if I was, I do business systems analysts work. I am not involved at a technical level except for a single question or two here and there.

It was complex in terms of understanding the users and their processes at that moment. We are doing interviews and trying to understand why that even was the way it was. That part is always complex. We are now going to translate them.

In terms of implementation strategy, we have multiple sites in our organization, and one site at a time was rolled out.

A few things are complex in the tool's deployment due to the missing information in the documentation. We first build a development environment on our on-premise server for our implementation strategy. We test it out and report to the support if we find any bugs. 

The solution's deployment is straightforward. Our implementation strategy involved the deployment of SAP systems with the product.

The initial setup was, and still is, complex because there are many components interacting with each other. There are multiple settings to check and configure. A vast knowledge of infrastructure, networking, security, software tools, and more are required to install a performant solution.

I was not a part of the initial setup. We have a team in place that handles the setup and deployment.

The initial setup is very straightforward and the configuration is quite easy.

Depending on the use case of the customer, a project can take between three months and maybe 12 months to deploy. It depends on how complex the requirements are of the use case.

If there is an integration that needs to be done, then it can take up to about 12 months.

Straightforward.

The initial setup was straightforward.