We use it as a single source of support for the company. We store all official confidential documents in OpenText as the final record, keeping with records retention policies.

I've worked at three or four different companies that have all used some version of OpenText Extended ECM for document management purposes.

Through the years, we've used the solution to manage massive amounts of data and ensure that the employees get what they need in a timely manner.

We use the archive as our official repository for all of our finalized documents.

By implementing Extended ECM, we wanted to have a central location for all finalized documents so that everyone knows where to go and look for them. We also wanted to have retention around documents.

Our company is an engineering company that creates documents for engineering projects. We use OpenText Extended ECM for the engineering model on top of the content server. We use OpenText Extended ECM to define the entire lifecycle of the document from creation to sending to the vendor and receiving the updated version from the vendor.

We have users all over the world. If someone wants to see the status of a document, they can run the report and get the latest information. They don't need to wait for anything since it is easily searchable from the system.

We use it for document storage. We also use it for reporting purposes, but mainly, it is for document storage.

I have used OpenText Extended ECM within the oil and gas industries for capital projects, workflow automation, and content storage and retention. We used the solution to enhance the performance and stabilize the applications. We also use it to add more capabilities into the extended ECM for the engineering module, which we use heavily in our industry, especially for document controllers.

One of the critical items I'm looking for is to enhance the transmitters within the third parties. I need a transmitter that receives inbound and outbound documents from third-party contractors who don't have access to our environment.

We use OpenText Extended ECM for our document management purposes. 

The biggest use case in our company, which I help support, is that our accounting department uses it to help compile and do all the tax returns that we use. We are a private company. We work for a wealthy Chicago family, and the accounting department handles thousands of tax returns that they do every year. We use the OpenText Capture product to bring in all the forms and documents and get them into the Content Server. We have built a workflow and reports around that process, which includes getting the documents, compiling the tax returns, having them go through multiple reviews, and then eventually filing them with the IRS.

I work with the business users who are using it. I work at a Utility Gas company. We have a storage team set up for post-project document storage, and now we are setting up the transmission pipeline team with both mid-project and post-project document storage.

By implementing Extended ECM, we were trying to address the challenge of retention management. The biggest challenge with our previous solution was retention management. We are working on implementing a pretty complicated schedule of retention for different documents connected to assets. Extended ECM has a lot of capacity for this kind of work.

We use it to manage our engineering documents. We use it for the drawings and our asset documents.

The challenge that we have is that some users are reluctant to use the system, so we still need to come up with a way to motivate company-wide acceptance.

We use OpenText Extended ECM to build a connector to view documents on ServiceNow. It also helps to create a custom search for archived documents. 

We build products that add value on the OpenText Extended ECM.

Building an ECM repository for a leading high street bank in Scotland and integration with internet banking applications.

We verify complex solutions and we implement it on the business process management system. 

ECM has extra value for us. We focus on both solutions and they are a little different. 

One is only ECM and the second is as a VPN, with ECM as well.

We are selling this solution to our clients and we have an implementation team that takes care of the delivery.

Most of the customers use it for information governance, records management, workflow capabilities, and basic document and version control.

Some of our clients also use the AppWorks technology for local app development solutions.

Our primary use is for software development. It also offers capture. So far, we have been satisfied with the product.