IBM FileNet Reviews

The thing I want most in my environment is to be able to work with a stable module like FileNet.

The important features to me are that it is stable, scalable, and the integration between this platform and other platforms is very good.

Also, FileNet is now introducing a newer client called IBM Content Integrator, so I think it's flexible.

Also migration. For example, if I want to move from my building to a new building, I have to move the physical server and everything would need to be changed, like network settings, etc. I think FileNet can handle this.

Many customers leave FileNet because of the licensing cost.

No, for the last 20 years I haven't faced any big stability issue.

I think FileNet can integrate with SharePoint, with Microsoft Office, with OpenText, so it can work with any other system.

When I face a big issue, I call IBM support and they are really helpful and their documentation over the internet can show you what you need, very well.

No, I didn't use anything before FileNet.

I would rate the installation process at about seven out of 10. It can be very complicated, and you need to to have an experienced resource.

The biggest issue is the cost of the FileNet, because the license cost is very high. If a customer doesn't have good technical guides that are aware of the license calculation, they will pay too much. FileNet's license calculation depends on the processor and number of users. So my advice to a new customer is to be very careful with your calculations before purchasing FileNet.

If you check the industry rankings, you can see that FileNet was the leader in the ACM category for four years in a row. Only in 2017 do you see that Microsoft SharePoint was the leader. I think that's because IBM doesn't offer new technologies every year, they offer new technologies after five years, for each release of the product.

It's not an open source product, and IBM support is very good.

• Document Management
• Records Management
• Business process and workflow
• Digital imaging
• Document classification
• Search 

• Streamlined our business processes.
• Centralized our business documents.
• Provides records management functions.

Records management to apply document classification for retention and disposition of business records. Email and instant messages are included.

It is still a leading ECM solution provider, however the cost to implement and maintain are higher than other solutions.

The best-scaling ECM solution now comes with a beautiful, extendable UI. I hope with the latest push on Case Management, IBM does not forget to flaunt the real beast under the hood, the Content Engine.

Archival, records management or workflows all get implemented best with FileNet. Over the years, I am witness to organizations picking a cheaper product with a little better UI, only to upgrade later to FileNet when the original solution did not scale well!

I have used it for 10 years.

We have encountered deployment issues, just like any other product.

We have not encountered any stability issues.

We have not encountered any scalability issues.

Customer service is 4 out of 5.

Technical support is 3.75 out of 5.

It's very robust. We have been using it for the last 15 years and we've never had any opinion to change it or not use it. So far, we have been very happy with it.

Slowly, we are streamlining all our document management systems. We are including all other departments into FileNet who were not using FileNet as a document management system.

The user interface for FileNet can be improved. It was not very professional, you could say, in the beginning, so we developed a custom user interface. With the new ICN, they have come a long way, but they still need to work on the ease of use for the user/customer. So, the user interface is one thing where they're lacking.

It's very expensive, so they could make it a little cheaper but still, it's good.

We never had any stability issues.

Scalability-wise and robustness-wise, it's awesome.

The technical support is very professional and efficient. So far, we have been very happy with it.

Before we started using FileNet on our own, we were subcontracting with other departments using their FileNet. So, around 2007, we decided to move to our own installation and our own system, rather than using the county's system.

I was involved in the initial setup. It's very straightforward, as long as you know what you're doing.

It's on the expensive side.

If someone is comparing FileNet against other solutions like SharePoint or open-source solutions, I think they should be looking into the scalability, robustness and the whole document lifecycle features.

When I look to work with a vendor, the most important criteria is their in-house expertise, how competent they are, the resources they have in their organization; and then, price. We always have to look at which vendor is good and cheap.

For our custom projects, we outsource to a couple of vendors, such as Imagine Solutions. We work with them. They are vendors for FileNet solutions. They don't compete against FileNet. They help us in upgrading FileNet. Those type of projects.

The most valuable features of this solution are:

• The ability to do version control in the documents that are stored within the IBM FileNet solution.
• To be able to retrieve the history accordingly.
• To be able to work with those in a microservice environment.

The data can be integrated into a microservice architecture. It has allowed us to more deeply integrate the ECM or the FileNet solution into various aspects of our product, where we may need to provide user access to documents, that might be within FileNet. They don't need to open up a specific page or request mechanism to get to them. They can be embedded directly within the page itself or the app itself or within the context of whatever the user is doing. Thus, this just improves the overall efficiency and productivity of our organization.

We've actually had this solution since 2008, so we've had it for a long time; it's really not new to us.

