IBM Datacap Reviews

Datacap is good at processing unstructured data. You can build up some nice data flows, and it is simple to configure. The tool adopts a low-code approach, but you can do a lot of coding if you want to customize and automate your flows. Datacap also has the flexibility to integrate. 

Datacap's technology seems a little behind the industry. It's still using the old .NET framework. They should move to .NET Core and start integrating some machine learning. You can do some integration yourself, but you expect a solution to include the latest machine-learning approaches if you're paying reasonable money for it. 

Datacap is stable. 

I rate Datacap 10 out of 10 for scalability because it's easy to integrate, and you can add load balancers to scale it up. 

I rate Datacap support seven out of 10. We've got an IBM support agreement and contacted them for a few answers. We typed in the questions and they gave us a response. The turnaround time was okay.

The licensing for Datacap was steep the last time I checked, but I don't know the current pricing models. 

I rate IBM Datacap seven out of 10. I would recommend it depending on the use case. 

We support clients who make use of IBM Datacap as an imaging solution where they scan forms and capture information in the system. Our clients have significantly improved efficiencies when opening accounts for end users. This solution has also helped in eliminating the manual process of getting documents signed and approved. 

The feedback from our clients that this solution has increased their efficiency and their turnaround time on opening any account for end users, thus attracting more customers.

The best features of this solution include auto-indexing. Using optical character recognition, it recognizes what is contained in a scanned document and indexes the information. There is no need for manual intervention.

Recognition between certain numbers and letters could be improved. Sometimes this solution misreads five with an "S" for Singapore.

I have used this solution for six years. 

The latest version of Datacap is very stable. Older versions of the solution used to get stuck but the overall stability and performance of the solution has been improved with version 9.1.7. 

This is a scalable solution. We are able to add additional Rulerunner servers if our business users or user base increases. We are able to have multiple nodes for the front-end and for the Content Navigator. We have total of 3,000 users across the United States of America.

The technical support from IBM is good. I would rate it an eight out of ten. 
There is sometimes a delay in getting support from the IBM team and we receive inadequate answers. If it is registered as a critical issue, we receive a response from IBM after one day which can cause our clients to lose business. 

Positive

If only one person was working on the deployment of this solution, it would take one to two weeks. 

The first step in setting up this solution is to install all the prerequisite software from IBM. Once installed, we run the installer on Rulerunner servers and on Taskmaster servers. We then install the IBM Content Navigator for use in the front-end followed by creating the default desktops of IBM Datacap.  The final step is to customize the solution using any plugins or any widgets based on our client's requirements.

IBM could offer more competitive pricing. This would allow them to attain more users. Some of our clients are considering moving to a different solution called Encapture which is similar but offers more competitive pricing. 

This solution is mostly used by financial organizations. I would recommend this product to all financial organizations who are looking to improve and eliminate their paper process and improve workflows. It could assist in reducing overall SLAs of manual processes.

This solution requires maintenance including the updating of patches, which have been released by IBM. Once a month, we complete a recycle of the complete Datacap setup and system maintenance. 

I would rate this solution a nine out of ten. 

Its main use case was to turn papers into electronic documents and extract data from the document.

The administration of the application following an error is most valuable. We are able to know easily when something is stuck in the system.

There should be an increase in the capacity of the workflows. Datacap is a little limited in this aspect. So, you cannot really implement all the possibilities. 

I started using it about 8 to 10 years ago, but I have not been using it all the time.

It is scalable.

I would rate them a four out of five.

Its deployment is quite fast. It's easy to set up, but it can grow quite easily. It can grow quite complex. You have a lot of options and possibilities.

It was done in-house.

For the development teams, it's not the easiest solution in terms of understanding how it works and how to develop things around it, but once you get the knowledge of it, it's quite fast. So, there is a steep learning curve at the beginning.

To read through the paper documents and get them to how you want, Datacap is not the best tool in terms of configuration. Datacap aims for bulk operation. It has a lot of possibilities and capabilities, but there are some products that are more focused and narrow in scope and are better. IBM has a couple of them as well. That's why I would rate it a seven out of ten. It's broad and you can do a lot of things, but on the downside, you are losing the abilities of a specific and narrow solution.

