What is your primary use case for IBM FileNet?

We use the product for document digitalization and workflow management. It is our document management system.

We use IBM FileNet for content management purposes.

IBM FileNet is an enterprise content management solution. We use the solution for document management in the legal, insurance, and banking sectors.

We use the platform for the automation of business digitalizing documents. We can turn the digital content into workflows for automation and monitoring processes.

I have been working remotely for an insurance client and I use IBM File Manager.

We use it to document content management. We have a payment system for every corporate payment that goes through our bank, it has to go through our application. We use it for the business process management data where multiple things have instability for that transaction. They do validations on it to see if the transaction is valid and next we use it according to the guidelines of the governments of countries like Singapore, India, and the USA. Every now and then countries impose sanctions on different countries and they have to make sure that the payments do not go in or out from those countries. We use it to audit.

Our client is using it for search and retrieval and for archiving. From the very onset, it was deployed for archiving of their legacy records. We did not implement any workflow for them. We use the FileNet Content Engine Web Services to retrieve documents. We use high-end production scanners to scan the records. After that, users can use FileNet to search for these records. There is automation involved in the process. At the point of scanning, the scanner dispatches the records to a particular folder. In each folder, there is an application that has been designed by us, which files the records in FileNet. We are not using any FileNet application to do the filing. We have an application which renames the XML to FileNet to do that. We mainly use it for inactive documents. These are records they don't need to edit any longer. They are still necessary for their day-to-day operations; they provide evidence about their operations so they cannot be deleted. Our client is using version 4.2 on-prem.

We are using it as a repository. We have multiple input sources where we receive files and, as of now, we are using it as a kind of a "dumping yard." We are not using it for end-to-end workflows and processes as well. We are just using it to get the files and keep them. It's deployed on-prem only.

We used it to develop document-management solutions for various public sectors, in India. We also use IBM BPM on top of it, which is primarily used for Workflow, with FileNet as the repository in the backend for document storage. Our solutions manage the entire lifecycle of content, right from creation to disposal. For example, when organizations receive invoices or proposals, using FileNet we have a solution which allows users to create the content, upload the content, manage the content, and it moves through the workflow. Our solution is called E-Office is, which handles the entire file movement, correspondence, file creation, committee meetings, etc. Wherever content is involved, the solution is involved. All day-to-day, paper-based activities have been automated using the help of BPM and FileNet. It's deployed as a hybrid. It's mostly on-premise but some of our customers have part of it on cloud.

We use it as a business documents repository for documents such as invoices, packing lists, POs, etc.

One of the primary use cases is for documentation processing, including image processing and all the content. It is also used for archiving and document management. For example, in the mobile telecom or financial industries, there are requirements to retain a customer's documents, depending on regulations, for five and sometimes ten years. In this instance, FileNet is used for archiving all of the documentation. We are using it for documentation automation projects, especially for content management such as customer contract management and some vendor contract management.

There are two use cases. One is as an extended datastore for IBM Connections, but we don't have many Connections customers. We have actually lost two such customers in the recent years because IBM didn't do anything for that product. The more common use case is as a general filestore for documents, with interfaces to the Web, etc. It is used to store incoming invoices and documents and to classify them. It's also used to automate the process of document storage, when documents come in. We have a mechanism to automatically categorize a document based on content. Based on that, we are able to create attributes for the content management system. Then we store the document in FileNet to enable retrieving it. We have PIDs, a universal access code, for each document and via that we are able to retrieve documents, even via applications. We have created some interfaces. We have a central solution to make it easy for customers to plug in their application systems in an easy, customizable way, without having to program it. We also work in the area of analytics where we use Cognos. We have customers who retrieve information about incoming invoices. They can click on a link and retrieve it automatically out of FileNet or Content Manager.

We usually use it for document management in insurance or finance companies. Some of our clients are using the workflow for insurance cases. In these companies, FileNet is ingesting a lot of documents and a lot of insurance claims. In terms of automation, we're using IBM Content Collector and we have started using RPA a bit. We're using ICC for some of our customers to ingest and automate the upload of multiple documents in bulk. We've just started using automation with RPA but not with the P8 system; rather for other functionality that customers need. Ninety percent of our customers in the insurance industry, here in Israel, are working with FileNet. Most of our customers use FileNet on-prem.

We have implemented it in a real estate environment. They receive many applications on the front-end and, before our implementation, they were processing them manually. When we implemented it, they moved to a completely paperless system. For example, a customer walks in at the front desk, the reception, and they ask that the company process a transfer or a no-demand certificate, which is a form used in real estate to clear charges against your property. The person at the front desk creates a case in Case Manager. It's processed by the Case Manager in two different departments, and it's completely paperless. The customer can view the status from their homes. We have created a very scalable application using FileNet and Case Manager. Our clients use it for office automation systems to have a paperless environment. Most customers are using it for paperless because Case Manager has more capability than any other product within case management and process flows.