The stability has been good.

Scalability is excellent and actually, it has been really great. It scales really well.

Previously, we were using just a file-based solution. It was not an equivalent solution and that was the reason as to why we moved over to IBM.

It really comes down to our ability to work together so as to address the gaps that we may have, i.e., between what FileNet needs to offer and what we need.

Ensure that the product itself matches the needs in your particular vertical. There are a lot of ECM products in the market space today that actually will vertically integrate into a given space. Whether it's the insurance, banking, manufacturing or whatever vertical that you're talking about, these ECM products will customize into that space so heavily, that it may supersede the existing functionality that you may have today. It's important that you look into what is it that the vendor is trying to resolve. Is it really meeting the gaps that you have? Lastly, does it extend beyond what you need it to do? These are all important factors to consider before selecting a product.

We always look for the ability in our vendors to provide their products in an integrated manner or that it will be integrated into our product seamlessly. This really comes down to the level of the APIs that they present. 

We look at various other factors before selecting a vendor, such as, Are the products themselves scalable and have they been tested out? What's the experience of the vendor in the space that we're in, i.e., for our specific vertical? Finally, we also look at the other customer recommendations.

It just allows us to do a lot more data management, just because we have a lot of services, as well as the whole content management we had to do. The whole the FileNet solution that we have integrated allows us to do all of that.

The benefit of this solution is that it provides the whole file services, given that we have a lot of content management. There are not a lot of other technologies available out there for us to efficiently manage the whole FileNet services.

They should continue having the same stack of stuff. There's nothing new that we are expecting. Given our use cases, this is pretty much what we need at this time.

Stability is pretty good, because we've evolved over a period of time. Initially, we used to have it at a different data center. Currently, we've evolved into a place where we feel much more comfortable, in regards to the stability of the system.

Scalability is also good. Although, I'll have to admit that with our use case right now, we have a very good prediction of the number of customers. So, we've been able to meet our benchmark. But, at the same time, if it has to become much more larger than that, I'm not quite sure about where we would end up.

Technical support is pretty good, given that we have a very good partnership with IBM.

Go for it!

The most important criteria while selecting a vendor are the initial support, the knowledge they have and then, being able to partner-up from the support perspective, for any future needs. That's the most important thing for us.

The most valuable features are that it is very well integrated and connected. To deploy many new applications and solutions it may sometimes not be very easy, but it is very robust, at the end of the day.

The benefit is a shorter time to market, especially.

In the next release, I would like to see features for how to move it to the cloud and enhance functionalities as you are developing new products.

Also, I come from a Spanish-speaking country. Sometimes, you have to work with people that don't speak Spanish and that makes that the overall solution a little trickier to implement, because of the language barrier. So, I think that a strong knowledge of the technical issues by people that also have good knowledge of the mother tongue of the country, that would help a lot.

Usually, IBM products are stable, although some of them require some changes or some upgrades for minor bugs, but the overall quality of the solutions is OK.

FileNet has helped us a lot with the customer documentation information and I think the solution is very strong.

Actually, right now, we are moving to the new version of FileNet. We are doing all the scalability right now to have more processes involved with the FileNet platform.

The technical support is good. I think that the guys have provided us with the solutions that we needed.

We didn't previously use any other solution. We decided to invest in a new solution because we understood that it was a benefit for us and our customers to have the solutions that FileNet, in this case, provided for us.

The setup was a little complex. Even though some of the projects or the solutions are not very complex, you have to integrate them with the company's old system. Some of the systems are not complex, so the overall solution sometimes requires effort, that if it's not on the FileNet solution itself, it's in another module that's integrated.

We were checking out other vendors. We were looking at Oracle, Microsoft and some smaller vendors that were developing some specific things for us.

When I'm selecting a vendor, I look for a vendor that you can trust, with whom you can have a long-term relationship, and you know that they are also on top of the technological wave. What you are going to implement is going to be constantly changing with new developments in the future.

Make a very good design at the beginning, understand what you need and also prepare the different phases of the project to ensure that you finish the projects. Have a clear view. Draw the lines of the software you need.

The most valuable feature is seamless storing and retrieval of documents irrespective of the format of the document

Our current document management solution has limited capability in terms of the type of document that can be stored. With Filenet and Datacap we can accept documents in various formats seamlessly without user intervention.

We are in the early stages of implementation of this solution. We have not encountered any stability issues

We were looking for a data solution because the other one was sort of cramping our style. It could be accessed only via limited workstations, so we were looking for another data storage solution.

We evaluated a few other products