IBM Datacap is used for capturing documents. Here's a use case: invoices come into an organization and the organization wants to get details from the invoices. They want to know where it came from, the date of the invoice, and the value of the invoice. They also want to know if there's a purchase order number on it, and if there are any line items on the invoice.

IBM Datacap will extract the information from those invoices, then pass the information into their line of business environment. It's a capture and extraction toolkit.

We implement and support solutions built on Datacap for our customers.

What could be improved in IBM Datacap from a technical perspective is having all configuration interfaces together in one place, rather than having several different configuration interfaces. For example: there is an interface for configuring background tasks, then a different interface for configuring how the application actually works, then there's a third interface for configuring user access. It would be nice to have everything in one place instead of needing to use different interfaces.

In the next release of IBM Datacap, I'd like the ability to leverage cloud-based OCR technologies or cloud-based OCR engines, such as Google Vision. There's the ability to be able to build things yourself, so as a partner, we could build those integrations, but it is possible that we would build something only to find later that it has been built by someone else. 

As a business, we were the first Datacap partner in Europe, and that was before the acquisition by IBM. I started with Open Connections originally in 2008 and have been working with IBM Datacap since 2008.

Solutions built on IBM Datacap tend to be very stable and this is maintained by regular updates from IBM. 

IBM Datacap was designed to be very scalable, e.g. you could have one server running background tasks, and individual threads can be configured for this purpose. Threads can be added as operational needs dictate, scaling "vertically". If the business needs dictate, additional servers can be added. Examples of background tasks are document ingesting from a mailbox, data extraction from documents or export of documents and data to the line-of-business system. 

In the past, technical support left a lot to be desired, but  IBM has listened and responded and our recent experience has been very favourable. On a scale of one to five, with five being the highest and one being the lowest, I'm scoring support a four out of five.

Positive

The complexity of initial setup depends very much on the architecture and use case for individual customers. A simple use case (for example, data extraction from a fixed form) can see a solution up and running in a few days, but more complex use cases with several document types and unstructured data can take longer to implement.

There are several options for the licensing and pricing of IBM Datacap. It's possible to purchase it as part of a wider portfolio of products called CloudPak for Business Automation, or on subscription from IBM, or you can purchase the licenses outright and just pay an annual maintenance fee. 

Pricing is very competitive. 

We have customers on various versions of IBM Datacap. The oldest version that we have customers using is version 8.1, which went out of support in 2018. We have customers on many subsequent versions up to the latest one.

We're an IBM business partner, so we implement and support IBM Datacap solutions for our customers, and sometimes we do it on behalf of IBM. Most of our deployments are on-premises, but more recently, we have seen that customers want to move to the cloud. IBM Datacap is not cloud-native but it can run in the Cloud, whether that be AWS, Azure or a customer's private cloud. 

IBM Datacap has built-in tooling which maintains deployed applications, so there's typically very little housekeeping once a system goes live.

The advice I would give to others looking to implement a solution built on IBM Datacap is, "Datacap will help you to streamline and automate your document driven capture processes, saving time and effort on manual, error-prone tasks.

My rating for IBM Datacap is eight out of ten, but if IBM were to improve the solution by having just one administration interface and add access to cloud-based OCR technology, then I would rate it nine.

Datacap is basically used to ingest the documentation of the clients, either from paper through scanners or through emails. In most scenarios, we either do scanning or consume email folders. It has connectors to read emails.

Its version depends a lot on the client and the project. I've been using version 9.1.6, and some clients have been upgrading to the latest version 9.1.9.

In terms of deployment, IBM has a solution on the cloud, but the solution I deploy is on-prem.