We have some projects now with a university in Bogota, here in Colombia. We developed a correspondence process and some administration processes with invoices. We also have a government project where the main process is around the lifecycle of documents. We use FileNet to automate correspondence processes when our clients receive documents. There a lot of legal requirements in Colombia and companies need to automate their processes around these requirements. We incorporate FileNet in the middle of the process and we collaborate to make our clients' processes more efficient. We offer FileNet to our clients with IBM's RPA capabilities and help to automate processes.

All of our customers are using it to ingest, process, and retrieve their documents on a daily basis.

Our primary use case was to have our complete documentation digitized and provide secure access to it for all employees in our organization. Along with that, we were to develop a workflow for check-in and check-out of the documents. We are currently using FileNet but for a limited purpose. We have just one workflow configured in it. It's only used for document scanning and retrieval.

Predominantly, we use Case Manager in order to automate technical design review processes. We also use it in collaboration with multitenant.

It's used for content management. It's not for business process automation but for digital, electronic archives: documents, folders, and access to the client's native IBM content. It's an IBM content manager, especially for IBM BPM.

We are using this product in Beijing. It is a good product to use. Our team programmed an automation workflow to use with it.

I work in the account-opening process, and we have IBM BPM, Workflow, and FileNet document repository. We use different products to generate documents. Our solution uses IBM BPM Workflow in which people fill out a questionnaire. That gives us a document that we store in FileNet. We deliver those documents either physically or via DocuSign. We get them signed to open the account.

As a developer, I am usually supporting this solution. I do things to automate it and make it work for our clients.

Primary usage is storing content for content management. We are the consultants, who provide the solution to our clients. We mostly use ECM solutions from IBM, not database.

We store our medical records.

We're an IBM business partner. We work with customers who purchase IBM and we help them implement business solutions. Often times, we just influence their decisions. Most of the time FileNet is being used for automation projects.

Digital business automation is the primary use case. This solution is not used by business users in our organization.

It is our unstructured record archive solution. It is mainly for internal users. We don't have end users for it, since it is only used internally. It has captures a maximum part of our organization to help with the efficiency in our records.

Our primary use case is document management for eliminating paper.

We store policies, documents, and customer data in the FileNet repository.

The primary use for this solution is customer and client demos, in order to share it with them, if they have a requirement for this particular type of capability. We position a product or solution like this to a client where there is a great fit, and it does have a return on investment in terms of efficiencies, cost savings, or job role function acceleration.

We are a ratings company. We store all of our ratings documents in a FileNet Content Manager. We also use the Datacap scanning solution to extract the data, then index it into FileNet. That is our main usage of the FileNet platform. We store documents on-premise. As a ratings company, we are not storing anything on the cloud at this time.

We use FileNet to store all the medical records and information for a patient. We have business users utilizing it in the whole organization for medical records.

It runs our document management and workflow systems.

Our primary use for this solution is implementing business automation from document collection, capture, and indexing through management and workflow up to document analytics.

Our primary use case for this solution is document storage and retrieval - Workflow.

It is usually the client's system of record for their documents. In addition, it can be used for digital assets, like video and recordings.

A lot of the time Datacap and FileNet work in tandem together. FileNet is like a database repository which can be connected to a bunch of different third-party applications or the Web. It's a very interesting technology in the sense of you can pull in a lot of information through the Datacap network, then connect it to servers on the FileNet side. The servers can communicate and assist in the automated workflow structure. This is especially helpful when it comes to multiple parties who are trying to work together.

We provide the content management platform for the company for official and unofficial records for all business processes.

We've been in the FileNet business for 25 years and we have found that 80 percent of our customers use FileNet for Accounts Payable processing. That's the single biggest pain point that larger customers are trying to resolve, uniformly, across industries: ingesting invoices, matching them up with purchase orders, doing the three-way match with receivers - if they're a manufacturing or distribution outfit - and then, potentially, if possible, automating the approval and payment of those invoices so nobody has to touch them. Then, they can focus on approvals and touchpoints only when they have to, and escalate when they need to based on grants of authority and delegate if somebody's not there. They can also make sure they get their prompt-payment discounts and the like. The other big use-case area is always compliance: Records retention, how do they prove that they're complying with policies and procedures and with regulatory issues - HIPAA, PII, etc.

It is about simplicity. It designs and builds the process, then adds document facilities for the documentation. Therefore, it is easier to model the process and include documents in this process.

It was used in a customer environment. IBM FileNet was used for combining incoming paper documents, as well as electronic documents. The environment consisted of FileNet, Documentum, and SharePoint. Each product was first tested, then used for different business processes.

We use it for content management and to manage documents. It has performed well.