I know, you’re thinking “Whaaatt? An OEM partnership is not even possible!”
Well, actually, it is possible and there are a variety of products available — from industry standard ISIS drivers to our analytics packages. You can check out the OpenText™ OEM page for information on all of the products we sell to OEM partners.
So why would you consider an OEM partnership with OpenText?
For the majority of industry-specialty vendors or structured data vendors, the advantage is simply that you don’t have to re-invent the wheel for a module that is not core to your product’s value proposition.
Think of it this way:
You could invest your research and development budget into building a completely bespoke content management solution, or even open source one. And, yes, you can probably make a good enough module to check off that RFI requirement or satisfy that nagging roadmap question that keeps coming up in customer advisory calls.
But what happens when the content types change/expand/die? Do you really want to keep spending your R&D budget on upgrades to what is basically a value-add?
Our OEM program is designed so that you can not only check off that box on the RFI and customer satisfaction questionnaire, but you also get a partner that actively invests — heavily — in products that are outside your sweet spot. In other words, you get a large R&D commit on a budget that makes sense for your roadmap.
When you work with OpenText, we not only help fill the gap you have identified in information management, but we understand how the product can do more — which lets you focus on your roadmap planning for your embedded products.
For example, in many transitional markets like healthcare, education, and banking, reliance on paper is slowing the transformation of these industries. Two of our key products in those spaces are OpenText™ Captiva and OpenText™ ACM (formerly known as ApplicationXtender)— both of which are available as part of our OEM program. Captiva is a top-of-the-line capture solution that can capture and digitize any type of document, email, or form, and then send it via API to any type of system of record. ACM is a content services solution that electronically stores, organizes, and manages virtually any kind of business content. It’s easy to integrate into applications as a back-end service for management of documents and extraction of data related to your processes. Oh, and by the way, these two products have out-of-the-box integration, so you can have a single embedded solution for any content to store it natively and provide access via your UI.
How would it work?
Let’s take healthcare as an example:
In a perfect world, organizations would have several different information management functions combined in a single, enterprise-wide health information management system with the flexibility to manage various use cases. But, many customers still use multiple systems to handle a variety of information sources. For example, financial information may be managed by the ERP or CPOE application while imaging is handled by DICOM systems.
To remain your customers’ preferred partner, you’re going to want to offer an application to ease the movement of information across the various administrative and clinical systems. You can either invest in several connectors or you can add the varied elements of a content services platform to your application portfolio.
I would argue that a healthcare vendor would be better off keeping up with ever-changing clinical needs (and saving their R&D dollars) by adding elements of a white-labeled content services platform.
There are three areas where adding ACM as a white-labeled content service provides value versus building extensions to a product offering:
- Cost of licensing: ACM has a flexible pricing model to ensure that OEM partners can build a full business model that incorporates the additional functionality without harming revenue potential.
- Maintaining permissions: Most healthcare organizations have a complex cross-departmental network of admission, transcription, and billing administration that is difficult to model without an additional layer of document and process-based security.
- Reducing the cost of innovation: OpenText maintains a robust API and SDK kit for ACM, taking the cost out of maintaining back-end connectivity between the document management repository and your system. As an OpenText partner, you have access to a larger portfolio of integrated products for managing information, including Captiva, OpenText™ LiquidOffice™, OpenText™ RightFax™, or OpenText™ Magellan™.
The benefits of working with OpenText as an OEM partner means we — not you — worry about ensuring that any type of content can be made manageable by your application. Working with start-ups and large established industry veterans, our OEM team is dedicated to ensuring that we understand how our portfolio of products fit into your roadmap.
Interested in learning more?
Contact us for more information.