We recently did a Datacap implementation for a client, and we used its functionalities to do a separation of the documents and automatically capture some fields from the documents that the client wanted to extract. Before that, the software they were using wasn't optimized to do that. They were manually doing the separation of the documents and capturing the values of the fields. With Datacap, the process is automated, and they can now just validate if the captured data is correct and if the separation is correct. After it is implemented for some time, it creates a database. So, it separates automatically more over time, and the program in the background validates everything. For most batches, the operators don't waste much time on this process. Previously, they used to waste plenty of time separating the documents manually. After that, they had to write the data from the documents. The data was then sent to another platform, such as FileNet, for further use by another department. 

It is very easy to develop this software. It is low code, and if you can't find the things you need on it, you can develop custom actions with more complex code underneath. They sync well, which is very useful for automating a lot of processes. It is a really valuable feature for the clients because we can ingest information and automate plenty of processes for them. The operators don't have to waste that much time on tasks. With Datacap, they can be automated.

I've faced some bugs or issues. They should do deeper testing of the product before releasing it because some of the bugs that I found were a bit simple. I understand that it is a massive product, and some of the functionalities can get overlooked.

Their platform for reporting bugs and issues works. Sometimes, it takes them too long to solve the issue, but eventually, they do. So far, every issue that I've found in reporting has been resolved, but their support can be improved in terms of resolving the issues faster.

In terms of additional features, I've been following the roadmap they have, and so far, it has been good.

As a developer, I've been using it for over two years.

The software always depends on the infrastructure of the clients because it's very network-based. If you follow all the recommendations that it requires, it is great. It works properly, and the performance is more than okay. If you have limitations in the infrastructure or network, it can be a bit tricky, but you can always find workarounds to solve the issues.

It is very easy to scale the solution for our clients. If you want to upgrade the product on processing, it's easy. You just have to check the license requirements and the cost because the cost increases if you want to increase the servers, specifications, and processing power, but it's very easy to scale the software.

I faced some issues, and sometimes, they take a bit too long to solve them. When you open a ticket for support, they do the initial testing to test the error on their side. After that, they send the error to the development team on their side. Sometimes, this process can take a while. There are several levels of priority when you open a ticket, but they could improve a bit in terms of how fast they work. I had some unpleasant talks with their first line of support.

I started with Datacap right away.

It is now very easy for me. For someone who is starting with the product, they have a manual, and it can be very straightforward if no issue occurs. If there are some issues, it can be a bit complex to solve when you're doing the setup. Because I already have a massive experience with the setup of the environment, it's quite easy. Even when I find errors, I manage to solve them quickly.

I do the implementation for the clients. In terms of maintenance, in the last few updates, they have been implementing some tools for it to be easier to monitor. It basically depends a lot on the implementation and the functions. It depends on the capability that a client wants, such as if they want something more robust or something with easier alerts when anything aborts or an error occurs. So, it basically depends on how much the client is willing to pay for a more robust solution. In terms of Datacap, you can set up more on the development side to monitor everything. You have a tool page if you don't want to automate monitoring for everything.

It varies, and it depends on the client's requirements and negotiations. Nowadays, Datacap is also included in the IBM Cloud Pak for Business Automation. 

Datacap can be very robust. It depends on the solutions that the client is using beforehand. Of course, if you're changing platforms, you're going to have an initial shock because it has different ways of working, but in the long run, it's a good solution to be implemented. It can automate plenty of processes, but you have to be willing to invest in it.

I would rate it a seven out of ten.

I work for a bank in Tunisia and we use Datacap for extracting information. We are partners of IBM and I'm a data and AI technical specialist.

I like the Rulerunner that can run Datacap Studio; Datacap Navigator is also a great feature and both help us develop apps. 

Third-party integration is slow especially through API calls because if you want to integrate between Datacap and BPM, it can only be done in that direction (and not BPM to Datacap). One of our customers needs it the other way and we had to make a development app for that to work. There also needs to be additional support for the Arabic language as the translation doesn't work well. Finally, I'd like to see an interface update in the next release.

I've been using this solution for three years. 

We use the solution continuously and stability is fine as long as the product has been installed with best practices.

We have between 200 and 250 users so the scalability is good. We carry out all our own maintenance, updates and fixes. 

I've contacted support many times, initially when we carried out the implementation and then again when we were in the development phase. They were very helpful and patient. 

If you're doing a custom deployment, it's easy. But if you're wanting a personalized setup then the initial deployment is complex because it requires a lot of research and there are numerous problems. 

I rate this solution eight out of 10. 

The most valuable features of IBM Datacap is the capturing and recognizing of pages, documents as well as the scanner and barcodes. I also like the fingerprint recognition.

I would like IBM Datacap to add features similar to Captiva. Currently, when you are entering invoices, you have to enter multiple rows. In Captiva, the multiple rows will be dynamically added. This would be a beneficial feature for IBM to add.

Our users prefer TM's navigator more than  IBM's current navigator. It could just be a training issue, however, they like having more options like filter badges.  

In one case, our client needed to scan 5,000 pages in five minutes, or less, Datacap was not able to accommodate this task. 

I have been using IBM Datacap for nine years.

The initial setup of IBM Datacap is easy, with no issues.

Pricing of the solution is reasonable.

I would rate this solution an 8 out of 10.

We use Datacap for scanning Proof of Delivery and Proof of Pickup from our delivery agents and drivers. We have a defined workflow in Datacap, and we process these documents into our imaging system and PODs or POPs for paying the drivers and agents for deliveries.

Datacap provides remote users with the ability to scan documents using some plugins. Internal customers can scan their documents and define their workflows, like where the document needs to be sent and how it needs to be indexed. That is one thing I like about Datacap. Several documents get scanned during the day, and they come from agents, drivers, internal workers, and customers. 

While we are doing indexing, we tag the document type. It's programmed inside of Datacap to automatically detect the document based on a given template. It auto-indexes that document, which means that it automatically tags the correct document type to the scanned document.

Datacap's workflows are helpful. 

When I scan a document in Datacap that has a watermark or the document is a little distorted, the image output is poor. It either becomes completely black, or there is so much distortion that we cannot read the numbers or the addresses mentioned in the POD. When we scan a document, we expect the output to be at least 95 percent accurate. If IBM could work on that particular thing, I think it would be fantastic.

I've been using Datacap for around 10 years now.

I have seen complaints on the older version, but we haven't had any issues with the new version so far. However, it's only been a week since we did the upgrade. Versions 9.1.4 had performance issues. For example, it used to take an hour to complete a batch job.  

IBM support is good. We open a ticket on the forums, and our questions are answered in a couple of days. So I wouldn't say it's bad.

I wasn't around when Datacap was deployed, but they have done two upgrades since I joined the company. The process was tedious. We needed to upgrade the server and the client. If it automatically upgraded the client when we updated the server, that would be fantastic. 

When we updated the client, we lost all our settings, like the shortcuts and preferences. Those settings go into an XML file or somewhere. The upgraded client should retain that file. It should not be completely deleted. The user has to set it up from scratch, which is frustrating.

I would rate IBM Datacap seven out of 10. If you're implementing Datacap, you need to understand the solution from end to end. In other words, you need to know how the server connects to the client. If you think there is a clear delineation between the server and client, you'd be wrong. 

There is a lot of dependency between these two, and you need to make sure the configuration XMLs are in place before you implement anything. You should also ask the Datacap technical support team about every attribute they're going to touch. Otherwise, it's going to be a nightmare.

We use it to capture documents issued from the business processes. For example in the sales department during the exhibition of our business process, we procure a huge amount of documents that are in paper format. To make it easier, we use Datacap to use the OCR in order to extract data from the documents to make the research of the documents easier for our clients. I have around 40 people on my team who are in charge of digitizing the documents. We have to start with the existing documents to make the gap smaller between the past and present documents. Once we finish with one department, we have to give them the means to digitize the work and the ability to do it themselves and continue the work. 

I am dedicated to code digitization which concerns too many documents at the same time. The batches are very heavy. In the same batch, we can have up to 14 folders and each folder can contain up to 1,000 pages. It's different than classic capture in which the employee has one or two documents and wants to implement them in the solution. 

I like the features that we just started using. The 2019 project was an as-is migration. With Captiva, we had a basic recognition process that was based on the indexation of each document apart. 

In tier one for example, in Casablanca, they are dealing with 2,000 folders per day. On each team, I have four people and each one is in charge of preparing the documents to review these days. Second-tier is in charge description of the documents. This discussion is made on an Excel sheet and then it generates descriptive documents that go with each folder. So we have a main page in which we can find all the metadata related to this document and so on. We ingest all of the folders in the system at the same time and the system is able to recognize all those folders and automatically classify them on Documentum. What I liked about DataCap and what made us decide to move to Datacap instead of Captiva was the licensing. With Captiva we had to pay for each page, the licenses, there are a number of pages. For Datacap we have a licensing model which is based on the number of users. We are not limited in the number of pages. This is the first thing we liked about a Datcap.

The second thing that I like about Datacap is the fingerprint capture which is easy to configure on Datacap. From the form of the document, if a document is redundant in the same department, we can configure the capture based on the form of the documents. We tell Datacap to bring this information from a certain day and then we have a symantec capture which is the ability to read the page and identify amounts based on the meaning of the phrase. For example, if the sentence says that the total amount of this operation is $2,000, for example, it will understand that $2,000 is the amount and put it as meter data.

The interface can be more intuitive. What is in common with the big solutions like EMC tool, OpenStack, IBM SharePoint, et cetera is that the platform and the interfaces are not generally user-friendly. They are powerful. This is common in between all of those solutions. It's hard to customize those interfaces to be intuitive and to be user-friendly. We have to create a new interface up to par of these strong solutions to make it user friendly. I tried many solutions in my life and I never had a beautiful solution that is powerful. 

We have been using IBM Datacap since 2019. 

It's not very stable. We use IBM support to resolve some issues but they're not huge issues. 

We use it daily on several sites.

I would rate their support a three out of ten. IBM support is one of the strongest and maybe after the quarantine they will be more reactive. 

It is easier to set up than Captiva. The configuration doesn't depend on the technical admin. The business admin can handle the configuration. In the past, we had billions of documents. For each type of document we have to configure the system to apply the security and it's important to configure each document apart. When we had Capatra we had to go back to our partner and configure the document. Now we can add members of documents without asking for support from the IT department.

To deploy a departmnet took two months without much customization. For the standard deployment, it won't take more than three months .

For a company that wants to install Datacap, make sure to choose a suitable person to manage it. It can't be a regular IT person. You have to check the laws in each country before implementing Datacap. We have to know the law for a retention policy before starting to implement it. 

I would rate it an eight out of ten. 

Datacap has all of the features that we need. 

We use it for extracting data for insurance filing purposes.

We are using data in flat files or XMLs and importing it directly into our database, or exporting it to clients who can process it and do insurance verification.

The solution automates manual data entry.

The usability is challenging and hard for our business users.

I would like better ease of use and more support options.

The stability is about average.

It is scalable. However, we are not scaling it up because we haven't got it over capacity yet.

It is hard for us to scale it up. I know it has potential, but it's not easy to do that.

The technical support is difficult and expensive.

There is a trend of moving toward automation and automotive processes.

The initial setup was complex because the system was complex inherently.

We used an integrator for the deployment, and our experience was very bad. They gave us an unreliable, broken solution which did not work, then they would not work with us. Afterward, we couldn't get a quote for more billable hours of support. They just disappeared and ghosted us.

The solution has increased our productivity, but not to our expectations.

The solution saves eight to 16 man-hours a week.

It has not reduced our operating costs.

We have worked with Imagine Solutions and have dealt with enChoice. However, Imagine Solutions was on the shortlist.

We chose Datacap because the team demonstrated expertise.

Manage expectations and confirm you have actual buy-in from upper management.

We plan to expand our use of automation in our organization.

We have integrated the solution with non-IBM tools.

I attended the technical track. I learned about the upcoming improvement, which is coming with the Datacap software. We are looking forward to that.